Dual-SIM simultaneous network testing: why it's a game-changer
How simultaneous dual-SIM network testing eliminates synchronization problems in operator benchmarking. Per-SIM Layer 3 tagging, RF measurement, and real-world use cases.
Operator benchmarking has always required comparing network performance between two or more carriers under identical conditions. The traditional approach β two phones, two holders, two logging sessions β introduces synchronization errors, increases equipment cost, and complicates post-processing. Dual-SIM simultaneous testing solves all of these problems on a single device.
This article explains why simultaneous dual-SIM collection is a fundamental improvement for mobile network benchmarking and field testing.
The problem with traditional multi-operator testing
When an RF engineer or benchmarking team needs to compare Operator A against Operator B, the standard approach has been:
- Two separate phones, each with one SIM, mounted side by side in a vehicle
- Two drive test tools running independently, with no shared clock reference
- Post-processing alignment where an analyst manually synchronizes the two log files by timestamp, GPS position, or both
This approach has several well-known problems:
Time synchronization
Even with NTP or GPS-synced clocks, the two devices do not perform measurements at exactly the same instant. A 500ms offset means the two phones may be on different cells, in different RRC states, or experiencing different fading conditions. At highway speeds (120 km/h), 500ms translates to 17 meters of displacement.
Environmental inconsistency
Two phones mounted in slightly different positions experience different RF conditions. One phone may be closer to the window; the other may be partially shielded by the dashboard or a passenger. These differences introduce systematic bias that is difficult to quantify or correct.
Equipment and logistics cost
Doubling the number of devices doubles the hardware cost, doubles the mounting complexity, and doubles the chance of a logging failure on one device corrupting the entire test run. For three-operator comparisons, the problem scales to three phones and three independent sessions.
Post-processing burden
Merging two separate log files into a single comparative dataset requires custom scripting, careful GPS alignment, and manual verification. This post-processing step can take as long as the drive test itself.
How dual-SIM simultaneous testing works
Modern Qualcomm chipsets (Snapdragon 8 series, 7 series, and select 6 series) support Dual SIM Dual Active (DSDA) or Dual SIM Dual Standby (DSDS) operation at the modem level. In DSDA mode, the chipset maintains two independent radio stacks β each SIM has its own RF chain, its own RRC connection, and its own measurement reporting.
A dual-SIM testing tool captures diagnostic data from both radio stacks simultaneously, tagging every measurement with a simIndex identifier (SIM 0 or SIM 1). This means:
- Every L3 message (RRC, NAS) is tagged with the SIM it belongs to
- Every RF measurement (RSRP, RSRQ, SINR, serving cell, neighbor list) is tagged per SIM
- Every data session (throughput, latency, packet loss) is associated with its SIM
- GPS position and timestamp are shared across both SIMs, ensuring perfect spatial and temporal alignment
The result is a single log file containing two complete, synchronized measurement streams from two different operators.
Use cases
1. Operator benchmarking
The primary use case: comparing two operators on the same route, at the same time, under the exact same conditions. No synchronization errors, no environmental bias, no post-processing alignment. The comparative analysis is immediate and trustworthy.
| Metric | SIM 0 (Operator A) | SIM 1 (Operator B) |
|---|---|---|
| Avg RSRP | -89 dBm | -95 dBm |
| Avg SINR | 14.2 dB | 9.8 dB |
| DL throughput | 78 Mbps | 42 Mbps |
| Handover count | 12 | 18 |
| VoLTE MOS | 3.9 | 3.4 |
This table is generated directly from a single drive test run β no manual alignment required.
2. Roaming validation
When an operator launches a roaming agreement with a foreign partner, the home network team needs to validate that roaming subscribers receive comparable QoS. Dual-SIM testing with one local SIM and one roaming SIM on the same device provides a controlled, apples-to-apples comparison of coverage, throughput, and voice quality.
3. MVNO vs host network comparison
MVNOs need to verify that their traffic is not deprioritized on the host operatorβs network. Dual-SIM testing with one MVNO SIM and one host operator SIM reveals any systematic QoS differences in real time, with Layer 3 evidence (QCI values, APN configurations, bearer setup times) to support escalation if needed.
4. Network upgrade validation
Before and after comparisons of network upgrades (new sites, carrier aggregation activation, 5G NR overlay) can be performed with dual-SIM: one SIM on the upgraded configuration, one on the baseline. This eliminates time-of-day and traffic load variations that confound sequential testing.
5. Regulatory benchmarking
National regulators (NRAs) conducting operator benchmarking campaigns benefit from dual-SIM testing because it ensures fairness: both operators are measured under identical propagation conditions, at the same GPS coordinates, at the same millisecond.
What makes dual-SIM testing technically challenging
Supporting dual-SIM at the diagnostic level is harder than it appears:
- DIAG multiplexing: the Qualcomm DIAG interface interleaves frames from both radio stacks on the same data stream. The parser must correctly demultiplex and tag each frame by
subscriptionIndex - Multi-radio state tracking: each SIM has its own RRC state machine, its own cell selection history, and its own measurement configuration. The tool must maintain two independent protocol state models
- Resource contention: in DSDS mode (as opposed to DSDA), the two SIMs share a single RF chain and take turns. The tool must account for this time-sharing when analyzing throughput or latency
- Data session isolation: when running simultaneous throughput tests, the tool must bind each test socket to the correct network interface (SIM 0 or SIM 1) to avoid routing cross-contamination
These challenges require deep integration with the Qualcomm modem stack and careful engineering of the DIAG parser and session manager.
HiCellTekβs dual-SIM implementation
HiCellTek is, to our knowledge, the only smartphone-based drive test tool that supports simultaneous dual-SIM data collection with per-SIM Layer 3 tagging. Every measurement, every decoded L3 message, and every data session KPI is automatically tagged with its simIndex, enabling direct side-by-side comparison without post-processing alignment.
Key capabilities:
- Simultaneous RF measurement on both SIMs (RSRP, RSRQ, SINR, PCI, EARFCN/NR-ARFCN)
- Per-SIM RRC and NAS message decoding with full ASN.1 output
- Per-SIM throughput, latency, and MOS measurement
- Single unified HLOG file with both SIM streams, GPS-synchronized
- Export to CSV, JSON, Parquet with
simIndexcolumn for analysis
Conclusion
Dual-SIM simultaneous testing eliminates the fundamental limitations of multi-device benchmarking: synchronization errors, environmental bias, and post-processing complexity. For any team performing operator comparisons, roaming validation, or MVNO quality assurance, it is a decisive improvement in methodology and efficiency.
Explore HiCellTekβs dual-SIM capabilities on the product page or review licensing options on the pricing page. For full field measurement specifications, see the Android drive test tool page.
Founder of HiCellTek. 15+ years in telecom, operator side, vendor side, field side. Building the field tool RF engineers deserve.
Request a personalized demo of HiCellTek β 2G/3G/4G/5G network diagnostics on Android.