What is the AT&T Network Ready programme?

AT&T Network Ready (also called Get Network Ready) is the AT&T carrier homologation programme for cellular IoT terminals, managed through the iotdevices.att.com portal. It builds on the IoT Network Certified (INC) industry certification, administered by CTIA Certification and derived from the PTCRB programme, then adds AT&T onboarding and the TRENDI network test (Test Requirements for Evaluating Network Ready Devices for IoT). AT&T certifies only 5G NR, LTE and LTE-M technologies.

Why is PTCRB not enough to activate a product on the AT&T network?

PTCRB and IoT Network Certified cover the 3GPP radio conformance shared across North American carriers, a necessary but generic cross-carrier foundation. AT&T adds its Network Ready programme: manufacturer onboarding via its portal, the TRENDI test which verifies that the product performs effectively on the AT&T network, that it receives SMS and that it runs the same firmware as the INC-certified one, and IMEI compliance (DTAC or periodic uploads). Without Network Ready, the product does not enter the AT&T certified device list.

What is the difference between AT&T module approval and device approval?

Module approval applies to the cellular module (Quectel, u-blox, Telit, Sierra Wireless, Murata, Sequans, Fibocom). When the module is already in the AT&T approved module catalogue, the final product follows a lighter three-step process: INC testing in a PTCRB authorised lab, AT&T onboarding, then post-test compliance. With a non-approved module or a custom chipset, AT&T adds lab and field testing, significantly longer and more expensive.

Which AT&T bands are required for Network Ready?

AT&T publishes a minimum set of required bands for US domestic operation: B2, B4 and B12 in LTE, and n2, n5, n66 and n77 in 5G NR. The AT&T deployment covers other bands (notably B5, B14, B30, B66), B14 being reserved for FirstNet. The exact current requirements are published via the AT&T IoT portal and evolve with the operator's deployment roadmap, so they must be checked at each submission.

Does eUICC change the AT&T homologation procedure?

North American tier-1 carriers, AT&T included, rely on the GSMA SGP.22 (consumer RSP) and SGP.32 (IoT RSP) specifications. The device-side LPA or IPA must be able to dialogue with the carrier's SM-DP+: profile download, enable, disable, delete, error handling. An eUICC absent from the GSMA list or a non-compliant proprietary LPA is a common cause of blockage in carrier homologation, a point to clear at module selection time.

Is FirstNet covered by Network Ready?

No. FirstNet (the dedicated network for US public-safety services on band B14) is a separate certification programme, conducted through AT&T under the supervision of the federal FirstNet Authority, with its own security, priority and listing requirements. An AT&T-certified commercial terminal is not automatically FirstNet-approved, and vice versa. For a product targeting public-safety users, the FirstNet programme must be conducted in addition.

What is the impact of AT&T 2G, 3G and NB-IoT sunsets on new approvals?

AT&T shut down its 2G network in 2017 and its 3G network in February 2022. In late 2024, AT&T announced the end of NB-IoT, with network decommissioning under way in 2025 and customer migration to LTE-M. AT&T now certifies only 5G NR, LTE and LTE-M products. A module relying on 2G, 3G or NB-IoT fallback no longer makes sense on the US AT&T network.

Which labs can perform AT&T Network Ready testing?

INC testing can be performed in any PTCRB authorised lab. AT&T has additionally negotiated tiered pricing with partner labs through its IoT Accelerator programme. AT&T-specific testing (non-approved module, network and field tests) goes through AT&T qualified labs. The current status of any given lab must be confirmed via the AT&T IoT portal before booking a campaign.

AT&T Network Ready: carrier homologation, cellular IoT

Author Hugues Orgitello Last updated 11 July 2026 ~13 min read

Guide · AT&T Network Ready

