| Edition 29 | 5 October 2026 |
CT3’s exposure study (TR 29.830) and interworking study (TR 29.833) are both at the skeleton stage. The starting point is clear: 5G’s NEF and CAPIF, and the exposure key issues SA6 is writing above them.
In 60 seconds
FS_6G_NCE_CT, WID CP-261283, 6 June 2026 to 9 September 2027.TR 29.833, 6G interworking with external data networks. Rapporteur from ZTE.TR 29.830 studies the protocol side of network capability exposure in 6G. It builds on requirements and architecture from SA2 and SA6 and security from SA3. Report rapporteur: Yue Sun (China Telecom). The work item (FS_6G_NCE_CT, WID CP-261283) is led by Meghna Khaturia (Samsung) and runs 6 June 2026 to 9 September 2027.
Status
v0.2.0 has placeholder key issues (#X, #Y, #Z) and solutions (#A, #B, #C). No content is proposed yet.
The CT3 article on exposure frameworks, by CT3 delegates including chair Yali Yan, sets out the 5G baseline the 6G study inherits:
a single and harmonized platform for exposure of all the 3GPP capability exposure APIs. It handles publication, discovery, authentication, routing, auditing, charging and user consent. It also carries non-3GPP APIs from ETSI MEC, TM Forum and CAMARA.
The 6G questions come from SA6’s TR 23.801-02 (Edition 25): intent-based exposure, exposure to third-party AI agents, and how CAPIF evolves. If agents become API consumers, CT3 has to decide whether exposure stays REST/OpenAPI or also supports an agent protocol. That question links it to TR 29.832 (Edition 30).
TR 29.833, “Study on CT aspects of 6G Network Interworking with External Data Networks” (FS_6G_IwkExtDns_CT), is led by Xiaojian Yan (ZTE). In 5G this area is the N6 side of the core: how the network connects to external data networks and their authentication and addressing services. The report’s first version was only filed in September 2026.
Still open
Both studies depend on SA2’s architecture decision and on SA6’s exposure conclusions. Expect key issues only after SA2#178.
Watch next
TR 29.830.Sources
Report contents are read from FriendlySpec renders of the draft TRs. Drafts change at every meeting; nothing in a draft TR is agreed until its conclusions are.