GSM Drive Test Checklist for Field Engineers

1. Pre-Drive Preparation and Audit Setup

A successful GSM drive test begins well before the vehicle leaves the staging area. Field engineers must execute a structured audit of the network configuration database, cell site parameter files, and target drive routes to ensure data integrity. Collecting data with incorrect cell configuration files or outdated frequency plans leads to erroneous conclusions and wasted drive hours.

Cell Engineering Database Validation

Verify that your drive software uses the current Cell Engineering File (CEF) or cell site database. Confirm the following site elements against actual network engineering records:

• Base Station Identity Code (BSIC): Verify Network Color Code (NCC) and Base Station Color Code (BCC) definitions for all target cells.
• BCCH Carrier Frequency: Check that assigned Absolute Radio Frequency Channel Numbers (ARFCN) match current spectrum allocations per 3GPP TS 45.008 specifications.
• Antenna Parameters: Audit site geographical coordinates, mechanical tilt, electrical tilt, and azimuth values. Tools like the GSM Azimut Checker help confirm expected directional bearings before driving.
• Neighbor Cell Lists: Ensure adjacent cell handover relations (both intra-frequency and inter-frequency) are properly populated in the active cell file.

Before launching test scripts, perform a static spot check directly under or near the serving cell site to confirm that the observed Cell ID (CID), Location Area Code (LAC), and ARFCN align perfectly with database expectations.

2. Pre-Drive Hardware Setup and Calibration Protocol

Hardware instability during a drive test compromises millions of data points. Establishing a stable hardware setup prevents power loss, thermal throttling of test phones, and erroneous RF signal attenuation.

Physical Installation Checklist

1. Power Management: Connect all mobile devices and RF scanners to a regulated pure sine wave inverter or calibrated vehicle power distribution unit. Unstable vehicle DC supply voltage can cause unexpected device reboots or altered transmitter power output.
2. Antenna Mounting: Mount magnetic-mount omnidirectional antennas on the center of the vehicle roof. Maintain a minimum separation distance of 50 centimeters (approximately half a wavelength at GSM 900 MHz frequencies) between receiving antennas to prevent mutual coupling and radiation pattern distortion.
3. Cable Inspection: Inspect all RF coaxial cables and RF connectors (SMA, N-type) for physical damage, tight pin alignments, and shield continuity. Cable bend radius must strictly comply with manufacturer limits to prevent micro-fractures in the inner conductor.
4. GPS Lock and Port Mapping: Verify a minimum 3D GPS fix with at least 4 active satellites before starting log recording. Confirm that the drive testing software maps individual COM ports correctly to trace phones, CW scanners, and GPS receivers.

Always conduct a 5-minute stationary benchmark test before departing. Verify that signal levels show low variance and that speech quality index (SQI) and RxLev values reflect accurate static RF conditions.

3. Essential GSM RF Parameters and Threshold Specifications

To evaluate network performance objectively, field engineers evaluate collected log data against defined 3GPP and ETSI performance benchmarks. The primary parameters evaluated during a GSM drive test include Received Signal Level (RxLev), Received Signal Quality (RxQual), Carrier-to-Interference Ratio (C/I), and Speech Quality Index (SQI).

RxQual and Bit Error Rate (BER) Classifications

Per ETSI TS 145 008 / 3GPP TS 45.008 standards, GSM measures voice link quality using RxQual values ranging from 0 to 7, which directly correspond to Bit Error Rate percentages measured prior to channel decoding.

Target Metric Thresholds for Field Audits

When auditing commercial or private GSM networks, evaluate coverage and quality against these industry accepted standard thresholds:

• RxLev (Full / Sub): Coverage target is RxLev > -85 dBm in urban areas and > -95 dBm in rural environments. Signal below -102 dBm indicates severe coverage gaps.
• RxQual (Full / Sub): Target average RxQual < 3.0 during active voice calls. Sustained periods above RxQual 5 trigger poor user experience and potential dropped calls.
• Carrier-to-Interference (C/I): Co-channel interference ratio must remain above 9 dB for unmodulated carriers, with a recommended target of C/I > 12 dB for acceptable voice codecs per ITU-R radio recommendation guidelines.
• Handover Success Rate (HOSR): Route-wide successful handover executions should exceed 98.5%.

4. Step-by-Step Drive Route Execution Checklist

Executing a drive test requires structured driving routines to capture both Idle Mode cell selection and Dedicated Mode call retention behavior under moving conditions. Tools like the GSM Drive Test platform help log real-time mobile dynamics across various drive scenarios.

Execution Phase Sequence

