Is PTCRB enough to activate a cellular product on the T-Mobile US network?

No. PTCRB proves multi-carrier radio conformance based on 3GPP test plans, but T-Mobile US conditions activation on its own validation: passage through the Live Test System (LTS) and/or the T-Mobile IoT lab, plus IMEI registration in its Equipment Identity Register (EIR). Without that registration, attach is filtered at the network level and any T-Mobile SIM shipped with the product remains blocked.

What is the T-Mobile Live Test System (LTS)?

LTS is the cellular test environment operated by T-Mobile to qualify IoT modules and devices against either its live network or a production mirror. It covers what PTCRB does not: T-Mobile-specific protocol behaviour, priority bands (notably n71 600 MHz and n41 2.5 GHz), sustained throughput, fail-over between cells and between radio technologies, SMS and USSD routed on T-Mobile signalling. Functionally, LTS is the T-Mobile counterpart of Verizon OPC and of AT&T NAF.

What is the T-Mobile approved modules list?

T-Mobile publishes a list of cellular modules already qualified on its network, comparable to the Verizon Approved Module List or to the AT&T Approved Devices List. Selecting a pre-approved module shortens device qualification because the module radio no longer has to be retested end-to-end. The list is available through the T-Mobile IoT developer portal and evolves over time, especially around NB-IoT, LTE-M and 5G NR.

Why does n71 600 MHz deserve specific attention on T-Mobile?

n71 (617 to 698 MHz) is historically a T-Mobile band in the United States, only lightly used by other tier-1 carriers. Many global modules either do not declare it by default or support it at reduced power, and compact IoT antennas tend to have mediocre gain below 700 MHz. Omitting n71 in the band declaration or under-dimensioning the antenna for it leads to degraded rural coverage and to LTS failures on network performance tests.

Has T-Mobile US sunset 3G?

Yes. T-Mobile US sunset its 3G UMTS network in 2022, in parallel with the retirement of the CDMA assets inherited from Sprint. Any IoT product relying on UMTS/HSPA fallback no longer works on the T-Mobile network. Modern designs need an LTE Cat-M, NB-IoT or LTE Cat-1/Cat-4 stack, ideally with a 5G NR path for current products. A legacy 2G/3G/4G hybrid module is, in practice, out of the T-Mobile US market.

How does IMEI registration in the T-Mobile Equipment Identity Register (EIR) work?

After successful LTS and/or IoT lab validation, T-Mobile authorises an IMEI/TAC range associated with the certified product. That range is added to its EIR, which acts as an attach filter: a T-Mobile SIM inserted in an IMEI outside the EIR is refused by the core network. The registration is processed through the IoT developer portal, in connection with the TAC allocation obtained from GSMA. Without that final step, even a clean LTS pass does not grant commercial activation.

What is the difference between T-Mobile, Verizon OPC and AT&T NAF?

All three carriers impose their own homologation on top of PTCRB. Verizon OPC runs from the ODI portal with a historic focus on SGP.22/SGP.32 eSIM and on B13/B66/n77. AT&T NAF (Network Approval Form) covers AT&T, FirstNet included, with strong attention to B14 and n14 mission-critical bands. T-Mobile US uses LTS plus its IoT lab, with n71 600 MHz and n41 2.5 GHz at the centre. No report is transferable from one carrier to another.

Do 5G slicing and private networks change the T-Mobile homologation procedure?

Partly. For a product intended to connect on a T-Mobile slice or private network (for instance the Advanced Industry Solutions offer), T-Mobile may require additional tests on NSSAI signalling, slice selection, SUCI/SUPI authentication and conformance to the contractual SLAs of the slice. These tests come on top of the standard LTS scope and are typically defined bilaterally with the T-Mobile enterprise team.

T-Mobile US: cellular IoT homologation and the LTS programme

Author Hugues Orgitello Last updated 27 May 2026 ~13 min read

Guide · T-Mobile US (IoT)

With PTCRB in hand, many teams assume their North American cellular dossier is closed. T-Mobile US, which became a US tier-1 after merging with Sprint in 2020, adds its own homologation layer before any IoT product can be activated on its network. That layer takes three concrete forms: a Live Test System (LTS) coupled with an internal IoT lab, a list of approved modules and devices, and IMEI registration in the Equipment Identity Register (EIR). This page covers the T-Mobile scope versus PTCRB, the carrier-specific bands (notably n71 600 MHz and n41 2.5 GHz), the developer workflow, 5G slicing and mission-critical considerations, and the pitfalls that block activation at launch.

