3GPP TSG-SA WG1 Meeting #113 S1-261000
09-13 February 2026, Goa, India
Title: 1st Draft Agenda for SA1#113
Source: SA1 Chair
Contact: Vasil Aleksiev
Submission Guidelines
o Tdoc number and CR number requests: Friday, 30th January 2026, 23:00 UTC
o Document submission: Friday, 30th January 2026, 23:00 UTC
· Please use the document templates available at https://ftp.3gpp.org/tsg_sa/WG1_Serv/TSGS1_113_Goa/templates
https://ftp.3gpp.org/tsg_sa/WG1_Serv/TSGS1_113_Goa/templates
· For CRs:
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-25xxxx, 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-25xxxx |
Source |
Title |
Agreed / Approved |
|
|
CR |
S1-25xxxx |
Source |
Title |
Revised to S1-25xxxx |
|
|
CR |
S1-25xxxx |
Source |
Title |
Noted |
|
|
CR |
S1-25xxxx |
Source |
Title |
Withdrawn |
|
|
CR |
S1-25xxxx |
Source |
Title |
Moved to section xxx |
|
|
CR |
S1-25xxxx |
Source |
Title |
Rejected |
|
|
CR |
S1-25xxxx |
Source |
Title |
Postponed |
|
|
CR |
S1-25xxxx |
Source |
Title |
Email Approval |
|
|
CR |
S1-25xxxx |
Source |
Title |
Not Handled |
|
|
|
S1-25xxxx |
|
|
Unallocated / Drafting |
|
1 Opening of the meeting |
|||||
|
Opening of the meeting at 09:00 on Monday 09 February 2026
|
|||||
1.1 Agenda and scheduling |
|||||
|
AGE |
S1-261000 |
SA1 Chair |
1st Draft Agenda for SA1#113 |
|
|
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 Previous SA1 meeting report |
|||||
|
The report of the last meeting will be approved at the start of the meeting.
|
|||||
|
REP |
S1-261004 |
ETSI |
Draft minutes of SA1#112 |
|
|
1.4 Information for delegates |
|||||
|
Draft TR/TS to SA plenary for information: delegates are encouraged to send draft TR/TS for information as soon as there is useful content to be reviewed. Draft TR/TS can be sent to SA plenary for information more than once.
Drafting p-CRs: - All changes must be shown using revision marks against existing text in the draft TS/TR, otherwise p-CRs may be Noted
- For more info: ftp://ftp.3gpp.org/tsg_sa/WG1_Serv/Delegate_Guidelines_v10.doc and https://www.3gpp.org/delegates-corner/faqs
When writing CRs, please follow the guidance provided in SP-2241007 (Guidelines to write CRs) |
|||||
1.5 Information for rapporteurs |
|||||
|
"Beginner's guide" for writing a new TS/TR is available at http://www.3gpp.org/specifications-groups/delegates-corner/writing-a-new-spec (feedback on content is welcome!)
For detailed drafting guidelines, please see TR 21.801
Rapporteurs are expected to produce a work item/study item status report for the end of the meeting. The template is available here.
For draft TR/TS, the rapporteur is expected to update the draft TR/TS with all contributions agreed at the meeting before the meeting is closed.
|
|||||
1.6 Working agreements |
|||||
|
None
|
|||||
2 Reports and action items |
|||||
|
|
|
|
|
|
|
3 Liaison Statements (including related contributions) |
|||||
|
|
|
|
|
|
|
4 New Work Items |
|||||
|
|
|
|
|
|
|
5 Quality improvement contributionsQuality improvements to requirements in TRs or TSs are encouraged (pCRs or CRs). In order to allow delegates to provide quality improvement contributions for work/study items where they do not want to attend drafting sessions, contributions submitted to this agenda item are handled in plenary. |
|||||
|
|
|
|
|
|
|
6 Rel-20 and earlier contributions |
|||||
6.1 Rel-20 correction and clarification CRs |
|||||
|
|
|
|
|
|
|
6.2 Release 18 & 19 Alignment CRs (aligning Stage 1 specifications with what has been implemented in Stage 2 and 3) |
|||||
|
|
|
|
|
|
|
6.3 Rel-19 and earlier CRs (other than alignment) |
|||||
|
|
|
|
|
|
|
7 Rel-21 contributions |
|||||
7.1 FS_SIMP [SP-251655] |
|||||
|
Work status prior to this meeting: Rapporteur : Erik Guttman (Samsung) Latest version : TR22.860v0.0.0 Target completion date : SA#114 (Dec 2026) Percentage completion : 0% |
|||||
|
|
|
|
|
|
|
8 Rel-20 6G contributions |
|||||
8.1 FS_6G-REQ [SP-241391] |
|||||
|
Work status prior to this meeting: Rapporteur: Xiaonan Shi (China Mobile), Jean Trakinat (T-Mobile USA) Latest version : TR22.870v1.1.0 Target completion date : SA#111 (03/2026) Percentage completion : 82% |
|||||
8.1.1 General |
|||||
|
|
|
|
|
|
|
8.1.2 System and Operation Aspects |
|||||
|
|
|
|
|
|
|
8.1.3 Artificial Intelligence |
|||||
|
|
|
|
|
|
|
8.1.4 Integrated Sensing and Communication |
|||||
|
|
|
|
|
|
|
8.1.5 Ubiquitous Connectivity |
|||||
|
|
|
|
|
|
|
8.1.6 Immersive Reality |
|||||
|
|
|
|
|
|
|
8.1.7 Massive Communication |
|||||
|
|
|
|
|
|
|
8.1.8 Further Use Cases on Industry and Verticals |
|||||
|
|
|
|
|
|
|
8.1.9 Other |
|||||
|
|
|
|
|
|
|
9 Other technical contributions |
|||||
|
|
|
|
|
|
|
10 Other non-technical contributions |
|||||
|
|
|
|
|
|
|
11 Work Item/Study Item progress |
|||||
11.1 Session information outputs |
|||||
|
|
|
|
|
|
|
11.2 Work Item/Study Item status update |
|||||
|
|
|
|
|
|
|
12 Next meetings (calendar) |
|||||
|
2026 meetings:
SA1#113 09-13 Feb 2026 Goa, India 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
|
|||||
13 Any other business |
|||||
|
|
|
|
|
|
|
14 Close of the meeting |
|||||
|
Close latest by 16:00 on Friday 13 February 2026
|
|||||
General meeting information:
According to S1-252010, No new use cases allowed for the 6G study in SA1#113.
The priority of SA1#113 is to consolidate TR 22.870.
According to SA guidance, SA1 is expected to prioritise Rel-20 6G study for completion by March 2026. This does not preclude 5GA items to be discussed if time is available.
We will use the local ftp server 10.10.10.10:
Remote participants will have read access to the local ftp server.
MS Teams will be used to support remote participation:
- Remote participants are only in listening mode.
- There will be one MS Teams instance for the main meeting room.
- MS Teams links will be provided via email to only to delegates registered for SA1#113 as remote participants.
Delegates can use the DRAFT folder of the local ftp server to share drafts.
Email discussion can be used to progress discussions, but:
- Comments given in emails are not considered part of the meeting and cannot prevent agreement of a contribution.
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). LS is subject to approval directly at working group level. SIDs/WIDs are subject to agreement at working group level (approved at SA plenary).
To maximize the efficiency of documents handling, the following guidelines apply:
- Incoming LSs where SA1 is in copy will have limited online presentation, unless specifically requested.
- Contribution Presenters shall assume that the delegates have read the contributions. As such, presenters are requested to make quick presentation to allow time for discussion. When presenting revisions, only the changes shall be presented.
Revisions will be handled in the following way:
- The Session Chair assigns a revision tdoc number for the revision by using the existing tdoc number and adding “r1” (or “r2”, “r3” …) at the end.
- The delegate can also request a revision tdoc number for the revision.
- Revisions must be uploaded to the INBOX of the local ftp server 10.10.10.10.
- Once a document reaches consensus, the session Chair assigns a new tdoc number (without any “rx”) and marks it as agreed/approved.
- “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).
- An official, new, 3GPP tdoc number will be assigned in these cases:
o Systematically for all the agreed/approved tdocs. Authors shall upload the tdoc with the new official tdoc number before the end of the meeting.
o Systematically for all noted tdocs. Authors shall upload the tdoc with the new official tdoc number before the end of the meeting.
o During plenary discussions (i.e. on Thursday and Friday – still opened “rx” tdocs are being discussed and further revised using official tdoc numbers)
- Only session chairs and MCC can assign “rx” versions
o Assignment to take place either immediately after tdoc/revision presentation or during meeting breaks (i.e. NOT during an ongoing session).
o A revision will not be treated if the agenda does not show it (e.g. self-assigned revision will be skipped until the next round).
- Drafts are still possible
o Using the (local server’s) “drafts” folder, using “_draftnn” as suffix to the tdoc name.
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.
o Before the meeting, the “inbox” and "draft” folders are under the respective meeting folder on the 3GPP portal.
o During the meeting, these folders are on the local server, at 10.10.10.10
Drafting sessions
There will be at most two drafting sessions scheduled in parallel. Drafting sessions will run over a maximum of 4 days and can be scheduled on Monday afternoon, Tuesday, Wednesday and potentially parts of Thursday. The allocation of parallel sessions will be determined after the tdoc submission deadline. How much of the meeting that will use parallel sessions depends on the amount of input documents and the progress during the meeting. Delegates must be aware that the agenda can be adjusted at any time.
The objective of all sessions (i.e. drafting 1 session and drafting 2 session) is to review input contributions for the respective agenda items, after which the corresponding session will conclude. Revisions are encouraged to be handled in parallel sessions. Documents unable to be handled in the parallel sessions (e.g. due to time constraints or to the interest of all delegates) will be handled in the main sessions without a scheduled parallel session.
Authority of the parallel sessions
The parallel sessions are authorized to:
- handle any type of document and propose agreement/approval for them (after potential revisions, as described in the paragraph above).
o The documents proposed to be agreed/ approved by the parallel sessions will be submitted to SA1 plenary sessions for SA1 official agreement/approval.
The parallel sessions are not authorized to:
- agree to WID/SID proposals
- approve Outgoing LSs, unless explicitly authorized to do so in exceptional circumstances
- create Working Agreements
Review of parallel sessions’ outcomes
- When all parallel sessions have been concluded, the SA1 Chair will ask in the main session whether there are any concerns with the decisions of the Tdocs from the parallel sessions. If no concerns are expressed, the outcomes from parallel sessions will be considered final.
Additional points
The MCC support (Mr. Alain Sultan) will be dedicated to the plenary session. The MCC will allocate a range of Tdoc numbers to the parallel sessions and the parallel sessions Chairs will be able to allocate new Tdoc numbers (for pre-agreed CRs or pre-approved pCRs). Delegates are requested to ask for revision Tdoc numbers from the person chairing the agenda item where the topic is allocated.
There will be no detailed reporting from the parallel sessions. However, in order to get some indication of agreements or controversial/blocking points, the parallel session Chair will record brief notes in parallel session Chair notes. These notes will be stored regularly in the local server. The merge of agendas and notes from the parallel sessions will be done at the conclusion of all parallel sessions, and this will form the basis of the Chair Notes for the rest of the meeting.