PTCRB test plans: NAPRD03 V6.26 specs, OTA and IoT rules
PTCRB has no single test plan. What a device must pass is set by NAPRD03, the technical requirements document that PTCRB shares with IoT Network Certified, and by the PTCRB test case database that NAPRD03 points to. Version 6.26 (October 2026) lists the reference specifications in Section 2.3: 3GPP conformance specifications for RF, protocol, RRM and EMC, the CTIA Certification over-the-air test plans, GSMA documents for SIM provisioning and connection efficiency, and a few OMA and ETSI specifications. This page maps those references by area, gives the rules NAPRD03 adds on top (OTA for IoT, test case categories, which bands to test), and quotes the LTE limits from the 3GPP text itself. Everything below is as of October 7, 2026.
How the requirements are organised
Section titled “How the requirements are organised”| Document | Version on October 7, 2026 | What it decides |
|---|---|---|
| NAPRD03 | V6.26, October 2026 | Reference test specifications (Section 2.3), test case categories (2.7.6), bands (2.8), OTA rules (2.9), UE capability audit (2.12), speech, cybersecurity, converged Wi-Fi and utility IoT (Section 4) |
| PTCRB test case database | Updated with each NAPRD03 release | "The primary reference for the actual test cases and applicable categories" (NAPRD03 2.2), with the validated test platforms for each test case |
| PPMD | V4.2, October 2026 | Process: which NAPRD03 version applies, how new tests enter, how results are reported |
| PVG.11 | V5.24.0 | PTCRB bands and supporting operators; prevails over NAPRD03 in case of conflict (NAPRD03 2.8) |
Two release rules from the PPMD matter for planning. NAPRD03 is released four times a year, and a device must complete all applicable tests published in one of the two most recent versions on the date it completes certification (PPMD 5.2). New tests recommended by the PVG enter as Category E for at least 90 days; to move to Category A a test must be approved by the PTCRB Working Group, validated and commercially available for at least 30 days, and available in at least one PTCRB Full Test Laboratory (PPMD 5.5.3).
Reference specifications in NAPRD03 V6.26
Section titled “Reference specifications in NAPRD03 V6.26”NAPRD03 cites specifications by number without a part or release. The part numbers in the third column are the 3GPP parts that cover each area.
| Area (NAPRD03 section) | Specification cited | What it covers |
|---|---|---|
| UTRA (2.3.2) | 3GPP TS 34.121, TS 34.123 | 3G RF conformance and protocol conformance |
| E-UTRA (2.3.3) | 3GPP TS 36.521, TS 36.523, TS 36.124 | LTE, LTE-M and NB-IoT RF conformance (36.521-1) and RRM (36.521-3), protocol (36.523-1), EMC (36.124) |
| NR (2.3.4) | 3GPP TS 38.521, TS 38.523, TS 38.533, TS 38.124 | 5G RF conformance (38.521-1 FR1, 38.521-2 FR2, 38.521-3 interworking such as EN-DC, 38.521-4 performance), protocol (38.523-1), RRM (38.533), EMC (38.124) |
| USIM and USAT (2.3.3, 2.3.4) | 3GPP TS 31.121, TS 31.124 | UICC and terminal interface, application toolkit |
| Network independent (2.3.27) | ETSI TS 102 230-1, 3GPP TS 31.121, TS 31.124 | UICC test cases run without a radio bearer |
| Data throughput (2.3.5) | 3GPP TR 37.901 | Application layer data throughput; PVG.09 is the verification guideline |
| Positioning (2.3.7, 2.3.12, 2.3.16) | 3GPP TS 37.571; OMA SUPL 1.0 and 2.0 test specifications; CTIA OTA test plan for A-GNSS radiated performance | Location conformance and A-GNSS radiated tests |
| IMS (2.3.13) | 3GPP TS 34.229 | IMS signalling conformance (the basis of VoLTE testing) |
| Device RF performance (2.3.9) | CTIA Certification Test Plan for Wireless Device Over-the-Air Performance; CTIA 2x2 Downlink MIMO and Transmit Diversity OTA test plan, both "Active Version" | TRP, TIS, MIMO OTA |
| Wi-Fi RF performance (2.3.10) | CTIA Certification and Wi-Fi Alliance Test Plan for RF Performance Evaluation of Wi-Fi Mobile Converged Devices | Cellular and Wi-Fi converged devices |
| Speech (2.3.24, 4.1) | CTIA Certification Speech Performance Test Plan V2.5.x | Speech performance, replacing 3GPP TS 26.132 |
| NFC (2.3.6, 2.18) | ETSI TS 102 694 (SWP), ETSI TS 102 695 (HCI), GSMA TS.27 | Embedded secure element |
| Connection efficiency (2.3.19, 2.16) | GSMA TS.35 | IoT devices of 3GPP Releases 8 to 12 |
| Remote SIM provisioning (2.3.20) | GSMA SGP.02, SGP.22, SGP.23, SGP.23-2, SGP.32, SGP.33-2 | eUICC for M2M, consumer and IoT |
| Cybersecurity (2.3.8, 4.2) | CTIA Cybersecurity Certification Test Plan for IoT Devices | Optional, IoT devices only |
| Utility IoT (2.3.22, 4.4) | CTIA Certification Utility IoT Device Test Plan | Optional, for IoT Network Certified for Smart Connected Infrastructure |
| NTN (2.3.25) | TS 36.521, 36.523, 36.124 (NB-IoT NTN); TS 38.521, 38.523, 38.533, 38.124 (NR NTN); TS 31.121, 31.124 | Satellite devices |
| RedCap (2.3.26) | TS 38.521, 38.523, 38.533, 38.124, 31.121, 31.124 | Reduced capability NR |
| Mission critical services (2.3.28) | 3GPP TS 37.579 | Added in V6.26 |
Section 2.3 also lists what is gone, marked "Deleted": all GERAN (GSM) specifications, UTRA USIM and audio references, MMS, OMA DM, TTY, AT-Commands and OMA FUMO.
LTE RF conformance: the limits in the 3GPP text
Section titled “LTE RF conformance: the limits in the 3GPP text”3GPP TS 36.521 Part 1 is the test specification; the limits it checks are the minimum requirements of the core specification, TS 36.101. The values below come from ETSI TS 136 101 V19.6.0 (August 2026, Release 19); the 36.521-1 test cases carry the same clause numbers and add test tolerances to these limits.
Transmitter (clause 6)
Section titled “Transmitter (clause 6)”| Test (clause) | Minimum requirement in TS 36.101 |
|---|---|
| UE maximum output power (6.2.2) | 23 dBm, tolerance ±2 dB, for power class 3 in most bands (Table 6.2.2-1); some bands also define power class 1 or 2 |
| Transmit OFF power (6.3.3) | -50 dBm, for every channel bandwidth |
| Frequency error (6.5.1) | ±0.1 ppm over one time slot (0.5 ms), relative to the carrier received from the eNode B |
| Error Vector Magnitude, EVM (6.5.2.1) | 17.5 % for QPSK or BPSK, 12.5 % for 16QAM, 8 % for 64QAM |
| E-UTRA ACLR (6.6.2.3) | 30 dB for every channel bandwidth (applies when the adjacent channel power is above -50 dBm) |
| Spurious emissions (6.6.3.1) | -36 dBm from 9 kHz to 1 GHz; -30 dBm (1 MHz) from 1 GHz to 12.75 GHz |
Receiver (clause 7)
Section titled “Receiver (clause 7)”| Test (clause) | Minimum requirement in TS 36.101 |
|---|---|
| Reference sensitivity (7.3) | Per band and channel bandwidth; see the next table. Pass criterion: throughput at least 95 % of the maximum |
| Maximum input level (7.4) | -25 dBm with the 64QAM reference channel; -27 dBm with 256QAM and 1024QAM |
| Adjacent channel selectivity (7.5) | 33 dB up to 10 MHz, 30 dB at 15 MHz, 27 dB at 20 MHz |
| In-band blocking (7.6.1) | Interferer at -56 dBm (case 1) and -44 dBm (case 2) |
| Spurious response (7.7) | CW interferer at -44 dBm |
| Wide band intermodulation (7.8.1) | Two interferers at -46 dBm each |
Reference sensitivity in PTCRB LTE bands (QPSK, two antenna ports)
Section titled “Reference sensitivity in PTCRB LTE bands (QPSK, two antenna ports)”| Band | 5 MHz | 10 MHz |
|---|---|---|
| 2 | -98 dBm | -95 dBm |
| 4 | -100 dBm | -97 dBm |
| 5 | -98 dBm | -95 dBm |
| 7 | -98 dBm | -95 dBm |
| 12 | -97 dBm | -94 dBm |
| 13 | -97 dBm | -94 dBm |
| 14 | -97 dBm | -94 dBm |
| 25 | -96.5 dBm | -93.5 dBm |
| 26 | -97.5 dBm | -94.5 dBm |
| 30 | -99 dBm | -96 dBm |
| 42 | -99 dBm | -96 dBm |
| 48 | -99 dBm | -96 dBm |
| 66 | -99.5 dBm | -96.5 dBm |
| 71 | -97.2 dBm | -94.2 dBm |
| 85 | -97 dBm | -94 dBm |
Source: TS 36.101 V19.6.0, Table 7.3.1-1. Band 26 is 0.5 dB lower when the channel is within 865-894 MHz (note 6). Band 106 is only defined at 1.4 MHz (-102.2 dBm) and 3 MHz (-99.2 dBm). A UE with four antenna ports gets a correction (for example -2.7 dB in Bands 2, 4, 25, 30 and 66, Table 7.3.1-1a). LTE-M and NB-IoT have their own sensitivity tables in the same clause.
NR and RRM
Section titled “NR and RRM”For 5G NR, 3GPP TS 38.521 is split by frequency range. For FR2 (n260 and n261 in PTCRB, tested as NSA EN-DC configurations), 3GPP specifies the UE requirements as radiated quantities only: EIRP for the transmitter and EIS (effective isotropic sensitivity) for the receiver (TS 38.101-2). An FR2 module cannot complete RF and RRM testing at module level; it is done in the end product certification (PPMD, as summarised on the scope page).
RRM conformance is in TS 36.521-3 for LTE and TS 38.533 for NR: idle mode cell selection and reselection, connected mode mobility and handover, timing and measurement performance.
OTA: the CTIA test plan and the NAPRD03 rules
Section titled “OTA: the CTIA test plan and the NAPRD03 rules”NAPRD03 2.9 makes RF performance evaluation mandatory for all device types going through PTCRB or IoT Network Certified. The test plan is the version of the CTIA Certification Test Plan for Wireless Device Over-the-Air Performance in effect when the certification request is submitted. Since Version 4.0 (published February 14, 2022) that plan is split into 17 topic documents, and NAPRD03 cites them by number: 01.01 (scope, proximity power reduction), 01.02 (operator priority list), 01.20 (anechoic chamber, including cellular and Wi-Fi coexistence in Section 4.9), 01.50 (radio technologies and overlapping band rules) and 01.51 (A-GNSS).
PTCRB does not use the 3GPP OTA specifications for this. Those exist separately: TS 37.544 for UTRA and E-UTRA OTA conformance, and TS 38.161 (requirements) with TS 38.561 (test methodologies) for NR FR1, where 3GPP calls the receive metric TRS.
Non-IoT devices (NAPRD03 2.9.1)
Section titled “Non-IoT devices (NAPRD03 2.9.1)”- Tested for OTA performance per the CTIA plan, including GNSS or A-GNSS if supported.
- Carrier aggregation: all relevant combinations on the target operators' priority list, no others unless an operator asks.
- Notebooks and tablets that can run cellular and 802.11 at the same time: cellular desensitization testing (CTIA 01.20, Section 4.9).
- Devices with a proximity sensor that reduces power: TRP per CTIA 01.01, Section 2.1.3, and documentation of the power reduction per band (NAPRD03 2.9.8).
Any TRP and TIS pass levels come from the CTIA plan; NAPRD03 does not restate them and the manufacturer must ask the target operators whether they have unique OTA requirements.
IoT devices (NAPRD03 2.9.2)
Section titled “IoT devices (NAPRD03 2.9.2)”The manufacturer answers three questions (Table 2.9.2-1):
| # | Question |
|---|---|
| 1 | In its intended application, does the device transmit more than 100 Kbytes in a transaction? |
| 2 | On average, does it send more than 24 transactions per day? |
| 3 | Are the device and its antenna installed in a fixed orientation relative to the horizon? |
| Answers | OTA test scope |
|---|---|
| Any answer | OTA only in the highest-order RAT supported, in each supported band of that RAT, plus any lower-order RAT band not covered by it |
| 1, 2 and 3 all "No" | TRP on all bands and channels; TIS on the mid channel only above 1 GHz, on low, mid and high channels below 1 GHz; anechoic or reverberation chamber |
| 1 and 2 "No", 3 "Yes" | Near-horizon metrics instead of TRP and TIS: NHPRP ±30° on all bands and channels, NHPIS ±30° on the mid channel; anechoic chamber, or reverberation chamber (reporting TRP and TIS) if the device is too large |
| 1 or 2 "Yes" | Applicability as determined by the CTIA OTA test plan |
Other OTA rules
Section titled “Other OTA rules”| Rule | NAPRD03 |
|---|---|
| Engineering change (ECO): OTA needed if hardware, calibration or maximum radiated power changes; not needed if none of these change and conducted power moved by no more than ±1 dB in every band | 2.9.3 |
| Receive diversity per the CTIA plan; MIMO per the CTIA 2x2 MIMO plan | 2.9.4 |
| LTE Category 1 and higher must support two antennas (3GPP TS 36.306), except Category 1bis (exception added in V6.26); otherwise a waiver is needed | 2.9.4 |
| Overlapping bands are not tested twice (CTIA 01.50 and 01.51 tables) | 2.9.5 |
| Radiated spurious emissions per PVG.04 | 2.9.7 |
Test case categories
Section titled “Test case categories”Each test case in the PTCRB database has a category (NAPRD03 Table 2.7.6-1):
| Category | Meaning | Effect on certification |
|---|---|---|
| A | Fully validated, available in the labs | Must be passed |
| B | Available with exceptions (part of the means of test not valid) | Must be passed, with exception to certain cases |
| C | Reserved | |
| D | Downgraded, no valid means of test | Not executed; moves to Category S after 45 days unless re-validated |
| E | Validated, under evaluation (new tests, features not supported by all operators such as MTSI voice via 5GS or EN-DC including FR2) | Must be executed and reported; a failure does not prevent certification |
| N | Not applicable in any NAPRD03 version | Not executed |
| P | New test case, never validated | Not executed |
| S | Was validated, downgraded to D and not re-validated within 45 days | Not executed |
Failures are handled under PVG.12. Test platforms carry their own status in the database: V (validated), E (exception, partly fulfilling the validation criteria) or D (downgraded, not recommended for certification) (NAPRD03 2.7.5). The lab reports the platform number used for each test case (PPMD 11.4.3.7.1). NAPRD03 does not name any test equipment vendor or model.
Which bands a test case runs in
Section titled “Which bands a test case runs in”NAPRD03 2.7.10 gives each band-dependent test case a "bearer to be tested" rule:
| Rule | What it means |
|---|---|
| All | Every PTCRB band of the RAT under test (bands from Section 2.8 and PVG.11) |
| Single | One PTCRB band, no priority |
| FR Single | One NR FR1 band and one NR FR2 band |
NR Single prio, EN-BI | One EN-DC configuration, in priority order: DC_5A_n66A, then DC_66A_n78A, then DC_12A_n66A, then any supported configuration |
NR Single prio, NR-BI | One NR SA band, in priority order: n66, then n71, then n2 |
| RAT All | Once per supported RAT, in PTCRB bands |
| I-RAT Single | Inter-RAT test case in a single band combination |
| TS Rule | Execution rules of the test specification itself |
Bands listed by both PTCRB and GCF are PTCRB bands. For GCF-only bands, GCF certification results are accepted if the test organisation is at least an active observing member of the PVG, and the PTCRB Primary Test Laboratory confirms what can be leveraged (NAPRD03 2.7.11). The device is tested with all bands enabled and may not be reconfigured for testing (2.11). The bands themselves are on the scope page.
Other NAPRD03 requirements
Section titled “Other NAPRD03 requirements”| Requirement | Applies to | NAPRD03 |
|---|---|---|
| UE capability audit (for example TS 36.523-1 test case 8.5.4.1 for an E-UTRA only device, TS 38.523-1 test case 8.1.5.1.1 for an NR or RedCap only device) | Initial certifications and parent devices; variants and ECOs that change UTRA, E-UTRA or NR functionality; also IoT devices on a certified module | 2.12 |
| Connection efficiency, GSMA TS.35 | IoT devices of 3GPP Releases 8 to 12, in the highest RAT supported; eUICC devices exempt for now | 2.16 |
| Network independent UICC test cases (RFT029, 058, 085) | Devices supporting at least one LTE-M or NB-IoT band | 2.24 |
| Embedded secure element, GSMA NFC test book | Devices with eSE | 2.18 |
| Speech performance, CTIA test plan in effect at submission | Devices with voice | 4.1 |
| Converged device testing, CTIA and Wi-Fi Alliance plan | Devices with consumer Wi-Fi (phones, access points), not Wi-Fi used for telemetry or control; notebooks, tablets and IoT devices follow 2.9 | 4.3 |
| IoT cybersecurity | Optional, IoT devices only; required for IoT Network Certified for Smart Connected Infrastructure | 4.2 |
| Utility IoT device test plan | Optional, for IoT Network Certified for Smart Connected Infrastructure | 4.4 |
Test scope by technology
Section titled “Test scope by technology”| Technology | Main references (NAPRD03 V6.26) |
|---|---|
| GSM / GERAN | Out of scope: GERAN requirements removed in NAPRD03 V6.22 (September 2025), GSM removed from the PPMD in V4.0 (October 2025) |
| UTRA (3G) | TS 34.121, TS 34.123; Bands II and V |
| LTE Cat-1 and higher | TS 36.521-1, 36.521-3, 36.523-1, 36.124; IMS (TS 34.229) if voice; CTIA OTA; two receive antennas except Cat-1bis |
| LTE-M, NB-IoT | Same 3GPP specifications; IoT OTA rules (2.9.2); TS.35 connection efficiency; network independent UICC tests |
| NR FR1 (SA and NSA) | TS 38.521, 38.523, 38.533, 38.124; NSA OTA per the CTIA operator priority list |
| NR FR2 | n260 and n261 as EN-DC; radiated requirements (EIRP, EIS); completed in the end product |
| RedCap | TS 38.521, 38.523, 38.533, 38.124 (Section 2.3.26, added in V6.22) |
| NB-IoT NTN, NR NTN | Section 2.3.25 (added in V6.21); NB-IoT NTN only devices use TS 36.523-1 test case 22.4.13a for the capability audit |
| Mission critical | TS 37.579 (Section 2.3.28, added in V6.26) |
NAPRD03 changes, 2024 to 2026
Section titled “NAPRD03 changes, 2024 to 2026”| Date | Version | Change (NAPRD03 Appendix A) |
|---|---|---|
| April 2024 | 6.16 | OTA requirements for non-IoT and IoT devices clarified; converged device exceptions |
| June 2024 | 6.17 | n13 added to the NR FR1 bands |
| September 2024 | 6.18 | Audio section and the CTIA Speech Performance Test Plan added |
| December 2024 | 6.19 | CTIA Speech Performance Test Plan becomes the mandatory speech requirement |
| April 2025 | 6.20 | References to OTA test plan Version 4.0 deleted; "Active Version" used instead |
| June 2025 | 6.21 | NTN added; Band 106 added; n258 removed from FR2 |
| September 2025 | 6.22 | RedCap added; more GSMA SGP documents; TTY and GERAN requirements removed |
| December 2025 | 6.23 | NAPRD03 covers both PTCRB and IoT Network Certified; E-UTRA TDD Band 41 removed; Network Independent section added |
| March 2026 | 6.24 | E-UTRA TDD Band 43 removed; USIM and USAT references streamlined |
| June 2026 | 6.25 | Applicable version of the OTA test plan clarified |
| October 2026 | 6.26 | Category 1bis exception; PVG.11 made the main source of band information; Mission Critical Services section |
Claims the texts contradict
Section titled “Claims the texts contradict”| Common claim (including on earlier versions of this page) | What the documents say |
|---|---|
| "Data throughput is driven by carriers, not the PTCRB baseline" | NAPRD03 2.3.5 lists 3GPP TR 37.901 for data throughput, with PVG.09 as the verification guideline |
| "IoT modules must pass AT command compliance" and "the module must interact with the platforms via its AT command set" | AT-command assessment is deleted from NAPRD03: Section 2.13 was deleted in V6.8 (March 2022) and reference 2.3.17 is marked Deleted |
| A list of Anritsu, Rohde & Schwarz and Keysight models as "the" PTCRB platforms | NAPRD03 names no vendor; validated test platforms are listed per test case in the PTCRB test case database with V, E or D status |
| "Typical OTA limits: smartphone TRP at least +14 dBm, IoT module +12 dBm, wearable +8 dBm, TIS -94 or -90 dBm" | No PTCRB document gives these figures; pass levels are in the CTIA OTA plan, and IoT devices follow the NAPRD03 2.9.2 rules. The figures have been removed |
| "Reference sensitivity -94 to -100 dBm depending on band" | TS 36.101 Table 7.3.1-1 gives one value per band and bandwidth: for example Band 4 is -100 dBm at 5 MHz and -97 dBm at 10 MHz, Band 25 is -93.5 dBm at 10 MHz |
| "Maximum output power 23 dBm ± 2.7 dB" | The 3GPP minimum requirement is 23 dBm ±2 dB for power class 3 (TS 36.101 6.2.2); the conformance test adds a test tolerance |
| "The 3GPP OTA specifications are the PTCRB OTA test plan" | PTCRB uses the CTIA OTA test plan (NAPRD03 2.3.9 and 2.9). TS 37.544, 38.161 and 38.561 are 3GPP OTA specifications that NAPRD03 does not cite |
| "NAPRD03 is updated several times a year" | Exactly four times a year (PPMD 5.2.1; NAPRD03 2.1 says quarterly), and the two most recent versions are usable |
| "RRM tests typically take 2 to 3 days in the lab" | No PTCRB document gives test durations; the figure has been removed |
| eCall and battery life as PTCRB test categories | Neither appears in NAPRD03. eCall is the EU in-vehicle emergency call system |
| "Legacy GSM test cases retired" | GERAN requirements were removed from NAPRD03 in V6.22 (September 2025) and GSM from the PPMD in V4.0; UTRA remains |
| "SIM/USIM tests come from 3GPP and ETSI SIM specifications" (unspecified) | TS 31.121 and TS 31.124 for USIM and USAT, ETSI TS 102 230-1 for network independent UICC tests, GSMA SGP documents for remote SIM provisioning |
| Interoperability with AT&T, Verizon and T-Mobile networks named as specific test campaigns | PTCRB does not run field interoperability; the Get Certified page asks manufacturers to check whether the device needs additional operator-specific testing. See the operator guides below |
In summary
Section titled “In summary”- NAPRD03 V6.26 and the test case database define what applies; the database is the primary reference for test cases and categories.
- Category A and B tests must pass, Category E must be run and reported.
- OTA is mandatory for every device type, with lighter rules for IoT devices that answer "No" to the three Table 2.9.2-1 questions.
- Testing fees are set by each lab; the official CTIA Certification fees are on the overview.
For the request steps see Procedure; for the test list and the bands see Required tests and Scope; for common questions see the FAQ.
See also
Section titled “See also”- EV charging IEC 61851, ISO 15118, OCPP: cellular backhaul for OCPP and 3GPP profiles seen in EV chargers.
- Antenna design and impedance matching: antenna design principles behind OTA test performance, and the CTIA plan documents.
- PCB design for EMC: layout discipline that protects RF conformance margins.
- EMC chamber types: SAC, FAR, OATS, reverb: anechoic and reverberation chambers, both allowed for IoT OTA.
- Calibration and measurement uncertainty (GUM): uncertainty budget behind 3GPP RF conformance limits.
- PTCRB and GCF compared: the two schemes side by side, including leveraged GCF results.
- AT&T NAF cellular IoT certification, Verizon Open Development IoT certification and T-Mobile IoT device certification: operator programs on top of PTCRB.
Sources & references
- PTCRB NAPRD03 V6.26, October 2026 (reference test specifications, test case categories, OTA rules, change history), CTIA Certification www.ptcrb.com/wp-content/uploads/2026/10/NAPRD03-V6.26.pdf
- PTCRB Program Management Document (PPMD) V4.2, October 2026, Sections 5.2 and 5.5, CTIA Certification www.ptcrb.com/wp-content/uploads/2026/10/PTCRB-PPMD-V4.2.pdf
- PVG.11 V5.24.0, PTCRB bands and supporting operators (XLSX), CTIA Certification www.ptcrb.com/wp-content/uploads/2026/10/PVG-11-V-5.24.0.xlsx
- PTCRB, Get Certified (process and requirements documents), PTCRB / CTIA www.ptcrb.com/get-certified/
- ETSI TS 136 101 V19.6.0 (2026-08), 3GPP TS 36.101 E-UTRA UE radio transmission and reception, ETSI / 3GPP www.etsi.org/deliver/etsi_ts/136100_136199/136101/19.06.00_60/ts_136101v190600p.pdf
- ETSI TS 136 521-1 V19.2.0 (2026-09), 3GPP TS 36.521-1 E-UTRA UE conformance, radio transmission and reception, ETSI / 3GPP www.etsi.org/deliver/etsi_ts/136500_136599/13652101/19.02.00_60/ts_13652101v190200p.pdf
- 3GPP TS 38.101-2, NR UE radio transmission and reception, Range 2 standalone, 3GPP www.3gpp.org/dynareport/38101-2.htm
- 3GPP TS 37.544, UTRA and E-UTRA UE over the air performance, conformance testing, 3GPP www.3gpp.org/dynareport/37544.htm
- 3GPP TS 38.161, NR UE TRP and TRS requirements, Range 1, 3GPP www.3gpp.org/dynareport/38161.htm
- 3GPP TS 38.561, NR UE TRP and TRS requirements and test methodologies for FR1, 3GPP www.3gpp.org/dynareport/38561.htm
- CTIA Certification publishes the Test Plan for Wireless Device Over-the-Air Performance Version 4.0 (February 14, 2022), CTIA Certification ctiacertification.org/news/ctia-certification-publishes-the-test-plan-for-wireless-device-over-the-air-ota-performance-version-4-0/
- 3GPP Test Specifications, 3GPP www.3gpp.org/specifications-technologies/specifications-by-series
Frequently asked questions
- Which document says what PTCRB tests?
- NAPRD03, the technical requirements document shared by PTCRB and IoT Network Certified. Version 6.26 (October 2026) lists the reference test specifications in Section 2.3, and the PTCRB test case database is the primary reference for the actual test cases and their categories. NAPRD03 is released four times a year and a device must complete the tests of one of the two most recent versions (PPMD V4.2, 5.2).
- Is OTA testing mandatory for PTCRB?
- Yes. NAPRD03 V6.26, Section 2.9, makes RF performance evaluation mandatory for all device types going through PTCRB or IoT Network Certified, using the CTIA Certification Test Plan for Wireless Device Over-the-Air Performance in effect when the request is submitted. IoT devices follow the reduced rules of Section 2.9.2.
- Does a test case have to pass for certification?
- It depends on its category in the PTCRB test case database. Category A must be passed; Category B must be passed with certain exceptions; Category E must be executed and reported but a failure does not prevent certification; Categories D, N, P and S are not executed (NAPRD03 V6.26, Table 2.7.6-1).
- Are AT commands, battery life or eCall part of PTCRB testing?
- No. AT-command assessment was deleted from NAPRD03 (Sections 2.3.17 and 2.13 are marked Deleted), NAPRD03 has no battery life requirement, and eCall is an EU in-vehicle emergency call system, not a PTCRB test category.