Cell Congestion vs RF Problem: How to Tell During a Drive Test

The Field Diagnostic Dilemma: Capacity vs. Coverage

During routine optimization or customer complaint verification, field engineers often encounter failed call setups, dropped voice channels, or severely degraded throughput. A common challenge in drive testing is determining whether the failure stems from a high utilization rate on the base station's transceivers or from physical layer propagation failures. Misdiagnosing a cell congestion vs RF problem leads to ineffective corrective actions: tweaking antenna tilt or transmitter power will not resolve an exhausted Standalone Dedicated Control Channel (SDCCH), while adding transceivers to a cell plagued by severe co-channel interference only wastes hardware resources.

To reliably isolate the root cause, drive test analysis must correlate Layer 1 RF metrics, such as Receive Signal Level (RxLev) and Receive Quality (RxQual), with Layer 2 and Layer 3 signaling procedures like Immediate Assignment rejects and Assignment Failures. System specifications documented by 3GPP establish clear boundaries for physical RF performance, giving engineers a solid baseline to compare field data against standard behavior.

Key GSM Metrics for Isolating Failure Modes

Differentiating capacity limits from RF degradation requires analyzing specific RF parameters side by side with signaling indicators:

• RxLev (Received Signal Level): Measured in dBm, this represents the downlink signal power received by the mobile station. According to ETSI TS 100 908 standards, valid sensitivity limits define useful coverage, typically down to -104 dBm for standard speech services.
• RxQual (Received Signal Quality): Measured on a discrete scale from 0 to 7 based on Bit Error Rate (BER) before channel decoding. RxQual 0 indicates a BER below 0.2%, while RxQual 7 represents a BER exceeding 12.8%.
• Carrier-to-Interference Ratio (C/I): Indicates whether the signal is limited by thermal noise or co-channel/adjacent-channel interference. GSM speech channels generally require a minimum C/I of 9 dB for acceptable voice quality without frequency hopping.
• Signaling Failure Causes: Layer 3 messages such as Immediate Assignment Reject or Channel Release carrying cause codes for resource unavailability point directly to capacity constraints rather than RF path loss.

Diagnostic Profiles: Identifying the Failure Pattern

When analyzing logs gathered with tools like GSM Drive Test, field observations typically fall into one of two primary diagnostic profiles.

Profile A: Pure RF Problem (Physical Layer Failure)

An RF failure occurs when the electromagnetic environment prevents successful demodulation or decoding, regardless of available channel capacity. Typical observations include:

• Low RxLev, High RxQual: The mobile receives signals near or below receiver sensitivity (e.g., -102 dBm to -110 dBm), driving RxQual to 6 or 7 due to thermal noise.
• High RxLev, High RxQual: The mobile receives strong signal power (e.g., -65 dBm), but RxQual degraded to 5-7. This signature indicates strong co-channel or adjacent-channel interference from neighboring cells.
• RACH Drops without Immediate Assignment Reject: The Mobile Station (MS) transmits Random Access Channel (RACH) bursts, but the Base Station System (BSS) never decodes them due to uplink path loss or high uplink interference.

Profile B: Pure Cell Congestion (Capacity Exhaustion)

Cell congestion occurs when the physical layer propagation is fully sufficient, but the network cannot allocate logical channels to serve the request. Typical observations include:

• High RxLev, Low RxQual: The RF link is clean (e.g., RxLev at -72 dBm, RxQual at 0 or 1), confirming excellent signal quality and minimal interference.
• Immediate Assignment Reject: The network returns an Immediate Assignment Reject message after a RACH request, indicating that all SDCCH timeslots are fully occupied.
• TCH Blocking or Call Setup Failure: The SDCCH assignment succeeds, but the subsequent signaling for Traffic Channel (TCH) assignment fails with cause codes indicating no circuit available.

Comparing RF Degradation and Cell Congestion Parameters

The following table summarizes the diagnostic differences observed at the drive test tool interface during call setup or active hold testing:

Step-by-Step Field Troubleshooting Workflow

When investigating service drops or call setup failures on site, follow this sequence to isolate the underlying cause:

1. Check Layer 1 RF Baseline: Record RxLev and RxQual at the exact point of failure. If RxLev is lower than -100 dBm, inspect antenna tilt using the GSM Azimuth Checker or verify link budget calculations in the GSM Coverage Planner.
2. Evaluate Interference Metrics: If RxLev is strong (> -80 dBm) but RxQual is worse than 4, perform a frequency scan to check for co-channel BCCH/BSIC collisions or inter-system interference.
3. Inspect Signaling Layer Messages: Review the drive test message log. Look for Channel Required followed by Immediate Assignment Reject. If rejects are present while RxQual is 0, the issue is SDCCH capacity exhaustion.
4. Verify Handover Parameters: If call drops occur during mobility, evaluate whether neighbor lists are complete. Overly restrictive handover thresholds can cause forced call drops in congested cells even when physical coverage is acceptable.

Engineering Limitations and Edge Cases

Field diagnostics are not always strictly isolated to one domain. Combined failure modes frequently occur in complex urban settings. For instance, high uplink interference can corrupt RACH bursts at the BTS receiver, mimicking SDCCH congestion because the network fails to reply. In addition, dynamic power control and discontinuous transmission (DTX) can cause transient fluctuations in reported RxQual during silence periods. Field engineers must verify that measurement logs capture active speech frames (RxQual Full vs RxQual Sub) to avoid misinterpreting suppressed transmission metrics as coverage gaps.

Frequently asked questions