After PTCRB, a cellular IoT product targeting the US market encounters a second approval layer: carrier homologation. AT&T calls this process Network Ready (the "Get Network Ready" programme on the AT&T IoT portal). It builds on the IoT Network Certified (INC) industry certification, then adds AT&T onboarding, the TRENDI network test and IMEI management. This page describes where Network Ready sits relative to PTCRB and INC, how the AT&T IoT portal and its approval workflow operate, the module vs device split, eUICC requirements, the specific place of FirstNet, and the pitfalls that delay durable service on the AT&T network.

Network Ready, TRENDI, ADAPT: the AT&T vocabulary

The AT&T Network Ready programme is the approval framework for cellular IoT terminals on the AT&T Mobility network. It is designed for connected objects: no screen, no end user manually triggering activation, strong power constraints, fleet management. Three terms structure AT&T documentation: Network Ready (the homologation programme itself), TRENDI (Test Requirements for Evaluating Network Ready Devices for IoT, the AT&T network behaviour test) and ADAPT (the accelerated validation track for new LTE chipsets, upstream of modules).

The underlying idea is constant: AT&T, US tier-1 carrier, only admits to its certified device list products that have completed its process, with compliant IMEI management (Dedicated IMEI Type Allocation Code, DTAC, or periodic IMEI uploads). Without that, the product is not recognised as certified for commercial operation on the AT&T network.

Network Ready vs PTCRB and INC, the right separation

PTCRB and Network Ready are often conflated. They happen in the same project phase, but their scope is distinct. Between the two sits IoT Network Certified (INC), the IoT certification administered by CTIA Certification and derived from the PTCRB programme: AT&T states explicitly that getting Network Ready starts with obtaining IoT Network Certified.

Criterion	PTCRB / INC	AT&T Network Ready
Nature	Cross-carrier programmes administered by CTIA Certification	AT&T-specific programme
Reference	PTCRB test plans based on 3GPP TS 36.521 and TS 38.521, INC requirements	AT&T onboarding plus TRENDI test (network behaviour, SMS, firmware identical to INC)
Scope	Generic cross-carrier radio conformance	Effective operation on the AT&T network, required AT&T bands, IMEI management
Granted by	CTIA Certification (PTCRB authorised labs)	AT&T via its IoT portal
Identifier	PTCRB / INC certification	Listing on the AT&T certified device list, DTAC or IMEI uploads
Required for AT&T activation	Yes	Yes, in addition to PTCRB / INC

PTCRB / INC is a prerequisite, not sufficient. Without INC certification, AT&T does not accept Network Ready entry. See PTCRB scope for the full list of carriers and covered bands.

Simple reading: PTCRB / INC certifies that the radio respects 3GPP, Network Ready certifies that the product works specifically on the AT&T network, in its required bands, with its IMEI management and its eSIM scheme.

The AT&T IoT portal, entry point

The AT&T IoT portal (iotdevices.att.com) is the reference route. It provides access to the AT&T approved module catalogue (including the ADAPT chipset tab), the certified device list, the TRENDI test instructions, the recommended labs and resources, and the Get Network Ready programme documentation. The onboarding submission itself goes through the projectone.att.com portal, once the PTCRB request number has been obtained.

AT&T does not publish a complete fee schedule; costs are built with the lab (AT&T has negotiated tiered pricing with partner labs through its IoT Accelerator programme) and depend heavily on the module status. For a European manufacturer submitting for the first time, plan for an additional administrative phase before the first test.

Two-tier structure, module and device

Network Ready follows the same logic as PTCRB and as the other North American carrier programmes: approval at module level and approval at end product level.

Tier 1, module approval

Applies to cellular module makers (Quectel, u-blox, Telit, Sierra Wireless, Murata, Sequans, Fibocom). The candidate module is evaluated for radio conformance on the required AT&T bands, attach behaviour on AT&T, eSIM / eUICC support, VoLTE where applicable, and LTE-M power management (PSM, eDRX). Once approved, the module is added to the AT&T approved module catalogue. Recent chipsets can go through the ADAPT track to speed up the validation of the modules that integrate them.

Tier 2, device approval