T-Mobile US in the carrier landscape

Since 2020, T-Mobile US has been the third US tier-1 cellular carrier alongside Verizon and AT&T. The Sprint merger had two direct consequences for IoT:

the absorption of Sprint spectrum, in particular the 2.5 GHz band (n41 in NR), which became the backbone of T-Mobile's mid-band 5G coverage;
the gradual retirement of legacy networks (Sprint CDMA, T-Mobile UMTS in 2022), making any IoT product that falls back to legacy North American 2G/3G stacks effectively obsolete.

For a cellular IoT manufacturer targeting the US market, T-Mobile counts as a standalone commercial target and cannot be addressed through PTCRB alone. The carrier publishes a distinct IoT test plan, operates a dedicated LTS environment, and runs its own integration lab for candidate modules and devices.

T-Mobile vs PTCRB, the right separation

PTCRB and T-Mobile share the 3GPP baseline but do not cover the same scope.

Criterion	PTCRB	T-Mobile US (LTS + IoT lab)
Nature	Cross-carrier programme (AT&T, T-Mobile, Verizon, Bell, Rogers, Telus)	T-Mobile US specific programme
Reference	PTCRB test plans based on 3GPP TS 36.521 and TS 38.521	T-Mobile test plan (LTS), superset of PTCRB plus T-Mobile network requirements
Scope	Generic multi-carrier radio conformance	T-Mobile network interoperability, priority bands, SMS, USSD, fail-over, throughput
Granted by	PVG (PTCRB Validation Group)	T-Mobile US, via IoT developer portal and IoT lab
Identifier	EPC (End Product Certification) or Modular Certification	T-Mobile Approved Devices listing, IMEI/TAC registered in the EIR
Required for T-Mobile activation	Yes	Yes, in addition to PTCRB

PTCRB is a prerequisite but not sufficient. Without a valid PTCRB, T-Mobile does not accept LTS entry. With PTCRB alone, the IMEI is not registered in the EIR and activation is refused at attach. See PTCRB scope for the carrier and band list covered by the consortium.

A simple reading: PTCRB certifies that the radio respects 3GPP, the T-Mobile programme certifies that the product behaves correctly on the T-Mobile network.

The Live Test System (LTS)

Live Test System (LTS) is the T-Mobile environment that runs the carrier-specific tests. Depending on the product profile, LTS combines:

a controlled access to the live network or a production mirror, with test SIMs provided by T-Mobile;
a stimulus generator that replays realistic network scenarios (inter-cell handover, signal loss, congestion, LTE-to-5G NSA-to-SA fail-over);
a protocol test suite covering attach, SMS and USSD signalling, IMS management, VoLTE behaviour, PLMN migration, and re-attach after reset;
an application measurement harness that evaluates throughput, latency, long-duration session stability, and PSM/eDRX behaviour for LPWAN modules.

What LTS adds over PTCRB is verification that the device stack responds correctly to T-Mobile-specific configuration choices (APN parameters, attach policies, IMS behaviour, SMS routing, USSD sequences). PTCRB tests 3GPP conformance; LTS tests T-Mobile conformance.

The T-Mobile IoT lab

Alongside LTS, T-Mobile runs an IoT lab for the tests that require a controlled RF chamber, an OTA chamber, or a physical integration bench. The IoT lab is typically used for:

OTA (Over The Air) measurements on T-Mobile bands, notably n71 600 MHz and n41 2.5 GHz, where antenna performance has a direct impact on real coverage;
RF co-existence measurements (Wi-Fi, Bluetooth, GNSS in the same device);
VoLTE and mission-critical testing for products that target alarm, critical telematics, or eHealth use cases;
fail-over testing across carriers for multi-IMSI or multi-profile eSIM products, which must keep consistent behaviour when T-Mobile is the active profile and then becomes unavailable.

The IoT lab can be coupled with partner labs (typically PTCRB labs recognised by T-Mobile) for tests that do not have to be conducted inside carrier premises.

Approved modules and devices

Like the Verizon Approved Module List, T-Mobile publishes a list of cellular modules already qualified on its network, plus a list of certified end devices (Approved Devices). Choosing a pre-approved T-Mobile module is the single most profitable optimisation in a T-Mobile certification programme.

With a pre-approved module:

