Daily Dose of 6G

Release 20 is not a 6G release

It is the study phase — twenty-seven parallel investigations that produce no normative 6G specification whatsoever. Understanding why that is deliberate is the prerequisite for reading everything that follows.

Transcribed from 3GPP’s published Release 21 timeline (© 3GPP 2026). Rel-20 is the 6G study phase; Rel-21 is the first 6G normative release.

The structural fact

3GPP splits a generation into a study phase and a normative phase. Release 20 is the former. Its 6G output is entirely Technical Reports — TR 22.870, TR 38.914, TR 38.760-x, TR 23.801-01, TR 33.801-01 and the rest. Not one of them is implementable. They exist to converge the industry on what problem is being solved before anyone writes a bit-level definition.

Roughly half of Rel-20 working-group time goes to these 6G studies. The other half continues 5G-Advanced evolution — which is why Rel-20 reads as two releases stapled together, and why its work plan confuses anyone who misses the split.

Where the twenty-seven studies sit

Two are already done. TR 22.870 — 590+ pages of use cases and service requirements, rapporteur Xiaonan Shi (China Mobile) — was approved at TSG#111 in Fukuoka, March 2026. TR 38.914, rapporteur Xiaoran Zhang (China Mobile), reached v1.0.0 at RAN#112 in Singapore on 14 June 2026. The rest close between March 2027 and September 2027.

Why the study phase is where decisions get made

A common misread is that studies are preamble and the normative release is where it counts. The opposite is closer to true. By the time TR 23.801-01 closes in March 2027, SA2 will have resolved its ~24 key issues into agreed conclusions — and Rel-21 Stage 2 largely transcribes those into TS 23.xxx procedures. The same holds for the radio: whatever TR 38.760-1 concludes on waveform, numerology and channel coding becomes the physical layer.

If you want to influence 6G, the window is now and it closes in early 2027. If you want to predict 6G, the study TRs are the highest-signal documents available.

One live tension worth watching

Rel-20 carries an unusual amount of AI scope, and it is not confined to one group. SA1 wrote network AI agents, third-party AI agents, and AI model training and inferencing into TR 22.870 as functional requirements. SA2 has four “beyond connectivity” work tasks including AI and computing coordination across UE, core and application server. CT3 runs TR 29.832, “Study on the Protocol for Artificial Intelligence in 6G”, rapporteur Apostolos Papageorgiou (Nokia Germany), and is openly weighing whether to adopt IETF agentic protocols, define 3GPP-specific ones, or assemble something from Agent2Agent, ANP, AGNTCY and MCP.

Three groups converging on the same question — what is an AI agent to a mobile network? — from requirements, architecture and protocol angles at once. Whether they converge on one answer is the most interesting open question in the release.