Applies to the final product integrating a cellular module. Even when the module is already in the AT&T catalogue, the device process remains mandatory, but it is lighter: INC testing in a PTCRB authorised lab (the final product must notably pass the radiated TRP / TIS tests, the RSE radiated spurious emission tests and the SIM electrical tests), AT&T onboarding via projectone.att.com, then the TRENDI test and IMEI compliance. The scope covers integration, not the raw radio behaviour: product antennas, power supply, firmware, end-to-end network behaviour.

See PTCRB procedure for project timeline and PTCRB tests for the cross-carrier radio foundation.

The benefit of an already-approved AT&T module

Selecting from the start a module already in the AT&T catalogue is the most effective optimisation of a Network Ready programme. Module approval is already done, the RF front-end is validated on the required AT&T bands, the cellular stack is known to AT&T, and the device process reduces to the three standard steps (INC, onboarding, post-testing).

Without a pre-approved module, or with a custom chipset, AT&T imposes a significantly more rigorous process: on top of the typical 8 to 12 weeks of PTCRB testing, add 4 to 6 weeks of AT&T lab and field testing, with additional fees. A decision to make at module selection time, not afterwards.

AT&T bands, what is required

AT&T publishes a minimum set of required bands for US domestic operation under Network Ready: B2, B4 and B12 in LTE, and n2, n5, n66 and n77 in 5G NR. The table below summarises the main AT&T bands, the exact requirements being verified on the IoT portal at each submission.

Family	Typical AT&T bands	Primary usage
LTE low-band	B5 (850 MHz), B12 (700 MHz)	Rural coverage, indoor penetration
LTE PCS / AWS	B2 (1900 MHz), B4 (1700/2100 MHz)	Urban LTE capacity, legacy
LTE WCS	B30 (2300 MHz)	Additional AT&T capacity
LTE FirstNet	B14 (700 MHz)	Dedicated FirstNet band, see dedicated section
LTE AWS-3	B66 (1700/2100 MHz)	Major modern AT&T LTE band
5G NR PCS	n2 (1900 MHz)	NR on the PCS spectrum
5G NR low	n5 (850 MHz)	NR refarming on 850 MHz
5G NR mid	n66 (AWS-3)	NR on AWS-3, the 5G counterpart of B66
5G NR C-band	n77 (3.7-3.98 GHz)	AT&T mid-band 5G capacity

mmWave NR bands remain a corner case: mass-market IoT products on these bands are rare. PTCRB / INC radio testing is performed on emulators (Anritsu MT8000A, Keysight UXM 5G, R&S CMX500) in an authorised lab. See FCC tests for the regulatory counterpart, which shares the spurious emission measurements but does not cover network behaviour.

Network Ready test content

The requirements published by AT&T for Get Network Ready fall into families.

Radio and SIM (via PTCRB / INC). Three test families are mandatory on the final product: TRP / TIS (radiated RF performance and sensitivity), RSE (radiated spurious emissions) and SIM electrical tests. They are performed in a PTCRB authorised lab.

TRENDI, the AT&T network test. TRENDI verifies that the product performs effectively on the AT&T network, that it can receive SMS, and that it runs the same firmware as the one certified under INC. The test runs with dedicated TRENDI SIMs and completes in roughly 24 hours.

AT&T lab and field testing. For products with a non-approved module or a custom chipset, AT&T adds a lab and field campaign (typically 4 to 6 weeks) that evaluates end-to-end network behaviour under real AT&T conditions.

Beyond these formal requirements, application behaviour remains the manufacturer's responsibility: long-session stability, automatic re-attach after signal loss, dual-stack IPv4 / IPv6 behaviour (AT&T deploys IPv6 broadly on LTE and NR). These points, not covered by PTCRB, should be validated before submission to avoid setbacks in operation.

eUICC and RSP, the structural topic

