PTCRB technical file

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

PTCRB · Pillar

The PTCRB file differs from the FCC file by its focus on radio configurations, the Integration Guide for modules, and IMEI traceability. This page details documentation expected for module and End-Product certifications.

PTCRB file structure

The file submitted in the PTCRB certification database (via the Primary lab) typically includes:

Administrative documents

Certification request (electronic form: Initial, Variant or ECO)
Cover letter describing the product, tested radio modes, scope
Manufacturer information, manufacturer, technical contact
Trademark and product info, trademarks, models

Technical documents

Block diagram electrical and functional (RF, baseband, supply, antennas)
Bill of Materials for critical RF components
Antenna specifications, gain, radiation pattern, impedance, model
Operational description of radio modes and supported 3GPP protocols
Detailed radio configurations (bands, modulations, powers, classes)

Test reports

RF Conformance test report (TS 36.521 / TS 38.521)
Protocol conformance test report (TS 36.523 / TS 38.523)
OTA test report (CTIA OTA test plan)
IMS test report if applicable
(P)ICS/(P)IXIT declarations of supported capabilities
Feature-specific test reports (A-GNSS, SIM/USIM, etc. per profile)
Carrier-specific reports where required by targeted operators

End-product documents (if applicable)

Module reference, used module reference and version
Integration verification, evidence of Integration Guide compliance
Final product OTA tests in final configuration

IMEI documents

TAC application for IMEI range assignment
IMEI management procedure, how the manufacturer manages its range

The Integration Guide

For cellular module manufacturers, the Integration Guide is the central document defining reuse conditions of the module certificate in integrators' final products.

Typical content:

Electrical conditions

Acceptable supply voltages
Peak currents (cellular TX bursts)
Required filtering (decoupling caps, ferrites)
Supply performance to avoid degrading RF

RF conditions

List of compatible antennas (model, max gain, polarisation, type)
Connection impedance (50 Ω, max VSWR)
Minimum ground plane (size, continuity)
Minimum distance from other RF components
RF routing between module and antenna (length, impedance)

Mechanical and thermal conditions

Enclosure required or not
Operational temperature range
Thermal management (dissipation, shielding)
Vibration and shock

Radio configurations

Bands enabled by default
Restrictive configurations (e.g. 5G disabled in noisy environments)
Recommended PSM / eDRX profiles

The Integration Guide is typically 50 to 150 pages, and the quality of this document determines ease of use of the module by integrators.

TAC and IMEI range

TAC assignment

For PTCRB devices, CTIA Certification issues the TAC (Type Allocation Code): it is the IMEI Administrator of the program and a GSMA Reporting Body, and it reports allocated TACs to GSMA. The TAC is an 8-digit identifier that identifies the model in the GSMA database.

A TAC allows 1 million unique IMEIs:

TAC: 35123456 (8 digits) — identifies the model
Serial: 123456 (6 digits) — unique per unit
Check: 7 (Luhn algorithm on first 14 digits)
=> IMEI: 351234561234567

For high-volume products, additional TACs are assigned to the same model as each 1,000,000-unit block is exhausted.

IMEI range management

The manufacturer must:

Maintain an internal database of issued IMEIs
Guarantee uniqueness of IMEIs within its range
Respect the Luhn formula for the Check Digit
Register IMEIs used in the GSMA database if required

A management error (duplicates, IMEIs out of range) can cause unit blocking by operators during network registration.

GSMA TAC database

The GSMA TAC database (https://imeidb.gsma.com/) is the worldwide reference. It is consulted by:

Operators during network registration
Authorities (police, customs) for traceability
National CEIRs (Central Equipment Identity Registers) for blocking stolen terminals

An IMEI not registered in GSMA can be refused by some operators or blocked after detection.

Modifications after certification

Post-certification modifications map onto the official PTCRB request categories (PPMD):

ECO (Engineering Change Order)

Recertification of an already certified device after a hardware or software update. The Primary lab assesses the change and determines the required delta testing; minor changes with no wireless impact need little or no retesting.

Variant

A device derived from a certified Parent (same device type, limited differences). The Variant process reuses the Parent's results and tests the deltas; the Variant receives its own TAC.

New platform (Initial Certification)

Changes beyond what the Variant process allows (for example a new RF architecture or platform) require a new Initial Certification with a complete test campaign.

The lab's assessment against NAPRD03 and the PPMD rules determines which category applies.

File retention

The PTCRB file must be retained for the complete commercial product lifetime, plus typically 5 to 10 years after end of production. PTCRB and operators may request access at any time.

Particularly important documents to retain:

Original test reports signed by the lab
Integration Guide in all distributed versions
List of distributed firmwares and their RF/network impact
IMEI history issued and their product correspondence
Operator tickets and resolutions of post-certification incidents

Certification maintenance

Unlike FCC which is a "lifetime" certification (except modifications), PTCRB requires active maintenance:

Following NAPRD03 and test case database evolutions (several releases per year)
ECO certification requests for hardware or software updates affecting radio
Regression tests for firmware updates affecting radio
Incident reporting to operators if production problems are noted

Budget an annual maintenance line for an active PTCRB certification (delta tests, ECO fees, operator communications); the amount depends on the product's update cadence.

User documentation

For the final product integrating the certified module:

Recommended mentions

PTCRB itself does not mandate user-manual wording or a product marking: certification is recorded in the public PTCRB certified devices database and the device is identified by its IMEI. In practice, manufacturers commonly document:

The PTCRB certification of the device or of the integrated module
The declared 3GPP capabilities (LTE Cat-1, 5G NSA, etc.)
The operator compatibility targeted

If the product has passed additional operator homologations (Verizon Open Development, AT&T Network Ready), these can be mentioned additionally, subject to each program's branding rules.