Skip to content
spilma

PTCRB technical file

Author Hugues Orgitello Last updated 25 May 2026

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

Section titled “PTCRB file structure”

The file submitted to PVG typically includes:

Administrative documents

Section titled “Administrative documents”
  1. PTCRB application form (electronic form)
  2. Cover letter describing the product, tested radio modes, scope
  3. Manufacturer information, manufacturer, technical contact, US Agent
  4. Trademark and product info, trademarks, models

Technical documents

Section titled “Technical documents”
  1. Block diagram electrical and functional (RF, baseband, supply, antennas)
  2. Bill of Materials for critical RF components
  3. Antenna specifications, gain, radiation pattern, impedance, model
  4. Operational description of radio modes and supported 3GPP protocols
  5. Detailed radio configurations (bands, modulations, powers, classes)

Test reports

Section titled “Test reports”
  1. RF Conformance test report (TS 36.521 / TS 38.521)
  2. OTA test report (CTIA Plan)
  3. IMS test report if applicable
  4. Inter-Operability test report
  5. Data Throughput test report
  6. Battery test report
  7. Service-specific test reports (eCall, A-GNSS, etc. per profile)

End-product documents (if applicable)

Section titled “End-product documents (if applicable)”
  1. Module reference, used module reference and version
  2. Integration verification, evidence of Integration Guide compliance
  3. Final product OTA tests in final configuration

IMEI documents

Section titled “IMEI documents”
  1. TAC application for IMEI range assignment
  2. IMEI management procedure, how the manufacturer manages its range

The Integration Guide

Section titled “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

Section titled “Electrical conditions”
  • Acceptable supply voltages
  • Peak currents (cellular TX bursts)
  • Required filtering (decoupling caps, ferrites)
  • Supply performance to avoid degrading RF

RF conditions

Section titled “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

Section titled “Mechanical and thermal conditions”
  • Enclosure required or not
  • Operational temperature range
  • Thermal management (dissipation, shielding)
  • Vibration and shock

Radio configurations

Section titled “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

Section titled “TAC and IMEI range”

TAC assignment

Section titled “TAC assignment”

Once PTCRB certification is obtained, GSMA assigns a TAC (Type Allocation Code) to the manufacturer for the certified module/product. The TAC is an 8-digit identifier that identifies the model in the GSMA database.

A TAC typically 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, multiple TACs can be assigned to the same model (up to ~5 TACs for high-volume smartphones).

IMEI range management

Section titled “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

Section titled “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

Section titled “Modifications after certification”

As for FCC, post-certification modifications follow a typology:

Minor modifications

Section titled “Minor modifications”
  • Software without RF impact: no recertification
  • Cosmetic: no recertification
  • Equivalent non-RF component: no recertification

Minor RF modifications

Section titled “Minor RF modifications”
  • Antenna with equivalent characteristics
  • Minor radio software modification
  • Partial OTA retest + simplified PVG submission

Major modifications

Section titled “Major modifications”
  • Band change
  • New technology (adding 5G to a 4G module)
  • RF architecture modification
  • Complete new certification + new TAC

The general criterion is substantiality with regard to 3GPP and operator compliance.

File retention

Section titled “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

Section titled “Certification maintenance”

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

  • Following PTCRB test plan evolutions (typically two releases per year)
  • Partial recertification when test plans evolve significantly
  • Regression tests for firmware updates affecting radio
  • Incident reporting to operators if production problems are noted

Annual maintenance cost for an active PTCRB certification of a cellular module is typically $10,000 to $30,000 (delta tests, PVG fees, operator communications).

User documentation

Section titled “User documentation”

For the final product integrating the certified module:

Mandatory mentions

Section titled “Mandatory mentions”
  • PTCRB Approval Code in user manual
  • TAC range (statistical information, not IMEI detail)
  • 3GPP compliance declared (LTE Cat-1, 5G NSA, etc.)
  • Operator compatibility declared

Product compliance

Section titled “Product compliance”

Indication of compliance with operator standards:

This device meets PTCRB requirements and is certified for use
on the following carriers: AT&T, T-Mobile, Verizon, Bell, Rogers, Telus.

If the product has passed additional operator homologations (Verizon OPC, AT&T NDD), these certifications can be mentioned additionally.

Sources & references

  1. PTCRB Documentation Requirements , PTCRB www.ptcrb.com/
Edited by AESTECHNO, Montpellier, France · Legal notice