Following the progressive adoption of GSMA SGP.32, IoT eSIM has become a central axis of cellular IoT projects targeting US tier-1 carriers. Three architecture generations coexist: SGP.02 (legacy M2M, push-mode, being retired), GSMA SGP.22 (Consumer RSP, pull-mode, for smartphones, watches, tablets) and GSMA SGP.32 (IoT RSP, introduces the eSIM IoT Manager role and redefines the LPA for objects without UI).

Product-side, the typical expectations of a tier-1 carrier include a GSMA SAS-UP-certified eUICC present on the GSMA list, a compliant LPA or IPA able to dialogue with the carrier's SM-DP+, correct handling of enable / disable / delete without hardware reset, clean rollback if the network fails during profile download, and correct interpretation of profile metadata.

Common pitfalls: uncertified eUICC, non-compliant proprietary LPA, outdated TLS on the LPA side, SGP.22 / SGP.32 confusion, profile metadata misinterpretation. Failures not detected by PTCRB, which does not test the eUICC + LPA + SM-DP+ triad against a real carrier.

FirstNet, a separate programme

FirstNet (First Responder Network) is the US public safety communications network. It runs on AT&T infrastructure but has its own certification framework and its own approved-device list, conducted through AT&T under the supervision of the federal FirstNet Authority.

Criterion	AT&T Network Ready (commercial)	FirstNet
Target network	Commercial AT&T Mobility	FirstNet, priority on band B14
Audience	Commercial IoT, telematics, B2B	Public-safety services (fire, police, emergency medical)
Authority	AT&T Mobility	AT&T under FirstNet Authority supervision
Key band	B2, B4, B12, n2, n5, n66, n77	B14 (700 MHz), with priority access and preemption
Additional requirements	None beyond Network Ready	Hardened security, priority and preemption, dedicated requirements
Does AT&T certification imply FirstNet?	No	-

A product targeting public-safety users must therefore run a FirstNet programme in addition to the commercial process. The logistics are similar (submission, labs, dedicated listing) but the application and security requirements are stricter. Conversely, a commercial IoT product has no reason to enter FirstNet.

2G, 3G and NB-IoT sunset, practical implications

AT&T shut down its 2G network in 2017 and its 3G network in February 2022. In late 2024, AT&T additionally announced the end of NB-IoT: sales and certifications stopped, network decommissioning under way in 2025, customer migration to LTE-M. AT&T now certifies only 5G NR, LTE and LTE-M products.

For any new project, no product relying on 2G, 3G or NB-IoT fallback has operational value on US AT&T, legacy modules (UMTS-only, GSM-only) are no longer approvable, and the LTE Cat-1 / LTE-M stack must work without a circuit-switched voice fallback. For a European manufacturer still maintaining 2G/3G or NB-IoT designs for non-US markets, this imposes variant management specific to the US market, a decision to take at product architecture stage rather than when submitting to AT&T.

Process, from PTCRB to AT&T activation

Recommended order for a cellular IoT product targeting the AT&T network:

Module selection: pick a module already in the AT&T catalogue, settle the SGP.22 / SGP.32 question, choose a certified LPA / IPA.
Hardware stabilisation: identify the PTCRB / INC lab, prepare the AT&T dossier, frame the product category and target bands.
Pre-certification: RF pre-tests in an OTA chamber, LPA pre-validation against the SM-DP+ (test environment provided by the eUICC vendor), internal review of the application firmware.
PTCRB / INC: testing in a PTCRB authorised lab, IoT Network Certified certification obtained.
AT&T onboarding: submission via projectone.att.com with the PTCRB request number, AT&T review.
Post-testing and activation: TRENDI test (roughly 24 hours), IMEI compliance (DTAC or periodic uploads), listing on the AT&T certified device list, verification on a real AT&T SIM, commercial launch.
Lifecycle: monitor portal bulletins, declare significant changes (cellular stack, antennas, power management, LPA, module).

For sequencing with CE/RED, see EU + US dual certification and certification timeline. FCC remains independent, obtained via a TCB with no AT&T dialogue.

Cost and lead time, qualitative

