Is PTCRB enough to launch 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 additionally requires its own IoT device certification: intake on the DICE portal (Device Intake Center for Engineering), documentation and functional compliance checks, Validation Lab testing, then Technical Acceptance (TA). Without that approval, the product does not enter the T-Mobile certified devices list.

What is the T-Mobile DICE portal?

DICE (Device Intake Center for Engineering) is the intake tool of T-Mobile IoT device certification. The manufacturer completes the initial questionnaire there, documents compliance with T-Mobile requirements (OEM functional tests, RF OTA TRP/TIS results), declares the product TAC via a TAC Data Card and prepares Validation Lab entry. Access is granted after a short onboarding through the T-Mobile for Business site.

What is the T-Mobile certified modules and devices list?

T-Mobile publishes on its website the list of products certified on its network, with two rating levels: Network Certified+ (meets all requirements, compatible with key strategic technology initiatives) and Network Certified (meets requirements partially). Using a module already certified by T-Mobile is the most profitable optimisation: T-Mobile then charges no certification fee and Technical Acceptance can be granted in as little as five business days.

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 a handicap against T-Mobile RF OTA (TRP/TIS) criteria.

Where do the T-Mobile US 2G and 3G sunsets stand?

T-Mobile's 3G UMTS network was retired on July 1, 2022, following the retirement of Sprint CDMA (March 31, 2022) and Sprint LTE (June 30, 2022). T-Mobile has announced the retirement of its 2G GSM network as of August 3, 2026. Any IoT product that depends on a North American 2G or 3G fallback must therefore migrate to an LTE Cat-1, LTE-M, NB-IoT or 5G NR stack to remain usable on the T-Mobile network.

How do the TAC and IMEI come into T-Mobile certification?

The TAC (Type Allocation Code), allocated by GSMA, identifies the product model in the first 8 digits of the IMEI. T-Mobile requires the manufacturer to declare the product TAC in the DICE portal via a TAC Data Card before lab entry. The certified product is identified by that TAC, so the GSMA allocation must be obtained early in the project.

What is the difference between T-Mobile, Verizon Open Development and AT&T Network Ready?

All three carriers impose their own homologation on top of PTCRB. Verizon Open Development runs from its Open Development portal, with eUICC validation (SGP.02 and SGP.22 paths) and the B13/B66 bands historically at the centre. AT&T Network Ready builds on the IoT Network Certified (INC) certification administered by CTIA Certification, with the TRENDI network test and FirstNet (B14, n14) for eligible products. T-Mobile US goes through its DICE portal, its Validation Lab and Technical Acceptance, with n71 600 MHz and n41 2.5 GHz at the centre. No report is transferable from one carrier to another.

T-Mobile US: cellular IoT device certification and DICE

Author Hugues Orgitello Last updated 11 July 2026 ~12 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: T-Mobile IoT device certification. It runs through the DICE portal (Device Intake Center for Engineering), compliance checks (documentation, functional testing, RF OTA TRP/TIS), a pass through the carrier's Validation Lab, and concludes with Technical Acceptance (TA) and the listing of the product among T-Mobile certified devices. This page covers the T-Mobile scope versus PTCRB, the carrier-specific bands (notably n71 600 MHz and n41 2.5 GHz), the manufacturer workflow, and the pitfalls that delay a 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 (March 31, 2022), Sprint LTE (June 30, 2022), T-Mobile 3G UMTS (July 1, 2022), and a 2G GSM retirement announced for August 3, 2026.

T-Mobile counts as a standalone commercial target and cannot be addressed through PTCRB alone. The carrier requires its own IoT device certification, run from the DICE portal and its Validation Lab.

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 IoT device certification
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 requirements: compliance documentation, functional testing, RF OTA TRP/TIS criteria
Scope	Generic multi-carrier radio conformance	Interoperability and performance on the T-Mobile network
Granted by	CTIA Certification (PTCRB scheme)	T-Mobile US, via the DICE portal and Validation Lab
Identifier	EPC (End Product Certification) or Modular Certification	Technical Acceptance (TA), Network Certified or Network Certified+ listing
Required for a T-Mobile launch	Yes	Yes, in addition to PTCRB

