SA2 #148E e-meeting 1. Deadlines for SA2#148E e-meeting are as follows: Docs request 08 Nov 2021 (Monday) 2359 UTC Docs submission 08 Nov 2021 (Monday) 2359 UTC Start of e-meeting 15 Nov 2021 (Monday) 0000 UTC CC#1 15 Nov 2021 (Monday) 1330 – 1530 UTC Revisions by 17 Nov 2021 (Wednesday) 1600 UTC Final Comments 18 Nov 2021 (Thursday) 1600 UTC CC#2 19 Nov 2021 (Friday) 1330 – 1530 UTC CC#3 22 Nov 2021 (Monday), AI#9.1.X only 1330 – 1530 UTC Close of e-meeting 22 Nov 2021 (Monday) 1700 UTC Upload Approved docs 23 Nov 2021 (Tuesday) 1700 UTC NOTE 1: Final Chair’s Notes will be made available shortly after the close of the e-meeting deadline. 2. Agenda: 2.1 Agenda for SA2#148E AI# Topic E-meeting Convener 1.1 Opening of the meeting 0000 UTC on Mon (15-Nov) Puneet 2 Agenda Puneet 2.1 IPR Call and Antitrust Reminder 3 SA2#147E Meeting report Puneet 4 General (to be decided after the Docs submission deadline) 4.1 Common issues and Incoming LSs 4.2 P-CRs/CRs related to use of inclusive language in 3GPP 5 Pre-Rel-17 Maintenance (excluding all 5G topics) NOTE: FASMO criterion will be strictly enforced. (Please do not submit documents directly to this agenda item.) (to be decided after the Docs submission deadline) 5.1 3GPP Packet Access Maintenance For corrections of any issues that relate to 3GPP access related aspects and for any work items from that area, like: SAE, CSFB, DÉCOR, MTC, CIoT, CUPS, V2X, EDCE5, ProSe_WLAN_DD_Stage2, PARLOS And for maintenance of functionality introduced by TEIx CRs (x<17) in the area of 3GPP Access. Also alignment to past features (e.g. SAES) related to 3GPP access related aspects and alignment to diverse features specified by other working groups. 5.2 QoS and PCC Maintenance For corrections of any issues that relate to QoS and PCC, including the policy related aspects of other Wis like from SAE, but also work items specific for that area like FMSS. And for maintenance of functionality introduced by TEIx CRs (x<17) in the area of QoS and PCC. Also QoS and PCC related alignments to past features (e.g. SAES) and alignment to diverse features specified by other working groups. 5.3 Non-3GPP Access Maintenance For corrections of any issues that relate to non-3GPP access related aspects and for any work items from that area, like: SEW1, VoWLAN. And for maintenance of functionality introduced by TEIx CRs (x<17) in the area of non-3GPP Access. Also for alignment to non-3GPP aspects from past features (e.g. SAES) and for alignment to diverse features specified by other working groups, etc. 5.4 IMS and IMS-Related Maintenance For corrections of any issues that are IMS-related and similar aspects and for any work items from that area, like: IMS, Emergency, PS_data_off. And for maintenance of functionality introduced by TEIx CRs (x<17) in the area of IMS-related. Also for alignment to IMS-related and similar aspects from past features and for alignment to diverse features specified by other working groups, etc. 6 Rel-15/Rel-16 Maintenance for 5G (only related to 5GS_Ph1 Work Item) NOTE: FASMO criterion will be strictly enforced. (Please do not submit documents directly to this agenda item.) (to be decided after the Docs submission deadline) 6.1 General aspects, concepts and reference models High level function descriptions that don't fit under any of the other, more specific agenda items. Reference models. 6.2 Common Access Control, RM and CM functions and procedure flows Related high level function descriptions, registration management procedures and RM and CM state models as long as common for 3GPP and non3GPP accesses. Related services/service operations where the AMF is the "NF producer". Including slice related aspects of AC, RM and CM. Any impacts from virtual environments that affect RM/CM. Any 3GPP or non3GPP access specific aspects of states or registration management procedures are for 6.7 or 6.10 respectively. 6.3 Session management and continuity functions and flows Related high level function descriptions. Perhaps state models. Related system procedure flows. Related services/service operations where the SMF is the "NF producer". Including slice related aspects of SM. 6.4 Security related functions and flows Related high level function descriptions. Related system procedure flows. Related service based procedures. 6.5 QoS concept and functionality Related high level function descriptions. Related system procedure flows. Related service based procedures. Any QoS related aspects from specific services support. 6.6 Policy and charging control Related high level function descriptions. Related system procedure flows. Related services/service operations where the PCF is the "NF producer". 6.7 3GPP access specific functionality and flows Related high level functions and procedures, including 3GGP access related specifics of RM and CM states and registration procedures. Related service based procedures, if primarily motivated by the procedures here. Also on radio and CN idle related aspects, i.e. including aspects of RRC_inactive. 3GPP access specifics of RM and CM states. Registration area management and area restriction handling. 3GPP access specific aspects of the registration management procedure. MICO, Handover procedures, Service Request procedures and related, including selective activation of UP connections Service Request with impact on SMF/UPF like changing those NFs is considered under 6.3. 6.8 Specific services support Any QoS related aspects from specific services support, like MPS, are handled under 6.5. - NAS level procedures and functions that are needed to support or enable specific services, e.g. for carrying SMS. All common NAS procedures/support for users like SM or SMS should be under 6.2. Here should be only users of common NAS, like SMS specific NAS or like NAS for Location Services. SM specific NAS is under 6.3. - SMS, PWS, IMS or Location Services procedures and functions that are above or outside NAS. 6.9 Interworking and Migration Related high level function descriptions. Related system procedure flows. Related service based procedures. 6.10 Non-3GPP access specific functionality and flows Related high level function descriptions including non3GPP access related specifics of RM and CM states and registration procedures. Related system procedure flows. Related service based procedures. 6.11 Framework functions Related high level function descriptions. Related system procedure flows. Related services/service operations for "NF producers" like NRF or UDM. Function/service registration, discovery, authorisation of usage, ... 7 Rel-16 Maintenance for 5G (excluding 5GS_Ph1) NOTE: FASMO criterion will be strictly enforced. (Please do not submit documents directly to this agenda item.) (to be decided after the Docs submission deadline) 7.1 Architecture enhancements for 3GPP support of advanced V2X services (eV2XARC) 7.2 Wireless and Wireline Convergence for the 5G system architecture (5WWC) 7.3 Access Traffic Steering, Switch and Splitting support in the 5G system architecture (ATSSS) 7.4 Cellular IoT support and evolution for the 5G System (5G_CIoT) 7.5 Enablers for Network Automation for 5G (eNA) 7.6 Enhancement to the 5GC Location Services (5G_eLCS) 7.7 5GS Enhanced support of Vertical and LAN Services (Vertical_LAN) 7.8 Enhancements to the Service-Based 5G System Architecture (5G_eSBA) 7.9 Architecture enhancements for the support of Integrated access and backhaul (IABARC) 7.10 Enhancement of URLLC supporting in 5GC (5G_URLLC) 7.11 Enhancement of Network Slicing (eNS) 7.12 Optimisations on UE radio capability signalling (RACS) 7.13 Enhanced IMS to 5GC Integration (eIMS5G_SBA) 7.14 User Data Interworking and Coexistence (UDICoM) 7.15 Enhancing Topology of SMF and UPF in 5G Networks (ETSUN) 7.16 5GS Transfer of Policies for Background Data Transfer (xBDT) 7.17 Single radio voice continuity from 5GS to 3G (5G_SRVCC) 8 Rel-17 WID (Please do not submit documents directly to this agenda item.) (to be decided after the Docs submission deadline) 8.1 Enablers for Network Automation for 5G - phase 2 (eNA_Ph2) 8.2 Enhanced support of Non-Public Networks (eNPN) 8.3 Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) 8.4 Enhancement of Network Slicing Phase 2 (eNS_Ph2) 8.5 Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) 8.6 Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (ATSSS_Ph2) 8.7 Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS) 8.8 System enhancement for Proximity based Services in 5GS (5G_ProSe) 8.9 Architectural enhancements for 5G multicast-broadcast services (5MBS) 8.10 System enablers for multi-USIM devices (MUSIM) 8.11 Architecture aspects for using satellite access in 5G (5GSAT_ARCH) 8.12 Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) 8.13 5G System Enhancement for Advanced Interactive Services (5G_AIS) 8.14 Enhancement to the 5GC LoCation Services-Phase 2 (5G_eLCS_Ph2) 8.15 Multimedia Priority Service (MPS) Phase 2 (MPS2) 8.16 Dynamic management of group-based event monitoring (TEI17_GEM) 8.17 N7/N40 Interfaces Enhancements to Support GERAN and UTRAN (TEI17_NIESGU) 8.18 System enhancement for Redundant PDU Session (TEI17_SE_RPS) 8.19 IMS Optimization for HSS Group ID in an SBA environment (TEI17_IMSGID) 8.20 Support for Signed Attestation for Priority and Emergency Sessions (TEI17_SAPES) 8.21 Dynamically Changing AM Policies in the 5GC (TEI17_DCAMP) 8.22 IP address pool information from UDM (TEI17_IPU) 8.23 Same PCF selection for AMF and SMF (TEI17-SPSFAS) 8.24 Support of different slices over different Non-3GPP access (TEI17_N3SLICE) 8.25 Minimization of Service Interruption (MINT) 8.26 Architecture Enhancement for NR Reduced Capability Devices (ARCH_NR_REDCAP) 8.27 Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS) 8.28 Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups This agenda is for topics that are not covered by the dedicated agenda items above, e.g. EPC-User Plane Integrity Protection, Non-Seamless WLAN Offload (NSWO) in 5GS, etc. 9 Project Planning and Management (Please do not submit documents directly to this agenda item.) Puneet 9.1 New and Revised Work Items, TS/TR Cover sheets, Exception Sheets (Please do not submit documents directly to this agenda item.) 9.1.1 Rel-17 new and revised Work Items 9.1.2 TS/TR Cover sheets 9.1.3 Revision of Rel-18 SID/WID proposal POSTPONED at SA2#147E 9.1.4 Revision of Rel-18 SID/WID proposal TECHNCIALLY ENDORSED at SA2#147E 9.1.5 Revision of Rel-18 SID/WID proposal APPROVED at SA2#147E 9.2 Review of the Work Plan, Rel-17 WID Status Reports 9.3 Planning future meetings 11 Close of e-meeting 1700 UTC on Friday (22-Nov) Puneet 2.2 Additional Information • 3GU (3GPP Ultimate) will be used for Tdoc # reservations and submission (https://portal.3gpp.org). • Please read introductory material kindly prepared by Maurice at: S2-150746 and by 3GPP. 2.3 Adopting a good practice with 3GU • Please remember to fill in all relevant fields for each document type when requesting a tdoc number. • Please take care to select the appropriate agenda item when requesting for a Tdoc number. Please avoid submitting to multiple agenda items. • Please include all Sources in the Source List field. If this list changes after having requested the tdoc number, please correct them in 3GU before uploading the tdoc. • If you are requesting a CR, remember to give also the relevant WI Code(s) as well as the Release, TS / TR number and Category. • If you are requesting a pCR, please fill in the TS/TR number - as well as the WI Code if it exists. • If you are requesting a TR or TR Cover sheet, please include the TS / TR number related to it. • Please do not use types you are not sure about (e.g. draftCR and response are only used by other WGs, we do not use these types in SA WG2; LS In is for MCC use). • Including all relevant information is a great help for meeting preparation for everyone and, in particular, for your management and support team. 3. E-meeting process: 1. SA2#148E will be an electronic meeting (e-meeting). Participation would be limited to SA2#148E e-meeting registered delegates only. 2. SA2#148E e-meeting will be conducted by e-mail only, i.e. there will be no conference calls (see exception below). All discussions will be public and conducted via the 3GPP_TSG_SA_WG2_EMEET@LIST.ETSI.ORG mailing list. There is no subscription to this list, people registered to the meeting will be added to the list after the end of the submission deadline - 08 Nov (2359 UTC). If you intend to participate in SA2#148E then please register for the meeting here - https://portal.3gpp.org/#/registration?MtgId=60095. 3. Following CC (Chaired by SA2 leadership) may be organized during SA2#148E e-meeting, if needed – CC#1 15 Nov 2021 (Monday) 1330 – 1530 UTC CC#2 19 Nov 2021 (Friday) 1330 – 1530 UTC CC#3 22 Nov 2021 (Monday), AI#9.1.X only 1330 – 1530 UTC • The objective of these conference calls would be to find a way forward on any controversial topics. They won't be used to discuss/process documents. • These CC during e-meeting will have approval power. • No recording of CC is allowed, like 3GPP rules for the F2F meeting. • For CC#2 there will be flexibility to generate new revisions (e.g. if a small change can remove a certain objection). • Additional conference calls may be organized during the e-meeting, if necessary. 4. Only tdocs requested and submitted via 3GU before the "Tdocs submission" deadline will be considered during the e-meeting. At this deadline, 3GU closes and no further tdocs can be requested or submitted. 5. Companies are encouraged to use the SA2 DISCUSSION list to provide comments after the submission deadline. It is better to provide consolidated comments. Author may take those comments into consideration and provide a revision (addressing those comments) at the start of the e-meeting. 6. Tdoc numbers for mirror CRs should be requested and documents submitted by the "Tdocs submission" deadline. Revisions of mirror CRs should not be produced until the CR to the earliest release is Approved. New Tdoc numbers will be allocated to the approved revisions at the Final deadline. 24 hours grace period after the Final deadline will be provided to the authors to upload/email final approved documents (along with any mirrors CRs, if applicable). 7. Any comments or revisions prior to the start of the e-meeting will not be considered. 8. If the Technical Document (TDoc) is not available by the "Docs submission" deadline, it will be marked as WITHDRAWN. 9. If there are no comments/objections on a document for approval by the "Revision by" deadline, it is APPROVED at that time. 10. Revisions may be proposed until the "Revision by" deadline. Comments in the email will not be automatically considered under revisions, so please provide a revision document with your changes. 10.1 For AI# 9.1.3, only the original author should provide the revision. If the non-author would like to provide a revision (e.g. to clearly show their changes) then they should put it in the drafts folder by adding their company name as a suffix (e.g. S2-21xxxxxr01-ABC.zip) on top of the author’s latest revision available in the revisions folder. 11. If there are no comments/objections on a certain revision by the "Final" deadline, it is APPROVED at the final deadline. 12. Any revision of the document can be approved as long as there are no objections. Having concerns/issues is not implicitly considered as an "objection". Therefore, please phrase any potential objections clearly. Providing a revision is not implicitly considered as an "objection" to the older revision(s). Please explicitly state if you have an "objection" to a specific revision and/or if there is another (older) revision that you can "accept". 13. Please clearly indicate "[SA2#148E, AI#, S2-21xxxxx] " in the e-mail subject line, when distributing the documents or commenting on the documents for e-mail approval. Everything between the quotation marks shall be shown as e-mail subject, including the squared brackets. Don't add any other info like the revision number to the e-mail subject. Do not include any other document number in the subject line.  E-mail without the tag "[SA2#148E, AI#, S2-21xxxxx]" will NOT be considered as part of the email approval.  Please DO NOT make changes to the subject line of ongoing e-mails to avoid breaking an e-mail thread.  Email servers from some companies include new tags in the email subject e.g. "[External]" or other characters. This breaks the email thread. Please try to avoid inserting unwanted tags in the email subject.  Please don't forget to indicate Agenda Item number "AI#" according to the Agenda Items shown in the Agenda table. Example: "[SA2#148E, AI#8.1, S2-2199999] Update of references in 23.501" 14. Information on Email "Comment for notes START/END" tag for automated Chair's Note generation:  Each email SHALL start with START/END tag as shown below Tag Format: Comment for notes <> YourName (YourCompanyName) <> Example: Comment for notes <> Michael (ABC Company) provides r01 <> Please find r01 here . This includes changes XYZ on top of the original version.  These are <>/<> tags. Please note "<<" and ">>" are part of tags. Macro searches for these tags. Please DO NOT change anything related to tags. Each email SHALL have these tags. Please ensure that tags are formatted correctly, including when you are copying/pasting tags from another email.  This text will be automatically captured in the Chair's Notes. This text should be very brief i.e., limited to 1 or 2 small sentences and SHALL include YourName (YourCompanyName). If a revision is provided, then this SHALL be indicated within the "Comment for notes <>/<>" tags. Please DO NOT put a hyperlink to the revision document in this part. For the same email thread exactly the same “comments for notes” are not added in the Chair’s Notes. To avoid such a case please modify your comments slightly for the same email thread.  This text will NOT be captured in the Chair's Notes. This text should contain your normal comments/question to document. This should include a hyperlink to the new revision, if provided.  Emails without "Comment for notes <>/<>" tags will be discarded. 15. Information on 3GU upload/FTP server:  SA2#148E e-meeting folder can be accessed at https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_148E_Electronic_2021-11.  Delegates will need to log in (using EOL account) to add files, anonymous access will allow download only.  Please DO NOT attach documents to your e-mails but upload them to the meetings folder on the 3GPP server (see below for more details on e-meeting folders). If you have problems uploading your documents, please send them to SA2 leadership (not the whole SA2 list). 16. Folders for sharing documents and File naming convention:  Inbox (https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_148E_Electronic_2021-11/Inbox) • Purpose: To upload final approved documents with new tdoc#. After the e-meeting FINAL deadline, all approved revisions will be assigned new tdoc# by the e-meeting conveners. • File Naming Convention: For Example - S2-21xxxxx.zip. • File Format: Files shall be in ZIP format. • Rules: Strict file naming convention shall be followed in this folder. Documents not adhering to the file naming convention will be discarded.  Draft (https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_148E_Electronic_2021-10/Inbox/Drafts) • Purpose: To share any draft document prior to the start of the e-meeting. • File Naming Convention: None but using "Draft_" prefix to a filename is recommended. • File Format: Any. • Rules: Please don't upload revisions in this folder during e-meeting. Any revisions shared in the draft folder prior to e-meeting shall be provided again in the revisions folder at the start of the e-meeting using appropriate file naming convention.  Revisions (https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_148E_Electronic_2021-11/Inbox/Revisions) • Purpose: To share revisions during e-meeting. • File Naming Convention: Please use "r01", "r02", etc suffix for revision (not "R01", not "rev1", not "r1", not "R1"). For Example - S2-21xxxxxr01.zip, S2-21xxxxxr02.zip, S2-21xxxxxr03.zip etc. Revisions shall start from r01 and should be increment by 1. Please check for the latest revision number before uploading your document as there may be clashes. • File Format: Files shall be in ZIP format. • Rules: Strict file naming convention shall be followed in this folder. Documents not adhering to the file naming convention will be discarded. Revisions will not be accepted before the start of the e-meeting.  Chair_Notes (https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_148E_Electronic_2021-11/Inbox/Chair_Notes) • Purpose: To share Chair's Notes. • File Naming Convention: ChairNotes__.doc. For Example – ChairNotes_Puneet_02-21-0900.doc, ChairNotes_Puneet_02-27-0900_FINAL.doc etc. • File Format: MS Doc. • Rules: File naming convention shall be followed in this folder. This folder shall only be used by SA2 leadership.  SA2#148E_CC#xx (https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_148E_Electronic_2021-11/INBOX/CCs) • Purpose: To share the way forward discussion/proposal on a controversial issue, show of hands questions, Minor revision of the document marked as “For CC#xx” in the Chair_Notes. • File Naming Convention: None, but for revisions please follow the revisions file naming convention. • File Format: Any. • Rules: Please make a way forward discussion/proposal on a controversial issue, a show of hands questions, latest revisions available at least 1 hour before the start of the CC. 17. Information on Uploading Approved Documents:  SA2 leadership will allocate new tdoc numbers to approved documents at the (or shortly after) FINAL deadline.  Authors need to upload/email final approved documents (along with any mirrors CRs, if applicable) in INBOX (https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_148E_Electronic_2021-11/Inbox) by Document Upload Deadline.  If an approved document has no revision (i.e. original document), then it will NOT get a new tdoc number. Please do not upload the original document again in INBOX as they are already available in the DOC folder.  If an approved document has revision but the original document is approved, then it will NOT get a new tdoc number. Please do not upload the original document again in INBOX as they are already available in the DOC folder.  Revisions will not get a new tdoc number. All revisions will be maintained on the 3GPP server. 18. Input document control for Agenda 8.X  Maximum 4 TDocs (CR) per company (as first author) per Rel-17 agenda item (8.X) will be handled. Since 5MBS (AI #8.9) is only 85% complete and requires major co-ordination with other WGs, maximum 7 TDocs (CR) per company (as first author) will be handled for 5MBS.  Any additional TDocs (CR) will be not be handled and removed from the initial Chair’s note.  Following will not be counted towards the quota - • Contributions on RAN co-ordination SIDs [MINT (AI#8.25), ARCH_NR_REDCAP(AI#8.27), IoT_SAT_ARCH_EPS (AI#8.27), (AI#8.28)] • Multi-company contribution with 10 or more co-signers • Any LS OUT and Discussion Papers • Any TDocs generated during the meeting • Planning documents/status reports from the Rapporteur • Multiple CRs on same topics and with same title but to different TSs (e.g., TS 23.501, 23.502 etc) will be counted as single CR. 19. Guidance on Rel-18 SID/WID  All Rel-18 SID/WID should follow the SID/WID template provided here - https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_147E_Electronic_2021-10/Inbox/DRAFTS/WID_template.docx  Rel-18 SID/WID should include the following - • Self-contained Work Tasks with interdependencies. • TU estimates at Work Task granularity. Please use TU at a granularity in multiple of 0.5 (or if really necessary, at multiple of 0.25 TU). Please avoid complex TU granularity (e.g., 0.13, 0.18 etc.). • Potential RAN dependency. • Potential inter Work Task dependency.  SA2#148E would be the last meeting to handle any new Rel-18 SID/WID (This doesn’t include TEI18 mini WIDs).