1. Idle Mode Drive Test: Drive the target route while the trace phones remain in idle mode. Record BCCH serving cell selection, cell reselection events, Location Area Updates (LAU), and neighbor measurement reports. This maps actual broadcast coverage boundaries without channel dedicated power control dynamics.
2. Dedicated Short Call Testing: Configure automated test sequences executing MOC (Mobile Originating Call) or MTC (Mobile Terminating Call) voice calls lasting 60 to 90 seconds, followed by a 15 to 20 second idle pause. This tests call setup success rate (CSSR), SDCCH drop rate, and TCH allocation efficiency.
3. Dedicated Long Call (Retention) Testing: Execute continuous voice calls lasting 15 to 30 minutes while driving across major cell boundaries. This stress tests continuous handover execution, ping-pong handovers, and drop call behavior under variable fading conditions.
4. Forced Handover and Lock Tests: Lock test phones to specific ARFCNs or bands (GSM 900 vs GSM 1800) to isolate individual sector footprints and verify tilt coverage limits calculated during RF planning in tools such as the GSM Coverage Planner.

5. Systematic Troubleshooting Sequence for Field Engineers

When drive logs indicate poor KPIs, engineers must systematically isolate the root cause using standardized diagnostic steps. Below is a structured troubleshooting workflow for common RF issues encountered during GSM drive testing.

Issue 1: High Signal Strength (RxLev > -75 dBm) with Poor Quality (RxQual > 5)

Diagnostic Sequence: Rule out interference standard causes before replacing physical site hardware.

1. Check C/I and C/A (Carrier-to-Adjacent) values on the test phone or RF scanner logs.
2. If C/I < 9 dB, inspect adjacent cell lists and frequency plans for co-channel ARFCN assignments within line-of-sight distance.
3. If C/I is high but RxQual remains poor, check for external non-GSM radio interference using a wideband spectrum analyzer.
4. Audit site synchronization and check for localized intermodulation distortion caused by corroded jumpers or damaged diplexers.

Issue 2: Frequent Call Drops During Handovers

1. Inspect log files for missing neighbor relationships. If the serving cell drops the call while a strong candidate cell is logged without being listed in the MEAS_REP (Measurement Report), add the missing neighbor relation.
2. Verify BSIC decoding. If the mobile station receives strong signal on a neighbor ARFCN but fails to decode the BSIC due to co-channel BSIC collision, update the target site's BSIC assignment.
3. Verify target cell TCH congestion. If handover command is issued but rejected with Cause Code 34 (No circuit/channel available), report capacity constraints to network planning.

Issue 3: Coverage Hole or Abrupt Signal Drop

1. Verify whether the physical antenna orientation matches planning records using the GSM Azimut Checker. An unintended azimuth shift or incorrect mechanical tilt causes major signal nulls along primary roads.
2. Inspect feeder loss and VSWR reports on the serving sector to confirm the transmitter output power is reaching the antenna.

6. Post-Drive Data Verification and Export Protocols

Data collection is only as useful as the post-processing verification behind it. Upon completing a drive route, execute strict log file verification routines before leaving the field area.

Log File Sanity Check Checklist

• File Size and Integrity: Confirm log files are non-zero in size and contain continuous trace data without corrupt frame timestamps.
• Geographic Mapping Synchronization: Replay the log file in post-processing tools to ensure latitude and longitude points line up correctly with actual roadways, verifying no GPS freeze occurred during testing.
• Parameter Completeness: Verify that call events, layer 3 messages (such as Immediate Assignment, Paging Response, Handover Command), and neighbor cell reporting blocks were fully recorded.
• Comparative Baseline Check: Cross-reference collected coverage footprints against predictive models generated by tools like the GSM Coverage Planner Web to highlight model discrepancies or real-world signal deviations caused by new structural developments.

7. Practical Field Limitations and Environmental Factors

Field engineers must account for physical and environmental factors that temporarily distort RF measurement data during a drive test.

Vehicle Shielding and Penetration Loss

When using internal handset antennas inside a vehicle without external roof-mounted antennas, signal attenuation (vehicle penetration loss) typically ranges from 3 dB to 12 dB depending on glass tinting, vehicle body construction, and phone position. Always document whether a test run used internal or external antennas in the drive test metadata.

Seasonal Foliage and Urban Multipath Dynamics

Dense vegetation can introduce additional propagation loss of 6 dB to 15 dB at GSM frequencies, especially when foliage is wet. In deep urban canyons, multipath Rayleigh fading causes rapid RxLev fluctuations. Drive speeds must be kept stable (ideally 30 to 50 km/h in urban zones) to ensure adequate spatial averaging over time windows prescribed by GSM measurement algorithms.

Frequently asked questions