PTCRB vs GCF: cellular device certification
Guide, cellular certification
PTCRB and GCF are the two certification schemes a cellular device usually has to clear before any mobile operator will let it onto a network. They are not government regulations, they sit alongside FCC authorisation and CE/UKCA marking, but commercially they are unavoidable: a modem module or an IoT product without the right record will be refused provisioning. The two schemes test against the same 3GPP TS 36.521-1 and 3GPP TS 38.521-1 conformance specifications, so the engineering overlaps, yet their governance, geography and operator backing differ enough that choosing the wrong one wastes a test campaign. This guide leads with a side-by-side decision table, then explains each axis, and closes with a clear answer to which one you actually need.
Decision table at a glance
Section titled “Decision table at a glance”The fastest way to orient yourself is the head-to-head below. Read it top to bottom, then use the sections that follow to dig into any row that matters for your product.
| Axis | PTCRB | GCF |
|---|---|---|
| Governance | Administered by CTIA (US wireless industry association) | Operator-led forum, member operators plus manufacturers |
| Primary geography | North America (US, Canada) | Global, strongest in Europe, Middle East, Africa, Asia-Pacific |
| Legal status | Private carrier scheme, not a regulation | Private operator scheme, not a regulation |
| Test source | 3GPP conformance test cases | 3GPP conformance test cases (same base) |
| Backing carriers | AT&T, Verizon, T-Mobile and other PTCRB operators | Vodafone, Deutsche Telekom, Orange, Telefonica and others |
| Scope | GSM, UMTS, LTE, 5G NR, SIM/USIM | GSM, UMTS, LTE, 5G NR, (e)UICC, plus field trials |
| Record database | PTCRB Certified Device list | GCF certification database |
| Relationship to operator acceptance | Prerequisite for AT&T NAF, Verizon OPC | Prerequisite for Vodafone and EMEA operator programmes |
| Typical user | OEM targeting North American carriers | OEM targeting European and global carriers |
| Module reuse | Pre-certified module can shortcut device cert | Pre-certified module can shortcut device cert |
If your distribution map is purely North American, PTCRB is the default. If it is European or global, GCF is the default. If it is both, plan a combined campaign. The rest of this guide explains why.
Governance and geography: who runs each scheme
Section titled “Governance and geography: who runs each scheme”The two schemes were born from different parts of the industry, and that origin still shapes how each is governed and where it carries weight.
PTCRB: a North American operator scheme under CTIA
Section titled “PTCRB: a North American operator scheme under CTIA”PTCRB (the name comes from the historical "PCS Type Certification Review Board") is managed by CTIA, the trade association of the US wireless industry. It is the de facto certification gate for the North American carrier ecosystem. A device that wants to operate on AT&T, Verizon, T-Mobile or the regional US and Canadian operators is expected to hold a PTCRB record for the relevant radio access technologies and bands.
PTCRB defines its process in the PPMD (Process Overview of the PTCRB Certification Program) and its technical requirements in NAPRD03, validates accredited laboratories, and publishes certified devices in a public list. Crucially, PTCRB is the baseline that the big North American carriers build their own acceptance programmes on top of, rather than a replacement for them.
GCF: a global, operator-led forum
Section titled “GCF: a global, operator-led forum”The Global Certification Forum is an operator-led membership organisation, not a regulator: its members are mobile operators and device manufacturers. Its centre of gravity is Europe, the Middle East and Africa, with strong adoption across Asia-Pacific. Operators such as Vodafone, Deutsche Telekom, Orange and Telefonica use a valid GCF record as the baseline for putting a device on their networks.
GCF maintains its own certification database, its own work-item process for declaring 3GPP test cases valid, and a field-trial component that complements lab conformance with real-network checks. Because membership is operator-driven and global, GCF is the natural scheme for products with worldwide distribution outside the strictly North American footprint.
Where the two overlap
Section titled “Where the two overlap”There is no hard geographic wall. Some operators recognise either scheme, and the underlying 3GPP test cases are identical. The practical difference is which database a given carrier checks before it will provision a device, which is why the geography column of the decision table is the single most useful filter.
Scope: what each scheme actually certifies
Section titled “Scope: what each scheme actually certifies”Both schemes certify the cellular radio and the SIM interface, drawing on 3GPP. Neither covers non-cellular radios.
| Capability | PTCRB | GCF |
|---|---|---|
| GSM / GPRS / EDGE | Yes | Yes |
| UMTS / HSPA | Yes | Yes |
| LTE / LTE-M / NB-IoT | Yes | Yes |
| 5G NR (FR1, FR2) | Yes | Yes |
| RF transmit/receive conformance | Yes (3GPP TS 36.521 / 38.521) | Yes (3GPP TS 36.521 / 38.521) |
| Protocol / signalling conformance | Yes (3GPP TS 36.523 / 38.523) | Yes (3GPP TS 36.523 / 38.523) |
| SIM / USIM / (e)UICC | Yes | Yes |
| Field trial on live network | Carrier-specific (via acceptance) | Yes, GCF field-trial work items |
| Wi-Fi, Bluetooth, GNSS | No (separate programmes) | No (separate programmes) |
The chips above point to the conformance families: 3GPP TS 36.521-1 for LTE RF, 3GPP TS 38.521-1 for 5G NR RF Range 1, with the protocol side handled by 3GPP TS 36.523-1 and 3GPP TS 38.523-1. For the full test-case structure see the 3GPP RF conformance test plan guide.
The 3GPP common foundation
Section titled “The 3GPP common foundation”The reason a single lab visit can feed both schemes is that neither writes its own physical-layer requirements. They both reference 3GPP.
3GPP publishes the conformance specifications; PTCRB and GCF each decide when a given 3GPP test case is mature enough to be mandatory, and which test platforms are validated to run it. So the question is never "PTCRB test or GCF test", it is "is this 3GPP test case currently required by PTCRB, by GCF, or by both, and on which validated platform". An accredited laboratory configures the campaign accordingly.
Test specification map
Section titled “Test specification map”| Technology | RF conformance | Protocol conformance |
|---|---|---|
| LTE | 3GPP TS 36.521 | 3GPP TS 36.523 |
| 5G NR | 3GPP TS 38.521 | 3GPP TS 38.523 |
| GSM | 3GPP TS 51.010 | 3GPP TS 51.010 |
| SIM / USIM | 3GPP TS 31.121 / ETSI test suites | 3GPP TS 31.121 / ETSI test suites |
Because the source is shared, the marginal cost of adding the second scheme to a campaign is far lower than the cost of the first. Labs that hold recognition under both run the shared cases once and submit two records.
When an OEM needs one, the other, or both
Section titled “When an OEM needs one, the other, or both”This is the heart of the decision. Map your target carriers to schemes, not the other way around.
You need PTCRB if
Section titled “You need PTCRB if”- You sell into AT&T, Verizon, T-Mobile or other North American operators.
- You build a cellular module intended for the North American module market, where a PTCRB module record lets your downstream integrators skip parts of device-level testing.
- Your end customer's procurement contract names PTCRB as a delivery condition.
You need GCF if
Section titled “You need GCF if”- You sell into European, Middle Eastern, African or many Asia-Pacific operators.
- You target Vodafone, Deutsche Telekom, Orange, Telefonica or other GCF-member operators.
- You build a module aimed at the global (non-North-American) market and want a GCF module record as the baseline for integrators.
You need both if
Section titled “You need both if”- Your roadmap is genuinely worldwide and you cannot rule out either region.
- You build a flagship module that integrators will deploy on any continent; carrying both records maximises its addressable market.
- You are a Tier-1 OEM whose device families ship into both North America and EMEA from the same hardware platform.
Step by step: scoping the campaign
Section titled “Step by step: scoping the campaign”- List every target carrier and country for the device's lifetime, not just launch.
- Map each carrier to its required scheme (PTCRB for North America, GCF for most of the rest).
- Check whether your modem module already holds the needed module-level records; reuse shortens device testing.
- Decide single-scheme or dual-scheme based on the map, and lock it before booking lab time.
- Build one combined 3GPP test plan covering the union of required test cases.
- Run the campaign at a laboratory recognised by every scheme in scope.
- Submit the records, then enter each carrier's separate acceptance programme.
Relationship to operator acceptance
Section titled “Relationship to operator acceptance”Certification is necessary but not sufficient. Each carrier layers its own acceptance programme on top, and that is where many launch delays actually happen.
| Operator | Scheme prerequisite | Acceptance programme |
|---|---|---|
| AT&T | PTCRB | Network Approval Framework (NAF) |
| Verizon | PTCRB | Open Development / OPC device certification |
| T-Mobile US | PTCRB | Operator-specific device acceptance |
| Vodafone | GCF | Vodafone device acceptance / IoT acceptance |
| Deutsche Telekom, Orange, Telefonica | GCF | Operator-specific acceptance |
PTCRB or GCF clears the conformance baseline; the carrier acceptance step then checks network-specific behaviour (provisioning, VoLTE, roaming profiles, field performance). For the operator-specific detail, see AT&T NAF cellular IoT certification and Vodafone global IoT acceptance.
Common pitfalls
Section titled “Common pitfalls”| Pitfall | Consequence | How to avoid it |
|---|---|---|
| Certifying only one scheme then trying to enter the other region | Second test campaign, weeks of delay | Map all target carriers before booking lab time |
| Assuming PTCRB or GCF replaces FCC or CE | Device cannot be legally sold | Treat regulatory and carrier schemes as separate gates |
| Treating certification as the finish line | Carrier refuses provisioning at acceptance | Plan NAF, OPC or Vodafone acceptance into the schedule |
| Ignoring module-level records | Re-testing radio already certified in the module | Reuse pre-certified module records where the design permits |
| Changing firmware after certification | Record invalidated, re-acceptance triggered | Apply change management against each scheme's delta rules |
| Out-of-scope radios assumed covered | Wi-Fi or Bluetooth left uncertified at launch | Certify each radio through its own programme |
Which one do you need
Section titled “Which one do you need”The short answer: let geography drive the choice. North America only, choose PTCRB. Europe and most of the rest of the world, choose GCF. Worldwide, do both in a single combined campaign. Then, whichever you pick, budget the separate operator acceptance step (NAF for AT&T, OPC for Verizon, the GCF-aligned programmes for Vodafone and EMEA carriers) because that is the gate that actually lets the device onto a live network. The cellular conformance work is shared 3GPP testing either way, so the real planning decision is the union of carriers you must serve over the product's life, scoped once, tested once, and submitted to each scheme that your carriers check.
Further reading
Section titled “Further reading”- PTCRB certification
- GCF: the Global Certification Forum
- 3GPP RF conformance test plan
- AT&T NAF cellular IoT certification
- Vodafone global IoT acceptance
- Verizon OPC IoT certification
Sources and references
Section titled “Sources and references”Sources & references
- PTCRB Certification Program overview , PTCRB / CTIA www.ptcrb.com/
- PTCRB PPMD: Process Overview of the PTCRB Certification Program , PTCRB / CTIA www.ptcrb.com/certification-resources/
- PTCRB NAPRD03: technical requirements for PTCRB certification , PTCRB / CTIA www.ptcrb.com/certification-resources/
- Global Certification Forum: about GCF , GCF www.globalcertificationforum.org/
- 3GPP TS 36.521-1: LTE UE conformance, radio transmission and reception , 3GPP www.3gpp.org/dynareport/36521-1.htm
- 3GPP TS 38.521-1: NR UE conformance, radio transmission and reception (Range 1) , 3GPP www.3gpp.org/dynareport/38521-1.htm
- AT&T Network Approval Framework (NAF) , AT&T www.att.com/devicecertification/
- Verizon Open Development / Device Certification , Verizon opendevelopment.verizonwireless.com/
Frequently asked questions
- What is the core difference between PTCRB and GCF?
- PTCRB is the certification scheme administered by CTIA for the North American carrier community (AT&T, Verizon, T-Mobile and others). GCF is a global, operator-led certification forum used mainly in Europe, the Middle East, Africa and parts of Asia-Pacific. Both run conformance against the same 3GPP test specifications, so the engineering work overlaps heavily, but the governance, the database of records and the regional carriers that recognise them differ.
- Does a device need both PTCRB and GCF?
- It depends on the target markets. A device sold only in North America typically needs PTCRB; a device sold across Europe and global operator networks typically needs GCF. A device with worldwide ambitions often pursues both, because most carriers will only accept the scheme aligned with their region. The two certifications can usually be obtained from a single test campaign at an accredited laboratory.
- Is PTCRB or GCF a legal requirement like FCC or CE?
- No. Neither is a government regulation. FCC equipment authorisation and CE/UKCA marking are legal market-access requirements. PTCRB and GCF are private, carrier-driven certification schemes. They are commercial gates, a mobile operator will generally refuse to provision a device or sell a SIM plan for it unless the relevant certification record exists, but they do not replace the regulatory approvals.
- Where do the actual test cases come from?
- Both schemes draw their conformance test cases from 3GPP specifications, principally TS 36.521 and TS 36.523 for LTE and TS 38.521 and TS 38.523 for 5G NR, plus protocol and SIM/USIM test suites. PTCRB and GCF maintain work items and validation status for each test case rather than writing their own physical-layer requirements, which is why a single lab campaign can feed both records.
- How does operator acceptance relate to PTCRB and GCF?
- Certification is the entry ticket; operator acceptance is the separate step where a specific carrier validates the device on its live network. AT&T (NAF) and Verizon (OPC) require PTCRB as a prerequisite, then add their own network-specific tests. Vodafone and other GCF-aligned operators require GCF as the baseline before their own acceptance programme. Passing PTCRB or GCF does not by itself guarantee a given carrier will provision the device.
- Can the same laboratory issue both PTCRB and GCF records?
- Yes, in most cases. Accredited test laboratories are recognised by both schemes and run the shared 3GPP test cases once, then submit the results to each scheme's database under the respective rules. This is why OEMs planning global distribution usually scope a combined campaign from the start rather than testing twice.
- Does PTCRB or GCF cover Wi-Fi, Bluetooth or GNSS?
- The cellular conformance scope of PTCRB and GCF centres on 3GPP radio access (GSM, UMTS, LTE, 5G NR) and the SIM/eUICC interface. Other radios such as Wi-Fi, Bluetooth and GNSS are certified through their own programmes (Wi-Fi Alliance, Bluetooth SIG) and are out of scope for the cellular certification itself, although a multi-radio device still needs each programme separately.
- How long is a PTCRB or GCF certification valid?
- Both records remain valid for the certified hardware and software configuration. Material changes to the modem, firmware, RF front end or antenna can trigger a re-test or a delta certification under each scheme's change rules. Operators may also require re-acceptance when a device's software is updated, so configuration management is essential across the device lifecycle.