RxLev and RxQual in GSM Drive Tests: A Field Engineer's Guide

1. Introduction to GSM Signal Metrics: RxLev and RxQual Fundamentals

In Global System for Mobile Communications (GSM) networks, evaluation of the radio frequency (RF) environment relies heavily on two foundational metrics: Received Signal Level (RxLev) and Received Signal Quality (RxQual). These parameters are reported by the Mobile Station (MS) and Base Transceiver Station (BTS) during active dedicated mode (a call in progress) and idle mode cell selection. While modern cellular generations employ Reference Signal Received Power (RSRP) or Signal-to-Interference-plus-Noise Ratio (SINR), GSM networks depend directly on RxLev to quantify power and RxQual to gauge modulation purity and channel distortion.

When performing field measurements using the GSM Drive Test platform, collecting clean RxLev and RxQual metrics provides an accurate picture of the physical layer performance. RxLev measures the raw broad-band RF power in standard channel bandwidths, whereas RxQual evaluates the Bit Error Rate (BER) on the dedicated physical channel prior to forward error correction (FEC) decoding. Understanding how these two parameters interact is critical for diagnosing coverage holes, identifying co-channel interference, tuning handover thresholds, and preventing dropped calls.

Engineers analyzing drive test traces must treat RxLev and RxQual as interdependent variables. High power does not guarantee a clear channel, and low power does not always trigger immediate dropped calls if the interference environment is benign. According to technical specifications published by 3GPP TS 45.008, both parameters are quantized into specific integer scales to optimize control channel signaling bandwidth on the slow associated control channel (SACCH).

2. Deciphering RxLev: Scale Mapping, dBm Conversion, and Cell Selection

RxLev is represented as a 6-bit integer ranging from 0 to 63, corresponding to received signal strength spanning from below -110 dBm up to greater than -48 dBm. The step size across the usable range is exactly 1 dB. Converting integer RxLev readings into absolute power in decibels relative to one milliwatt (dBm) follows a straightforward linear relationship defined in ETSI specifications.

The mathematical conversion formula for integer RxLev values between 1 and 62 is:

For boundary conditions, an RxLev of 0 represents an input power less than -110 dBm, while an RxLev of 63 indicates an input power greater than or equal to -48 dBm. The standard mapping table below summarizes key intervals across the dynamic range:

During initial cell selection and reselection, the mobile unit uses RxLev Full or RxLev Sub measurements to evaluate candidate cell power against the baseline parameter C1 (path loss criterion) and C2 (cell reselection criterion). In initial radio link design, calculating these cell edges accurately requires robust RF propagation models available in tools like the GSM Coverage Planner and the GSM Coverage Planner Web.

3. Deciphering RxQual: Bit Error Rate (BER) Scale and Speech Quality Correlation

RxQual quantifies signal degradation caused by multipath fading, co-channel interference (C/I), adjacent channel interference (A/I), and noise floor elevation. It is formatted as a 3-bit integer ranging from 0 to 7, where 0 represents the cleanest transmission state and 7 denotes severe bit destruction. Unlike RxLev, which maps linearly to logarithmic power, RxQual maps logarithmically to the raw bit error rate measured on the bursts prior to channel decoding.

The mapping from raw Bit Error Rate to integer RxQual values is defined in 3GPP TS 45.008 Section 8.2.4 as follows:

To measure voice frame transmission performance accurately, GSM distinguishes between RxQual_Full and RxQual_Sub. RxQual_Full evaluates all 104 frames within a 480 ms SACCH reporting period. Conversely, RxQual_Sub evaluates only the subset of frames transmitted when Discontinuous Transmission (DTX) is active (specifically, mandatory speech frames and Comfort Noise Insertion descriptor frames). Analyzing RxQual_Sub during drive testing eliminates false poor-quality reports generated by muted silence periods when DTX is enabled.

Subjective voice evaluations governed by ITU-T Recommendation P.800 show that when RxQual degrades from 3 to 5, the Mean Opinion Score (MOS) drops below 3.0, causing audio distortion, robotization, and frame dropping.

4. Analyzing the Combined RxLev / RxQual Matrix in Drive Test Datasets

When diagnosing drive test logs, reviewing RxLev or RxQual independently can lead to incorrect conclusions. RF field engineers combine both metrics into a four-quadrant diagnostic matrix to isolate physical layer root causes. The matrix categorizes RF conditions into distinct operational scenarios:

• High RxLev / Good RxQual (RxLev > 25, RxQual 0-2): Optimal RF conditions. The receiver enjoys high carrier power and minimal interference. No physical or frequency layer action is required.
• High RxLev / Poor RxQual (RxLev > 25, RxQual 5-7): Severe Interference or Distortion. Strong signal is present, but bit error rate is high. Primary causes include co-channel interference (C/I < 9 dB), adjacent channel interference, strong multipath delay spread, or bad frequency hopping sequences.
• Low RxLev / Good RxQual (RxLev < 15, RxQual 0-2): Weak Coverage / Clean Environment. Received power is near the thermal noise floor, but low interference allows the channel decoder to recover data. Handover to a stronger neighbor should be configured.
• Low RxLev / Poor RxQual (RxLev < 15, RxQual 5-7): Thermal Noise Floor Limitation or Coverage Hole. Power is insufficient to overcome environmental thermal noise, leading to carrier-to-noise (C/N) degradation. The connection is at immediate risk of dropping.

