TSG RAN#111 in Fukuoka: the plenary where 6G stopped being a concept and started becoming a system

3GPP TSG RAN#111 met in Fukuoka, Japan, from March 9 to 12, 2026, right at the point where 3GPP’s 6G program had to move from broad study mode into something much more disciplined. By then, 3GPP had already framed Release 20 as the study release for 6G and Release 21 as the normative release, which meant RAN#111 was not just another quarterly checkpoint. It was one of the meetings that had to make the Release 20 study output usable for Release 21 planning.

The easiest way to understand the plenary is to look at the contribution spine. The key anchors were RP-260073 carrying TR 38.914 v0.4.0 on Study on 6G Scenarios and requirements, RP-260074 as the status report for that study, and RP-260039 on the Release 21 timeline. Around those sat the adjacent work streams that tell you what RAN thought mattered most at this point: RP-260257 / RP-260258 on ISAC, RP-260394 / RP-260773 on AI/ML for NG-RAN Phase 3, and RP-260222 / RP-260826 on Ambient IoT scope evolution. That combination is revealing. It says RAN#111 was not a plenary about one headline feature; it was a plenary about locking the moving parts together.

At the center of it all was RP-260073 / RP-260074. By RAN#111, the 6G RAN study had reached 90% completion, with the agreed baseline already covering key technical principles, deployment scenarios, and broader operational requirements. TR 38.914 also appears in the public 3GPP database as the draft report for the 6G scenarios-and-requirements study, which reinforces how central this document had become. In practice, that meant Fukuoka was no longer about whether RAN would do a 6G study. It was about which open questions still had to be narrowed before the study could close cleanly and hand over to Release 21 normative work.

The most important of those open questions was probably the least glamorous one: maximum channel bandwidth. Around the RP-260073 / RP-260074 study pair, RAN ended up resolving the 6G maximum-channel-bandwidth argument by compromise rather than vote. The outcome mattered because it imposed discipline without pretending that every issue was closed. Downlink 400 MHz channel bandwidth remained on the table, but only with explicit UE and air-interface constraints, while the uplink maximum bandwidth discussion stayed open. This was a classic 3GPP moment. The real win was not a symbolic number. The real win was preventing one parameter fight from destabilizing the study as a whole.

What made the plenary especially interesting is that the 6G discussion also started looking much more deployment-aware. RAN#111 did not stay at the level of “future radio principles.” It moved into questions that only arise when a system is becoming concrete. The plenary tasked RAN1 and RAN2 to study 6G-6G spectrum aggregation for non-collocated FR1-FR2 deployments, and it asked RAN1 to provide a further MRSS performance assessment by September. That is the kind of detail that rarely gets top billing outside the room, but it is exactly how a generation becomes standardizable. Once plenary discussion starts assigning work on non-collocated spectrum use and time-bound performance follow-up, the conversation has moved beyond aspiration.

The AI/ML story at RAN#111 was just as important. The TDoc flow shows RP-260394 and RP-260773 carrying the active AI/ML track for NG-RAN Phase 3, but the plenary result went further than simply keeping the study alive. RAN assigned lead working groups for 6G AI/ML use cases and approved the follow-up RAN3 AI/ML work item. That is a significant step. AI/ML only becomes real in 3GPP when it stops being a theme and starts being decomposed into architecture, interface behavior, data handling, and ownership by specific WGs. Fukuoka pushed AI/ML firmly in that direction.

ISAC followed a similar pattern. The anchor contributions were RP-260257 / RP-260258, and the plenary outcome was not vague encouragement but a push to closure: RAN3 was given additional guidance to finish the ISAC architecture study. That is a telling signal. ISAC is no longer being treated as an eye-catching 6G extra. At RAN#111 it was treated like a real architecture problem that needs completion conditions, internal consistency, and a path to specification-grade work.

NTN, meanwhile, was handled with a level of realism that deserves more attention. One of the quieter but more strategic outcomes from the plenary was agreement on a structured regulatory survey path for NTN use on terrestrial bands. That is exactly the right instinct for this phase. Once a topic becomes serious inside 3GPP, spectrum coexistence and regulatory timing stop being footnotes and become part of the engineering problem itself. RAN#111 did not slow NTN down; it forced NTN to mature.

It is also worth stressing that Fukuoka was not a 6G-only plenary. Ambient IoT remained a real Release 20 track, and the contribution pair RP-260222 / RP-260826 shows it was not being handled as filler work. The plenary completed the study on outdoor active devices and updated the work item accordingly. That matters because it shows RAN keeping one foot in near-term commercial evolution even while the other foot is stepping into 6G. Ambient IoT is exactly the kind of feature area that tests whether a release is responding to ecosystem and deployment needs, not just to future-generation branding.

Another reason RAN#111 mattered is that it tied technical convergence to schedule discipline. That is why RP-260039, the Release 21 timeline contribution, deserves more attention than it might get in a casual retelling. Public 3GPP planning had already made clear that Release 21 would be the official start of normative 6G work and that the Release 21 timeline was expected to be settled by around mid-2026. In that context, RP-260039 was not administrative trivia. It was part of the same strategic equation as RP-260073 and RP-260074. A study can be 90% complete and still fail to shape a release if the timing is not aligned. Fukuoka was one of the meetings trying to make sure that would not happen.

And then there is the part of the plenary story that outsiders usually miss: the enormous maintenance and conformance tail that sits beneath the strategic headline items. RAN#111 was loaded with that work. Just in the NTN and IoT NTN stream, you can see contributions like R4-2600124 and R4-2600125 on TS 36.102 NTN, R4-2602044 and R4-2602843 on IoT-NTN demodulation and conformance performance, R5-260351 on orbital ephemeris updates for IoT NTN, R5-261656 on time-drift handling, and R5-261615 on IoT NTN performance test limits, plus a long run of 36.521-x and 36.523-x CRs. None of that is glamorous. All of it is essential. A standard only becomes real when it can be tested, corrected, and shipped.

That is the best way to read TSG RAN#111 as a whole. It was not the plenary where 6G was “announced.” That had already happened in roadmap terms. It was the plenary where 6G started to lose its rhetorical freedom and gain engineering shape. RP-260073 / RP-260074 narrowed the requirement study. The bandwidth compromise imposed realism. RP-260394 / RP-260773 pushed AI/ML toward real ownership. RP-260257 / RP-260258 kept ISAC on an architectural path. RP-260222 / RP-260826 showed that Release 20 still had to deliver commercially relevant evolution. And RP-260039 made it clear that none of this mattered unless the Release 21 handoff could be made on time.

That is why Fukuoka deserves to be remembered. Not for a single dramatic approval, but for something harder: it made 6G look standardizable.