PTCRB is a prerequisite but not sufficient: T-Mobile asks for proof of PTCRB compliance in its lab-entry prerequisites. With PTCRB alone, the product does not enter the T-Mobile certified devices list. See PTCRB scope for the carrier and band list covered by the consortium.

Worth noting: unlike AT&T, whose Network Ready programme explicitly builds on the IoT Network Certified (INC) certification from CTIA Certification, the process published by T-Mobile references PTCRB directly in its prerequisites.

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

The T-Mobile IoT device certification process

T-Mobile publishes a four-step process, driven from the DICE portal (Device Intake Center for Engineering), accessible after a short manufacturer onboarding on the T-Mobile for Business site.

Device Intake: initial questionnaire and product dossier creation in DICE.
Compliance Checks: documentation of compliance with T-Mobile requirements, functional sanity testing and RF OTA results.
Lab Validation Testing: the T-Mobile team evaluates whether the device is ready for lab entry, then runs it through its Validation Lab.
Complete Certification: T-Mobile grants Technical Acceptance (TA) and publishes the device in its certified products list.

Two figures published by T-Mobile frame the effort: with a module already certified by T-Mobile, the carrier charges no certification fee, and if all requirements are met without issues, Technical Acceptance can be granted in as little as five business days.

Lab-entry prerequisites

T-Mobile publishes a list of OEM prerequisites before Validation Lab entry:

demonstrated PTCRB compliance (PCS Type Certification Review Board);
OEM-performed functional test results, submitted to T-Mobile for review and analysis;
T-Mobile RF OTA (TRP/TIS) performance criteria met or exceeded, with the detailed RF requirements provided in the programme documentation;
IPv6 support: IPv4/IPv6 dual stack or IPv6 only. An IPv4-only product must commit to an IPv6 time frame and obtain T-Mobile approval for a Maintenance Release;
TAC declared in DICE via a TAC Data Card, in connection with the TAC allocation obtained from GSMA;
lab samples delivered at least 48 hours before the lab entry slot, with tracking details.

T-Mobile also mentions minimum band requirements, the details of which are confirmed at intake in the portal's requirements documentation.

Certified modules and devices

T-Mobile publishes on its website the list of products certified on its network (modules, routers, hotspots, trackers and other connected devices), with two rating levels:

Network Certified+: meets all requirements, compatible with T-Mobile's key strategic technology initiatives;
Network Certified: meets most requirements, possibly with partial compatibility.

Choosing a module already certified by T-Mobile is the single most profitable optimisation in a homologation programme:

the module radio has already been validated on T-Mobile bands, reducing RF risk at device level;
the device certification scope narrows to integration (antennas, power, application firmware);
T-Mobile charges no certification fee for a device built on a certified module.

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

Cellular technology coverage and T-Mobile bands

T-Mobile US offers the full range of cellular technologies for IoT: NB-IoT, LTE-M, LTE and 5G, 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.

Unlike AT&T, which announced it is dropping NB-IoT, T-Mobile currently maintains its NB-IoT offer alongside LTE-M.

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 RF design is most demanding. A module that does not declare n71, or supports it at reduced power, loses T-Mobile's low-band coverage advantage and starts with a handicap against the RF OTA (TRP/TIS) criteria.

VoLTE and voice products

For voice-capable IoT products (POS, embedded telematics, panic button, eHealth), VoLTE/IMS conformance with the T-Mobile network is part of the functional and lab checks, all the more since 3G voice fallback has been gone since 2022 and 2G disappears in 2026. An absent or partial IMS stack on a module that was not designed for voice is a structural risk to address at module selection.

T-Mobile homologation workflow, step by step

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

