SA2 #176 · 2026-09-27

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

The verdict

  1. No KI#18 interim conclusion was recorded. The multi-company interim-conclusion baseline, led by Huawei with nine co-submitters, was noted, and separate interim-conclusion inputs from Samsung (S2-2607288), China Telecom and NTT DOCOMO (all three also co-submitters of the baseline) were not treated. Noted means the meeting did not approve the text, not that its content was rejected. (S2-2608878 (Huawei (with China Mobile, OPPO, ETRI, LG Uplus, SK Telecom, Ewha Womans University, Samsung, NTT DOCOMO, China Telecom); register: noted). S2-2608878. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2608878.zip; S2-2607681 (China Telecom; register: not treated). S2-2607681. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2607681.zip; S2-2607437 (NTT DOCOMO; register: not treated). S2-2607437. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2607437.zip)
  2. SA2 approved 15 pCRs (per the TDoc register) to the 6G architecture study TR 23.801-01 under KI#18 (AI for 6G), all updates to existing solution variants except a new variant #18.8 on roaming for the AI domain (Google with ZTE, Ericsson, AT&T, T-Mobile USA, Huawei, NTT DOCOMO, Nokia and others). These are study text, not normative decisions. (S2-2609048 (pCR. Register status: approved at S2-176.). S2-2609048, Google, 3GPP TSG SA WG2 #176. © Google. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609048.zip; S2-2609203 (pCR. Register status: approved at S2-176.). S2-2609203, ZTE, 3GPP TSG SA WG2 #176. © ZTE. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609203.zip; S2-2609043 (pCR. Register status: approved at S2-176.). S2-2609043, InterDigital, 3GPP TSG SA WG2 #176. © InterDigital. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609043.zip)
  3. For the 5G core, the CRs agreed at working-group level are, by their titles, clarifications and alignment: a Rel-19 and Rel-20 pair on SCP alignment (TS 23.501), Rel-19 clarifications on Signalling Storm Analytics and on model information in analytics context transfer (TS 23.288), and a Rel-20 clarification on the time interval supporting vertical federated learning (TS 23.288, S2-2608886). All still need plenary approval. (S2-2608275 (CR. Register status: agreed at S2-176.). S2-2608275, vivo, 3GPP TSG SA WG2 #176. © vivo. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2608275.zip; S2-2609066 (CR. Register status: agreed at S2-176.). S2-2609066, Huawei, 3GPP TSG SA WG2 #176. © Huawei. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609066.zip; S2-2609068 (CR. Register status: agreed at S2-176.). S2-2609068, Huawei, 3GPP TSG SA WG2 #176. © Huawei. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609068.zip)

What was agreed

New solution variant: roaming for the AI domain (study text). A new variant #18.8 on roaming support for the AI domain was approved into TR 23.801-01.
pCR approved (text for the study TR, not normative); 23.801-01, Rel-20[KI#18, Solution Variant #18.8 New]: Support of roaming for AI domain. S2-2609048 (pCR. Register status: approved at S2-176.). S2-2609048, Google, 3GPP TSG SA WG2 #176. © Google. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609048.zip
Intent handling and a separate AI domain (study text updates). Updates were approved to variant #18.2 (intent handling embedded in other 6G core NFs) and to the variant for a new domain separated from the PS domain (listed as #3, numbered #18.3 in the TR). Approving updates does not choose between variants.
pCR approved (text for the study TR, not normative); 23.801-01, Rel-20[KI#18, Solution Variant #18.2, Update] Intent handling capability embedded in other 6G CN NFs, to handle requests including intent. S2-2609043 (pCR. Register status: approved at S2-176.). S2-2609043, InterDigital, 3GPP TSG SA WG2 #176. © InterDigital. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609043.zip
pCR approved (text for the study TR, not normative); 23.801-01, Rel-20[KI#18, Solution Variant #3 update] New separated domain from PS domain, within 6G CN. S2-2609044 (pCR. Register status: approved at S2-176.). S2-2609044, Nokia, 3GPP TSG SA WG2 #176. © Nokia. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609044.zip
Intent transport and fulfilment (study text updates). Updates were approved to variants #18.4 and #18.5 (transport of intent from UE and AF) and #18.6 (intent fulfilment).
pCR approved (text for the study TR, not normative); 23.801-01, Rel-20[KI#18, Solution Variant #18.4, #18.5, update] Solution updates for transport of intent from UE and AF. S2-2609199 (pCR. Register status: approved at S2-176.). S2-2609199, ETRI, 3GPP TSG SA WG2 #176. © ETRI. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609199.zip
pCR approved (text for the study TR, not normative); 23.801-01, Rel-20[KI#18, Solution variant #18.6, update] Updates to solution on Intent fulfilment. S2-2609200 (pCR. Register status: approved at S2-176.). S2-2609200, Huawei, 3GPP TSG SA WG2 #176. © Huawei. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609200.zip
Agents, tools and operator control (study text updates). Updates were approved to variant #18.16 (tool invocation and multi-agent communication), #18.17 and #18.18 (AI capability access) and #18.22 (control of the network's use of AI capabilities).
pCR approved (text for the study TR, not normative); 23.801-01, Rel-20[KI#18, Solution Variants#18.16, update] Tool invocation and multi-agents communication. S2-2609203 (pCR. Register status: approved at S2-176.). S2-2609203, ZTE, 3GPP TSG SA WG2 #176. © ZTE. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609203.zip
pCR approved (text for the study TR, not normative); 23.801-01, Rel-20[KI#18, Solution variant #18.17, #18.18 update] Solution update for AI capability access. S2-2609053 (pCR. Register status: approved at S2-176.). S2-2609053, vivo, 3GPP TSG SA WG2 #176. © vivo. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609053.zip
pCR approved (text for the study TR, not normative); 23.801-01, Rel-20[KI#18, sol var #18.22, update] Control of the network's use of AI capabilities. S2-2609135 (pCR. Register status: approved at S2-176.). S2-2609135, Samsung, 3GPP TSG SA WG2 #176. © Samsung. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609135.zip
5G core: SCP alignment in TS 23.501 (CRs agreed at working-group level). Rel-19 and Rel-20 CRs with the same title from vivo, the register does not show whether one mirrors the other. Both still need plenary approval.
CR agreed at working-group level (subject to plenary approval); 23.501, Rel-19AIML_CN SCP related alignment. S2-2608275 (CR. Register status: agreed at S2-176.). S2-2608275, vivo, 3GPP TSG SA WG2 #176. © vivo. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2608275.zip
CR agreed at working-group level (subject to plenary approval); 23.501, Rel-20AIML_CN SCP related alignment. S2-2608276 (CR. Register status: agreed at S2-176.). S2-2608276, vivo, 3GPP TSG SA WG2 #176. © vivo. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2608276.zip
5G core: analytics clarifications in TS 23.288 (CRs agreed at working-group level). Rel-19 and Rel-20 clarifications on Signalling Storm Analytics (Huawei with HiSilicon and CATT) and on model information in analytics context transfer (Huawei with HiSilicon), plus a Rel-20 clarification on the time interval supporting vertical federated learning, VFL (ZTE).
CR agreed at working-group level (subject to plenary approval); 23.288, Rel-19Clarification on Signalling Storm Analytics. S2-2609066 (CR. Register status: agreed at S2-176.). S2-2609066, Huawei, 3GPP TSG SA WG2 #176. © Huawei. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609066.zip
CR agreed at working-group level (subject to plenary approval); 23.288, Rel-19Clarification on Model information in Analytics Context Transfer. S2-2609068 (CR. Register status: agreed at S2-176.). S2-2609068, Huawei, 3GPP TSG SA WG2 #176. © Huawei. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609068.zip
CR agreed at working-group level (subject to plenary approval); 23.288, Rel-20Clarifications on the time interval supporting VFL. S2-2608886 (CR. Register status: agreed at S2-176.). S2-2608886, ZTE, 3GPP TSG SA WG2 #176. © ZTE. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2608886.zip

Who pushed what

What should the KI#18 interim conclusion say?

None of these texts was approved: the multi-company baseline was noted and the others were not treated. China Telecom and NTT DOCOMO differ on where training and inference sit: China Telecom wants both dedicated and embedded NFs, NTT DOCOMO a dedicated training entity with local inference optional.

Huawei (with China Mobile, OPPO, ETRI, LG Uplus, SK Telecom, Ewha Womans University, Samsung, NTT DOCOMO, China Telecom)The noted baseline includes closed-loop operation for intent assurance.
6G CN shall support closed-loop operation to assure satisfaction of the Target of 3GPP Intent or performance of ML models.
S2-2608878, paragraph 159. S2-2608878, Huawei, 3GPP TSG SA WG2 #176. © Huawei. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2608878.zip; register: noted
China TelecomChina Telecom's bullet 8 input; its introduction weighs dedicated against embedded inference NFs; not treated.
For ML inferencing, considering both legacy 5G scenarios and new 6G use cases, this contribution concludes that both a dedicated 6GC NF with inference capability [...]
S2-2607681, paragraph 9. S2-2607681, China Telecom, 3GPP TSG SA WG2 #176. © China Telecom. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2607681.zip; register: not treated
NTT DOCOMONTT DOCOMO proposes a dedicated training entity; not treated.
6G CN shall support ML model training by a dedicated entity that provides the ML training and provisioning services for other AI Capable 6G NFs.
S2-2607437, paragraph 12. S2-2607437, NTT DOCOMO, 3GPP TSG SA WG2 #176. © NTT DOCOMO. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2607437.zip; register: not treated
SamsungSamsung proposes mandatory fallback to default procedures; not treated.
Fallback/rollback to default procedure shall be supported in the 6G system.
S2-2607288, paragraph 36. S2-2607288, Samsung, 3GPP TSG SA WG2 #176. © Samsung. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2607288.zip; register: not treated

Where should 6G AI and intent handling sit in the core?

Two approved variants coexist in the study: intent handling embedded in existing NFs, and a separate, optional AI domain. Approved texts are merged or revised documents shown under their register submitters. Orange's proposal, not treated, is a distinct architecture based on 5G core evolution.

InterDigital (with Oracle)Approved merged text for variant #18.2 routes intents to an NF with embedded intent handling, such as the PCF.
The NEF discovers and selects a 6G CN NF with embedded intent handling capabilities (e.g., a PCF), and it authenticates and authorizes the intent via [...]
S2-2609043, paragraph 77. S2-2609043, InterDigital, 3GPP TSG SA WG2 #176. © InterDigital. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609043.zip; register: approved
Nokia (with NVIDIA, Federated Telecoms Hub, T-Mobile USA, AT&T, Qualcomm, Verizon, Deutsche Telekom, Turkcell, Ericsson, BT, Google)Approved update to variant #18.3, which describes an AI domain separate from the PS domain.
A new 6G CN AI domain is introduced which is separated from 6G CN PS domain.
S2-2609044, paragraph 20. S2-2609044, Nokia, 3GPP TSG SA WG2 #176. © Nokia. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609044.zip; register: approved
OrangeOrange proposed a new variant with an AI gateway function that triggers AI-domain agents; not treated.
AI-GWF (AI Gateway Function) processes and interprets the intent, choose and trigger the appropriate AI agent functions in the AI domain via the AIa reference [...]
S2-2607568, paragraph 23. S2-2607568, Orange, 3GPP TSG SA WG2 #176. © Orange. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2607568.zip; register: not treated

How should tool use and operator control of network AI be governed?

The approved variant #18.16 text includes an accept or reject response to tool invocation requests, and the approved #18.22 update lets operator control include explainability checks for certain actions. China Telecom's #18.22 input and the Ericsson-led OAM input were not treated; their content may have fed the merged approved texts.

ZTE (with China Mobile, Huawei, HiSilicon, vivo, Samsung, OPPO, CATT, ETRI)Approved #18.16 text includes an accept or reject response to tool invocation requests.
The tool invocation request is a structured message without intent, in response to which the tool invocation entity may receive a tool invocation acceptance or [...]
S2-2609203, paragraph 74. S2-2609203, ZTE, 3GPP TSG SA WG2 #176. © ZTE. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609203.zip; register: approved
Samsung (with SK Telecom)Approved #18.22 update: explainability evaluation for state-changing AI/ML-derived actions, as an option.
For selected AI/ML-derived candidate network actions whose enforcement changes network state or affects externally observable service behaviour, operator control may include evaluation of explainability-related information [...]
S2-2609135, paragraph 16. S2-2609135, Samsung, 3GPP TSG SA WG2 #176. © Samsung. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2609135.zip; register: approved
China Telecom#18.22 update on NF-level control, including UE or AF approval of selected risky tools; not treated.
The UE/AF supports confirmation of the risk information, including approval or rejection of the use of the selected tools for network task execution.
S2-2607685, paragraph 13. S2-2607685, China Telecom, 3GPP TSG SA WG2 #176. © China Telecom. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2607685.zip; register: not treated
Ericsson (with AT&T, T-Mobile USA, Deutsche Telekom)#18.22 input on operator governance through OAM with NF-level enforcement; not treated.
Define management layer (OAM) providing capabilities providing, e.g. global/local reliability rules, monitoring individual NFs for intent handling configuration per, e.g. applications.
S2-2606935, paragraph 20. S2-2606935, Ericsson, 3GPP TSG SA WG2 #176. © Ericsson. https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_176_Prague_2026-08/Docs/S2-2606935.zip; register: not treated

Still open

What to watch next meeting

Sources

Coverage: SA2 #176 (Prague, 2026-08-24 to 2026-08-28), agenda items 20.6.18, 19.15.2. Scout read 22 recorded decisions and 122 company positions or contribution passages on these agenda items (catalog synced 2026-09-23) and cites 13 decisions and 11 positions from 20 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.