Rule of Thumb: If RxLev is strong (-65 dBm) but RxQual is worse than 5, stop looking for hardware coverage solutions and begin investigating frequency reuse plans or physical sector overlaps.

5. Root-Cause Analysis for RF Anomalies: Co-Channel Interference vs. Weak Coverage

Distinguishing between co-channel interference (CCI) and pure coverage weakness is a critical skill during drive test post-processing. GSM standard GSM 05.08 / 3GPP TS 45.008 requires a minimum Carrier-to-Interference ratio (C/I) of 9 dB for Gaussian Minimum Shift Keying (GMSK) modulation to maintain acceptable speech frame error rates.

In a co-channel interference scenario, a drive test log shows an RxLev of -70 dBm (RxLev 40) paired with an RxQual spiking between 5 and 7. The mobile unit receives two or more cells operating on the same Absolute Radio Frequency Channel Number (ARFCN) with comparable signal strengths. Because the subscriber unit cannot reject the interfering ARFCN, the burst error rate escalates rapidly.

To fix co-channel interference, verify sector orientation using the GSM Azimut Checker to confirm physical antenna bearings. Unintended over-shooting sectors caused by improper mechanical or electrical downtilt often beam strong signals miles past their planned coverage boundaries, polluting co-channel cells in neighboring clusters.

In contrast, pure coverage weakness shows RxLev dropping steadily from -95 dBm down to -108 dBm, accompanied by a simultaneous linear deterioration of RxQual from 2 up to 7 as the signal approaches the mobile receiver sensitivity limit. Here, hardware output power, cable attenuation, antenna gain, or terrain obstruction are the root causes rather than frequency plan collisions.

6. Step-by-Step Drive Test Troubleshooting Sequence

When drive test field logs reveal sustained periods of RxQual greater than 4 or unexpected drop calls, follow this systematic field troubleshooting workflow:

1. Filter and Isolate Dedicated Mode Logs: Verify whether DTX is enabled. Switch logging visualization to inspect RxQual_Sub and RxLev_Sub to exclude silence periods.
2. Check Serving Cell Absolute Signal Level: If RxLev is below -100 dBm (RxLev < 10), classify the issue as a low signal coverage boundary. Check target handover candidate lists on the SACCH.
3. Evaluate Serving vs. Neighbor ARFCNs: If RxLev is strong (-75 dBm or higher) but RxQual is high, list the serving cell ARFCN and scan all neighbor cell BCCH/BSIC allocations in the log. Identify if a neighbor or distant sector is broadcasting on the same ARFCN or N+1/N-1 adjacent channel.
4. Audit Physical Site Alignments: Cross-check the current vehicle position against site database coordinates. Use the GSM Azimut Checker to measure actual antenna bearings relative to target sectors to confirm that sector swapping or azimuth drift has not occurred.
5. Inspect Site Hardware Alarms: Verify if the serving BTS reports Voltage Standing Wave Ratio (VSWR) alarms, low transmit power on specific Transceiver (TRX) units, or faulty low-noise amplifiers (LNAs) in the receive path.
6. Validate Handover Threshold Parameters: Check if handover execution thresholds (such as RxLev_Min, HO_Margin, or PMR thresholds) are set too high or too low, preventing timely handovers before quality collapses.

7. Practical Field Limitations, Handover Thresholds, and Mitigation Strategies

Drive testing presents several practical limitations that field engineers must account for during data interpretation. First, fast fading (Rayleigh fading) causes rapid fluctuations in instantaneous signal level. Because SACCH reporting occurs once every 480 ms, short power dips can occur between reporting intervals, resulting in momentary quality drops that are not fully captured in averaged RxLev figures.

Second, vehicle speed alters the Doppler shift and multipath fading profile. At higher velocities, channel equalizer algorithms inside mobile station basebands work harder to correct phase distortion, which can increase BER even if RxLev remains stable.

To mitigate these effects and improve key performance indicators (KPIs), network performance teams tune specific network parameters:

• Frequency Hopping (FH): Implementing Synthesized or Baseband Frequency Hopping converts continuous co-channel interference into randomized burst errors, allowing forward error correction algorithms (Convolutional Coding and Fire Codes) to successfully reconstruct corrupted frames.
• Antenna Tilt Optimization: Applying remote electrical tilt (RET) to over-shooting sectors reduces far-field coverage footprint while maintaining strong local dominance. Re-evaluate coverage contours using the GSM Coverage Planner.
• Power Control Parameters: Tuning Downlink Power Control (DLPC) and Uplink Power Control (ULPC) ensures that mobile stations and base stations lower output power when close to the site, reducing overall interference across the cluster.
• Handover Threshold Optimization: Lowering RxQual_HO_Threshold ensures the network triggers quality-based handovers before speech frame erasure rates reach critical levels.

Frequently asked questions