the module radio stack has already been validated on n71, n41, n25 and the T-Mobile LTE priority bands, reducing RF risk;
the T-Mobile-specific protocol scenarios have already been cleared at module level, so the device-level LTS narrows to integration and application;
the eSIM configuration (LPA, SM-DP+) is generally already proven against T-Mobile infrastructure.

Conversely, a module never submitted to T-Mobile requires a full module-level qualification before reaching device-level LTS, with elevated failure risk on n71 600 MHz (insufficient power margin) or on USSD/SMS sequences.

The decision belongs in the design phase, not after the fact. As with Verizon OPC, changing modules mid-project triggers PCB redesign, FCC re-validation, a fresh PTCRB campaign and a new T-Mobile LTS.

Cellular technology coverage and T-Mobile bands

T-Mobile US deploys the full range of cellular technologies relevant to IoT, with specific emphasis on certain bands.

LTE and LPWAN

LTE Cat-1 / Cat-1 bis / Cat-4 for mid-to-high throughput IoT products;
LTE-M (Cat-M1) for low-power sensors and trackers, with PSM and eDRX;
NB-IoT (Cat-NB1/NB2) for massive low-throughput deployments, fixed or low mobility.

LTE-M and NB-IoT are the dominant T-Mobile vehicles for new low-power cellular IoT projects in the United States.

5G NR

T-Mobile has deployed 5G NR on three spectrum tiers:

n71 (600 MHz), low band, wide rural and indoor coverage;
n41 (2.5 GHz), mid-band, high throughput and capacity (Sprint legacy);
n25 (1.9 GHz), complementary mid-band, intermediate deployment.

The mmWave bands (n260, n261) are marginal on T-Mobile and rarely relevant to general-purpose IoT.

T-Mobile priority bands

Band	Frequency	Technology	Specificity
n71	617 to 698 MHz	5G NR	T-Mobile rural coverage band, lightly used by other US tier-1s, IoT antennas often under-dimensioned
n41	2496 to 2690 MHz	5G NR	Sprint-legacy mid-band capacity band, high throughput, urban 5G backbone for T-Mobile
n25	1850 to 1995 MHz	5G NR	LTE B25 extension into NR, complement to n41
B2	1850 to 1990 MHz	LTE	Classic LTE band, broadly supported
B4	1710 to 2155 MHz (uplink/downlink split)	LTE	AWS-1, heavily used on T-Mobile
B12	698 to 716 MHz	LTE	Low LTE band, complement to n71
B66	1710 to 2200 MHz	LTE	AWS-3, shared with Verizon
B71	617 to 698 MHz	LTE	LTE counterpart of n71, still deployed

n71 and n41 are the two bands where T-Mobile qualification is most demanding. A module that does not declare n71, or supports it at reduced power, does not pass LTS on low-band coverage tests.

VoLTE and mission-critical considerations

For voice-capable IoT products (POS, embedded telematics, panic button, eHealth), T-Mobile enforces VoLTE conformance aligned with its IMS. LTS testing covers:

initial and post-reset IMS registration;
call establishment, hold, transfer and release;
service continuity during inter-cell handover mid-call;
signal-loss behaviour and automatic re-registration;
codec management (AMR-NB, AMR-WB, EVS) per module profile.

For products eligible to a mission-critical use (alarm, emergency, telesurveillance), T-Mobile may require additional tests on call priority, Public Warning System (PWS), and priority routing. These come on top of the standard LTS scope.

Absent or partial IMS stacks are a structural cause of LTS failure for modules that were not designed for voice in the first place.

SMS, USSD and T-Mobile signalling

SMS and USSD are the sequences where LTS most often surfaces module stack bugs:

SMS-over-IP versus SMS-over-SGs depending on whether VoLTE is active;
T-Mobile SMSC acknowledgement and store-and-forward behaviour;
USSD sequences for auto-provisioning and carrier service codes;
MO/MT SMS long concatenation (multi-segment UDH).

A module that passes the generic PTCRB SMS plan can still fail T-Mobile LTS on specific USSD sequences or on SMSC acknowledgement timing. LTS replays the real T-Mobile SMSC and is not substitutable by generic emulation.

T-Mobile homologation workflow, step by step

A typical T-Mobile US cellular IoT path follows this sequence.

