AT&T Network Ready: cellular IoT certification after INC
After PTCRB, a cellular IoT product for the US market meets a second gate: carrier certification. AT&T calls its programme Get Network Ready. It starts with the IoT Network Certified (INC) industry certification, then adds a project record in the AT&T onboarding portal, the 24-hour TRENDI network test, AT&T radiated performance minimums per band, and a device identification method. This page follows the AT&T documents as published on iotdevices.att.com in October 2026: the three steps, the TRENDI timers, the TRP/TIS table, the module vs chipset split, eUICC approval, FirstNet, and the claims those documents contradict.
What AT&T actually requires, in one table
Section titled “What AT&T actually requires, in one table”AT&T describes Get Network Ready as the programme that gets an "eligible data-only or data-with-voice device ready for network operation" for devices deployed in North America. Devices deployed only outside North America go through a separate Global Compatibility route.
| Step | What AT&T asks | Source |
|---|---|---|
| 1. INC testing | Any authorised PTCRB lab. Three tests named: TRP/TIS, RSE (radiated spurious emissions), SIM electrical | Get Certified page |
| 2. AT&T onboarding | Project record in Project One (www.att.com/onboarding) using the PTCRB request number, then TRENDI on an AT&T TRENDI SIM, about 24 hours | Get Certified page, TRENDI instructions |
| 3. Post-testing acceptance | Device identification: dedicated TAC or periodic upload of all IMEIs (the TRENDI page also lists LwM2M) | Get Certified page, TRENDI instructions |
| Before listing | PTCRB certification paid and the device shown as "Approved" on the PTCRB site, AT&T TRP/TIS minimums met | TRENDI instructions |
| Extra for AT&T-branded devices | "Network Optimized" certification with additional testing, when the device is branded by AT&T or part of an AT&T solution with an AT&T business sponsor | Get Certified page |
Network Ready vs PTCRB and INC
Section titled “Network Ready vs PTCRB and INC”IoT Network Certified is the CTIA Certification programme "born out of the PTCRB device certification program". Its own site states that "getting AT&T Network Ready means first getting IoT Network Certified". PTCRB and INC certify conformance to industry requirements; Network Ready is the AT&T layer on top.
| Criterion | PTCRB / INC | AT&T Network Ready |
|---|---|---|
| Owner | CTIA Certification (INC), PTCRB | AT&T |
| Reference | PTCRB requirements, including 3GPP conformance tests such as 3GPP TS 36.521 and TS 38.521, and the CTIA OTA test plan | AT&T requirements document 13340 (cited by AT&T), TRENDI criteria, AT&T TRP/TIS minimums |
| Where tested | Authorised PTCRB lab | PTCRB lab for TRP/TIS, live AT&T network for TRENDI, AT&T Qualified Test (AQT) labs for unapproved modules and FirstNet |
| Output | PTCRB / INC certification | AT&T Technical Acceptance (TA) letter, called "Notice of Network Compatibility" on the AT&T IMEI page |
| Device identity | IMEI in the PTCRB record | Dedicated TAC, IMEI uploads or LwM2M, tied to the AT&T Device ID |
One AT&T wording point matters for planning. The Get Certified page says onboarding comes "once you have completed INC certification and received your PTCRB request number". The TRENDI instructions say to "initiate" INC certification, get the request number, and that the request must be "started" before TRENDI. In practice the PTCRB request number is what unlocks onboarding; confirm the expected state with your lab before fixing a schedule. See PTCRB scope and PTCRB procedure.
Approved module, unapproved module, chipset
Section titled “Approved module, unapproved module, chipset”AT&T sorts device projects by what the radio is built on. The AT&T IoT Devices home page grades each build option.
| Build option | AT&T certification route | Cost statement by AT&T |
|---|---|---|
| Certified ready-to-go device | Pick a device already on the AT&T certified device list | No new certification |
| Device with an embedded modem or an integrated approved module | Three steps: INC, onboarding and TRENDI, post-testing acceptance | INC testing paid to the lab; "AT&T Certification: No cost with an AT&T approved module" |
| Device with an unapproved module | AT&T Device Compliance Matrix, PTCRB testing ("can take 8-12 weeks"), AT&T lab and field testing in AT&T qualified labs ("can take 4-6 weeks") | "May be subject to additional certification fees" |
| Device built on a chipset | "Must be fully certified against the AT&T requirements, and are not treated like module integrations" | "Additional charge for AT&T testing and support" |
The approved module list is a downloadable spreadsheet. The version online in October 2026 (file last modified on 1 July 2026) has four data tabs: Approved Modules, Approved Module SW Versions, Verified Chipsets and Approved eUICC. It lists 666 module rows from 64 companies, with TA dates running from July 2011 to May 2026, 285 rows flagged FirstNet, and 202 verified chipsets. The module software version tab matters: TRENDI expects "an AT&T approved module with an approved software version".
TRENDI: the criteria AT&T checks
Section titled “TRENDI: the criteria AT&T checks”TRENDI (Test Requirements for Evaluating Network Ready Devices for IoT) runs on the live AT&T network with a SIM whose ICCID begins with 8901170. AT&T says the updated process, launched in early 2022, activates and deactivates the SIM automatically, so one SIM and one device are enough. The device must run the final production hardware and the exact software submitted for PTCRB, configured "EXACTLY as your end customer would use" it, and it must actually perform its data, SMS or voice functions during the 24 hours.
| Phase | Parameter | AT&T value |
|---|---|---|
| Activated | PDP context kept on inactivity | Up to 8 hours, then network-initiated PDN detach |
| Activated | TCP session kept at the AT&T firewall (NAT/PAT) | Up to 60 minutes |
| Activated | UDP session kept | Up to 2 minutes |
| Activated | Authentication requests | Fewer than 19 per hour, ideally fewer than 6 |
| Activated | Non-emergency keep-alive | Not more often than once every 60 seconds |
| Deactivated (HSS/HLR off) | Retry back-off in steady state | Not more often than once every 4 hours (AT&T example: 1, 5, 10, 15, 30 min, 1 h, 2 h, then 4 h repeatedly) |
| Deactivated | Authentication requests | Fewer than 19 per hour, ideally fewer than 6 |
| Test APN | LTE / 5G | m2m.com.attz / 213x.m2m.com.attz |
| Records | Tests per project record | No more than 15, one running at a time, no cancellation once submitted |
The practical lesson: TRENDI is a behaviour test of your firmware, not of the module. A product whose application reconnects in a tight loop after a rejection fails on the deactivated phase even with an approved module.
AT&T bands and TRP/TIS minimums
Section titled “AT&T bands and TRP/TIS minimums”The AT&T Radiated Performance Requirements version 2.1 (history entry dated 23 July 2025, aligned with AT&T requirements 13340 v25.2) set the band rules:
- All IoT LTE devices must support LTE Bands 2, 4 and 12; Bands 5, 14, 29 and 30 are "highly desired".
- If 5G is supported, n2, n5, n66 and n77 are required. FR2 is optional; if supported, n260 must be enabled.
- Every AT&T band enabled on the device needs a TRP/TIS report (B29 is TIS only, B30 may be TIS only if uplink is disabled). Band 2 results may be replaced by Band 25, Band 5 by Band 26.
- Extra module bands beyond 2, 4 and 12 may be disabled, but the certification records for PTCRB and AT&T must reflect the active bands.
- 5G devices must support 4x4 MIMO by default; single-antenna NR FR1 is not permissible.
- Testing follows the current CTIA Test Plan for Wireless Device Over-the-Air Performance.
| Device class | Band | Minimum TRP | Minimum TIS / C-TIS |
|---|---|---|---|
| LTE Cat 1 and above, free space | B2, B4, B66 | +20.0 dBm (PC3) | C-TIS -92.0 dBm/10 MHz |
| LTE Cat 1 and above, free space | B5 | +18.0 dBm | C-TIS -90.5 dBm/10 MHz |
| LTE Cat 1 and above, free space | B12 | +18.0 dBm | C-TIS -92.0 dBm/5 MHz |
| LTE Cat 1 and above, free space | B14 | +17.0 dBm | C-TIS -90.5 dBm/10 MHz |
| LTE-M, free space | B2 / B4 / B12 | +20.0 / +20.0 / +18.0 dBm (PC3), +17.0 / +17.0 / +15.0 dBm (PC5) | -96.0 / -98.0 / -93.0 dBm |
| LTE-M, small form factor (under 107 mm) | B2 / B4 / B12 | +12.0 / +12.0 / +10.0 dBm (PC3) | -88.0 / -90.0 / -85.0 dBm |
| 5G NR FR1, free space | n2, n66 | +20.0 dBm (PC3) | C-TIS -92.0 dBm/10 MHz |
| 5G NR FR1, free space | n5 | +18.0 dBm (PC3) | C-TIS -90.5 dBm/10 MHz |
| 5G NR FR1, free space | n77 | +17.0 dBm (PC3), +20.0 dBm (PC2), +23.0 dBm (PC1.5) | C-TIS -92.0 dBm/20 MHz |
| RedCap, free space | n2, n66 / n5, n14 | +20.0 / +18.0 dBm (PC3) | C-TIS -92.0 / -90.5 dBm/10 MHz |
Version 2.1 also removed the Band 17 requirements (Band 12 with MFBI is used instead). Earlier changes recorded in the same history: Band 48 added in March 2025, NB-IoT tables removed in July 2024, RedCap values added and n77 made required in June 2024. TRP/TIS applies to LTE-M devices with an embedded antenna or an external antenna cabled under 20 cm, "even if it is not yet mandatory for PTCRB". NR and LTE conformance tests themselves stay on the PTCRB side, see PTCRB tests.
Device identification after the tests
Section titled “Device identification after the tests”AT&T requires one identification method before the device is accepted:
- Dedicated TAC. The TAC (first eight digits of the IMEI) must be unique to your company and device, not a range shared with another company or with your module supplier. A family TAC across similar products is accepted. The TAC usually has to be given to the module maker at manufacture.
- IMEI upload. A CSV (or API) feed with manufacturer, model, host software version, the AT&T Device ID and the 15-digit IMEI, sent "at least every three months, beginning at the time AT&T TA is granted", including legacy data for all manufactured devices. The host software version is the device firmware, not the modem firmware.
- LwM2M, listed as a third option on the TRENDI page.
eUICC and eSIM
Section titled “eUICC and eSIM”AT&T lists the GSMA specifications GSMA SGP.22 and GSMA SGP.32 (and SGP.02) as the eSIM references, and sets three rules on its SIM page:
- An eUICC not already on the Approved eUICC tab must go through the AT&T SIM Approval Program (ASAP); AT&T says new certifications "can take approximately 8 weeks".
- Only integrated SIM products based on tamper resistant elements are certifiable; "Soft SIM and TEE-SIM solutions are not permitted".
- The eSIM or eUICC should hold a GSMA certificate; other third-party solutions are not permitted.
The Approved eUICC tab maps each eUICC part number to the AT&T profile SKU codes per network code (310-030 IoT Enterprise, 310-170 IoT, 313-100 FirstNet, 310-410 IoT) and per delivery method (QR card, activation code, pre-paired). Pick the profile with an AT&T solutions engineer first, then the eUICC.
FirstNet, an additional certification
Section titled “FirstNet, an additional certification”FirstNet is overseen by the First Responder Network Authority, an independent agency within NTIA, and built through a public-private partnership with AT&T. Device certification for FirstNet is run by AT&T, and AT&T is explicit that it "must be obtained in addition to carrier certification".
| Item | AT&T Network Ready | FirstNet (on top) |
|---|---|---|
| UICC | AT&T IoT profiles | 313-100 UICC on the FirstNet packet core |
| Bands | LTE 2, 4, 12 required | Band 14 plus commercial 2, 4 and 12 required (LTE-M devices must disable Band 14, per the TRP/TIS document) |
| Testing | INC, TRENDI | Plus lab testing at an authorised AQT lab, field testing at an authorised AQT field provider, security validation, mission critical applications (for example MC-PTT) |
| Letter | AT&T Technical Acceptance Letter | Plus a FirstNet Technical Acceptance Letter, the route AT&T names for listing on the FirstNet NIST site |
| Eligibility | Any eligible device | Finished, fully integrated devices only; socket, serial and USB modems need pre-approval; consumer smartphones and tablets are out of scope |
A FirstNet SIM is provided only to eligible first responders, and AT&T notes that certifying a device "does not necessarily mean that the users of your device will be eligible for FirstNet". AT&T also asks manufacturers to onboard and confirm test deliverables before contracting any outside lab.
NB-IoT is out
Section titled “NB-IoT is out”In November 2024 AT&T said it had "stopped the certification of new NB-IoT devices and the sale of data plans utilizing the NB-IoT network", was moving customers to LTE-M and aimed to finish decommissioning in the first quarter of 2025 (statement quoted by Light Reading). The AT&T TRP/TIS document had already dropped its NB-IoT tables in July 2024. The approved module spreadsheet still contains multi-mode modules flagged NB1 or NB2; that tells you the module was approved, not that the NB-IoT mode can be used on AT&T. For a European design that keeps NB-IoT for other markets, plan a US variant with LTE-M or LTE.
Claims the texts contradict
Section titled “Claims the texts contradict”| Common claim (some made by earlier versions of this page) | What the AT&T documents say |
|---|---|
| "ADAPT" is an AT&T accelerated track that speeds up modules built on new chipsets | No current AT&T page we fetched mentions ADAPT. The spreadsheet has a Verified Chipsets tab, and chipset-based devices "must be fully certified against the AT&T requirements, and are not treated like module integrations" |
| AT&T publishes no cost information | AT&T states "No cost with an AT&T approved module" for AT&T certification, and additional fees for unapproved modules and chipsets. INC lab fees remain |
| Band 14 is reserved for FirstNet | AT&T uses Band 14 on the FirstNet core along with its other bands; Band 14 is "highly desired" for all IoT LTE devices, and LTE-M devices must disable it even for FirstNet |
| Identification is DTAC or IMEI upload only | The TRENDI page also lists LwM2M; IMEI uploads are due at least every three months from TA, legacy data included |
| TRENDI checks that firmware matches INC | AT&T rejects results if hardware, software or module firmware deviates from what was or will be used for PTCRB; TRENDI itself checks attach, keep-alive and back-off timers |
| FirstNet device approval is run by the FirstNet Authority | The FirstNet Authority oversees the network; device certification, AQT testing and both acceptance letters come from AT&T |
| A commercial device needs nothing beyond Network Ready | AT&T-branded devices, or devices in an AT&T solution with an AT&T business sponsor, also need Network Optimized certification |
| PTCRB TRP/TIS is enough for AT&T | AT&T applies its own per-band minimums and requires LTE-M TRP/TIS even where PTCRB does not yet |
Common pitfalls
Section titled “Common pitfalls”Assuming PTCRB is enough for AT&T. The same mistake as at Verizon (Verizon Open Development) and T-Mobile: a PTCRB-certified product still needs onboarding, TRENDI and an identification method.
Module on the list, software version not. The approved module spreadsheet has a separate software version tab; a module firmware outside it breaks the "approved module" route.
Aggressive reconnect logic. TRENDI caps authentication requests at fewer than 19 per hour and steady-state retries at once every 4 hours after a network reject. Retry loops written for bench testing fail here.
Firmware drift. Hardware or firmware different from the PTCRB submission voids TRENDI results.
Shared TAC. A TAC range shared with the module supplier is not accepted for the dedicated TAC method.
Unapproved eUICC. ASAP adds about 8 weeks according to AT&T; soft SIM and TEE-SIM are refused. See PTCRB pitfalls for the industry side.
Promising FirstNet. FirstNet is a second certification with its own labs, security validation and letter.
Connection with other US certifications
Section titled “Connection with other US certifications”FCC authorisation stays independent of AT&T: the FCC ID comes from a TCB, and FCC tests share spurious emission measurements but say nothing about network behaviour. PTCRB tests and INC form the cross-carrier base; Verizon Open Development and T-Mobile certification are separate carrier programmes. A cellular product sold on AT&T therefore stacks FCC ID, PTCRB / INC, the AT&T TA letter and an identification method. Data-with-voice devices (VoLTE) fall under the same programme. For sequencing with CE/RED, see EU + US dual certification, certification timeline and certification costs. For eSIM vocabulary, see the spilma glossary.
See also
Section titled “See also”- Telstra, Optus, TPG: cellular IoT acceptance in Australia
- HAC: Hearing Aid Compatibility (FCC 20.19, C63.19)
- Verizon Open Development: carrier homologation after PTCRB
- T-Mobile US: cellular IoT device certification and DICE
- Orange Connected Validation: IoT device labels
- Vodafone Global IoT: device acceptance and eSIM
- PTCRB vs GCF
Sources & references
- AT&T, Get Certified (Get Network Ready programme), AT&T iotdevices.att.com/wp/get-certified.aspx
- AT&T, TRENDI test instructions and criteria, AT&T iotdevices.att.com/wp/trendi-test-instructions.aspx
- AT&T, IoT Radiated Performance Requirements version 2.1 (TRP/TIS), AT&T iotdevices.att.com/Uploaded_Docs/radiated_performance_requirements_2_1_20251023050310567.pdf
- AT&T, Approved Module, Verified Chipset and eUICC spreadsheet, AT&T www.business.att.com/content/dam/attbusiness/collateral/ATT_Approved_Modules.xlsx
- AT&T, IoT Devices home (build options and certification cost), AT&T iotdevices.att.com/
- AT&T, Identification through IMEI upload, AT&T iotdevices.att.com/wp/id-through-imei.aspx
- AT&T, Using a Type Allocation Code (TAC) to identify your device, AT&T iotdevices.att.com/wp/using-type-allocation-code-tac-to-identify-your-device.aspx
- AT&T, SIM and eSIM (ASAP eUICC approval), AT&T iotdevices.att.com/wp/sim.aspx
- AT&T, FirstNet device certification, AT&T iotdevices.att.com/wp/firstnet-device-certification.aspx
- IoT Network Certified program, CTIA Certification iotnetworkcertified.com/
- PTCRB Certification Program, PTCRB www.ptcrb.com/
- FirstNet Authority, About, FirstNet Authority www.firstnet.gov/about
- AT&T to discontinue NB-IoT (secondary, quotes the AT&T statement), Light Reading www.lightreading.com/iot/at-t-to-discontinue-nb-iot-but-t-mobile-and-verizon-keep-the-faith
- GSMA eSIM specifications (SGP.02, SGP.22, SGP.32), GSMA www.gsma.com/solutions-and-impact/technologies/esim/esim-specification/
Frequently asked questions
- What is the AT&T Network Ready programme?
- Get Network Ready is the AT&T certification programme for data-only or data-with-voice devices deployed in North America, described on iotdevices.att.com. For a device built on an AT&T approved module it has three steps: IoT Network Certified (INC) testing in any authorised PTCRB lab, AT&T onboarding with a 24-hour TRENDI network test, then post-testing acceptance (device identification by dedicated TAC or IMEI upload). INC is the CTIA Certification programme that grew out of PTCRB.
- Why is PTCRB not enough to activate a product on the AT&T network?
- PTCRB and INC certify conformance to industry requirements shared by carriers. AT&T adds its own steps: a project record in its onboarding portal (Project One), the TRENDI test that checks attach, keep-alive and back-off behaviour on the live AT&T network, the AT&T TRP/TIS minimums per band, and a device identification method. AT&T also rejects TRENDI results when hardware, software or module firmware differs from what is submitted for PTCRB.
- What is the difference between using an approved module and building on a chipset?
- With a module from the AT&T approved module list, AT&T certification follows the three-step process and AT&T states it is at no cost. With an unapproved module, AT&T requires its Device Compliance Matrix, PTCRB testing (8 to 12 weeks according to AT&T) and lab and field testing in AT&T qualified labs (4 to 6 weeks), with possible extra fees. A device built directly on a chipset must be fully certified against AT&T requirements and is not treated like a module integration.
- Which bands does AT&T require?
- AT&T Radiated Performance Requirements version 2.1 (July 2025) require LTE Bands 2, 4 and 12 for all IoT LTE devices, with 5, 14, 29 and 30 highly desired. If 5G is supported, n2, n5, n66 and n77 are required, and if FR2 is supported n260 must be enabled. Every AT&T band enabled on the device needs a TRP/TIS report against the AT&T minimums.
- Does eUICC change the AT&T certification procedure?
- AT&T permits only GSMA-certified eSIM and eUICC solutions built on tamper resistant elements; soft SIM and TEE-SIM are not permitted. An eUICC not already on the Approved eUICC tab of the AT&T module spreadsheet must go through the AT&T SIM Approval Program (ASAP), which AT&T says takes approximately 8 weeks for a new certification.
- Is FirstNet covered by Network Ready?
- No. AT&T states that FirstNet certification must be obtained in addition to carrier certification. It adds lab testing at an authorised AT&T Qualified Test (AQT) lab, field testing, a security validation for most devices, mission critical application testing where relevant, and a separate FirstNet Technical Acceptance Letter. FirstNet devices must support Band 14 plus AT&T commercial bands 2, 4 and 12.
- Does AT&T still certify NB-IoT devices?
- No. In November 2024 AT&T said it had stopped certifying new NB-IoT devices and selling NB-IoT data plans, and was moving customers to LTE-M, with decommissioning targeted for the first quarter of 2025. Its radiated performance requirements dropped the NB-IoT tables in version 1.92 (July 2024).
- Which labs can perform AT&T Network Ready testing?
- Any authorised PTCRB lab can perform INC testing, and AT&T lists PTCRB labs with tiered test pricing under its IoT Accelerator programme. Lab and field testing for unapproved modules, and FirstNet lab testing, go through AT&T Qualified Test (AQT) labs. AT&T advises onboarding and confirming deliverables before contracting third-party labs for FirstNet.