Read this before quoting the page
Two independent accounts agree on the CU-DU option and on P2P-over-SBI, and RAN3's FTP listing independently shows matching conference blocks. That is three-way alignment on topics and two-way on outcomes — it is still not TR text. A folder proves a group allocated discussion time; it proves nothing about the outcome.
Two base-station design options
Ericsson: the base station as a single unit, as agreed at the start of the study; or a higher-layer split dividing processing into a distributed unit and a centralised unit, agreed in June 2026.
The RU becomes a named seam
Xingqin Lin (NVIDIA): "In 6G, the RU will be recognized as a distinct logical unit inside the aNB. The recognition is intentionally scoped: the RU functions and the interface between the RU and the rest of the aNB remain outside 3GPP specification." 3GPP names the seam and declines to specify it; details go to the O-RAN Alliance.
Point-to-point, not service-based
For connectivity services, both sources report a P2P design between the aNB and a 6G CN entity rather than a service-based interface — with the protocols to be determined later in the study.
Interfaces in scope
CU-DU; CU-CP/CU-UP; RAN-to-core; and aNB-to-aNB.
Live conference blocks
RAN3's own drafts folder lists CB #8_6GCharacteristsAndPerformance, #9_6G_SA2Reply, #10_6GSBI_NewSection, #11_6GHLS, #12_ISAC_arch, #13_ISACproc, #20_6GPaging, and two 6G AI/ML blocks.