T-Mobile IoT developer portal registration. Manufacturer account tied to the legal entity, KYC documentation for non-US manufacturers, project DRI identification.
Module selection from the T-Mobile approved list and confirmation of target bands (n71 effectively mandatory for any meaningful rural coverage).
TAC allocation from GSMA for the product IMEI range, prerequisite to later EIR registration.
Project submission on the T-Mobile IoT developer portal, with product description, module datasheet, antennas, band plan, application profile, eSIM profile.
Internal pre-tests at the manufacturer or at a PTCRB lab (RF, OTA, IMS, eSIM) before LTS entry, to reduce LTS iteration cost.
PTCRB EPC granted in parallel or in advance (T-Mobile LTS requires a valid PTCRB).
LTS campaign on the T-Mobile network and/or in the T-Mobile IoT lab. Firmware iterations if any tests fail.
Approved Devices validation and T-Mobile listing for the product.
IMEI/TAC registration in the EIR, authorising T-Mobile SIM attach on the product's IMEI range.
Commercial launch on the T-Mobile network, with monitoring of IoT developer bulletins for later test plan changes.

For the global PTCRB sequencing, see certification timeline, and for the overall US cellular programme cost see certification costs.

T-Mobile vs Verizon vs AT&T, comparative view

Targeting the three US tier-1 carriers means three distinct programmes on top of PTCRB.

Criterion	T-Mobile US (LTS + IoT lab)	Verizon OPC	AT&T NAF (Network Approval Form)
Programme	LTS + IoT lab, Approved Devices listing	Open Product Certification, ODI portal	Network Approval Form, AT&T IoT programme
Priority LTE bands	B2, B4, B12, B66, B71	B2, B4, B5, B13, B66	B2, B4, B5, B12, B14, B17, B29, B30, B66
Priority NR bands	n25, n41, n71	n5, n66, n77, n260, n261	n5, n14, n66, n77
eSIM RSP	SGP.22 / SGP.32	SGP.22 / SGP.32 enforced	SGP.22 / SGP.32 enforced
Mission-critical	Optional per product	Optional per product	FirstNet (n14, B14) integrated for eligible products
Final identifier	EIR-registered IMEI/TAC + Approved Devices	OPC ID + Verizon-Approved IMEI	NAF ID + AT&T-registered IMEI
Report portability	None (T-Mobile only)	None (Verizon only)	None (AT&T only)

No report is transferable from one carrier to another. A manufacturer targeting Verizon, AT&T and T-Mobile therefore accumulates PTCRB + OPC + NAF + LTS, plus FCC ID. The same applies to Sprint legacy: since the Sprint absorption by T-Mobile, older Sprint Approved Devices dossiers are migrated but do not substitute for the modern LTS.

See also AT&T NAF for the AT&T counterpart (companion guide in the same publishing batch).

5G slicing and private networks

T-Mobile US is rolling out 5G SA, slices and private network offerings (Advanced Industry Solutions, Hybrid Mobile Network). For a cellular IoT product intended for a T-Mobile slice or private network, the standard LTS is enriched:

NSSAI conformance (Network Slice Selection Assistance Information): device-driven slice selection, fallback if the target slice is unavailable;
SUCI/SUPI conformance (5G primary authentication), especially for enterprise profiles;
interoperability with the slice SMF/UPF, which may impose specific APN and QoS constraints;
roaming behaviour between the T-Mobile macro network and the private network, for mobile industrial use cases.

These tests are not systematic. They are triggered at submission depending on the declared product category. A classical LTE-M sensor does not need them. An industrial enterprise terminal can spend a meaningful share of the programme on them.

Sunsets, Sprint legacy and compatibility

Three lifecycle topics warrant specific attention on T-Mobile US.

3G UMTS sunset in 2022

T-Mobile sunset its 3G UMTS in 2022. Any IoT product based on a legacy module stack that falls back to North American 3G stops working on the network. A general-purpose 2G/3G/4G module with automatic US HSPA fallback is effectively incompatible.

Sprint CDMA retired

The Sprint CDMA assets were retired post-merger. Modules that declared CDMA-1xRTT or EVDO Sprint compatibility are only relevant for historical dossiers. A new IoT product targeting T-Mobile US should not embed a CDMA stack.

Sprint legacy IoT, migration

IoT products historically certified on Sprint are migrated by T-Mobile into its own Approved Devices dossier, typically with partial retesting to validate coverage on active T-Mobile bands. Migration is not automatic; it goes through an administrative path on the T-Mobile IoT developer portal.

Common pitfalls

1. Assuming PTCRB is enough

This is the structural pitfall common to all three US tier-1 carriers. A PTCRB-certified product without a T-Mobile LTS will activate temporarily on partner SIMs but is blocked at commercial attach once the IMEI hits the T-Mobile EIR filter. Discovery often happens at launch, when the first T-Mobile SIMs distributed refuse attach.

