GCF: Global Certification Forum cellular device scheme

Author Hugues Orgitello Last updated 30 May 2026 ~10 min read

Guide, cellular certification

The Global Certification Forum (GCF) is the operator-led, global certification scheme for cellular devices. Founded in 1999 by mobile operators and manufacturers, it certifies that a phone, module or IoT terminal conforms to the relevant 3GPP radio, protocol and performance specifications, plus a set of operator-driven test cases. GCF shares almost all of its technical baseline with PTCRB, the North American scheme, yet differs in governance, geography and certificate format. This guide explains how GCF is structured (Work Items, Device Certification Criteria, Field Trials), how its scope maps onto 3GPP conformance, which test platforms are recognised, and how an OEM decides between GCF, PTCRB and operator acceptance.

What GCF is, and what it is not

GCF is an independent, non-profit certification scheme governed by its members: mobile network operators, device and module manufacturers, and test equipment makers. Its purpose is to give the cellular ecosystem a single, shared statement that a device conforms to a defined baseline of 3GPP specifications and operator-agreed test cases. A GCF certificate is recognised by operators across most of the world outside North America, which is why GCF is sometimes described as the global counterpart of PTCRB.

GCF does not write conformance test cases. The RF, Radio Resource Management (RRM) and protocol test cases are written by 3GPP and published as the TS xx.521 and TS xx.523 series. GCF selects which of those validated test cases are mandatory, defines on which validated test platforms they must run, and adds real-network Field Trial requirements. GCF is therefore a selection, validation and governance layer on top of the 3GPP technical reference, not a separate set of measurements.

It is equally important to state what a GCF certificate is not. It is not a regulatory approval: it does not replace FCC equipment authorisation, an EU RED assessment or any national radio approval. It is not operator homologation either: a single operator may still demand its own acceptance campaign on top of GCF. GCF sits between raw 3GPP conformance and operator-specific acceptance.

GCF and PTCRB, compare and contrast

GCF and PTCRB are frequently conflated because they share the same 3GPP technical core. The distinction is real and structural.

Criterion	GCF	PTCRB
Nature	Global, operator-led, non-profit scheme	North American scheme run by CTIA
Founded	1999, by operators and manufacturers	1997, by North American operators
Geographic centre	Europe, Middle East, Africa, much of Asia and Latin America	United States and Canada
Technical baseline	3GPP TS 36.521, 3GPP TS 38.521, TS xx.523	The same 3GPP conformance specifications
Scope unit	Work Item, governed by criteria (DCC)	Test case lists per band and feature
Real-network step	GCF Field Trials	Carrier-driven field testing where required
Certificate	GCF certificate in the GCF certified-device database	PTCRB device (end-product) certification or modular certification, PVG validated
Recognised by	Operators worldwide outside North America	North American carriers (AT&T, T-Mobile, Verizon, Bell, Rogers, Telus)

The practical reading: the RF, RRM and protocol measurements are largely the same because both schemes adopt the same 3GPP test cases. What differs is the declared band list, the recognised labs, the governance bodies and the certificate format. A device declared for European and Asian bands is shaped by GCF Work Items; a device declared for North American carrier bands is shaped by PTCRB test lists. See PTCRB scope for the carrier and band coverage on the North American side, and the dedicated PTCRB versus GCF comparison for a side-by-side decision view.

Why so many products carry both

Because the underlying lab work is shared, running GCF and PTCRB in parallel mutualises most of the cost. The RF transmitter and receiver measurements, the RRM mobility tests and the protocol signalling sequences are executed once on a validated platform and reused, with only the scheme-specific band and feature deltas adding incremental test time. A global smartphone or a worldwide cellular module almost always holds both certificates. A region-locked IoT product may hold only one.

Work Items and the CAG, how scope is defined

The unit of GCF certification is the Work Item. A Work Item defines a discrete area of certification: a 3GPP feature, a frequency band, a radio access technology (LTE, NR, NB-IoT, LTE-M) or a service such as VoLTE. Each Work Item references the specific 3GPP test specifications and the individual test cases inside them, names the validated test platforms permitted to execute those cases, and states the pass criteria.

Work Items are agreed and maintained through GCF's working structure. The conformance agreement work (carried out by the Conformance Agreement Group (CAG)) keeps the Work Item database aligned with each 3GPP release, adding, modifying or retiring test cases as the specifications evolve. For an OEM, the Work Item database is the practical map of GCF: you assemble the set of Work Items that correspond to your device's declared features and bands, and that set defines your certification scope.

Anatomy of a Work Item

A typical Work Item contains:

