Daily Dose of 6G

The four work tasks that keep the phone a phone

The radio arc is closed; TR 23.801-01 opens the architecture one. Half of it is not about AI, sensing or agents at all — it is about emergency calls, messaging, roaming, satellites and the unglamorous obligation that a 6G handset still work like a phone.

Transcribed from 3GPP’s published Release 21 timeline (© 3GPP 2026). Thirteen editions have highlighted a RAN row; this is the first on an SA one. TR 23.801-01 is a Stage 2 document, and Rel-21 SA Stage 2 complete is the milestone its architecture has to satisfy.

One study, two records, two pens

The SA2 architecture study is FS_6G_ARC, work item 1080057, approved at TSG SA#108 in June 2025 under WID SP-251633 and running 5 June 2025 to 3 March 2027. Its deliverable is TR 23.801-01, and the portal prints the title with a suffix the shorthand drops: “Study on Architecture for 6G System; Stage 2”.

This newsletter names the rapporteur for every study it covers, and here that is two names, because there are two records. The work item record gives Malla Reddy Sama of NTT DOCOMO; the specification record gives Stefan Rommer of Ericsson LM. Neither corrects the other: one is accountable to TSG SA for the study, the other for the document. NTT DOCOMO now heads the RAN1 physical layer, the FS_6G_Radio parent and this study — the deepest position any company holds in the release.

Four and four

Tao Sun, TSG SA Vice Chair, China Mobile, writing on 3gpp.org, sets out the division:

SA2’s drafting directories carry those eight as folder names, which is firmer than a summary. The Connectivity four are WT#1, WT#2, WT#7 and WT#8 — and the first of those, the baseline system itself, has been broken into sub-tasks of its own.

A folder called WT#1.4_Voice_Regulatory is this edition’s argument in one string. Every generation is sold on what is new, and every one spends a large share of its architecture effort re-establishing that emergency calls connect and that a text message arrives. 6G is doing both at once; only one of them gets a press release.

Twenty-four key issues, twenty-four folders

Each group leaves a different fingerprint on the open drafting tree. RAN4 files by agenda item, RAN3 by conference block. SA2 files by key issue. The FS_6G_ARC drafts directory holds 27 entries: General, TR, one unrelated Rel-20 item — and KI#1 through KI#24, one folder each, none skipped. Five are named for services a 5G study would recognise on sight: Voice, Emergency Voice, Location, Messaging, Other Essential/Regulatory Services for 6G.

A Nokia contribution in that same tree, filed to SA2#174’s folder for Malta in April 2026, is candid about running both halves at once: progress was “hindered for many key issues such as KI#1.1, KI#2, KI#18, KI#21 due to parallel debate, lack of clarity and varying views on AI agent integration in the network”. Two of those four are Connectivity issues. One company’s view, not an agreement — but it says the Beyond-Connectivity debate has been slowing the Connectivity work.

Ninety-four kilobytes to eighty-two megabytes

3GPP’s specification archive keeps every draft, with its size and date. For TR 23.801-01 that is an unusually legible growth curve.

(The newsletter’s own reading of primary data.) An archive size is compressed Word plus figures, not a page count, so treat the ratio loosely — but the shape is unmistakable. The first five months added a skeleton and some key issues; then, between mid-June and the end of July 2026, the document quintupled. That is the solutions phase: two dozen key issues each acquire a stack of candidate solutions and the report becomes an anthology before anyone cuts it back. Compare TR 38.760-4, still at v0.0.1. RAN4 has no inputs yet; SA2 has more than it can keep.

What the report assumes before it argues

Version 0.4.0 opens with assumptions rather than questions, and they are conservative. The 5G core’s service-based architecture is “assumed as a starting point for discussion”. The 6G RAN is “a single technology framework based on a stand-alone architecture”. The system “is assumed to maintain the RAN and CN functionality split as in 5GS”. Operator-controlled voice and video stay with IMS. And terrestrial and non-terrestrial networks are supported natively — which is why NTN is a work task and not an extension.

One detail is worth printing exactly as it stands. The scope clause cites the Stage 1 requirements the architecture must satisfy as TS 22.abc [x] — a placeholder. The study was drafted before it could name its own requirements specification, which Edition 05 covered as TS 22.270.

Three meetings, then it stops

The arithmetic is tighter than the radio study’s. FS_6G_ARC ends 3 March 2027, fifteen months before FS_6G_Radio. After SA2#176 closed on 28 August the calendar leaves three meetings: SA2#177 in October 2026, SA2#178 in November, and SA2#179 on 22–26 February 2027, which ends five days before the study is due. Each RAN working group has five meetings for its part of the radio. SA2 has three, for twenty-four key issues, in a document that has just quintupled.

Which is why the Connectivity half matters more than its billing. Something in the anthology has to be cut, and a study that runs out of meetings does not cut its regulatory obligations.