2. Forgetting the n71 600 MHz declaration

n71 is T-Mobile-heavy. A module that does not declare n71, or supports it at reduced power, loses a major coverage advantage in rural and deep-indoor scenarios. A compact IoT antenna (for instance a chip antenna originally designed for 2.4 GHz Wi-Fi) typically has mediocre gain below 700 MHz, which amplifies the problem. n71 belongs in the antenna specification, not in a last-minute fix.

3. Non-conformant T-Mobile USSD/SMS sequences

PTCRB covers SMS and USSD at 3GPP level, but the T-Mobile SMSC has its own timing, UDH format and error-handling quirks. A module that passes PTCRB can still fail LTS on USSD sequences or on SMSC acknowledgement timing. A USSD/SMS pre-test session, usually with the chipset vendor, is essential before LTS.

4. IMEI not registered in the EIR

Even with a clean LTS pass, if IMEI/TAC registration in the T-Mobile EIR is missing, the product does not activate. EIR registration is a post-LTS administrative step that is sometimes overlooked, particularly when the programme is outsourced to a cellular integrator. The IoT developer portal must explicitly confirm EIR registration before any SIM deployment.

5. Relying on a Sprint-legacy module

A module historically Sprint Approved is not automatically T-Mobile Approved post-merger. Dossier migration is not guaranteed without retest. A new IoT project must select a module from the current T-Mobile list, not from a Sprint history.

6. Underestimating n41 2.5 GHz

n41 is the urban 5G backbone of T-Mobile. A US-market IoT product that focuses on LTE Cat-M and ignores n41 loses the most widely deployed 5G NR capacity in cities. For high-throughput products (telematics, connected camera, industrial edge), n41 belongs in the module band matrix from day one.

7. Confusing AT&T FirstNet n14 with T-Mobile

AT&T FirstNet uses B14 and n14, reserved for public safety. T-Mobile has no FirstNet. A product that advertises "mission-critical US" without distinguishing T-Mobile (standard LTS plus options) from AT&T FirstNet (NAF plus B14/n14 mandatory) conflates two ecosystems. T-Mobile mission-critical coverage does not run on n14.

8. Advertising 5G slicing without testing

Claiming T-Mobile slice compatibility without having passed the NSSAI and SMF/UPF tests exposes the product to slice certification refusal. If slicing is not in the spec, it is safer not to advertise it commercially.

Project sequencing, the right timing

The recommended order for a cellular product targeting T-Mobile US:

Module design phase: pick a T-Mobile pre-approved module, validate n71 and n41 support, choose an SGP.22/SGP.32-conformant LPA.
Antenna design phase: size the antenna for 600 MHz (n71/B71) without degrading 2.5 GHz (n41); this is one of the harder RF trade-offs in compact IoT.
Hardware stabilisation phase: open the T-Mobile IoT developer account, GSMA TAC allocation, partner IoT lab identification.
Pre-certification phase: RF, OTA, IMS, eSIM pre-tests, plus T-Mobile-specific USSD/SMS pre-tests.
PTCRB phase: Modular then End-Product submission, EPC granted.
T-Mobile LTS phase: network and/or IoT lab campaign, firmware iterations as needed.
Approved Devices + EIR phase: T-Mobile listing granted, IMEI/TAC registered in the EIR.
Commercial launch and monitoring of T-Mobile IoT developer bulletins (test plan changes, new bands, slice evolution).

For the global EU + US sequence including CE/RED, see EU + US dual certification.

Connection with other US certifications

T-Mobile US scope is distinct from other US requirements:

FCC, intentional and unintentional emitters: independent. FCC ID obtained via TCB, with no T-Mobile dialogue.
FCC radio bands: overlap T-Mobile bands (notably n71 from the FCC 600 MHz Auction 1000) but the test plans are disjoint.
PTCRB tests: the common multi-carrier baseline that T-Mobile LTS extends.
Verizon OPC: separate Verizon programme, non-transferable.
AT&T NAF: separate AT&T programme, non-transferable.

A cellular product sold on T-Mobile in the United States therefore accumulates: FCC ID (regulator), PTCRB EPC (carrier consortium), T-Mobile Approved Devices listing (carrier), IMEI/TAC registered in the T-Mobile EIR.

For the vocabulary (LTS, EIR, TAC, IMSI, NSSAI, IMS, VoLTE), see the spilma glossary.