SA2 #177 · 2026-10-19

Top 3 things that happened on AI in the 6G and 5G core at SA2 #177

The verdict

  1. SA2 approved interim conclusions on operator control of AI use (aspect #18.22) as study text for TR 23.801-01, with OAM details left FFS in SA5. (S2-2611398 (pCR. Register status: approved at S2-177.). S2-2611398, Samsung, 3GPP TSG SA WG2 #177. © Samsung. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2611398.zip)
  2. An update to solution variant #18.1, a dedicated intent-serving network function, was also approved as study text. This refines the solution description and does not select it over other variants. (S2-2611402 (pCR. Register status: approved at S2-177.). S2-2611402, China Mobile, 3GPP TSG SA WG2 #177. © China Mobile. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2611402.zip)
  3. Competing KI#18 conclusion pCRs on the AI domain, UE intent transport and ML model provisioning were not treated or postponed. Agreements beyond the register outcomes are pending the meeting report. (S2-2610362 (Nokia (with Federated Telecoms Hub, Qualcomm, Ericsson, InterDigital, Deutsche Telekom, NVIDIA, T-Mobile USA, Turkcell); register: not treated). S2-2610362. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2610362.zip; S2-2611367 (China Telecom (with Ericsson, AT&T, T-Mobile USA, Deutsche Telekom, ETRI, LG Uplus, Ewha Womans University, China Mobile, NTT DOCOMO, Qualcomm, Google); register: postponed). S2-2611367. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2611367.zip)

What was agreed

Operator controllability study text. Interim conclusions on aspect #18.22 controllability were approved into TR 23.801-01 as study text, with OAM details FFS in SA5.
pCR approved (text for the study TR, not normative); 23.801-01, Rel-20[KI#18, Conclusion] Interim conclusions for #18.22 (controllability). S2-2611398 (pCR. Register status: approved at S2-177.). S2-2611398, Samsung, 3GPP TSG SA WG2 #177. © Samsung. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2611398.zip
Intent architecture solution update. An update to solution variant #18.1, a dedicated intent-serving network function, was approved into TR 23.801-01 as study text.
pCR approved (text for the study TR, not normative); 23.801-01, Rel-20[KI#18, Solution variant #18.1, update] Updates for solution variant #18.1. S2-2611402 (pCR. Register status: approved at S2-177.). S2-2611402, China Mobile, 3GPP TSG SA WG2 #177. © China Mobile. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2611402.zip
Adjacent, non-AI: area-based UPF event exposure. A Rel-20 CR clarifying UPF event exposure related to an Area of Interest reached working-group agreement, subject to plenary approval.
CR agreed at working-group level (subject to plenary approval); 23.502, Rel-20Clarification on UPF event exposure service related with AOI in R20 23.502. S2-2610970 (CR. Register status: agreed at S2-177.). S2-2610970, China Mobile, 3GPP TSG SA WG2 #177. © China Mobile. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2610970.zip
Abnormal traffic analytics. A Rel-20 CR clarifying Abnormal User Plane Traffic Analytics reached working-group agreement, subject to plenary approval.
CR agreed at working-group level (subject to plenary approval); 23.288, Rel-20Clarification on Abnormal User Plane Traffic Analytics. S2-2610891 (CR. Register status: agreed at S2-177.). S2-2610891, CATT, 3GPP TSG SA WG2 #177. © CATT. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2610891.zip
UPF event exposure parameters. A Rel-20 CR adding missing UPF event exposure parameters reached working-group agreement, subject to plenary approval.
CR agreed at working-group level (subject to plenary approval); 23.502, Rel-20Addition of missing parameters for UPF event exposure. S2-2610892 (CR. Register status: agreed at S2-177.). S2-2610892, vivo, 3GPP TSG SA WG2 #177. © vivo. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2610892.zip

Who pushed what

Where should the 6G core handle requests with intent?

The approved variant #18.1 update describes intent-serving function (ISF) roles, which refines that solution without selecting it. A nine-company conclusion pCR, not treated, proposes an optional AI domain, and a postponed SV#18.2 update includes PCF-embedded planning among its subvariants.

China Mobile (with CAICT, China Unicom, China Telecom, Huawei, ZTE, CATT, OPPO, Xiaomi, Tejas Networks, Futurewei, HONOR, NTT DOCOMO)China Mobile and co-submitters describe one or two ISF instances with two logical roles.
Two deployment options are considered in this figure, in one option, only one instance of ISF is deployed in the network, therefore IHLF and IFLF [...]
S2-2611402, paragraph 200. S2-2611402, China Mobile, 3GPP TSG SA WG2 #177. © China Mobile. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2611402.zip; register: approved
Nokia (with Federated Telecoms Hub, Qualcomm, Ericsson, InterDigital, Deutsche Telekom, NVIDIA, T-Mobile USA, Turkcell)Nokia and eight co-submitters, including InterDigital, propose an optional AI domain separate from the PS domain in a not-treated conclusion pCR.
A new optional 6G CN AI domain which is separated from 6G CN PS domain is specified. [...]
S2-2610362, paragraph 25. S2-2610362, Nokia, 3GPP TSG SA WG2 #177. © Nokia. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2610362.zip; register: not treated
InterDigital (with Ofinno)InterDigital and Ofinno's postponed SV#18.2 update lists PCF-embedded AI agent planning as one subvariant.
The 6G PCF uses embedded AI Agent capabilities to derive the set of procedure elements that are required to satisfy the intent, and it builds [...]
S2-2611322, paragraph 29. S2-2611322, InterDigital, 3GPP TSG SA WG2 #177. © InterDigital. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2611322.zip; register: postponed

Should UE intent use the control plane or user plane?

No transport outcome was recorded. A nine-company conclusion pCR, not treated, proposes user-plane transport toward an AI domain, while China Mobile proposes NAS toward a network agent function.

Nokia (with Federated Telecoms Hub, Qualcomm, Ericsson, InterDigital, Deutsche Telekom, NVIDIA, T-Mobile USA, Turkcell)Nokia and eight co-submitters propose UP transport to the AI domain in a not-treated conclusion pCR.
S2-2610362, paragraph 25. S2-2610362, Nokia, 3GPP TSG SA WG2 #177. © Nokia. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2610362.zip; register: not treated
China MobileChina Mobile proposes a dedicated or existing NAS message to carry UE intent to a network agent function.
Principle 4: UE intent can be transported to the NW-Agent function either by encapsulating it in a dedicated NAS message or by piggybacking it on [...]
S2-2609683, paragraph 11. S2-2609683, China Mobile, 3GPP TSG SA WG2 #177. © China Mobile. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2609683.zip; register: not treated

How should operators control AI use in the 6G core?

The approved interim conclusion places operator control in 6G CN enforcement and OAM-based control. China Mobile's and Ericsson's pCRs were not handled individually, and this evidence does not show whether their content fed the approved text.

Samsung (with SK Telecom)Samsung and SK Telecom's approved interim text places operator control in 6G CN enforcement and OAM-based control, with OAM details FFS in SA5.
Operator control of the network's use of AI capabilities is realized through enforcement in the 6G CN and the operator control orchestration and management domain [...]
S2-2611398, paragraph 22. S2-2611398, Samsung, 3GPP TSG SA WG2 #177. © Samsung. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2611398.zip; register: approved
China MobileChina Mobile proposes an operator control functionality governing AI use under operator requirements.
- Operator control functionality (OCF): A logical 6GC functionality that controls the AI usage in AI capable entities according to the AI usage control requirements [...]
S2-2610037, paragraph 82. S2-2610037, China Mobile, 3GPP TSG SA WG2 #177. © China Mobile. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2610037.zip; register: not treated
EricssonEricsson proposes that a request needing AI is processed without it when AI is disabled or constraints are unmet.
If AI capabilities are needed to process a request, but AI capabilities are not enabled or applicable constraints are not met, the request is processed [...]
S2-2609462, paragraph 13. S2-2609462, Ericsson, 3GPP TSG SA WG2 #177. © Ericsson. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2609462.zip; register: not treated

Should 6G network functions exchange trained ML models?

Ericsson and Qualcomm took opposite positions in their own pCRs, which were not treated, and both co-sign China Telecom's later pCR. That pCR was postponed, so its proposed Editor's Note on how to support model provisioning is not in the TR.

Ericsson (with AT&T, T-Mobile USA, Deutsche Telekom)Ericsson, AT&T, T-Mobile USA and Deutsche Telekom propose that the 6G CN not standardize ML model exchange between NFs.
The 6G CN does not standardize ML model sharing/exchange between NFs.
S2-2609425, paragraph 40. S2-2609425, Ericsson, 3GPP TSG SA WG2 #177. © Ericsson. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2609425.zip; register: not treated
QualcommQualcomm proposes trained-model provisioning from a dedicated training NF to AI-capable NFs.
4. A trained ML model can be provisioned from the dedicated 6G CN NF with ML model training capability to AI capable NFs (e.g., a [...]
S2-2609772, paragraph 11. S2-2609772, Qualcomm, 3GPP TSG SA WG2 #177. © Qualcomm. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2609772.zip; register: not treated
China Telecom (with Ericsson, AT&T, T-Mobile USA, Deutsche Telekom, ETRI, LG Uplus, Ewha Womans University, China Mobile, NTT DOCOMO, Qualcomm, Google)China Telecom's postponed pCR, co-signed by Ericsson, Qualcomm and nine others, proposes an Editor's Note leaving open how model provisioning and multi-vendor interoperability would be supported.
Editor’s Note: How to support Model provisioning and multi-vendor interoperability in ML model provisioning is FFS.
S2-2611367, paragraph 10. S2-2611367, China Telecom, 3GPP TSG SA WG2 #177. © China Telecom. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_177_Prague_2026-10/Docs/S2-2611367.zip; register: postponed

Still open

What to watch next meeting

Sources

Coverage: SA2 #177 (Prague, 2026-10-12 to 2026-10-16), agenda items 20.6.18, 19.15.2, 20.3.2. Scout read 5 recorded decisions and 117 company positions or contribution passages on these agenda items (catalog synced 2026-10-18) and cites 5 decisions and 10 positions from 13 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.