Service / 02 — Protocol Validation

Modem protocol validation.

3GPP conformance, IODT, performance, and field validation across cellular modems and IoT radios. The same protocol-stack discipline that Qualcomm, Broadcom, MediaTek, and Nvidia apply before their silicon ships.

Why we validate here

Standards are contracts.

A 5G modem implements a contract written in over ten thousand pages of 3GPP specification. Every layer — PHY, MAC, RLC, PDCP, RRC, NAS, IMS — has hundreds of message exchanges, timers, and corner cases that must behave exactly as specified, on every network, in every region.

Protocol validation is how that contract is actually enforced. Done well, it catches bugs before silicon tape-out, before regulatory submission, and long before an end-user sees a dropped call. Done poorly, it produces device recalls and carrier blacklists.

We run protocol validation at a discipline consistent with what the largest modem vendors expect: conformance suites, IODT campaigns, performance benchmarking, field validation, and root-cause down to L1 traces.

Capabilities

What we actually do.

/ 01

3GPP conformance

TS 38.521 / 38.523 (NR), TS 36.521 / 36.523 (LTE) protocol conformance. RF, RRM, and signaling test campaigns on certified test equipment.

/ 02

Inter-Operator Device Testing (IODT)

IODT campaigns against operator core and RAN setups — Verizon, AT&T, T-Mobile, Vodafone, Reliance Jio, Airtel, NTT, KDDI, SoftBank, China Mobile, and tier-2 operator scenarios.

/ 03

Network emulation & lab

Full RAN emulation on Keysight UXM, R&S CMX, Anritsu MT8000A. End-to-end IMS, EPC, and 5GC lab setup with controllable impairments and channel models.

/ 04

Field validation

Drive testing, ride testing, and stationary measurement campaigns across multi-operator footprints. Coverage, capacity, mobility, and handover characterization.

/ 05

Performance & KPI

Throughput, latency, attach-time, handover-success, voice MOS, jitter, and battery life under representative workloads. Statistical regression across modem firmware revisions.

/ 06

L1 / L2 / L3 debug

Layer-1 trace analysis, MAC scheduler debug, RLC AM/UM corner cases, RRC reconfiguration debugging, and NAS authentication / session management triage.

/ 07

Carrier acceptance

Carrier-specific test plans for major operators worldwide. PTCRB, GCF, FCC, and regional regulatory submission packages.

/ 08

IoT & NTN protocol validation

NB-IoT, LTE-M, 5G RedCap, and 5G NTN conformance. Power-saving mode (PSM), eDRX, and small-data transmission validation across 3GPP releases.

Stack

The tools we work with.

A practical, opinionated stack — chosen for production reliability, not novelty. We add to it carefully, and we share what we learn.

Standards

  • 3GPP NR (Rel-15 to 19)
  • LTE-A Pro
  • 5G NTN
  • VoNR / VoLTE
  • IMS SIP
  • NB-IoT / LTE-M / RedCap

Test equipment

  • Keysight UXM 5G
  • R&S CMX500 / CMW500
  • Anritsu MT8000A / MD8475B
  • Spirent Landslide
  • VIAVI TM500

Protocol tools

  • QXDM / QCAT
  • Wireshark
  • MobileInsight
  • Tektronix Sniffer
  • Custom log parsers

Frameworks

  • Python pytest
  • Robot Framework
  • TTCN-3
  • Custom test harnesses

Field tools

  • Rohde & Schwarz TSME
  • VIAVI CellAdvisor
  • Keysight Nemo
  • PCTel SeeGull

Certifications

  • PTCRB
  • GCF
  • Operator acceptance
  • Regional regulatory
Outcomes

What an engagement looks like.

Engagement model Per-feature, per-release, or sustaining engagements8 weeks to multi-quarter programs
Typical deliverables Test plans, automation, conformance reports, IODT logsCarrier and certification submission packages
Quality bar 100% mandatory test pass, optional features trackedField KPIs aligned with operator acceptance bars
Hand-off & ownership All scripts, logs, and reports; defect tracking continuityOptional retainer through certification cycles
Talk to us

Bring us a problem in this layer.

We work with a small number of partners each year. The right first step is usually a conversation. Or look at what we build.

Start a conversation

See product wings →