T-Mobile for Business onboarding: manufacturer contact form, then access to the DICE portal.
Module selection from the T-Mobile certified products list and confirmation of target bands (n71 strongly recommended for rural coverage).
TAC allocation from GSMA for the product IMEI range.
Device Intake in DICE: initial questionnaire, TAC Data Card, product documentation.
Internal pre-tests at the manufacturer or at a PTCRB lab (RF, OTA TRP/TIS, functional, IPv6) to reduce iteration risk.
PTCRB EPC granted in advance or in parallel (lab-entry prerequisite).
T-Mobile Compliance Checks: submission of compliance evidence and OEM functional test results.
Lab Validation Testing: samples delivered at least 48 hours before the slot, Validation Lab campaign, firmware iterations as needed.
Technical Acceptance and publication of the product in the T-Mobile certified devices list.
Commercial launch on the T-Mobile network, with monitoring of requirement changes through the portal.

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 (DICE + Validation Lab)	Verizon Open Development	AT&T Network Ready
Programme	IoT device certification, Technical Acceptance, Network Certified listing	Open Development device certification, ODP portal	Network Ready, built on IoT Network Certified (CTIA), TRENDI test
Prerequisite	PTCRB	PTCRB	IoT Network Certified (derived from the PTCRB programme)
Priority LTE bands	B2, B4, B12, B66, B71	B2, B4, B5, B13, B66	B2, B4, B12 (published minimum)
Priority NR bands	n25, n41, n71	n5, n66, n77	n2, n5, n66, n77
Mission-critical	Optional per product	Optional per product	FirstNet (B14, n14) for eligible products
Final identifier	TA + Network Certified or Network Certified+ listing	OPC + Verizon-Approved IMEI	Network Ready listing + IMEI management
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 + Network Ready + T-Mobile certification, plus FCC ID. On the Sprint legacy side: the Sprint networks have been retired since 2022, and a historical Sprint approval does not substitute for current T-Mobile certification.

See also AT&T Network Ready for the detailed AT&T counterpart.

5G Advanced Network Solutions and private networks

T-Mobile markets its enterprise network offers as 5G Advanced Network Solutions, in three flavours: Public Mobile Network, Hybrid Mobile Network and Private Mobile Network. Standard IoT device certification covers public network use. For a product intended for a hybrid or private deployment (industrial site, campus, logistics), any additional requirements (QoS, integration, security) are scoped bilaterally with T-Mobile enterprise teams, on top of the standard device certification. If private networking is not in the spec, it is safer not to advertise specific compatibility.

Sunsets and Sprint legacy

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

3G UMTS retired on July 1, 2022

T-Mobile retired its 3G UMTS network on July 1, 2022. Any IoT product based on a legacy 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 and LTE retired in 2022

The Sprint legacy was retired after the merger: Sprint CDMA on March 31, 2022, Sprint LTE on June 30, 2022. 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, and a module historically approved on Sprint must go through current T-Mobile certification.

2G GSM: retirement announced for August 3, 2026

T-Mobile has announced the retirement of its 2G GSM network as of August 3, 2026, the last 2G network of a US tier-1 still in service. IoT fleets that still rely on a GSM fallback in the United States must have migrated to LTE, LTE-M, NB-IoT or 5G NR before that date.

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 T-Mobile certification does not enter the certified devices list and cannot be launched cleanly on the network. Discovery often happens late, when the commercial calendar is already committed.

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 against the TRP/TIS criteria. n71 belongs in the antenna specification, not in a last-minute fix.

3. IPv4-only stack

T-Mobile requires IPv6 support (IPv4/IPv6 dual stack or IPv6 only). An IPv4-only firmware forces a commitment to an IPv6 migration time frame and T-Mobile approval for a Maintenance Release. Planning dual stack from the initial firmware avoids that negotiation.

4. Declaring the TAC too late

The TAC Data Card in DICE is part of the lab-entry prerequisites, and TAC allocation from GSMA takes time (technical file, fees). A missing TAC blocks Validation Lab entry even when everything else is ready.

5. Relying on a Sprint-legacy module

A module historically Sprint Approved is not automatically T-Mobile certified post-merger. 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 from AT&T FirstNet (Network Ready plus B14/n14) conflates two ecosystems. T-Mobile mission-critical coverage does not run on n14.

8. Neglecting lab logistics

T-Mobile requires lab samples to arrive at least 48 hours before the lab entry slot, with tracking details. A late delivery pushes back Validation Lab entry and can slide the whole launch schedule.

Project sequencing, the right timing

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

