Standards & Generations · Explainer

How a Standard Gets Written

From chaos to consensus

How a Standard Gets Written
Figure 1 — Working groups, releases and why interoperability is the whole point.

A wireless standard begins not with a document but with a problem: two devices made by different companies, in different countries, need to exchange data flawlessly over air. Without a shared specification governing every detail — channel bandwidth, frame timing, coding scheme, error handling — they cannot. Interoperability is not a nice-to-have; it is the entire reason the process exists.

The body that writes most of the cellular world's air-interface standards is 3GPP, the 3rd Generation Partnership Project — a collaboration of regional standards development organisations including ETSI in Europe. 3GPP does not sell anything and does not certify devices. It produces technical specifications that any manufacturer can implement, and it organises that work into releases: numbered snapshots of the specification frozen at a point in time so that vendors can build against a stable target.

Work begins inside working groups, each with a defined scope. Some handle the radio layer, others the core network, others codecs or security. A company — a network operator, a chipmaker, a device vendor — brings a contribution: a written technical proposal arguing for a particular approach to a problem. Nothing is decided by executive fiat; proposals are debated, modified and, where consensus fails, put to a vote. A controversial feature may survive dozens of rounds of revision before it stabilises.

Once a feature passes within its working group it moves upward for integration and consistency checks across the whole release. When the release is frozen, the specifications become the shared blueprint. The next release opens immediately, carrying forward whatever the previous one left unfinished and adding new work items.

Nothing is decided by executive fiat; proposals are debated, modified and, where consensus fails, put to a vote.

From this piece

This machinery is slow by design. Reaching consensus among hundreds of participating organisations across competing commercial interests takes time. But the slowness buys something: when a device built in one country connects to a network built by a different vendor on another continent, it works. That outcome — unremarkable to the user, extraordinary in its engineering coordination — is exactly what the process was designed to produce.

The working group

Where the text is written

A standing group of delegates from operators, vendors and research bodies. It meets, argues over contributions, and agrees text by consensus rather than by vote wherever possible.

Role, not an individual — Spectrum Notes names no delegates.

The rapporteur

Who holds the pen

The delegate responsible for a single work item: collecting comments, reconciling contradictory proposals and bringing a clean draft back to the group.

Role, not an individual — Spectrum Notes names no delegates.

Organisations named in this piece, for your own reading: 3GPP ↗ ETSI ↗ ITU ↗