AT&T does not publish a complete official fee schedule for Network Ready. Orders of magnitude depend on the module status (AT&T catalogue or not, the primary lever), the product category, the number of target bands, eUICC / LPA complexity, the number of iterations if the first campaign fails, and whether the FirstNet programme runs in parallel.

A few benchmarks published by AT&T: with an approved module, the process reduces to INC, onboarding and post-testing, and the TRENDI test completes in roughly 24 hours; without an approved module, expect 8 to 12 weeks of PTCRB testing plus 4 to 6 weeks of AT&T lab and field testing, with additional fees. The final quote depends on the exact scope retained at submission and is best built with the lab once the scope is framed. For overall logistics, see certification costs.

ADAPT, chipset pre-validation and lifecycle

The AT&T ADAPT track accelerates the validation of newly developed LTE chipsets; the list of covered chipsets appears in the module catalogue of the AT&T IoT portal. A product built on a chipset that has already gone through ADAPT, or on an already-approved module, benefits from prior work that reduces the device scope to the risk zones (antenna integration, application firmware, power management, product LPA).

On post-approval lifecycle, the firmware of the marketed product must remain the validated one (TRENDI explicitly verifies firmware consistency with the INC certification), and IMEI compliance (DTAC or periodic uploads) is a continuous obligation. Significant changes (cellular stack, radio, eSIM) must be declared and can require re-certification, the exact rule to be confirmed with AT&T case by case.

Common pitfalls

Assuming PTCRB is enough for AT&T. The structural mistake, identical to what is seen at Verizon (Verizon Open Development) and T-Mobile. A PTCRB-certified product without Network Ready is not recognised for commercial AT&T operation. The discovery often happens just before launch.

Ignoring INC. IoT Network Certified is the explicit entry point of the AT&T process. Planning PTCRB without INC, or the reverse, leads to an incomplete campaign.

Module selected without AT&T filter. Picking a module solely on PTCRB and cost criteria leads to paying for the full process (lab plus field) when the module is not in the AT&T catalogue. The filter must be applied at module selection time, in parallel with the Verizon and T-Mobile filters if the project targets several US carriers.

Firmware divergence between INC and production. TRENDI verifies that the product runs the same firmware as the one certified under INC. Shipping a firmware different from the tested one invalidates the logic of the process and exposes the product to refusal or later challenge.

IPv6 neglected. AT&T deploys IPv6 on LTE and NR. An IPv4-only product, or one whose IPv6 stack is not operational, is exposed to operational problems, even though this point is not explicit in PTCRB.

eUICC without a compliant LPA. A certified eUICC is not enough; the device-side LPA / IPA must be compliant. Many integrators re-implement a proprietary LPA that blocks carrier homologation. Fix: use the module LPA when it is integrated and certified, or a certified third-party LPA aligned with SGP.22 / SGP.32.

Confusing Network Ready and FirstNet. A commercial AT&T-certified terminal is not FirstNet-approved. A FirstNet-targeted terminal must run both programmes. Promising FirstNet without having run the dedicated programme is a commercial risk.

Ignoring the 2G/3G/NB-IoT sunsets. Designing with 2G, 3G or NB-IoT fallback for the US no longer makes sense on the AT&T network. Historical designs intended to be sold in the US as well must be migrated to LTE-M or LTE before any new submission.

Unconfirmed lab. INC testing goes through PTCRB authorised labs, but AT&T-specific testing goes through AT&T qualified labs. Confirm the status upfront, or risk double billing. See PTCRB pitfalls for the broader picture.

Underestimating portal admin time. For a European manufacturer submitting for the first time, portal account opening, administrative validation and submission review take several weeks before the first test.

Connection with other US certifications

The AT&T Network Ready scope is distinct from the other US requirements: FCC (intentional and unintentional radiator) remains independent, FCC ID obtained via a TCB with no AT&T dialogue; PTCRB tests and INC form the cross-carrier foundation that Network Ready extends for AT&T; Verizon Open Development is a separate Verizon-specific programme; T-Mobile certification is a third separate programme not covered here.

