[{"name":"SP-230398","title":"LS from SA WG5: LS reply to Reply LS cc SA5 on Network federation interface for Telco edge consideration","source":"SA WG5","contact":"Deepanshu Gautam","contact-id":81664,"tdoctype":"LS in","for":"Action","abstract":"S5-232047 (SP-221321) mentions the following as SA WG5 response SA WG5 is looking into solutions to support requirements on east\/west bound interface including edge federation in the edge computing management work and network slice management capability exposure in the management aspects of network slice management capability exposure work. SA WG5 would provide further updates as appropriate. SA WG5 would like to correct the above statement as follows SA WG5 is looking into solutions to support requirements on east\/west bound interface including edge federation in the edge computing management work (eECM) and network slice management capability exposure work (FS_NSCE). SA WG5 would provide further updates as appropriate. Action: SA WG5 kindly requests TSG SA to consider the correction provided above.","secretary_remarks":"Postponed SP-230270 from SP-99E. Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10270,"status":"noted","reservation_date":"2023-04-27 14:31:54","uploaded":"2023-05-02 16:10:52","revisionof":"SP-230270","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, SA WG6","lsoriginalls":"S5-233147","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230398.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230402","title":"LS from TSG RAN: Reply to LS to 3GPP on ECC request for standardisation support related to ECC Decision (22)07 on 'harmonised framework on aerial UE usage in MFCN harmonised bands'","source":"TSG RAN","contact":"Asbj?rn Gr?vlen","contact-id":60217,"tdoctype":"LS in","for":"Information","abstract":"TSG RAN thanks ETSI TC MSG\/ERM TFES for their LS informing of the ECC request for standardisation support on implementation in harmonised standard of relevant components of ECC Decision (22)07 on harmonised framework on aerial UE usage in MFCN harmonised bands . TSG RAN discussed the issues raised in the LS and took the following actions: To address the OOBE requirements listed in point a), a RAN WG4 objective was added to the Rel-18 NR UAV work item to study and specify the necessary UE types and OOBE requirements for protection of the referred frequency ranges from aerial UE emissions. The updated work item is attached in RP-230782. o The above referred Rel-18 NR UAV work item only addresses NR RAT. To address the same requirements for E-UTRA, a corresponding work item was agreed in RP-230783. o As ETSI TFES work on aerial UE is supposed to be based on the UE conformance testing specification from RAN WG5, related work is planned to be triggered once RAN WG4 completes its task in Q2 2023. For requirements listed in points b), c) and d), RAN WG2 will in the existing Rel-18 NR UAV work item do further technical analysis of existing 3GPP specifications to verify if these three ECC requirements are already covered by the specifications. Depending on the outcome of the analysis, RAN will decide if additional work is needed in the working groups. TSG RAN will keep ETSI TC MSG\/TFES updated on the progress of the work.","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-04-27 14:31:54","uploaded":"2023-05-02 16:10:52","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI MSGTFES","Cc":"TSG SA, RAN WG2, RAN WG4, RAN WG5, SA WG2, CT WG1, GSMA, ERMTG AERO","lsoriginalls":"RP-230804","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230402.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230404","title":"LS from ETSI ISG MEC: LS on publication of ETSI ISG MEC specifications","source":"ETSI ISG MEC","contact":"Dario Sabella","contact-id":104289,"tdoctype":"LS in","for":"Action","abstract":"ETSI ISG MEC would like to inform you that the group has recently published a number of specifications related to the ongoing MEC Phase 3 work (2021-2023). In particular, deliverables on MEC Federation Enablement APIs, V2X Information Services API, IoT API, Location API, MEC Guidelines on Interoperability testing, a MEC Application Package Format and Descriptor Specification and a study on MEC in Park Enterprises deployment scenario. We believe that these topics can be relevant or interesting for your work. {. . .} Action: Please consider using the above information provided by ETSI ISG MEC.","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-04-27 14:31:54","uploaded":"2023-05-02 16:10:52","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT, TSG SA, Other Bodies","Cc":"","lsoriginalls":"MEC(23)000114r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230404.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230405","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 in October 2023 alongside the ITU-T SG13 meeting 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":10080,"status":"noted","reservation_date":"2023-04-27 14:31:54","uploaded":"2023-05-02 16:10:52","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU study groups and external IMT-2020 liaison partners","Cc":"","lsoriginalls":"sp17-jca-imt2020-oLS-00013","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230405.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230406","title":"LS from ITU-T SG13: LS on consent of new Recommendation ITU-T Y.3123 (ex.Y.IMT2020-CEFEC) Framework of edge computing capability exposure for IMT-2020 networks and beyond","source":"ITU-T SG13","contact":"Marco Carugi","contact-id":31658,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs ITU-T SG11 and 3GPP about the consent of new Recommendation ITU-T Y.3123 (formerly Y.IMT2020-CEFEC) Framework of edge computing capability exposure for IMT-2020 networks and beyond","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-04-27 14:31:54","uploaded":"2023-05-02 16:10:52","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG11, 3GPP","Cc":"","lsoriginalls":"SG13-LS75","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230406.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230407","title":"LS from GSMA UPG: LS Response from GMSA UPG to ETSI TFES on harmonised framework on aerial UE usage in MFCN harmonised bands","source":"GSMA UPG","contact":"Wayne Cutler","contact-id":57295,"tdoctype":"LS in","for":"Information","abstract":"GSMA NG\/UPG thanks ETSI TFES for its LS on for standardisation support related to ECC Decision (22)07 on harmonised framework on aerial UE usage in MFCN harmonised bands . The LS was discussed in the NG\/UPG#06 meeting. NG\/UPG Responses to ETSI TFES The incoming LS requested feedback relating to four principal requirements for an aerial UE, namely:- 1. Additional OOBE requirements applicable to aerial UEs in the following frequency bands 1710-1785 MHz, 2500-2570 MHz, 2570-2620 MHz, 2. A mechanism\/feature coherent with the above aerial UE definition in order to differentiate an aerial UE, as defined by ECC Decision 22(07) from terrestrial UE operating under LTE\/NR 5G networks, 3. Differentiation of aerial UE from other terrestrial UE shall not be changed by the end-user, 4. The aerial UE shall not be capable to connect to LTE\/NR 5G networks without aerial subscription. As stated in the incoming LS, the fourth requirement is within the scope of GSMA NG\/UPG. For this requirement, GSMA NG\/UPG would like to draw attention to GSMA PRD NG.128 ( LTE UNI Aerial Profile ). The document is attached to this LS response. With reference to clause 4.2 of GSMA PRD NG.128, the aerial UE must use the well-known UAS APN and this APN must be included in the subscription data of the user of the UE in the HSS of the H-PLMN. GSMA NG\/UPG believes that this enables the stated requirement to be met.","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-04-27 14:31:54","uploaded":"2023-05-02 16:10:52","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TFES","Cc":"TSG SA, TSG RAN, TC-AERO, TC-ERM","lsoriginalls":"UPG06_122","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230407.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230408","title":"LS on progress of 3GPP SA5 R18 work on intent driven management","source":"SA WG5","contact":"Ruiyue Xu","contact-id":61969,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 is responsible for Management and Orchestration which covers aspects such as operation, assurance, fulfillment and automation, including management interaction with entities external to the network operator (e.g. service providers and verticals). Intent driven management for mobile networks is an important topic introduced in SA WG5 as friendly used API to allow a customer to provide intents as the desired state of the network or its services, without any detailed information of how to get to the desired state. SA WG5 started the work item intent driven management for mobile networks since 2018, and completed its Release 17 work on the intent driven management services for mobile networks in June 2022, corresponding published specification is TS 28.312 (Management and orchestration; Intent driven management services for mobile networks). TS 28.312 specifies the concept, use cases, requirements and solutions (including intent management operations and intent model) for the intent driven management for service or network management. {. . .}","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-04-27 14:31:54","uploaded":"2023-05-03 13:37:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG2, GSMA OPG, ITU FG-AN, ITU-T SG2, ETSI NFV IFA, ETSI ZSM, TM Forum","Cc":"TSG SA","lsoriginalls":"S5-233276","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230408.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230409","title":"LS on 3GPP SA5 work on intent interface collaboration","source":"SA WG5","contact":"Ruiyue Xu","contact-id":61969,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 has completed its Release 18 study work on the enhanced intent driven management services for mobile networks. One of the main outcomes is the investigations and potential solutions for collaboration with other SDOs. For the management of 3GPP network and services, two potential deployment scenarios for intent interface are identified: {. . .}","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-04-27 14:31:54","uploaded":"2023-05-03 13:37:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPG, ETSI ZSM, TM Forum","Cc":"TSG SA","lsoriginalls":"S5-233277","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230409.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230410","title":"LS reply to LS on work progress of M.fidtom, 'Framework of intent driven telecom operation and management'","source":"SA WG5","contact":"Ruiyue Xu","contact-id":61969,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank ITU-T SG2 for your LS\/r on work progress of M.fidtom, Framework of intent driven telecom operation and management and the responses on questions in the liaison statement S5-225599. Regarding the 1st explanation related to intent definition, thanks for the update of the intent definition and the reference of 3GPP TS 28.312. However, the definition in the attached SG2-TD232\/PLEN is not referred to the latest version of 3GPP TS 28.312. Following is the intent definition in TS 28.312 v17.3.1: intent: expectations including requirements, goals and constraints given to a 3GPP system, without specifying how to achieve them Regarding the 2nd explanation related to intent driven management, thanks for the detailed clarification on intent driven telecom operation and management and intent driven management . Based on the attached SG2-TD232\/PLEN, our understanding is ITU-T SG2 focuses on defining framework of intent driven telecom operation and management based on a top layered functional framework of AITOM, and intent driven management is introduced as one of the function set. SA WG5 focuses on specifying intent driven MnS (Management Service) to manage 3GPP network and services with adopting SBMA (Service Based Management architecture). Intent driven management services allow MnS consumer to express different types of intents (including intent-CSC, intent-CSP and intent-NOP) and obtain the intent fulfilment information from the MnS producer. The flexibility of SBMA allows the intent driven MnS can be provided by any entity, which means the intent driven MnS may also be provided by intent driven management as defined in ITU-T SG2 to allow corresponding consumer to express their intent. Therefore, SA WG5 suggest ITU-T SG2 to consider to reuse the 3GPP intent driven MnS where appropriate. SA WG5 will continue Rel-18 intent driven management enhancement normative work in June 2023 and welcome to collaborate with ITU-T SG2 and exchange information on the intent driven management topic.","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-04-27 14:31:54","uploaded":"2023-05-03 13:37:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2","Cc":"TSG SA","lsoriginalls":"S5-233545","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230410.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230411","title":"LS from SA WG5: LS reply to TM Forum Liaison: Update on TM Forum Intent Management API and Ontologies - Connector model and 3GPP connector mode","source":"SA WG5","contact":"Thomas Tovinger","contact-id":3654,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank TM Forum for Liaison: Update on TM Forum Intent Management API and Ontologies Connector model and 3GPP connector mode in the liaison statement S5-233194. We appreciate your interest in reuse of 3GPP specifications in your work, but we noted that some 3GPP content has been used and modified in TM Forum documents. We kindly inform you that: 1. 3GPP specifications in TM Forum document can be directly referenced without copying the 3GPP specification content. 2. If referencing alone is not appropriate for the document and if you would like to copy the content from a 3GPP specification, please ask for copyright permission to 3GPP. Such authorization could then be granted (on basis of existing agreement between ETSI and TM Forum if applicable) but without the right to modify the content. If you are concerned about the 3GPP specifications changing afterwards, then TM Forum can use dated references (either to Release or individual Version). TM Forum will also need to monitor to see if changes made by 3GPP need to be reflected by updating the dated references or not.","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-04-27 14:31:54","uploaded":"2023-05-03 13:37:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TM Forum","Cc":"3GPP PCG, TSG SA","lsoriginalls":"S5-233549","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230411.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230412","title":"LS from SA WG5: Reply LS on Resubmitted LS on O-RAN - Applicability of TS 32.404 in NR","source":"SA WG5","contact":"Deepanshu Gautam","contact-id":81664,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks O-RAN WG-10 for the LS on Applicability of TS 32.404 in NR. SA WG5 would like to provide the response as follows: SA WG5 would like to inform O-RAN WG-10 that 3GPP TS 32.404 does relate with 5G as depicted in the scope of the TS. The 5G Performance Measurement defined in 3GPP TS 28.552 (flagged as applicable for the 5G radio technology in the specification repository on the 3GPP Portal (https:\/\/portal.3gpp.org\/)) are based on the template specified in 3GPP TS 32.404. Further, SA WG5 would like to inform that specification repository on the 3GPP Portal (https:\/\/portal.3gpp.org\/) has been updated to flag 3GPP TS 32.404 as applicable to 5G.","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-04-27 14:31:54","uploaded":"2023-05-03 13:37:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG10","Cc":"TSG SA","lsoriginalls":"S5-233613","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230412.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230413","title":"LS from SA WG5: Reply LS on the Consent of draft Recommendations ITU-T M.3384 (ex. M.il-AITOM) and M.3385 (ex. M.ilef-AITOM)","source":"SA WG5","contact":"Xi Cao","contact-id":83332,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank ITU-T SG2 for your LS on the Consent of draft Recommendations ITU-T M.3384 (ex. M.il-AITOM) and M.3385 (ex. M.ilef-AITOM) informing SA WG5 about progress in intelligence levels evaluation of AITOM. SA WG5 would also like to have a clear view on the relationship of draft Recommendations ITU-T M.3384 and M.3385. {. . .}","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-04-27 14:31:54","uploaded":"2023-05-03 13:37:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2","Cc":"TSG SA","lsoriginalls":"S5-233711","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230413.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230414","title":"LS from SA WG5: Reply LS on initiation of a new work item M.eiil-AITOM, 'Effectiveness indicators of intelligence level for AI enhanced telecom operation and management'","source":"SA WG5","contact":"Xi Cao","contact-id":83332,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank ITU-T SG2 for your LS on initiation of a new work item M.eiil-AITOM, Effectiveness indicators of intelligence level for AI enhanced telecom operation and management informing SA WG5 about the initiation of a new work item on effectiveness indicators of intelligence level for AITOM. SA WG5 would also like to inform ITU-T SG2 that SA WG5 is now doing the study on evaluation of autonomous network levels, the study output will be captured in TR 28.909 (the latest version is draft TR 28.909 V0.2.1). In draft TR 28.909 V0.2.1, concept of key effectiveness indicator (KEI) is described in Clause 4.1 and KEI for evaluating autonomy capability for a use case (radio network optimization) is investigated.","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-04-27 14:31:54","uploaded":"2023-05-03 13:37:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2","Cc":"TSG SA","lsoriginalls":"S5-233712","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230414.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230417","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":"CT3 thanks SA6 for on the work carried out on CAPIF alignment with ETSI ISG MEG.CT3 has agreed the attached C3-232625 (CR#0297 to TS 29.222) to enhance 3GPP TS 29.222 to support AEFs with non-RESTful NBIs defined by other SDOs (e.g. ETSI MEC) and as indicated in the CR, this enhancement is not applicable to the AEFs (e.g. SCEF, NEF) defined by 3GPP.CT3 has also agreed the attached CRs C3-231685 (CR#0669 to TS 29.122), C3-230392 (CR#0287 to TS 29.222) to support the extensibility requirement by defining the mechanisms for supporting vendor-specific extensions to the data model.CT3 is still working on this and will provide further feedback based on the progress of CAPIF extensibility.","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-04-27 14:31:54","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"TSG SA, TSG CT","lsoriginalls":"C3-232686","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230417.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230429","title":"LS from SA WG5: LS on Slice based (wholesale) differentiation and charging in roaming","source":"SA WG5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Information","abstract":"3GPP SA5 thanks GSMA NG ENSWI for their LS on Slice based (wholesale) differentiation and charging in roaming.SA5 would like to inform GSMA NG ENSWI, SA5 has created a Rel-18 work item to cover the charging solution for addressing the Business requirements for slice-based (wholesale) differential reporting and charging of traffic in the roaming case, expressed in the LS, based on the TS 23.501 and TS 23.502 procedures related description. This work item (attached S5-234455) is submitted for approval to the next June 3GPP SA#100. SA5 can confirm, by allowing the mapping of the VPLMN S-NSSAI(s) to the HPLMN S-NSSAI(s) to be available to CHF in VPLMN, this solution will allow wholesale with slice based differentiation.The solution is valid for Roaming Home routed as well as for LBO.","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-04-27 14:31:55","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG ENSWI","Cc":"GSMA WAS, GSMA IDS, GSMA NRG, TSG SA","lsoriginalls":"S5-234453","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230429.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230430","title":"LS from SA WG5: LS on LS Reply on O-RAN \u2013 Transport Network Slicing Enhancement IM\/DM TS28.541","source":"SA WG5","contact":"Jan Groenendijk","contact-id":49147,"tdoctype":"LS in","for":"Information","abstract":"3GPP SA5 would like to thank O-RAN for their interest and use of the SA5 specifications for network slicing. This reply documents the actions for SA5 and answers from SA5.","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-04-27 14:31:55","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG SA, SA WG3","lsoriginalls":"S5-234824","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230430.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230431","title":"LS from SA WG6: LS on Reply LS on 3GPP TR 23.700-98 V1.2.0 Analysis","source":"SA WG6","contact":"Sapan Shah","contact-id":76271,"tdoctype":"LS in","for":"Information","abstract":"SA6 thanks GSMA OPAG for their rely LS on 3GPP TR 23.700-98 V1.2.0 Analysis.For, OPAG comments and questions regarding KI#9, #17 and #20, SA6 would like to inform that SA6 would discuss the requirements in a future release.Regarding, \u201cOPAG kindly asks 3GPP SA6 if there have been any updates in their latest versions of the TR related to these KIs (i.e. #6, #10, #22, #9, #17 and #20) and their proposed solutions\u201d \u2013 SA6 would like to inform OPG that SA6 is currently finalizing stage 2 normative work and SA6 will provide further update in future.","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-04-27 14:31:55","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPAG","Cc":"TSG SA","lsoriginalls":"S6-232127","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230431.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230432","title":"LS from ITU-T SG15: LS on information on actions taken by SG15 on inclusive language","source":"ITU-T SG15","contact":"Stefano Ruffini","contact-id":88491,"tdoctype":"LS in","for":"Action","abstract":"This liaison provides information on actions taken by SG15 on the topic of non-inclusive language","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2023-04-27 14:31:55","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IEEE 1588 WG , O-RAN WG4, O-RAN WG5, O-RAN WG6, O-RAN WG9, TSG RAN, TSG SA, IEEE 802.1, IEEE 802.3, IETF","Cc":"","lsoriginalls":"SG15-LS059","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230432.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230433","title":"LS from O-RAN: LS on O-RAN \u2013 Transport Network Slicing Enhancement IM\/DM TS28.541","source":"O-RAN","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"The O-RAN Alliance is committed to evolving radio access networks, making them more open and smarter than previous generations. The key principles of the O-RAN Alliance include: ? Lead the industry towards open, interoperable interfaces, RAN virtualization, AI\/ML and big data enabled RAN intelligence.? Specify APIs and interfaces, driving standards to adopt them as appropriate, and exploring open source where appropriate.? Maximize the use of common-off-the-shelf hardware and merchant silicon and minimizing proprietary hardware. O-RAN Working Group 9 (WG9) is developing O-RAN Transport Network Element (TNE) management interfaces and best practices to support transport capabilities and service demands of RAN and Core subsystems.","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-04-27 14:31:55","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA, TSG RAN","lsoriginalls":"O-RAN-WG9-LS-2023-005","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230433.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230434","title":"LS from 5GAA: 5GAA submission to the 3GPP TSG RAN Rel-19 workshop","source":"5GAA","contact":"Khaled Hassan","contact-id":83637,"tdoctype":"LS in","for":"Information","abstract":"5GAA has submitted a contribution to the TSG RAN Rel-19 workshop with a list of topics prioritized from the automotive perspective. Some of the topics may be relevant to the work of the TSG SA and SA working groups. 5GAA is kindly asking TSG SA to take note of the input it has submitted for the TSG RAN Rel-19 Workshop.","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-04-27 14:31:55","uploaded":"2023-06-05 05:42:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"","lsoriginalls":"5GAA_WG4-236950","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230434.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230435","title":"LS from ITU-T SG11: LS on initiation of new work item ITU-T Q.Req_Frame_RRDN 'Requirements and framework for rapid response to sudden natural disasters in network'","source":"ITU-T SG11","contact":"Ritu Ranjan Mittar","contact-id":71891,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs ITU-T SG2, SG16, ITU-R WP5A, ITU-R WP6A, 3GPP, GSMA that ITU-T SG11 initiated the new work item Q.Req_Frame_RRDN 'Requirements and framework for rapid response to sudden natural disasters in network' during Study Group 11 meeting (Geneva, 10-19 May 2023).","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10250,"status":"noted","reservation_date":"2023-04-27 14:31:55","uploaded":"2023-06-06 07:47:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, SG16, ITU-R WP5A, ITU-R WP6A, 3GPP, GSMA","Cc":"","lsoriginalls":"SG11-LS77","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230435.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]