• The radio access technology and the band or band combination it covers.
• The 3GPP test specification references, for example 3GPP TS 38.521-1 for NR FR1 RF.
• The list of mandatory and conditional test cases, each identified by its 3GPP test case number.
• The validated test platforms and the validated software versions for those cases.
• Any associated Field Trial requirement.
• The applicable 3GPP release and the version of the test cases.

Because a Work Item is tied to a 3GPP release, the same feature can change scope between releases. Citing a Work Item without its version, or a test case without its release, is insufficient for a certification file, exactly as it is for the raw 3GPP references discussed in the 3GPP RF conformance guide.

Device Certification Criteria (DCC)

The Device Certification Criteria, abbreviated DCC, are the rules that turn a declared feature set into a concrete test obligation. The DCC answer the question: given that a device declares these bands, these radio access technologies and these services, which Work Items apply and how many test cases within them must pass?

Key properties of the DCC:

• They are versioned. A device is certified against a specific DCC version, which is recorded in the certification file.
• They map declared capabilities to Work Items, so the manufacturer's Implementation Conformance Statement (the declared feature set) drives the scope.
• They evolve with 3GPP releases, so the same declared feature can require a different test count between DCC versions.
• They distinguish mandatory test cases from conditional ones that apply only when a related feature is declared.

The DCC are the reason two superficially similar devices can have very different GCF scopes: a richer declared feature set (more bands, carrier aggregation combinations, NR Standalone plus Non Standalone, VoLTE, positioning) pulls in more Work Items and more test cases.

GCF Field Trials

Laboratory conformance proves a device behaves correctly against an emulated network in a callbox. It cannot fully reproduce the messiness of live networks. GCF Field Trials fill that gap. The device under test is operated on live commercial operator networks selected by GCF, where it meets real cells, real neighbour lists, real handovers, real interference and real inter-operator roaming.

Field Trials are not run for every Work Item. They are required for areas where real-network behaviour matters and is hard to emulate, typically:

• New radio access technologies at their introduction (for example early NR deployments).
• Mobility behaviour across real cell boundaries and across operators.
• Key services such as voice (VoLTE), where end-to-end establishment, handover and call retention are observed.
• Roaming behaviour on visited networks.

The Field Trial result feeds into the certification record alongside the lab conformance results. A device cannot complete certain Work Items on lab conformance alone. This is one of the clearest differences in emphasis from a pure conformance scheme, and the GCF Field Trial glossary entry summarises the concept.

Relationship to 3GPP conformance

GCF, PTCRB and operator acceptance all stand on the same foundation: the 3GPP UE conformance specifications. The three families that matter are:

Domain	LTE specification	NR specification	What it covers
RF transmitter and receiver	3GPP TS 36.521-1	3GPP TS 38.521-1	Power, EVM, ACLR, spurious emissions, sensitivity
Radio Resource Management	TS 36.521-3 (and RRM parts)	TS 38.521-3	Mobility, cell selection and reselection, handover, power control
Protocol and signalling	3GPP TS 36.523-1	3GPP TS 38.523-1	RRC and NAS message sequences, layer-3 conformance

GCF takes the validated test cases from these specifications, selects the required subset per Work Item, and records the outcome. The certification record is the database entry that ties a device, its declared features, the DCC version, the Work Items passed and the lab results together. The certified-device database is searchable, so an operator can confirm a given device model holds the relevant certificate.

The single technical reference shared with PTCRB is the point worth remembering: a passing RF measurement on a validated platform is, in principle, valid evidence for both schemes. The schemes diverge in which results they require and how they record them, not in how the measurement itself is performed. See PTCRB tests and PTCRB standards for the North American expression of the same baseline.

Test platforms recognised by GCF

The scheme validates the conformance test systems (callboxes and software) that labs may use. Only results produced on a validated platform, with a validated software version, count toward certification. The dominant vendors are:

Vendor	Representative platforms	Typical coverage
Anritsu	MT8000A (5G), MT8821C (LTE)	NR FR1 and FR2, LTE RF, RRM, protocol
Keysight	UXM 5G E7515B, plus legacy UXM	NR signalling, LTE anchor, conformance suites
Rohde and Schwarz	CMX500, CMW500	NR and LTE RF, RRM, protocol, callbox emulation

Each Work Item names the platforms validated for its test cases. The validation status of a platform plus software version can change as 3GPP releases progress, so a lab and an OEM must confirm validation before booking a campaign. This mirrors the platform situation described in the 3GPP RF conformance guide, where the same callboxes execute the underlying test cases.

When an OEM needs GCF, PTCRB or operator acceptance