Module design phase: pick a T-Mobile certified module, validate n71 and n41 support, plan IPv4/IPv6 dual stack.
Antenna design phase: size the antenna for 600 MHz (n71/B71) without degrading 2.5 GHz (n41), with the TRP/TIS criteria in mind. This is one of the harder RF trade-offs in compact IoT.
Hardware stabilisation phase: T-Mobile for Business onboarding, DICE access, GSMA TAC allocation.
Pre-certification phase: RF, OTA TRP/TIS, functional and IPv6 pre-tests.
PTCRB phase: Modular then End-Product submission, EPC granted.
T-Mobile certification phase: DICE intake, Compliance Checks, Validation Lab campaign, firmware iterations as needed.
Technical Acceptance phase: TA granted, product published in the certified devices list.
Commercial launch and monitoring of T-Mobile requirement changes (bands, sunsets, new technologies).

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, direct prerequisite of T-Mobile Validation Lab entry.
Verizon Open Development: separate Verizon programme, non-transferable.
AT&T Network Ready: 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 Technical Acceptance and certified devices listing (carrier).

For the vocabulary (TAC, IMEI, IMS, VoLTE, NSA, OTA), see the spilma glossary.

Frequently asked questions

Is PTCRB enough to launch 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 additionally requires its own IoT device certification: intake on the DICE portal (Device Intake Center for Engineering), documentation and functional compliance checks, Validation Lab testing, then Technical Acceptance (TA). Without that approval, the product does not enter the T-Mobile certified devices list.
What is the T-Mobile DICE portal?: DICE (Device Intake Center for Engineering) is the intake tool of T-Mobile IoT device certification. The manufacturer completes the initial questionnaire there, documents compliance with T-Mobile requirements (OEM functional tests, RF OTA TRP/TIS results), declares the product TAC via a TAC Data Card and prepares Validation Lab entry. Access is granted after a short onboarding through the T-Mobile for Business site.
What is the T-Mobile certified modules and devices list?: T-Mobile publishes on its website the list of products certified on its network, with two rating levels: Network Certified+ (meets all requirements, compatible with key strategic technology initiatives) and Network Certified (meets requirements partially). Using a module already certified by T-Mobile is the most profitable optimisation: T-Mobile then charges no certification fee and Technical Acceptance can be granted in as little as five business days.
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 a handicap against T-Mobile RF OTA (TRP/TIS) criteria.
Where do the T-Mobile US 2G and 3G sunsets stand?: T-Mobile's 3G UMTS network was retired on July 1, 2022, following the retirement of Sprint CDMA (March 31, 2022) and Sprint LTE (June 30, 2022). T-Mobile has announced the retirement of its 2G GSM network as of August 3, 2026. Any IoT product that depends on a North American 2G or 3G fallback must therefore migrate to an LTE Cat-1, LTE-M, NB-IoT or 5G NR stack to remain usable on the T-Mobile network.
How do the TAC and IMEI come into T-Mobile certification?: The TAC (Type Allocation Code), allocated by GSMA, identifies the product model in the first 8 digits of the IMEI. T-Mobile requires the manufacturer to declare the product TAC in the DICE portal via a TAC Data Card before lab entry. The certified product is identified by that TAC, so the GSMA allocation must be obtained early in the project.
What is the difference between T-Mobile, Verizon Open Development and AT&T Network Ready?: All three carriers impose their own homologation on top of PTCRB. Verizon Open Development runs from its Open Development portal, with eUICC validation (SGP.02 and SGP.22 paths) and the B13/B66 bands historically at the centre. AT&T Network Ready builds on the IoT Network Certified (INC) certification administered by CTIA Certification, with the TRENDI network test and FirstNet (B14, n14) for eligible products. T-Mobile US goes through its DICE portal, its Validation Lab and Technical Acceptance, with n71 600 MHz and n41 2.5 GHz at the centre. No report is transferable from one carrier to another.
Do T-Mobile private networks or 5G slicing change the certification procedure?: Standard IoT device certification covers public network use. T-Mobile markets its enterprise network offers as 5G Advanced Network Solutions, in three flavours: Public Mobile Network, Hybrid Mobile Network and Private Mobile Network. For a product intended for a hybrid or private deployment, any additional requirements are scoped bilaterally with T-Mobile enterprise teams, on top of the standard device certification.