[{"name":"SP-231209","title":"LS from ITU-T SG20: LS on the consent of draft Recommendation ITU-T Y.4493 (ex Y.IoT-AOS-prot) 'Autonomic operations support protocols in the Internet of things'","source":"ITU-T SG20","contact":"Hyoung Jun Kim","contact-id":46093,"tdoctype":"LS in","for":"Information","abstract":"This Liaison Statement informs about the consent of draft Recommendation ITU-T Y.4493 (ex Y.IoT-AOS-prot) 'Autonomic operations support protocols in the Internet of things' in Q3\/20.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2023-11-07 10:19:15","uploaded":"2023-11-07 10:20:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG11, IRTF, IETF, ETSI, 3GPP, IEEE","Cc":"","lsoriginalls":"ls96-cover","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231209.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231210","title":"LS from ITU-T SG2: LS on the initiation of a new work item on draft Supplement ITU-T Y.Sup.VFS 'Functional architecture of connected vehicle formation supporting based on edge computing'","source":"ITU-T SG2","contact":"Hyoung Jun Kim","contact-id":46093,"tdoctype":"LS in","for":"Information","abstract":"This Liaison Statement informs ITU-T SG13, ITU-T SG16, 3GPP, ISO\/TC204 on the initiation of a new work item on draft Supplement ITU-T Y.Sup-VFS 'Functional architecture of connected vehicle formation supporting based on edge computing'.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2023-11-07 10:19:15","uploaded":"2023-11-07 10:20:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG13, ITU-T SG16, 3GPP, ISO\/TC204","Cc":"","lsoriginalls":"ls102-cover","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231210.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231211","title":"LS from NGMN Board: NGMN Liaison Statement to 3GPP regarding a new NGMN Board 6G Publication","source":"NGMN Board","contact":"Luke Ibbetson","contact-id":75739,"tdoctype":"LS in","for":"Information","abstract":"Sharing recent publication entitled 6G Position Statement: An Operator View The NGMN Board would like to point 3GPP PCG, 3GPP OP, TSG RAN, TSG CT and TSG SA to it s recent 6G publication entitled 6G Position Statement: An Operator View , available at https:\/\/www.ngmn.org\/wp- content\/uploads\/NGMN_6G_Position_Statement.pdf. This NGMN Board publication describes how the industry needs to transform the way new technology generations are introduced taking a proactive stance and emphasising the need for a graceful evolution towards 6G. The publication provides comprehensive guidance across several key requirements and design principles, including network simplification, absolute energy reduction, network AI transformation and predictive network management, safe and resilient infrastructure, global 6G standards, software upgrade to 6G, no intrinsic need for hardware refresh, no compromise to existing services (Voice) and access across mobile, fixed and non-terrestrial networks. NGMN encourages 3GPP members to review the Position Statement and take it into consideration for development of 3GPP standards towards 6G. NGMN Board members will make themselves available for further explanation offline upon request.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2023-11-07 10:19:15","uploaded":"2023-11-07 10:20:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP PCG, 3GPP OP, TSG RAN, TSG CT, TSG SA","Cc":"","lsoriginalls":"LS to 3GPP 6GPS V1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231211.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231212","title":"LS from GSMA 5GMRR: LS reply to S3-233786 and S3-234296 on the introduction of the domain ipxnetwork.org and clarifications of the Outsourced SEPP and Hosted SEPP deployment scenarios","source":"GSMA 5GMRR","contact":"Pieter Veenstra","contact-id":86411,"tdoctype":"LS in","for":"Information","abstract":"GSMA NG 5GMRR thanks SA WG3 for the reply to our LS on the use of the domain ipxnetwork.org in certain GSMA deployment scenarios for 5G SA Roaming. This LS provides some background on the use of the domain ipxnetwork.org in the broader context of the GSMA defined set of 5GS deployment models for 5G SA Roaming, and responds to the questions regarding the Outsourced SEPP and Hosted SEPP deployment scenarios.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2023-11-07 10:19:15","uploaded":"2023-11-07 10:20:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"TSG SA, SA WG1, SA WG2, CT WG4","lsoriginalls":"5GMRR Doc 44_36r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231212.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231213","title":"LS from ITU-T CITS: LS on the establishment of an Expert Group on Communications Technology for Automated Driving","source":"ITU-T CITS","contact":"T. Russell Shields","contact-id":51121,"tdoctype":"LS in","for":"Information","abstract":"Through this liaison statement, the ITU Collaboration on ITS communication standards (ITU CITS) would like to inform about the establishment of an Expert Group on Communications Technology for Automated Driving. ITU-T SG 16, ITU-R SG 5, and organizations participating in ITU CITS are invited to provide experts to participate in this Expert Group.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2023-11-07 10:19:15","uploaded":"2023-11-07 10:20:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"External Bodies","Cc":"ITU-T TSAG, SG 2, SG 3, SG 5, SG 9, SG 11, SG 13, SG 15","lsoriginalls":"CITS-LS14","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231213.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231215","title":"LS from CT WG4: LS on modifications for PRINS middle box","source":"CT WG4","contact":"Shunsuke Dojiri","contact-id":96171,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 would like to thank TSG SA for the LS on 'Reply LS on Roaming Hubs' in C4-234380 \/ SP-231203. CT WG4 is positively willing to start the stage 3 protocol work to support the requirement defined by the Roaming5G work item, and CT WG4 is planning to have it approved in Rel-18 by March 2024. And CT WG4 kindly requests SA WG3 to finalize the corresponding stage2 by December 2023.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10220,"status":"noted","reservation_date":"2023-11-07 10:19:15","uploaded":"2023-11-07 10:20:17","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"TSG CT, GSMA NG 5GMRR, SA WG1, TSG SA","lsoriginalls":"C4-234666","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231215.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231217","title":"LS from SA WG5: Reply to Liaison Statement from ETSI EE PS","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks ETSI EE\/EEPS for your Liaison Statement to SA WG5. SA WG5 would like to provide you with the following updates: 1. 3GPP Release 18 work item on Energy Efficiency is planned to be completed by December 2023; 2. Some of the three topics mentioned in your LS are still being addressed in the context of this release, e.g. defining an EE KPI for URLLC based on reliability; 3. The remaining topics will be addressed in Release 19, starting from January 2024, as left-over topics from Release 18. This includes defining EE KPIs for other types of network slices (e.g. V2X), estimating the energy consumed by Containerized VNFs (as, for now, only VM-based VNFs have been considered); 4. The content of the Release 19 study on energy efficiency \/ energy saving is currently under construction and will be stable by December 2023 latest. With regard to the work undertaken in ETSI EE PS on multi-dimensional energy efficiency metrics, SA WG5 would be happy to collaborate with ETSI EE EEPS. In general, SA WG5 is willing to pursue the collaboration with ETSI EE and ITU-T SG5 on aspects related to energy efficiency and energy saving, and expects we ll keep each other updated.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2023-11-07 10:19:15","uploaded":"2023-11-07 10:20:17","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI EE EEPS","Cc":"ITUT SG5, TSG SA","lsoriginalls":"S5-236930","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231217.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231218","title":"LS from SA WG6: LS on developing a security solution for PINAPP architecture","source":"SA WG6","contact":"Michel Roy","contact-id":72161,"tdoctype":"LS in","for":"Information","abstract":"Based on TSG SA#101 guidance quoted below: TSG SA ask SA WG3 and SA WG6 to discuss the work on PINAPP Security in Q4\/2023 and if any further work that requires an Exception is needed in Rel-18, then inform TSG SA#102. SA WG6 asks SA WG3 to specify the appropriate security mechanisms that are essential for completion of R18 PINAPP work-item, based on the Stage 2 architecture specified in TS 23.542. NOTE: within TS 23.542, the term application layer architecture is synonymous with application enablement layer SA WG6 summarizes PINAPP security aspects described in 3GPP TS 23.542 below: The architectural security requirements of the application enablement layer are defined in clause 5.2.7. The reference points between functional entities of the application enablement layer are defined in clauses 6.2 and 6.4. The procedures and information flows of the application enablement layer are defined in clause 8, and include aspects related to security credentials usage, authentication, and authorization. For completeness, SA WG6 indicates that related stage 3 work is ongoing in CT WG1 (TS 24.583), and in CT WG3 (TS 29.583).","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10140,"status":"noted","reservation_date":"2023-11-07 10:19:15","uploaded":"2023-11-07 10:20:17","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"CT WG3, CT WG1, TSG SA","lsoriginalls":"S6-233112","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231218.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231219","title":"LS from GSMA 5GMRR: Elaborated LS reply to S3-234350 on Roaming Hub requirements as applicable to the Modified PRINS solution","source":"GSMA 5GMRR","contact":"Pieter Veenstra","contact-id":86411,"tdoctype":"LS in","for":"Information","abstract":"GSMA NG 5GMRR thanks SA WG3 for further improving PRINS as we already welcomed in our initial reply to SA. This LS is acknowledging SA WG3 s Objective: for 5G SA roaming to address certain security shortcomings in 2G-4G roaming, most notably the lack of end-to-end security in the signalling between VPLMN and HPLMN. This design principle is also the ultimate Objective: for the work in GSMA NG 5GMRR, which seeks a solution that achieves this Objective: while still allowing roaming hub business. Please note that GSMA NG 5GMRR is sending in two separate LS items in response to S3-234350 on the topic of Modified PRINS for both Roaming Hub (this LS) and for IPX Service Hub (the accompanying LS).","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2023-11-07 10:19:15","uploaded":"2023-11-10 10:01:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"TSG SA, SA WG1, TSG CT, CT WG4","lsoriginalls":"5GMRR Doc 45_13r7","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231219.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231220","title":"LS from GSMA 5GMRR: Elaborated LS reply to S3-234350 on Roaming Hub requirements as applicable to the Modified PRINS solution","source":"GSMA 5GMRR","contact":"Pieter Veenstra","contact-id":86411,"tdoctype":"LS in","for":"Information","abstract":"GSMA NG 5GMRR thanks SA WG3 for further improving PRINS as we already welcomed in our initial reply to SA. This LS is acknowledging SA WG3 s Objective: for 5G SA roaming to address certain security shortcomings in 2G-4G roaming, most notably the lack of end-to-end security in the signalling between VPLMN and HPLMN. This design principle is also the ultimate Objective: for the work in GSMA NG 5GMRR, which seeks a solution that achieves this Objective: while still allowing IPX Service Hub business. Please note that GSMA NG 5GMRR is sending in two separate LS items in response to S3-234350 on the topic of Modified PRINS for both IPX Service Hub (this LS) and for Roaming Hub (the accompanying LS).","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2023-11-07 10:19:15","uploaded":"2023-11-10 10:01:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"TSG SA, SA WG1, SA WG2, TSG CT, CT WG4","lsoriginalls":"5GMRR Doc 45_14r7","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231220.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231221","title":"LS from ITU-T JCA-IMT2000: LS on Invitation to update the information in the IMT-2020 and beyond roadmap","source":"ITU-T JCA-IMT2000","contact":"Scott Mansfield","contact-id":42415,"tdoctype":"LS in","for":"Information","abstract":"The ITU-T Joint Coordination Activity for IMT2020 and Beyond (JCA IMT2020) thanks all that have replied to previous requests for input on IMT-2020 and beyond related standardization work. The current online version of the roadmap is available from the JCA-IMT2020 website. The objective of the roadmap is to support IMT-2020 and beyond standardization coordination. IMT-2020 and beyond are the important topics for our industry, and many standardization-related activities are held in various entities. The JCA is progressing this work in a form of roadmap of IMT2020 and beyond standardization. JCA-IMT2020 will keep updating this roadmap, and therefore we solicit your information about updates. If you send us the latest information of your activity related to 5G and beyond as well as Network Function Virtualization (NFV), programmable networks, self-managed networks, autonomous network, slicing (including orchestration and capability exposure), fixed-mobile and satellite convergence (FMC) and Information-Centric Networking (ICN), machine learning and other activities that are strongly related to IMT 2020, we will reflect it in the next roadmap update, which will be performed online soon after the next JCA IMT2020 meeting. Please submit your updates using the template to be found in appendix below. In the last column of this template we expect to get a direct pointer to your document and not to the website where one needs to search for your document. Should you wish to communicate any additional information about your specifications and projects, we invite you to do so. If you have a representative that wishes to present at an upcoming JCA-IMT2020 meeting, please let us know. In addition, if not done yet, we invite the ITU-T Study Groups, SDOs, fora to nominate a representative to this group. JCA-IMT2020 anticipates having its next meeting on 5 March 2024 alongside the ITU-T SG13 activities in Geneva. We invite your inputs\/updates to the roadmap.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2023-11-07 10:19:15","uploaded":"2023-11-10 10:01:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXternal Bodies","Cc":"","lsoriginalls":"sp17-jca-imt2020-oLS-00014","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231221.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231222","title":"LS from ITU-T SG13: LS on initiation of new work item ITU-T Y.ecs-reqts 'Edge computing Functional requirements of edge computing service (ECS)'","source":"ITU-T SG13","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement introduces the initiation of new draft Recommendations on 'Edge computing - Functional requirements of edge computing service (ECS)'.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2023-11-07 10:19:16","uploaded":"2023-11-24 07:46:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG11, SG16, SG20, ISO\/IEC JTC 1\/SC 38, ETSI, IETF, TSG SA","Cc":"","lsoriginalls":"SG13-LS129","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231222.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231223","title":"LS from CT WG3: Reply LS on CAPIF extensibility","source":"CT WG3","contact":"Abdessamad EL MOATAMID","contact-id":89270,"tdoctype":"LS in","for":"Information","abstract":"CT WG3 thanks SA WG6 and SA WG3 on the work carried out on CAPIF alignment with ETSI ISG MEG. CT WG3 would like to inform SA WG6 and SA WG3 that CT WG3 progressed on the definition of the related stage 3 work by supporting the extensibility of query parameters via the attached agreed CRs to the concerned specifications.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10210,"status":"noted","reservation_date":"2023-11-07 10:19:16","uploaded":"2023-11-24 07:46:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, SA WG6","Cc":"ETSI ISG MEC, TSG CT, TSG SA","lsoriginalls":"C3-235619","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231223.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231225","title":"LS from SA WG1: Reply LS on requirements for slice-based PLMN selection","source":"SA WG1","contact":"Kurt Bischinger","contact-id":26063,"tdoctype":"LS in","for":"Information","abstract":"Requirement related to slice-based PLMN selection as defined in 3GPP TS 22.261 as follows: For a roaming UE activating a service\/application requiring a network slice not offered by the serving network but available in the area from other network(s), the HPLMN shall be able to provide the UE with prioritization information of the VPLMNs with which the UE may register for the network slice. SA WG1 has agreed to remove the requirement in Rel. 18 and will coordinate with CT WG1 about any future service requirements on this topic.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2023-11-07 10:19:16","uploaded":"2023-11-24 07:46:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"TSG SA, TSG CT, SA WG2","lsoriginalls":"S1-233272","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231225.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231227","title":"LS Reply on developing a security solution for PINAPP architecture","source":"SA WG3","contact":"Alec Brusilovsky","contact-id":72017,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank SA WG6 for their incoming LS in (S6-233112, LS on developing a security solution for PINAPP architecture) where SA WG6 is requesting SA WG3 to specify the appropriate security mechanisms that are essential for completion of the Rel-18 PINAPP work item. After investigating the SA WG6 request, SA WG3 agreed on the following: The PINAPP security solution can be based on HTTPS and focus on protection of PINAPP reference points A security token can be pre-provisioned on the PINE\/PEMC\/PEGC\/PIN Server\/AS for authentication and authorization (it is up to implementation. how to distribute credentials) SA WG6 can define the format of the token for interoperability between PINE\/PEMC\/PEGC\/PIN Server\/AS The PIN Server can be authorized to generate and distribute the tokens (similar to Edge Configuration Server in Edge), for example when a PINE joins the PIN it may receive the token.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2023-11-07 10:19:16","uploaded":"2023-11-24 07:46:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"CT WG3, CT WG1, TSG SA","lsoriginalls":"S3-235074","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231227.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231228","title":"LS from SA WG4: Reply LS on documenting code normatively in 3GPP Forge","source":"SA WG4","contact":"Richard Bradbury","contact-id":82569,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 would like to thank SA WG5 for its LS on documenting code normatively in 3GPP Forge (rather than in specification documents) and is following this topic with interest with a view to possibly adopting this practice in its stage 3 technical specifications. SA WG4 would like get confirmation about some assumptions and open questions based on the Discussion Paper [S5-235145] attached to the LS {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2023-11-07 10:19:16","uploaded":"2023-11-24 07:46:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA","lsoriginalls":"S4-231915","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231228.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231284","title":"LS from SA WG5: LS on issues with Packet Uu Loss Rate with delay threshold in the DL per DRB per UE","source":"SA WG5","contact":"Ashutosh Kaushik","contact-id":91962,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 is trying to define a new KPI on DL reliability with delay threshold in RAN. The KPI intends to use a measurement newly defined in TS 38.314, clause 4.2.1.5.2. Here below, SA WG5 provides its understanding of the problem that exist in this measurement. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10180,"status":"noted","reservation_date":"2023-11-24 07:57:26","uploaded":"2023-11-24 08:12:04","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"TSG SA, RAN WG3","lsoriginalls":"S5-237941","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231284.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231285","title":"LS from SA WG5: LS on network energy related information exposure","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 has observed the TR 23.700-66 V0.1.0 Key Issue #1 (Network energy related information exposure), and would like to provide SA WG2 with the following information. SA WG5 has been already working on energy efficiency and energy saving for several releases and has specified Energy Consumption (EC) KPIs, including (but not limited to): {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2023-11-24 07:57:26","uploaded":"2023-11-24 08:12:04","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG SA, SA WG1","lsoriginalls":"S5-238106","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231285.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231286","title":"LS from SA WG5: LS on the progress update of AI\/ML Management specifications in SA5","source":"SA WG5","contact":"Hassan Al-kanani","contact-id":47274,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 has been following the progress of study on Artificial Intelligence (AI) \/ Machine Learning (ML) for NR air interface (FS_NR_AIML_air) as documented in TR38.843, RAN intelligence function (NR_AIML_NGRAN-Core) support for AI\/ML-based services (AIMLsys) as documented in TS 23.288 and would like to draw your attention to the relevant work that SA WG5 has been conducting on the specifications of AI\/ML management, addressing OAM support for the AI\/ML features and capabilities in 5GS including the RAN domain. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10200,"status":"noted","reservation_date":"2023-11-24 07:57:26","uploaded":"2023-11-24 08:12:04","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG1, RAN WG2, RAN WG3, SA WG2","Cc":"SA WG1, TSG SA, TSG RAN","lsoriginalls":"S5-238107","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231286.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231446","title":"LS from ETSI ISG ISAC: Launch of new ETSI ISG ISAC","source":"ETSI ISG ISAC","contact":"Alain Mourad","contact-id":72138,"tdoctype":"LS in","for":"Information","abstract":"ETSI has recently launched a new Industry Specification Group for Integrated Sensing and Communications (ISG ISAC) for an inaugural 2-year release. This group will establish the technical foundations for ISAC technology development and standardization in 6G. 87 participants from both the industrial sphere and the academic sphere took an active part in the kick-off meeting, which was held at ETSI premises, in Sophia Antipolis, France, on November 17, 2023. The founding members of the group elected Alain Mourad from InterDigital as Chair of the group, and Ayman Naguib from Apple, Richard Stirling-Gallacher from Huawei, and Henk Wymeersch from Chalmers University of Technology as the Vice Chairs. ISAC refers to the use of radio signals to detect and estimate characteristics of objects in the environment with the network acting as a radar sensor utilizing its own radio signals to comprehend the physical world it operates within. This enables the network to collect data on a plethora of device and object features, which can be used to enhance network operations, augment existing services such as XR and digital twins, and enable new services like gesture and activity recognition, object detection and tracking, and imaging and environment reconstruction. The ETSI ISAC ISG s mission is to enable ETSI members to coordinate their 6G pre-standard research efforts on ISAC and pave the way for the 6G standardization of the technology. The group will define a prioritized set of 6G use cases and sensing types, along with a roadmap for their analysis and evaluation. The group also aims to develop advanced channel models for ISAC use cases and sensing types, with validation through extensive measurement campaigns, addressing gaps in existing channel models (e.g., 3GPP, IEEE 802. ITU-R). Output for architectures and deployment considerations, KPIs, and evaluation methodologies will also be provided. In parallel, the group will undertake two studies, with a first analysis of the privacy and security aspects associated with sensing within the ISAC 6G framework, and a second analysis of the impact of widespread deployment of ISAC on the UN sustainable development goals. ETSI ISG ISAC initially (in the first 2-year release) intends to produce informative documents such as ETSI Group Reports (GR), as well as evaluation framework documents including simulations and measurements. The group s activities and deliverables will be complementary to existing work on ISAC in standards development organizations including ETSI. ISG ISAC will establish relationships with other ETSI bodies and the wider industry to avoid duplication, maximize synergies and act to ensure broad industry adoption of ISAC technology. Further information on the ETSI ISG ISAC terms of reference, work programme, planned deliverables, and other documentations are available through the ISG portal: ETSI ISAC committee page To get involved with ETSI ISG ISAC, please contact isgsupport@etsi.org.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10230,"status":"noted","reservation_date":"2023-11-30 13:21:32","uploaded":"2023-11-30 13:56:13","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP and External Bodies","Cc":"","lsoriginalls":"ISC(23)000016r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231446.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231589","title":"LS from ETSI EE: Liaison statement to 3GPP SA5","source":"ETSI EE","contact":"Beniamino Gorini","contact-id":68683,"tdoctype":"LS in","for":"Information","abstract":"ETSI EE \/ EEPS would like to acknowledge the reception of the liaison S5-236930. Actions: Related to that liaison, ETSI EE would like to inform SA WG5 that: Regarding ES 203 228 a new WI (RES\/EE-EEPS69) has been started in the meeting ETSI EE #64 in October 2023. This new WI will gather updates on the ES also accordingly to the items we exchanged in previous liaisons and on which you inform us you will be working in Release 18 (latest updates) and Release 19 (new topics). An alignment on these points is then welcome in the next months. Particularly, the new WI scope is based on the following items o Investigate on the definition of new EE KPIs which consider aspects such as e.g. coverage area, user experience, reliability of URLLC network slice, o Specify new EE KPIs for network slices, e.g.: EE KPI for V2X, EE KPI for URLLC based on reliability o Integrate EC metrics for NF composed by VNFs and evolutions such as Containerized VNFs Regarding Multi-Dimensional EE, the current status of the activities (also considered in the above mentioned new WI) is related to the inclusion of quality measurements for the case of eMBB set of use cases. The WI will further investigate similar measurements for the URLLC and MMTC cases. ETSI EE would appreciate an update of the latest status on these topics from SA WG5 after the next meetings, as scheduled and reported in the liaison sent.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10240,"status":"noted","reservation_date":"2023-12-05 06:19:34","uploaded":"2023-12-05 06:26:22","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA","lsoriginalls":"EE(23)064031r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231589.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]