3GPP Scout / Meetings / SA2 #176

SA2 #176Final

SA2 #176: what was agreed

24 August to 28 August 2026Prague3GPP TSG SA WG2Last updated 2026-09-29

At a glance

  1. The register confirms approval of the KI#1.1 interim-conclusion pCR, submitted by Nokia with ten co-submitters, and the 2A2 modular-NAS update. The supplied evidence does not expose the conclusion text, and these approvals are not normative decisions.

    Sources: S2-2609156, Nokia (pCR. Register status: approved at S2-176.); S2-2609158, Huawei (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © Nokia, Huawei.

  2. Approved pCR text covers both embedded intent handling in other 6G CN NFs and a separate 6G CN AI domain. The register records study-TR approvals, not a choice between these approaches.

    Sources: S2-2609043, InterDigital (pCR. Register status: approved at S2-176.); S2-2609044, Nokia (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © InterDigital, Nokia.

  3. Approved ISAC pCRs add a sensing-UE mobility scenario, non-3GPP sensing data, and general 6G ISAC design text. These are study-TR approvals, not a normative architecture decision.

    Sources: S2-2609119, ZTE (pCR. Register status: approved at S2-176.); S2-2609215, Qualcomm (pCR. Register status: approved at S2-176.); S2-2609250, Xiaomi (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © ZTE, Qualcomm, Xiaomi.

TDocs registered
2,538
Decisions read
38
Agreements explained
6
Points still open
3

Your topic

Follow a topic and get its next outcome by email.

Scout emails you when a new agreement or decision on it is recorded, with the source for each. Or ask Scout and get an answer that cites the exact TDoc. Free to start.

  • Study on Architecture for 6G System (FS_6G_ARC) - support for control signalling for 6G SystemFollowAsk Scout
  • Study on Architecture for 6G System (FS_6G_ARC) - AI for 6G architectureFollowAsk Scout
  • Study on Architecture for 6G System (FS_6G_ARC) - Integrated Sensing and CommunicationFollowAsk Scout
  • Study on Architecture for 6G System (FS_6G_ARC) - QoS Framework for 6GFollowAsk Scout
  • Should 6G NAS evolve from 5G NAS or use modular NAS with a separate SRF? Ericsson, Huawei (with HiSilicon, Deutsche Telekom, CATT, HONOR, vivo, ZTE, IIT Bombay, Reliance Jio, Xiaomi, ETRI, OPPO)Ask Scout

Another topic or company? Follow it

What was agreed

Agenda itemTopicTDocsAgreed hereStill open
20.6.1Study on Architecture for 6G System (FS_6G_ARC) - support for control signalling for 6G System13831
20.6.18Study on Architecture for 6G System (FS_6G_ARC) - AI for 6G architecture21821
20.6.20Study on Architecture for 6G System (FS_6G_ARC) - Integrated Sensing and Communication14111
Figure 1. The agenda items this page covers. TDocs counts every document registered under the item. Agreed here and Still open count the points this page explains.

20.6.1Study on Architecture for 6G System (FS_6G_ARC) - support for control signalling for 6G System

pCR approved (text for the study TR, not normative)

A 6G architecture proposal was approved

It updates Solution Variant 2A1 for Key Issue 1.1.

Sources: S2-2609027, Nokia (pCR. Register status: approved at S2-176.); S2-2609029, vivo (pCR. Register status: approved at S2-176.); S2-2609033, Xiaomi (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © Nokia, vivo, Xiaomi.

pCR approved (text for the study TR, not normative)

Interim conclusion for key issue 1.1 approved

The approved change records an interim conclusion for this key issue.

Sources: S2-2609156, Nokia (pCR. Register status: approved at S2-176.); S2-2609158, Huawei (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © Nokia, Huawei.

pCR approved (text for the study TR, not normative)

Interim conclusion for key issue 1.2 approved

The approved change records an interim conclusion for this key issue.

Source: S2-2609034, Samsung (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © Samsung.

20.6.18Study on Architecture for 6G System (FS_6G_ARC) - AI for 6G architecture

pCR approved (text for the study TR, not normative)

Intent handling can be embedded in other 6G core functions

The approved update covers handling requests that include intent.

Sources: S2-2609043, InterDigital (pCR. Register status: approved at S2-176.); S2-2609044, Nokia (pCR. Register status: approved at S2-176.); S2-2609048, Google (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © InterDigital, Nokia, Google.

pCR approved (text for the study TR, not normative)

An update on AI techniques was approved

The approved update concerns Solution Variant 15.

Sources: S2-2609051, Samsung (pCR. Register status: approved at S2-176.); S2-2609053, vivo (pCR. Register status: approved at S2-176.); S2-2609054, CATT (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © Samsung, vivo, CATT.

20.6.20Study on Architecture for 6G System (FS_6G_ARC) - Integrated Sensing and Communication

pCR approved (text for the study TR, not normative)

6G sensing study adds UE mobility scenario

The approved change adds the scenario under key issue 20, bullet 2.

Sources: S2-2609119, ZTE (pCR. Register status: approved at S2-176.); S2-2609215, Qualcomm (pCR. Register status: approved at S2-176.); S2-2609250, Xiaomi (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © ZTE, Qualcomm, Xiaomi.

Who pushed what

20.6.1Study on Architecture for 6G System (FS_6G_ARC) - support for control signalling for 6G System

Proposed

Should 6G NAS evolve from 5G NAS or use modular NAS with a separate SRF?

The excerpts show parallel solution variants, not a recorded choice. Ericsson's item updates existing SV#1.1.1 and was not treated, which is not rejection.

EricssonHuawei (with HiSilicon, Deutsche Telekom, CATT, HONOR, vivo, ZTE, IIT Bombay, Reliance Jio, Xiaomi, ETRI, OPPO)

Compare the 2 proposals
CompanyWhat they proposeSource
EricssonEricsson's not-treated editor-note update includes existing SV#1.1.1 text on 5G-core and NAS evolution.
Their words
The core network and NAS signalling for 6G system is proposed to be an evolution for 5G core and 5G NAS respectively.
S2-2607217paragraph 58 · register: not treated
Huawei (with HiSilicon, Deutsche Telekom, CATT, HONOR, vivo, ZTE, IIT Bombay, Reliance Jio, Xiaomi, ETRI, OPPO)Huawei with co-submitters separates MM in the AMF from signalling routing in a new SRF.
Their words
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 [...]
S2-2609158paragraph 72 · register: approved

20.6.18Study on Architecture for 6G System (FS_6G_ARC) - AI for 6G architecture

Proposed

Should AI capability sit in a separate CN domain or within 6G CN NFs?

The contributions describe a separated AI domain and AI-capable NFs handling requests without intent. The supplied evidence does not record a choice between these approaches.

Nokia (with NVIDIA, Federated Telecoms Hub, T-Mobile USA, AT&T, Qualcomm, Verizon, Deutsche Telekom, Turkcell, Ericsson, BT, Google)Samsung

Compare the 2 proposals
CompanyWhat they proposeSource
Nokia (with NVIDIA, Federated Telecoms Hub, T-Mobile USA, AT&T, Qualcomm, Verizon, Deutsche Telekom, Turkcell, Ericsson, BT, Google)Nokia and co-submitters describe separate 6G CN PS and AI domains.
Their words
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.
S2-2609044paragraph 47 · register: approved
SamsungSamsung's not-treated proposal says NFs with AI capabilities may handle requests without intent.
Their words
The 6G UE and AF are agnostic to whether specific requests without intent are handled by NFs with AI capabilities in 6G CN.
S2-2607297paragraph 11 · register: not treated

20.6.1Study on Architecture for 6G System (FS_6G_ARC) - support for control signalling for 6G System

Proposed

How should UE-CN control signalling for operator services be transported?

The contributions describe NAS signalling through an SDMF and a new interface between the UE and an intermediate NF. They do not establish a selected mechanism.

Huawei (with HiSilicon, China Mobile, CATT, vivo)Samsung

Compare the 2 proposals
CompanyWhat they proposeSource
Huawei (with HiSilicon, China Mobile, CATT, vivo)Huawei and co-submitters describe NAS signalling between the UE and SDMF for discovery and authorization.
Their words
The UE and the SDMF use NAS signalling to support the generic mechanism for service discovery and service authorization.
S2-2609035paragraph 65 · register: approved
SamsungSamsung's solution introduces a UE-to-intermediate-NF signalling interface.
Their words
A new signalling interface between UE and the intermediate NF is introduced to enable common service authorization and discovery for operator service.
S2-2609164paragraph 29 · register: approved

Company contributions to 3GPP TSG SA WG2 #176. Each TDoc is © the company named in its row. These are proposals, not decisions.

Still open

Still open

  • The supplied register entries do not state which KI#1.1 NAS design is selected.

    Sources: S2-2609027, Nokia (pCR. Register status: approved at S2-176.); S2-2609156, Nokia (pCR. Register status: approved at S2-176.); S2-2609158, Huawei (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © Nokia, Huawei.

  • The register records approvals for embedded intent handling and a separate AI domain, but no choice between them.

    Sources: S2-2609043, InterDigital (pCR. Register status: approved at S2-176.); S2-2609044, Nokia (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © InterDigital, Nokia.

  • The supplied register confirms approved mobility, non-3GPP data, and general-design updates, but names no selected ISAC architecture.

    Sources: S2-2609119, ZTE (pCR. Register status: approved at S2-176.); S2-2609215, Qualcomm (pCR. Register status: approved at S2-176.); S2-2609250, Xiaomi (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © ZTE, Qualcomm, Xiaomi.

What to watch next meeting

  • Track whether later KI#1.1 text identifies a selected NAS design across the approved variant updates.

    Sources: S2-2609156, Nokia (pCR. Register status: approved at S2-176.); S2-2609158, Huawei (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © Nokia, Huawei.

  • Track whether later KI#18 text selects a separated AI domain or embedded intent-handling architecture.

    Sources: S2-2609043, InterDigital (pCR. Register status: approved at S2-176.); S2-2609044, Nokia (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © InterDigital, Nokia.

  • Check whether later text adds detail beyond the approved sensing-UE mobility scenario.

    Source: S2-2609119, ZTE (pCR. Register status: approved at S2-176.). 3GPP TSG SA WG2 #176. © ZTE.

Sources

All 19 TDocs cited
  • S2-2609156 [KI#1.1, Bullet all, Conclusion] Interim conclusion for KI#1.1. Nokia (with Deutsche Telekom, Qualcomm, vivo, Samsung, CATT, Ericsson, Huawei, HiSilicon, MediaTek, Apple). pCR. Register status: approved at S2-176.
  • 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-2609043 [KI#18, Solution Variant #18.2, Update] Intent handling capability embedded in other 6G CN NFs, to handle requests including intent. InterDigital (with Oracle). pCR. Register status: approved at S2-176.
  • S2-2609044 [KI#18, Solution Variant #3 update] New separated domain from PS domain, within 6G CN. Nokia (with NVIDIA, Federated Telecoms Hub, T-Mobile USA, AT&T, Qualcomm, Verizon, Deutsche Telekom, Turkcell, Ericsson, BT, Google). pCR. Register status: approved at S2-176.
  • S2-2609119 [KI#20, Bullet 2, 20.0 new] Adding Sensing UE mobility scenario to 6.20.0. ZTE (with IIT Bombay, Apple, Xiaomi, vivo, Huawei, HiSilicon, CATT, InterDigital). pCR. Register status: approved at S2-176.
  • 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-2609027 [KI#1.1, Solution Variant #2A1, update] Solution 2A1 update proposal. Nokia (with Deutsche Telekom). pCR. Register status: approved at S2-176.
  • S2-2609029 [KI#1.1, Solution Variant #2B1, update] Solution proposal on NAS security. vivo (with IIT Bombay, Huawei, HiSilicon, Nokia). pCR. Register status: approved at S2-176.
  • S2-2609033 [KI#1.1, Solution Variant #1.1.4 update] Update on 6G N2 based Handover. Xiaomi (with LG Electronics, vivo, Ericsson, Huawei, HiSilicon). pCR. Register status: approved at S2-176.
  • S2-2609034 [KI#1.2, Conclusion] Interim conclusion for KI#1.2. Samsung. 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-2609051 [KI#18, Sol var#15, update] AI techniques. Samsung (with China Mobile, vivo, Huawei, HiSilicon, Ewha Womans University, NTT DOCOMO, Nokia, China Telecom, Lenovo, ETRI, LG Uplus). pCR. Register status: approved at S2-176.
  • S2-2609053 [KI#18, Solution variant #18.17, #18.18 update] Solution update for AI capability access. vivo (with ZTE, Oracle, China Mobile, Tejas Networks, Huawei, HiSilicon, Google, Samsung, ETRI, Ewha Womans University). pCR. Register status: approved at S2-176.
  • S2-2609054 [KI#18, Solution variant #18.19 update] Capability exchange and NW-Agent based procedure for request-based monitoring. CATT (with vivo, Huawei, HiSilicon, NTT DOCOMO). 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-2607297 [KI#18, Sol var#10, update] Update for architecture principles for requests without intent. Samsung. pCR. Register status: not treated at S2-176. No decision recorded in the register.
  • 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.

Coverage: SA2 #176 (Prague, 2026-08-24 to 2026-08-28), agenda items 20.6.1, 20.6.18, 20.6.20.

What this page read and what it leaves out

Scout read 38 recorded decisions and 141 company positions or contribution passages on these agenda items (catalog synced 2026-09-29) and cites 15 decisions and 6 positions from 19 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.

The supplied decision items are register records, not chair or session reports.

Register evidence confirms pCR approval into the study TR, not normative decisions.

Company inputs marked not treated are pre-meeting proposals, not evidence of meeting discussion.

Next outcome

Get the SA2 #177 outcome by email.

Scout emails you when SA2 records a new agreement or decision, with the source for each. Free to start.

Built by 3GPP Scout from the public meeting record (2538 TDocs registered, catalog synced 2026-09-29). Significance scores compare each topic's activity at this meeting with the group's topics over the past 12 months. Excerpts are at most 25 words and link to the original on the 3GPP file server.