3GPP TSG-SA WG1 Meeting #112-Ad Hoc-e S1-260003
12-16 January 2026, Online
Title: 1st Draft Agenda for SA1#112-Ad Hoc-e
Source: SA1 Chair
Contact: Vasil Aleksiev
Submission Guidelines
o Tdoc number requests: Thursday, 08th January 2026, 23:00 UTC
o Document submission: Thursday, 08th January 2026, 23:00 UTC
· Please use the document templates available at https://ftp.3gpp.org/tsg_sa/WG1_Serv/TSGS1_112_Ad Hoc-e/templates
· MCC will populate SA1_emeet list with email addresses of all the delegates who have registered by the deadline to the SA1#112-Ad Hoc-e
· MCC will send the MS Teams invitations for the calls on SA1_emeet mailing list after registration deadline
LEGEND
Doc Type: AGE (Agenda), CC (Incoming Liaison Statement Copied to SA1), Cont (Contribution), CR (Change request), LS OUT(Outgoing Liaison Statement), TO (Incoming Liaison Statement To SA1), TR (Technical Report), TS (Technical Specification), REP (Report), WID (Work Item Description), WP (Work Plan)
Conclusion: Agreed, Approved, Revised to S1-26xxxx, Noted, Withdrawn, Moved to section xxx, Rejected, Postponed, Email Approval, Not Handled, Unallocated, Drafting
|
Doc Type |
Tdoc number |
Sourcing company(ies) |
Document Title |
Conclusion |
Comments |
|
CR |
S1-26xxxx |
Source |
Title |
Agreed / Approved |
|
|
CR |
S1-26xxxx |
Source |
Title |
Revised to S1-26xxxx |
|
|
CR |
S1-26xxxx |
Source |
Title |
Noted |
|
|
CR |
S1-26xxxx |
Source |
Title |
Withdrawn |
|
|
CR |
S1-26xxxx |
Source |
Title |
Moved to section xxx |
|
|
CR |
S1-26xxxx |
Source |
Title |
Rejected |
|
|
CR |
S1-26xxxx |
Source |
Title |
Postponed |
|
|
CR |
S1-26xxxx |
Source |
Title |
Email Approval |
|
|
CR |
S1-26xxxx |
Source |
Title |
Not Handled |
|
|
|
S1-26xxxx |
|
|
Unallocated / Drafting |
|
1 Opening of the meeting |
|||||
|
Opening of the meeting at 08:00 UTC on Monday 12 Jan 2026 by starting e-mail discussions by the chair. First call Monday January 12th
|
|||||
1.1 Agenda and scheduling |
|||||
|
AGE |
SA1 Chair |
2st Draft Agenda for SA1#112-Ad Hoc-e |
Noted |
|
|
|
AGE |
SA1 Chair |
Agenda for SA1#112-Ad Hoc-e |
Approved |
|
|
|
AGE |
SA1 Chair |
Set of slides for SA1#112ad-hoc-e 12-16 January 2026 |
Noted |
|
|
|
AGE |
S1-260008 |
SA1 Chair |
SA1#112-Ad Hoc-e - Chair's notes at end of the meeting |
|
|
1.2 IPR, antitrust and competition laws |
|||||
|
|
IPR call reminder I draw your attention to your obligations under the 3GPP Partner Organizations’ IPR policies. Every Individual Member organization is obliged to declare to the Partner Organization or Organizations of which it is a member any IPR owned by the Individual Member or any other organization which is or is likely to become essential to the work of 3GPP. Delegates are asked to take note that they are thereby invited: · to investigate whether their organization or any other organization owns IPRs which were, or were likely to become Essential in respect of the work of 3GPP. · to notify their respective Organizational Partners of all potential IPRs, e.g., for ETSI, by means of the IPR Information Statement and the Licensing declaration forms. Antitrust policy Reminder I also draw your attention to the fact that 3GPP activities are subject to all applicable antitrust and competition laws and that compliance with said laws is therefore required of any participant of this WG meeting including the Chairperson and Vice Chairperson. In case of question I recommend that you contact your legal counsel. The leadership shall conduct the present meeting with impartiality and in the interests of 3GPP. Furthermore, I would like to remind you that timely submission of work items in advance of TSG/WG meetings is important to allow for full and fair consideration of such matters. Consensus-based Approach The attention of the delegates to the meeting is drawn to the fact that 3GPP endeavours to reach consensus on all decisions and therefore depends on a cooperative spirit of the Individual Members. In particular, Individual Members are encouraged to seek a consensus-based solution and only to sustain objections as a very last resort, and where absolutely necessary and well justified. The leadership will conduct the present meeting in a manner whereby informal methods of reaching consensus are encouraged, whilst ensuring that well justified concerns are taken into account. |
|
|||
1.3 Editor’s notes solving to FS_6G-REQ [SP-241391] |
|||||
|
Day 1 call – Editor’s notes |
|||||
|
Cont |
6G Study Rapporteurs |
pCR on updating definition of SHE (Service Hosting Environment) and computing section skeleton |
|
Concerns raised from QC, E///, LG about exclusion of RAN in the proposed definition. Possible way forward using a note (proposed by LG). Some companies would like to see the proposed CPRs in the computing section – to decide on the tables headings naming. |
|
|
Cont |
China Mobile E-Commerce Co. |
Resolve EN of 5.5.1 |
Merged into S1-260075r1 |
|
|
|
Cont |
DISA |
Pseudo-CR on 5.5.1 EN of term “decentralised environment” |
Revised to S1-260075r1 |
|
|
|
Cont |
DISA |
Pseudo-CR on 5.5.1 EN of term “decentralised environment” |
|
Revision of S1-260075. Proposals not to use new term but add descriptive text. QC proposed rewording of the concerned requirement: [PR 5.5.1.2-5] The 6G network shall support a means for elements of the core network to establish security in scenarios where not all network elements of one operator's network will be deployed in the same cloud or data centre. |
|
|
Cont |
CATT |
Resolve EN of 8.19 |
Revised to S1-260066r1 |
|
|
|
Cont |
CATT |
Resolve EN of 8.19 |
Revised to S1-260066r2 |
Revision of S1-260066. |
|
|
Cont |
CATT |
Resolve EN of 8.19 |
|
Revision of S1-260066r1. Clarifications needed on the scenario; energy constraint needs to be addressed/based on the CEWiT contribution in a simpler way. |
|
|
Cont |
CEWiT |
Update on 8.19 for EN resolution |
Revised to S1-260071r1 |
|
|
|
Cont |
CEWiT |
Update on 8.19 for EN resolution |
Revised to S1-260071r2 |
Revision of S1-260071. |
|
|
Cont |
CEWiT |
Update on 8.19 for EN resolution |
Merged into S1-260066r2 |
Revision of S1-260071r1. |
|
|
Cont |
China Mobile E-Commerce Co. |
Resolve EN1 of 6.38 Application round trip latency |
Merged into S1-260077r1 |
|
|
|
Cont |
Ericsson LM |
Revised to S1-260077r1 |
|
||
|
Cont |
Ericsson LM |
Solving two editor’s notes in 6.38 AI for disability |
|
Revision of S1-260077. HW raised need for more details on the split between audio and video. “additional end-to-end communication latency” needs to be revised. |
|
|
Cont |
TELEFONICA S.A. |
Solving EN on subscriber permission in CPRs |
Revised to S1-260079r1 |
|
|
|
Cont |
TELEFONICA S.A. |
Solving EN on subscriber permission in CPRs |
|
Revision of S1-260079. Concerns raised with the changed wording of CPRs. Some companies indicated the concept of the user and its actions still is needed in the CPRs. Disagreement on CPR 14.1.8-3-17 to change permission to configuration. |
|
|
Cont |
Samsung |
22.870 pCR on Subscriber Permission |
Revised to S1-260076r1 |
|
|
|
Cont |
Samsung |
22.870 pCR on Subscriber Permission |
|
Revision of S1-260076. Some companies pointed further clarification about the notes is needed. Telefonica, Vodafone, KPN do not see a need for the definition. |
|
|
Cont |
CATT |
Update the table titles of 14.1.11 ubiquitous connectivity |
|
Presented, comments are expected via email. |
|
|
Cont |
InterDigital, Inc. |
Resolve EN clause 7.25.6 |
|
Presented, comments are expected via email. |
|
|
Cont |
Siemens, EDF |
Pseudo-CR on Resolution of editor’s notes in 11.29.6 |
|
Presented, comments are expected via email. |
|
|
Cont |
China Mobile Com. Corporation |
|
Presented, simple change, comments expected via email. |
||
|
Cont |
Huawei |
Pseudo-CR on adding pointer to reference figure 6.59.3-1 in clause 6.59.3 |
|
Presented, simple change, comments expected via email. |
|
|
Cont |
6G Study Rapporteurs |
Revised to S1-260074r1 |
|
||
|
Cont |
6G Study Rapporteurs |
Removal of ENs for Consolidation |
|
Revision of S1-260074. Intention to remove the EN which are not addressed so far. Further comments via email. |
|
|
Cont |
China Mobile E-Commerce Co. |
Resolve EN1 of 6.38 Application round trip latency |
Withdrawn |
|
|
1.4 Consolidation of service and performance requirements to FS_6G-REQ [SP-241391] |
|||||
|
Day 2 call – AI and System |
|||||
|
Cont |
6G Study Rapporteurs |
Table 14.1.8-1 General AI |
|
|
|
|
Cont |
6G Study Rapporteurs |
Table 14.1.8-2 Network AI agent |
|
|
|
|
Cont |
Huawei |
Pseudo-CR to extend S1-260014 with two CPRs on Network AI Agent |
|
To be merged with S1-260014 |
|
|
Cont |
6G Study Rapporteurs |
Table 14.1.8-2 3rd party AI agent |
|
|
|
|
Day 3 call – System and ISAC |
|||||
|
Cont |
6G Study Rapporteurs |
Table 14.1.1-1 legacy support |
|
|
|
|
Cont |
6G Study Rapporteurs |
Table 14.1.1-2 enhanced legacy |
|
|
|
|
Cont |
6G Study Rapporteurs |
Table 14.1.10-1 – ISAC |
|
|
|
|
Cont |
S1-260021 |
6G Study Rapporteurs |
EoD-Table 14.1.1-1 legacy support |
|
Reserved for End of Discussion status |
|
Cont |
S1-260022 |
6G Study Rapporteurs |
EoD-Table 14.1.1-2 enhanced legacy |
|
Reserved for End of Discussion status |
|
Cont |
S1-260023 |
6G Study Rapporteurs |
EoD-Table 14.1.8-1 General AI |
|
Reserved for End of Discussion status |
|
Cont |
S1-260024 |
6G Study Rapporteurs |
EoD-Table 14.1.8-2 Network AI agent |
|
Reserved for End of Discussion status |
|
Cont |
S1-260025 |
6G Study Rapporteurs |
EoD-Table 14.1.8-2 3rd party AI agent |
|
Reserved for End of Discussion status |
|
Cont |
S1-260026 |
6G Study Rapporteurs |
EoD-Table 14.1.10-1 – ISAC |
|
Reserved for End of Discussion status |
|
Cont |
S1-260031 |
6G Study Rapporteurs |
Approved Table 14.1.1-1 legacy support |
|
Reserved for final approvable version |
|
Cont |
S1-260032 |
6G Study Rapporteurs |
Approved Table 14.1.1-2 enhanced legacy |
|
Reserved for final approvable version |
|
Cont |
S1-260033 |
6G Study Rapporteurs |
Approved Table 14.1.8-1 General AI |
|
Reserved for final approvable version |
|
Cont |
S1-260034 |
6G Study Rapporteurs |
Approved Table 14.1.8-2 Network AI agent |
|
Reserved for final approvable version |
|
Cont |
S1-260035 |
6G Study Rapporteurs |
Approved Table 14.1.8-2 3rd party AI agent |
|
Reserved for final approvable version |
|
Cont |
S1-260036 |
6G Study Rapporteurs |
Approved Table 14.1.10-1 – ISAC |
|
Reserved for final approvable version |
|
Day 4 call – KPIs consolidation |
|||||
|
Cont |
China Unicom (moderator) |
Immersive KPIs |
|
|
|
|
Cont |
Telefonica (moderator) |
ISAC KPIs |
|
|
|
|
Cont |
Nokia (Moderator) |
Ubiquitous KPIs |
|
|
|
|
Cont |
China Unicom (moderator) |
AI KPIs |
|
|
|
|
Cont |
Nokia (Moderator) |
Massive KPIs |
Noted |
For Information only |
|
|
Cont |
Nokia (Moderator) |
Verticals KPIs |
Noted |
For Information only |
|
|
Cont |
S1-260051 |
China Unicom (moderator) |
EoD-Immersive KPIs |
|
Reserved for End of Discussion status |
|
Cont |
S1-260052 |
Telefonica (moderator) |
EoD- ISAC KPIs |
|
Reserved for End of Discussion status |
|
Cont |
S1-260053 |
Nokia (Moderator) |
EoD-Ubiquitous KPIs |
|
Reserved for End of Discussion status |
|
Cont |
S1-260054 |
China Unicom (moderator) |
EoD-AI KPIs |
|
Reserved for End of Discussion status |
|
Cont |
S1-260061 |
China Unicom (moderator) |
Approved Immersive KPIs |
|
Reserved for final approvable version |
|
Cont |
S1-260062 |
Telefonica (moderator) |
Approved ISAC KPIs |
|
Reserved for final approvable version |
|
Cont |
S1-260063 |
Nokia (Moderator) |
Approved Ubiquitous KPIs |
|
Reserved for final approvable version |
|
Cont |
S1-260064 |
China Unicom (moderator) |
Approved AI KPIs |
|
Reserved for final approvable version |
2 Work Item/Study Item progress |
|||||
2.1 Work Item/Study Item status update |
|||||
|
TR |
6G Study Rapporteurs |
TR 22.870 v.1.0.1 as baseline for this meeting |
|
For information |
|
|
TR |
S1-260004 |
6G Study Rapporteurs |
TR 22.870 output of the meeting |
|
|
|
REP |
S1-260005 |
6G Study Rapporteurs |
6G SID status update |
|
|
|
Cont |
S1-260007 |
SA1 chair |
Next steps after SA1#112-Ad Hoc-e |
|
|
3 Next meetings (calendar) |
|||||
|
2026 meetings:
SA1#113 09-13 Feb 2026 Indiia, Goa SA1#114 18-22 May 2026 China, location TBD SA1#115 24-28 Aug 2026 Prague, Czech Republic SA1#116 16-20 Nov 2026 Calgary, Canada
|
|||||
4 Close of the meeting |
|||||
|
Close latest by 16:00 UTC on Friday 16 January 2026
|
|||||
General meeting information specific for SA1#112-Ad Hoc-e:
Start of email discussions: Monday January 12th, 08:00 UTC
· The chair will start email discussions on SA1 mailing list with header [SA1#112-ad-hoc], [tdoc#], [tdoc name].
End of email discussions: Thursday January 15th, 17:00 UTC
Authors provide their final versions after Thursday January 15th, 17:00 UTC
Final review period Thursday 23:00 UTC till Friday 10:00 UTC
· If no disagreement is raised for a specific tdoc during final review period, it is considered as approved
All tdocs are open for discussion from the very beginning of the meeting after sending the initial opening discussions emails from the chair.
The PRs which are cleared from editor’s notes in this e-meeting will be considered for consolidation in the SA1#113 (Feb 2026).
Only the author can create next tdoc revision with file name: [tdoc#]r1, r2, rx (without formal revision request to the Chair/MCC). The author announces each new revision version on the SA1 mailing list. The latest version is the one announced and available on the inbox.
Companies can comment and propose updates of the content of the tdocs by:
• email by plain text on the SA1 mailing list
• and/or by using a draft (e.g. for more complex proposals), using the draft file name: “draft-[tdoc#rx]-[companyname]” place it in “drafts” folder and announce it on the SA1 mailing list.
For the final review period the rapporteurs will create new tdocs that reflect the status of the end of the discussions and for approval that are going into TR 22.870.
According to S1-252010, no new use cases and no use cases updates allowed for the 6G study in SA1#112-Ad Hoc-e.
The target of SA1#112-Ad Hoc-e is to solve the editor's notes and to consolidate TR 22.870.
Please use the “6G TR22.870 Rapporteurs list with pending topics.xls” as a reference.
MCC will populate SA1_emeet list with email addresses of all the delegates who have registered by the deadline to the SA1#112-Ad Hoc-e.
MCC will send the MS Teams invitations for the calls on SA1_emeet mailing list after registration deadline. The following calls will be scheduled:
· Day 1: Monday January 12th
• 05:30-07:30 PT / 13:30 – 15:30 UTC /22:30-00:30 JST
• Call (2 hours) – Opening – approving the agenda, editor’s notes contributions.
· Day 2: Tuesday January 13th
• 05:30-07:30 PT / 13:30 – 15:30 UTC / 22:30-00:30 JST
• Call (2 hours) – AI and System consolidation
· Day 3: Wednesday January 14th
• 05:30-07:30 PT / 13:30 – 15:30 UTC / 22:30-00:30 JST
• Call (2 hours) – System and ISAC consolidation
· Day 4: Thursday January 15th
• 05:30-07:30 PT / 13:30 – 15:30 UTC / 22:30-00:30 JST
• Call (2 hours) - KPIs consolidation (Immersive, ISAC, Ubiquitous, AI)
· Day 5: Friday January 16th
• 05:00-08:00 PT / 13:00 – 16:00 UTC / 22:00-01:00 JST
• Closing call (3 hours)
There is no strict timing separation between the topics in a call. The actual timing depends on email discussions status and possibilities to reach agreement on certain topics/CPRs wording before calls.
Document Handling
According to 3GPP rules, a CR is subject to agreement at working group level (approved at SA plenary) and pCR is subject to approval directly at working group level (no need for SA approval).
To maximize the efficiency of documents handling, the following guidelines apply:
- Contribution Presenters shall assume that the delegates have read the contributions. As such, presenters are requested to make quick presentations to allow time for discussion. When presenting revisions, only the changes shall be presented.
Revisions will be handled in the following way:
- “rx” tdocs are not official 3GPP documents
o During the meeting, they are uploaded (to the local server’s) “inbox” folder for conveniency reasons.
o But, after the meeting, they will be placed (on the 3GPP FTP) in a “drafts” folder.
o They are part of the session chair’s notes/agenda (with some additional remarks based on comments) and will not appear in the official minutes. Noted “rx” tdocs will be captured in official minutes with their initial official tdoc (and with their final official number if there is one).
o An official, new, 3GPP tdoc number will be assigned by the chair systematically for all the approved tdocs. Authors shall upload the tdoc with the new official tdoc number before the end of the meeting.
Best Practices
- It is strongly recommended to download documents before the meeting.
- It is strongly recommended NOT to share attachments over the email reflector but instead place any document that must be shared in the inbox or in the DRAFTs folder and share only the URL.