Coverage planning
GSM Cell Reselection Parameters Explained
Learn how GSM idle mode cell reselection works. Master C1 and C2 algorithms, CRO, TO, PT, and CRH parameter tuning, field limitations, and step-by-step troubleshooting workflows.
Understanding Idle Mode Cell Reselection Architecture
In Global System for Mobile Communications (GSM) networks, mobile stations spend a significant portion of operational time in idle mode. During idle mode, the mobile station is registered with the network but does not have an active dedicated channel allocated. To ensure mobile-terminated calls, short messages, and data sessions can be successfully routed, the terminal must continuously monitor surrounding radio frequency (RF) conditions and camp on the best candidate base transceiver station (BTS). This continuous process is defined as GSM cell reselection.
According to 3GPP technical specification 3GPP TS 05.08, cell reselection allows a mobile station to select a target cell that offers optimal downlink signal quality and acceptable uplink link budget conditions without network intervention. While handovers occur in dedicated mode under direct BSC (Base Station Controller) command, idle mode cell reselection is an autonomous process executed entirely by the mobile station based on system information parameters broadcast over the System Information Messages (specifically SI3, SI4, SI7, and SI8 on the BCCH channel).
Properly configured GSM cell reselection parameters prevent frequent ping-ponging between adjacent cells, optimize mobile battery life, reduce signaling congestion on the Random Access Channel (RACH), and ensure smooth location area updates. Radio network engineers must balance coverage, capacity, and mobility dynamics by tuning parameters such as Cell Reselection Offset (CRO), Temporary Offset (TO), Penalty Time (PT), and Cell Reselection Hysteresis (CRH).
Deconstructing the C1 Path Loss Criterion
The foundation of idle mode mobility in GSM is the path loss criterion, known as C1. A mobile station evaluates C1 for the serving cell and all monitored neighboring cells broadcast in the BA (BCCH Allocation) list. The C1 value represents whether a cell meets the minimum radio link coverage requirement for camping.
The mathematical formulation for C1, defined in 3GPP TS 05.08, is expressed as:
C1 = (RXLEV - RXLEV_ACCESS_MIN) - MAX(MS_TXPWR_MAX_CCH - P, 0)
The components of the C1 equation represent specific RF performance thresholds:
- RXLEV: The measured average received signal level at the mobile station, expressed in dBm.
- RXLEV_ACCESS_MIN: The minimum received signal power level required for a mobile station to access the system, broadcast in system information.
- MS_TXPWR_MAX_CCH: The maximum RF output power level an MS is permitted to use when accessing the control channel of the target cell.
- P: The maximum RF output capability of the specific mobile station class.
If a mobile station has sufficient maximum power capability such that P >= MS_TXPWR_MAX_CCH, the term MAX(MS_TXPWR_MAX_CCH - P, 0) reduces to 0. In this standard scenario, C1 simplifies directly to RXLEV - RXLEV_ACCESS_MIN. A cell is considered suitable for camping only if its C1 value is strictly greater than 0 dB. If the serving cell C1 falls below 0 dB for a duration of 5 seconds, the terminal immediately initiates a search for a new candidate cell.
To evaluate baseline link budgets and model initial candidate coverage during site placement, RF engineers rely on the GSM Coverage Planner to establish realistic target RXLEV boundaries across varied terrain types.
Master Class on C2 Criterion: CRO, TO, and PT Dynamics
While C1 ensures basic path loss suitability, standard GSM networks utilize the C2 cell reselection criterion to artificially shape traffic distribution and prioritize specific cells (such as microcells or layer-2 capacity cells) over macro coverage cells. C2 incorporates artificial offset and timer parameters broadcast in System Information Type 3 and Type 4.
The calculation of C2 depends on the duration for which a candidate neighbor cell has been logged as a suitable candidate, controlled by the parameter PENALTY_TIME (PT). The standard formula for C2 is defined as follows:
For the current serving cell:
C2 = C1 + CELL_RESELECT_OFFSET
For a non-serving neighbor cell when PENALTY_TIME is not set to 11111 (binary special condition):
- If elapsed timer
T < PENALTY_TIME:C2 = C1 + CELL_RESELECT_OFFSET - TEMPORARY_OFFSET - If elapsed timer
T >= PENALTY_TIME:C2 = C1 + CELL_RESELECT_OFFSET
When PENALTY_TIME is deliberately coded as 11111 (all bits set to 1), the temporary offset functionality is altered: C2 = C1 - CELL_RESELECT_OFFSET regardless of timer duration. This special mode is often used to penalize problematic cells or prevent fast-moving terminals from camping on small microcells.
Parameter Breakdown and Valid Ranges
| Parameter | Broadcast Range | Step Size / Units | Engineering Purpose |
|---|---|---|---|
CELL_RESELECT_OFFSET (CRO) | 0 to 63 | 2 dB (0 to 126 dB) | Artificially increases cell candidate C2 value to encourage idle camping on capacity layers. |
TEMPORARY_OFFSET (TO) | 0 to 7 | 10 dB (0 to 60 dB, 7 = infinity) | Applies a temporary reduction in C2 to prevent fast-moving mobiles from reselecting a cell too quickly. |
PENALTY_TIME (PT) | 0 to 31 | 20 seconds (20s to 620s) | Duration for which TO is applied after a neighbor cell is listed as a top candidate. Setting to 31 (binary 11111) flips CRO sign. |
By applying a high CRO combined with a non-zero TO and PT, a stationary terminal moving into a microcell coverage area will wait until PENALTY_TIME expires before the full CRO boost takes effect. If a fast-moving vehicle passes through the microcell in less time than PENALTY_TIME, the C2 value remains artificially degraded, successfully preventing an unnecessary reselection.
Location Area Boundaries and Cell Reselection Hysteresis (CRH)
When a mobile station performs cell reselection across cells belonging to different Location Areas (LA), it must immediately perform a Location Area Update (LAU) signaling procedure over the Standalone Dedicated Control Channel (SDCCH). Frequent LA updates consume significant battery resources and load control channel capacity.
To prevent continuous ping-pong reselection between neighboring cells straddling a Location Area Code (LAC) boundary, GSM standard introduces the Cell Reselection Hysteresis (CRH) parameter, broadcast in SI3/SI4. The CRH parameter ranges from 0 to 14 dB in 2 dB steps (represented as binary values 0 to 7).
When comparing a candidate neighbor cell that resides in a different Location Area against the current serving cell, the candidate cell C2 must exceed the serving cell C2 by at least the CRH margin for a continuous period of 5 seconds:
C2 (Neighbor, LAC_B) > C2 (Serving, LAC_A) + CRH
If the neighbor cell belongs to the exact same Location Area as the serving cell, CRH is omitted (or treated as 0 dB in comparison). Setting CRH too high (e.g., 14 dB) delays mandatory Location Area Updates when moving deep into a new boundary, potentially causing brief paged call failures if the serving downlink degrades severely before reselection triggers. Setting CRH too low (e.g., 0 to 2 dB) leads to excessive SDCCH load due to constant LA updates along street intersections.
Comprehensive Parameter Formula Matrix
To summarize how idle mode criteria interact during field evaluation, review the consolidated decision logic implemented by mobile stations compliant with 3GPP TS 05.08 and guidelines from GSMA operational documents.
| Condition / Variable | Formula / Rule | Key Impact on Mobile Behavior |
|---|---|---|
| Base Path Loss Criterion (C1) | (RXLEV - RXLEV_ACCESS_MIN) - MAX(MS_TXPWR_MAX_CCH - P, 0) | Determines absolute candidate cell suitability (Must be > 0 dB). |
| Serving Cell C2 | C1 + CRO | Establishes reference reselection score for current server. |
| Neighbor Cell C2 (T < PT, PT != 31) | C1 + CRO - TO | Suppresses neighbor candidate rank during initial evaluation window. |
| Neighbor Cell C2 (T >= PT, PT != 31) | C1 + CRO | Applies full offset boost after mobile remains adjacent for target duration. |
| Neighbor Cell C2 (PT == 31) | C1 - CRO | Permanently penalizes candidate cell rank regardless of duration. |
| Different LAC Reselection Rule | C2 (Neighbor) > C2 (Serving) + CRH | Requires additional RF differential before triggering cross-border reselection. |
To verify parameter execution and evaluate actual signal performance in the field, engineers frequently use the GSM Drive Test tool to capture real-time system information broadcasts, RXLEV metrics, and C1/C2 values directly from test handsets.
Practical Field Limitations and Real-World Trade-offs
While theoretical GSM cell reselection models assume uniform signal propagation and static user velocity, field conditions introduce several practical limitations that RF engineers must carefully manage.
1. High-Speed Mobility and Timer Expirations
Along railway lines or highways, fast-moving mobile stations may traverse small cell coverage areas in under 10 to 15 seconds. If PENALTY_TIME is configured to 20 or 40 seconds, the terminal will pass through the microcell coverage without ever applying the full positive CRO. While this prevents ping-ponging, improper tuning can leave high-speed users on distant macrocells with poor frame error rates.
2. High Traffic Load on SDCCH
Aggressive use of CRO to push traffic toward indoor microcells can backfire if the target microcell lacks sufficient Standalone Dedicated Control Channels (SDCCH). When mobile terminals select a target cell and immediately attempt a Location Area Update or periodic registration, SDCCH congestion causes paging access failures.
3. Antenna Misalignment and Propagation Distortions
Cell reselection parameters assume accurate physical antenna orientation. If an antenna physical azimuth is skewed due to mechanical failure or poor installation, the broadcast CRO and CRH parameters will push mobile stations toward a cell section suffering from severe inter-cell interference or delayed handover execution. Field engineers should verify physical site alignment using the GSM Azimut Checker prior to applying aggressive logical parameter offsets.
4. Hardware Power Class Discrepancies
In regions with mixed legacy equipment, mobile terminals with low output capability (such as small IoT modems or handheld units with low max power P) will suffer from non-zero MAX(MS_TXPWR_MAX_CCH - P, 0) penalties. This reduces their calculated C1 relative to high-power handsets, occasionally leading to unequal reselection behavior on identical cell sites.
Step-by-Step Field Troubleshooting Sequence
When field engineers encounter abnormal ping-ponging, dropped idle registrations, or delayed cell reselection in a GSM network, follow this structured troubleshooting workflow to isolate root causes:
- Capture System Information Logs: Use an RF diagnostic tool like GSM Drive Test or a protocol analyzer to record broadcast messages on the BCCH. Extract parameters for System Information Type 3 and Type 4 (specifically
RXLEV_ACCESS_MIN,CRO,TO,PT, andCRH). - Verify Baseline C1 Calculations: Compare measured RXLEV with
RXLEV_ACCESS_MIN. Ensure that candidate cell C1 values are reliably above 0 dB. If C1 fluctuates rapidly around 0 dB, evaluate physical downlink path loss using the GSM Coverage Planner Web tool. - Audit C2 Offset Timers: Observe candidate cell log duration. Determine if
PENALTY_TIMEis expiring before reselection occurs. If high-speed vehicles are missing candidate cells, lowerPENALTY_TIMEor reduceTEMPORARY_OFFSET. - Inspect Location Area Code (LAC) Boundaries: Check if target neighbor cells belong to a different LAC. If excessive Location Area Updates (LAU) are observed on the control channel, increase
CRHfrom default levels (e.g., increase from 4 dB to 8 dB or 10 dB). - Audit Mechanical and Physical Line-of-Sight: If C1/C2 values match parameter expectations but real-world service drops occur immediately after reselection, perform a site visit. Use the GSM Azimut Checker to confirm antenna mechanical azimuth, down-tilt, and feeder line integrity.
- Validate Neighbor Relation Lists (BA List): Confirm that the target candidate cell's ARFCN is explicitly defined in the serving cell's BCCH Allocation (BA) list. Mobile stations will not measure or reselect to candidate cells omitted from the BA list, regardless of signal strength.
Frequently asked questions
What is the primary difference between C1 and C2 in GSM cell reselection?
C1 is the basic path loss criterion that measures whether a cell meets minimum signal and power requirements for camping (C1 > 0 dB). C2 is an offset-adjusted criterion derived from C1, incorporating Cell Reselection Offset (CRO), Temporary Offset (TO), and Penalty Time (PT) to prioritize traffic layer management and manage high-speed mobility.
How does setting PENALTY_TIME to 31 (binary 11111) affect cell reselection?
When PENALTY_TIME is set to 31 (binary 11111), the standard temporary offset calculation is bypassed. Instead, the Cell Reselection Offset (CRO) is subtracted from C1 (C2 = C1 - CRO). This effectively penalizes the cell, making it far less likely for a mobile station to select it.
What happens if Cell Reselection Hysteresis (CRH) is set too high?
If CRH is set excessively high (e.g., 14 dB), a mobile station crossing into a new Location Area will delay reselecting candidate cells. This can cause the terminal to stay on a rapidly degrading serving cell in a different LAC, leading to lost paging messages or dropped call setups.
Why does a mobile station fail to reselect a strong neighbor cell even if C2 is high?
Common causes include: the neighbor cell's ARFCN is missing from the serving cell's BA (BCCH Allocation) list, the target cell is set to Cell Barred, the mobile terminal fails the access threshold (RXLEV_ACCESS_MIN), or the neighbor cell belongs to a restricted PLMN/LA.
Sources and further reading
- 3GPP TS 05.08: Radio subsystem link control, 3GPP
- ETSI TS 100 912: Digital cellular telecommunications system (Phase 2+); Radio subsystem link control, ETSI
- GSMA Official Documentation and Technical Guidelines, GSMA
Technical parameters can vary by network, equipment and software release. Verify changes against current vendor documentation and your operator's procedures.