KI#1.1 interim conclusion. An interim conclusion pCR for KI#1.1 was approved into the study TR. The register entry does not specify its technical principles.
KI#1.2 interim conclusion. An interim conclusion pCR for KI#1.2 was approved into the study TR. This is approval of study text, not a normative operator-services mechanism.
AI architecture variants. Updates covering a separated AI domain and intent handling embedded in other 6G core network functions were both approved as study TR text.
AI study summary and roaming. A high-level summary baseline for KI#18 solution variants and a roaming solution variant for the AI domain were approved into the study TR.
Should 6G NAS evolve 5G NAS or separate signalling routing from mobility management?
In a proposal submitted but not treated, Ericsson proposed evolving 5G core and NAS. The approved Huawei and co-submitter pCR instead describes a dedicated Signalling Routing Function as a study variant, not a selected design.
EricssonEricsson proposed an evolved 5G core and NAS in a contribution not treated.
The core network and NAS signalling for 6G system is proposed to be an evolution for 5G core and 5G NAS respectively. [...]
Huawei (with HiSilicon, Deutsche Telekom, CATT, HONOR, vivo, ZTE, IIT Bombay, Reliance Jio, Xiaomi, ETRI, OPPO)Huawei and co-submitters placed signalling routing in a dedicated SRF.
In this reference architecture, 6G MM and signalling routing functionalities are separated into different network entities: 6G MM is kept in the 6G AMF, while [...]
How should operator-service discovery and authorization reach the UE?
Both approved study variants address common operator-service mechanisms. Huawei and co-submitters describe NAS signalling with an SDMF, while Samsung describes a new signalling interface to an intermediate network function.
Huawei (with HiSilicon, China Mobile, CATT, vivo)Huawei and co-submitters use NAS between the UE and SDMF.
The UE and the SDMF use NAS signalling to support the generic mechanism for service discovery and service authorization.
How should intent handling relate to the 6G core architecture?
The Nokia-led approved pCR depicts separate PS and AI domains. The approved China Mobile and co-submitter pCR assumes an intent serving function that interacts with other core network functions over 6G SBI. These descriptions do not establish an exclusive choice.
Nokia (with NVIDIA, Federated Telecoms Hub, T-Mobile USA, AT&T, Qualcomm, Verizon, Deutsche Telekom, Turkcell, Ericsson, BT, Google)Nokia and co-submitters depict separated PS and AI domains.
Figure 6.18.3.1.1-1 provides an overview of the 6G CN architecture with separated 6G CN PS and 6G CN AI domains.
China Mobile (with ETRI, IIT Bombay, CAICT, China Unicom, China Telecom, Huawei, HONOR, ZTE, CATT, OPPO, Xiaomi, Tejas Networks, Futurewei, vivo)China Mobile and co-submitters assume SBI interaction for an intent serving function.
NOTE X: It is assumed that the intent serving function interacts with other 6G NF via 6G SBI.
Should sensing UE mobility work be documented under sensing architecture variants or variant 20.5?
These proposals were submitted to the meeting but not treated. vivo argued that mobility solutions depend on architecture and do not belong under variant 20.5; ZTE proposed placing SenF re-location in clause 20.5.
vivovivo argued against documenting the mobility solutions under variant 20.5.
Also, based on Observation #2, one can see solutions for Bullet #2 are NOT independent of the architecture and hence, cannot be documented under Solution [...]
S2-2609215 [KI#20, bullet 3, new] New solution variant for supporting non 3GPP sensing data. Qualcomm (with Ericsson, Xiaomi). pCR. Register status: approved at S2-176.
S2-2609250 [KI#20, solution variant#6.20.2.1. update] Solution on general design for 6G ISAC system. Xiaomi (with OPPO, China Mobile, ZTE, Huawei, vivo). pCR. Register status: approved at S2-176.
S2-2609136 [KI#18, Solution variant #18.0, update] Baseline for high-level summary of solution variants. Huawei. pCR. Register status: approved at S2-176.
S2-2609048 [KI#18, Solution Variant #18.8 New]: Support of roaming for AI domain. Google (with ZTE, Ericsson, AT&T, T-Mobile USA, vivo, Huawei, HiSilicon, NTT DOCOMO, Nokia, IIT Bombay). pCR. Register status: approved at S2-176.
S2-2607217 [KI#1.1, Solution variant #1.1.1, update] Update to resolve ENs. Ericsson. pCR. Register status: not treated at S2-176. No decision recorded in the register.
S2-2609158 [KI#1.1, Solution Variant 2A2 update] Update solution of NAS routing terminated at 6G SRF. Huawei (with HiSilicon, Deutsche Telekom, CATT, HONOR, vivo, ZTE, IIT Bombay, Reliance Jio, Xiaomi, ETRI, OPPO). pCR. Register status: approved at S2-176.
S2-2609035 [KI#1.2, Solution Variant #1.2.1 update] Resolve some ENs and update solution details. Huawei (with HiSilicon, China Mobile, CATT, vivo). pCR. Register status: approved at S2-176.
S2-2609164 [KI#1.2, Solution variant #1.2.4, update] Resolution of Editor s notes. Samsung. pCR. Register status: approved at S2-176.
S2-2609247 [KI#18, Solution variant #18.1, update] Updates for SV#18.1. China Mobile (with ETRI, IIT Bombay, CAICT, China Unicom, China Telecom, Huawei, HONOR, ZTE, CATT, OPPO, Xiaomi, Tejas Networks, Futurewei, vivo). pCR. Register status: approved at S2-176.
S2-2607730 [KI#20, Bullet#2] Discussion on documentation of solutions for Bullet #2. vivo. Contribution. Register status: not treated at S2-176. No decision recorded in the register.
S2-2607527 [KI#20, Bullet 2, discussion] Discussion and proposal on the Sensing UE mobility solution variant. ZTE. Contribution. Register status: not treated at S2-176. No decision recorded in the register.
S2-2609157 [KI#1.1, Solution Variant #1.1.1 update] Addressing editor s notes for Solution Variant 1.1.1. Qualcomm (with NTT DOCOMO, Ericsson, Apple). pCR. Register status: approved at S2-176.
Coverage: SA2 #176 (Prague, 2026-08-24 to 2026-08-28), agenda items 20.6.1, 20.6.18, 20.6.20. Scout read 38 recorded decisions and 141 company positions or contribution passages on these agenda items (catalog synced 2026-09-29) and cites 12 decisions and 8 positions from 18 TDocs. Every quoted passage was matched verbatim against the TDoc text; the summaries around the quotes are Scout's reading. Register statuses are copied from the 3GPP TDoc register: not treated means a document was not handled on its own, though its content may have fed feature-lead summaries or merged revisions. Not covered: other agenda items and meetings, plenary TDocs and plenary decisions after the meeting, email discussions after the meeting, and anything not yet in the chair notes or register.
Decision evidence for these topics consists of register outcomes. The register entries do not expose the technical content of the approved interim conclusions or record explicit FFS decisions.
The sensing mobility documentation dispute is visible only in contributions marked not treated, so this brief does not present it as a meeting discussion or outcome.
Hottest topics
Study on Architecture for 6G System (FS_6G_ARC) - support for control signalling for 6G Systemsignificance 59 of 100, 138 TDocs
Study on Architecture for 6G System (FS_6G_ARC) - AI for 6G architecturesignificance 57 of 100, 218 TDocs
Study on Architecture for 6G System (FS_6G_ARC) - Integrated Sensing and Communicationsignificance 56 of 100, 141 TDocs
Study on Architecture for 6G System (FS_6G_ARC) - QoS Framework for 6Gsignificance 56 of 100, 118 TDocs
Study on Architecture for 6G System (FS_6G_ARC) - Migration and Interworkingsignificance 55 of 100, 70 TDocs
Previous: SA2 #175 (18 May 2026)All meetingsNext: SA2 #177 (12 October 2026)
Built by 3GPP Scout from the public meeting record (2538 TDocs registered, catalog synced 2026-09-29). Significance scores rank topics by decisions, contention, breadth and volume. Excerpts are at most 25 words and link to the original on the 3GPP file server.