A cellular product sold on AT&T therefore stacks FCC ID (regulator), PTCRB / INC certification (industry), Network Ready status (AT&T-specific) and IMEI compliance in the AT&T system. Targeting the three US carriers means planning three separate carrier programmes in addition to PTCRB. For vocabulary (PVG, EPC, LPA, IPAd, SM-DP+, eUICC, eIM), see the spilma glossary.

Frequently asked questions

What is the AT&T Network Ready programme?: AT&T Network Ready (also called Get Network Ready) is the AT&T carrier homologation programme for cellular IoT terminals, managed through the iotdevices.att.com portal. It builds on the IoT Network Certified (INC) industry certification, administered by CTIA Certification and derived from the PTCRB programme, then adds AT&T onboarding and the TRENDI network test (Test Requirements for Evaluating Network Ready Devices for IoT). AT&T certifies only 5G NR, LTE and LTE-M technologies.
Why is PTCRB not enough to activate a product on the AT&T network?: PTCRB and IoT Network Certified cover the 3GPP radio conformance shared across North American carriers, a necessary but generic cross-carrier foundation. AT&T adds its Network Ready programme: manufacturer onboarding via its portal, the TRENDI test which verifies that the product performs effectively on the AT&T network, that it receives SMS and that it runs the same firmware as the INC-certified one, and IMEI compliance (DTAC or periodic uploads). Without Network Ready, the product does not enter the AT&T certified device list.
What is the difference between AT&T module approval and device approval?: Module approval applies to the cellular module (Quectel, u-blox, Telit, Sierra Wireless, Murata, Sequans, Fibocom). When the module is already in the AT&T approved module catalogue, the final product follows a lighter three-step process: INC testing in a PTCRB authorised lab, AT&T onboarding, then post-test compliance. With a non-approved module or a custom chipset, AT&T adds lab and field testing, significantly longer and more expensive.
Which AT&T bands are required for Network Ready?: AT&T publishes a minimum set of required bands for US domestic operation: B2, B4 and B12 in LTE, and n2, n5, n66 and n77 in 5G NR. The AT&T deployment covers other bands (notably B5, B14, B30, B66), B14 being reserved for FirstNet. The exact current requirements are published via the AT&T IoT portal and evolve with the operator's deployment roadmap, so they must be checked at each submission.
Does eUICC change the AT&T homologation procedure?: North American tier-1 carriers, AT&T included, rely on the GSMA SGP.22 (consumer RSP) and SGP.32 (IoT RSP) specifications. The device-side LPA or IPA must be able to dialogue with the carrier's SM-DP+: profile download, enable, disable, delete, error handling. An eUICC absent from the GSMA list or a non-compliant proprietary LPA is a common cause of blockage in carrier homologation, a point to clear at module selection time.
Is FirstNet covered by Network Ready?: No. FirstNet (the dedicated network for US public-safety services on band B14) is a separate certification programme, conducted through AT&T under the supervision of the federal FirstNet Authority, with its own security, priority and listing requirements. An AT&T-certified commercial terminal is not automatically FirstNet-approved, and vice versa. For a product targeting public-safety users, the FirstNet programme must be conducted in addition.
What is the impact of AT&T 2G, 3G and NB-IoT sunsets on new approvals?: AT&T shut down its 2G network in 2017 and its 3G network in February 2022. In late 2024, AT&T announced the end of NB-IoT, with network decommissioning under way in 2025 and customer migration to LTE-M. AT&T now certifies only 5G NR, LTE and LTE-M products. A module relying on 2G, 3G or NB-IoT fallback no longer makes sense on the US AT&T network.
Which labs can perform AT&T Network Ready testing?: INC testing can be performed in any PTCRB authorised lab. AT&T has additionally negotiated tiered pricing with partner labs through its IoT Accelerator programme. AT&T-specific testing (non-approved module, network and field tests) goes through AT&T qualified labs. The current status of any given lab must be confirmed via the AT&T IoT portal before booking a campaign.