The decision is driven by the target market and the customer operators, not by a single global rule.

Situation	What is typically required
Device sold mainly in Europe, the Middle East, Africa, much of Asia or Latin America	GCF
Device for the North American carriers	PTCRB
Global product across both regions	Both GCF and PTCRB, run in parallel
Launch on a specific named operator	GCF or PTCRB plus that operator's acceptance
Region-locked IoT product, single region	The scheme matching that region only

Operator acceptance sits on top of either scheme because individual operators add network-specific requirements: priority bands, attach and roaming policies, eSIM provisioning checks, throughput and field behaviour against their own core network. Examples include AT&T NAFI, Verizon OPC and Vodafone Global IoT acceptance. GCF or PTCRB is necessary, but for a launch on a named network it is rarely sufficient.

Step by step, scoping a GCF programme

1. Declare the device capabilities. Fix the bands, radio access technologies (LTE, NR Standalone and Non Standalone, NB-IoT, LTE-M), carrier aggregation combinations and services (VoLTE, positioning). This declaration drives everything downstream.
2. Resolve the DCC version. Identify the current Device Certification Criteria version applicable to the target 3GPP release, and record it.
3. Assemble the Work Items. Map each declared capability to its Work Items, listing mandatory and conditional test cases.
4. Confirm validated platforms. Check that the chosen lab holds validated platforms and software versions for every Work Item in scope.
5. Run lab conformance. Execute RF, RRM and protocol test cases on the validated platform.
6. Run Field Trials where required. Complete the live-network phase for the Work Items that mandate it.
7. Record the certificate. The GCF certificate ties the device, DCC version, Work Items and results together in the certified-device database.
8. Layer operator acceptance. Where a named operator is targeted, run its acceptance programme on top of GCF.

For sequencing this alongside regulatory work, see the certification timeline and the EU plus US dual certification guides.

Common pitfalls

Pitfall	Why it happens	How to avoid it
Treating GCF as a regulatory approval	Confusing a scheme certificate with equipment authorisation	Plan FCC, RED and national radio approvals separately from GCF
Assuming GCF replaces operator acceptance	Believing a scheme certificate is enough to launch on a named network	Budget operator homologation on top of GCF where a specific operator is targeted
Citing a Work Item without its DCC and release version	Test scope changes between 3GPP releases	Record the DCC version and the 3GPP release in the certification file
Using a non-validated test platform or software version	Platform validation status changes over time	Confirm validation per Work Item before booking the lab campaign
Under-declaring features to shrink scope	Hoping to cut test count	Declare honestly; an incomplete declaration fails operator acceptance and audits later
Skipping Field Trials	Believing lab conformance is the whole scheme	Identify which Work Items require Field Trials early and book live-network time
Running GCF and PTCRB as separate, sequential projects	Not realising the lab work is mostly shared	Mutualise the shared 3GPP test cases and add only the scheme-specific deltas
Forgetting eSIM and provisioning scope	eUICC behaviour is easy to overlook	Include the relevant GSMA and 3GPP provisioning test cases where the device carries an eSIM

Further reading

• PTCRB pillar: scope, procedure and tests
• PTCRB versus GCF: choosing the cellular scheme
• 3GPP RF conformance: TS 36.521 and TS 38.521
• AT&T NAFI: carrier homologation after the scheme
• Vodafone Global IoT: device acceptance and eSIM
• spilma glossary: GCF, PTCRB, 3GPP and more

GCF and PTCRB programme scoping

Let us scope your GCF and PTCRB cellular dossier in 30 minutes.

AESTECHNO maps your declared bands and features to the right GCF Work Items and DCC version, identifies which campaigns can be mutualised with PTCRB, and flags the Field Trial and operator acceptance steps, free of charge, over a video call.

Book a cellular audit

Sources and references

Sources & references

1. GCF, Global Certification Forum, official site , GCF www.globalcertificationforum.org/
2. GCF certification scheme overview and certified devices database , GCF www.globalcertificationforum.org/certification.html
3. 3GPP TS 36.521-1, LTE UE conformance specification, Part 1: RF , 3GPP www.3gpp.org/dynareport/36521-1.htm
4. 3GPP TS 38.521-1, NR UE conformance specification, FR1 standalone , 3GPP www.3gpp.org/dynareport/38521-1.htm
5. 3GPP TS 38.523-1, NR protocol conformance specification, Part 1 , 3GPP www.3gpp.org/dynareport/38523-1.htm
6. PTCRB Certification Program , PTCRB www.ptcrb.com/
7. GSMA, mobile network operator industry resources , GSMA www.gsma.com/