[{"name":"SP-220722","title":"LS from 5G-MAG: 5G-MAG TARGET 2023 - REFERENCE TOOLS FOR 5G-BASED MEDIA SERVICES","source":"5G-MAG","contact":"Johann Mika","contact-id":94955,"tdoctype":"LS in","for":"Information","abstract":"The 5G Media Action: Group (5G-MAG) is a cross industry association which drives collaboration on the implementation of 5G solutions in the domains of production and distribution of audio-visual media content and services. In its role as 3GPP Market Representation Partner, 5G-MAG brings into 3GPP a consensus view of market requirements for the implementation and deployment of 5G technologies on the topics and features of interest of the media industry. One of the core efforts coordinated by 5G-MAG is the 5G-MAG Reference Tools development programme providing common open-source reference tools to support the implementation and interoperability of 5G Media technologies. For details refer to http:\/\/www.5g-mag.com\/reference-tools. As part of this programme, 5G-MAG is currently in the process of defining a roadmap for the 5G-MAG Reference Tools development programme in 2023 in close contact with the industry and the community of developers under the umbrella title Target 2023 . Details are here https:\/\/www.5g-mag.com\/target2023. As part of this process, the 5G-MAG community has been provided with an overview of media-centric 5G technologies and features in 3GPP Rel-16 & Rel-17 by 3GPP experts. We collected market-oriented use cases and applications that may benefit from 5G media functionalities and may be benefit from a common reference implementation. Based on use cases and technology descriptions, we are currently evaluating implementation efforts and prioritizing use cases based on member support, interest and feasibility. We expect the 2023 roadmap to communicated at IBC 2022 in September 2022. Attached to this letter is the current status and draft roadmap. We would kindly like to inform SA WG4 about the status of the work, and to invite 3GPP members to participate in this open and public collaboration. We also interested in any feedback and new developments with respect to 5G Media technologies.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"","lsoriginalls":"RT0093","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220722.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220723","title":"LS from ETSI ISG MEC: LS reply to 3GPP on Alignment of EDGEAPP and ETSI MEC","source":"ETSI ISG MEC","contact":"Pekka Kuure","contact-id":68365,"tdoctype":"LS in","for":"Information","abstract":"ETSI ISG MEC would like to thank SA WG6 for the LS and consideration for the alignment work. Indeed, as already expressed in past exchanges, the ISG welcomes a collaboration with 3GPP aiming at an alignment between MEC Phase 3 and 3GPP Rel.18 specifications, that would be beneficial for the edge ecosystem as we create consistent standards and avoid duplication of work. This mean that a common approach should be taken, by respecting the autonomous nature of the two standard bodies, but by looking at the joint opportunity to align the standardization work in this convenient time frame (Phase 3 and Rel.18). On the 4 specific guiding principles proposed by 3GPP: 1. ETSI ISG MEC acknowledges that the scope of 3GPP alignment efforts between EDGEAPP and ETSI MEC are to be limited to architecture enhancements that apply only to EDGEAPP. Dually to 3GPP, ETSI ISG MEC is happy to liaise with SA WG6 for architecture recommendation (if any). 2. The ISG acknowledges that the architecture enhancements to support alignment shall ensure backwards compatibility with the existing EDGEAPP architecture. As said, we believe that a reasonable target for the joint alignment is related to Release 18 and MEC Phase 3 specifications (and the intent of the alignment is to not impact on previous specifications, i.e. pre-Phase 3 MEC work). ETSI ISG MEC is happy to liaise with SA WG6 on this aspect if necessary. 3. The ISG agrees that the scope of the alignment shall only focus on the overlapping aspects between the EDGEAPP and ETSI MEC architectures. In particular, the ISG agrees on the 4 alignment aspects suggested by 3GPP, which are analysed in detail in the attached PPT presentation: a. alignment of EAS profile (EDGEAPP) and AppInfo (ETSI MEC), b. alignment of EDGE-3\/Mp1 reference points c. alignment of EDGE-9\/Mp3 reference points d. usage of CAPIF between the two architectures The ISG also agrees that the term alignment does not imply that the reference points will be exactly equivalent. 4. The ISG acknowledges that architecture enhancements shall ensure that EDGEAPP architecture can remain as a standalone or a complete system i.e. EDGEAPP can be deployed independent of the ETSI MEC architecture. Likewise, ETSI MEC architecture can be deployed independently of the EDGEAPP architect. However, the ISG believes that alignment should facilitate a range of deployment options that are able to leverage combinations of the complimentary parts of each independent architecture (for a better context, please refer to the Annex B of the 23.700-98).","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"TSG SA, TSG CT, SA WG3, CT WG3","lsoriginalls":"MEC(22)000383r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220723.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220724","title":"LS from GSMA OPAG: East\/West Bound Interface for Telco Edge consideration","source":"GSMA OPAG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"1 Introduction GSMA OPG Operator Platform API Group (OPAG) has been progressing the development of its roadmap. Through this liaison statement OPAG would like to share the East\/West bound interface drafts aiming to allow load deployments across multiple operative domains. Those capabilities are described in the document EWBI API, and the corresponding YAML file Federation API attached to this LS. 2 Edge computing federation APIs These documents are under draft status and did not reach yet PRD approval. However, those are seen as stable to start considering these interfaces as possible baseline to be evolved to support telco edge federation. 3 Conclusion and actions Telco edge and federation are seen as key capabilities by OPAG. OPAG and GSMA expect that industry harmonisation is reached for telco edge federation definition and support across the industry and SDOs. OPAG is looking forward to collaborating to ensure that fragmentation is avoided on the federation definition by converging towards a common and unique interface reference. Therefore, 3GPP and ETSI are kindly requested to consider OPAG input as a baseline proposal for edge federation that should evolve towards a common industry reference. Furthermore GSMA proposes to 3GPP and ETSI to discuss and agree upon the approach to be adopted to avoid industry fragmentation for edge federation.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI ISG MEC, SA WG6, SA WG2, SA WG5, SA WG3","Cc":"TSG SA","lsoriginalls":"OPAG_25_Doc_05","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220724.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220725","title":"LS from GSMA OPAG: Network federation interface for Telco edge consideration","source":"GSMA OPAG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"1 Introduction As communicated previously GSMA Operator Platform API Group (OPAG) is progressing the documentation of its East West Band allowing federation of Telco Edge computing platforms. Through this liaison statement OPAG would like to share the latest draft of the East West Bound interface aiming to allow loads deployments across multiple operative domains. Those capabilities are described in the documents EWBI API and the corresponding YAML file Federation API attached to this LS. 2 Edge computing service APIs The document is now under final stage review within OPAG and OPG. The document is expected to reach PRD stage in October 2022. 3 Conclusion and actions OPAG expects its EWBI PRD to be used as base reference for ETSI and 3GPP federation concepts under definition and is willing to collaborate in order to avoid market fragmentation. 3GPP and ETSI to consider OPAG input as part of their ongoing standardization activities. 3GPP ETSI and OPG\/OPAG to agree upon the approach to be adopted to avoid market fragmentation for edge platforms federation.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5, SA WG6, SA WG2, ETSI ISG MEC","Cc":"OPG, TSG SA","lsoriginalls":"OPAG_34_Doc_06","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220725.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220726","title":"LS from GSMA OPAG: Network integration interface for Telco edge consideration","source":"GSMA OPAG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"1 Introduction GSMA Operator Platform API Group (OPAG) has been progressing further the definition of its South Band Network Resources (SBI-NR) interface. Through this liaison statement OPAG would like to share the latest draft of the South Band network interface aiming to allow the operator platform to access network functionalities and information. These capabilities are described in the SBI NR document highlighting the network interface and corresponding SDO references needed by the platforms. Edge computing service APIs The document is now under final stage review within OPAG and OPG. The document is expected to reach PRD stage in October 2022. 2 Conclusion and actions OPAG expects to use this document as a baseline of the network capabilities made available to service exposure layer and hope to open a collaboration channel with 3GPP and ETSI in order to enhance these functionalities if required by OPG roadmap. 3GPP and ETSI to consider OPAG input as part of their ongoing standardization activities. 3GPP ETSI and OPG\/OPAG to agree upon the approach to be adopted in order to enhance further network capabilities and interfaces if require against OPG roadmap.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5, SA WG6, SA WG2, ETSI ISG MEC","Cc":"OPG, TSG SA","lsoriginalls":"OPAG_34_Doc_07","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220726.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220727","title":"LS from GSMA OPG: LS to 3GPP SA5 on UE to application server latency","source":"GSMA OPG","contact":"Sandra Ondrusova","contact-id":77474,"tdoctype":"LS in","for":"Information","abstract":"Background GSMA OPG has been working on Network Slice as a Service and its impact on GSMA OP architecture. A relevant metric for a NSC is the latency between the UE and Application Server associated to the network slice. One of the requirements from the NSC is to get the latency between these two endpoints measured and assured. This latency is the sum of the SA WG5 defined E2E delay for network slice (c.f. clause 6.3.1.8 from 3GPP TS 28.554 v17.7.0) and the GST defined latency from (last) UPF to Application Server (c.f. clause 3.4.36 from GSMA NG.116 v7.0). GSMA OPG is keen to understand if there are any existing mechanisms or KPIs that can be used to measure UE-to-Application Server latency defined as above.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA, SA WG6, GSMA ENSWI","lsoriginalls":"OPG_100_Doc_08","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220727.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220728","title":"LS from GSMA OPG: LS reply to 3GPP SA6 on Clarification of Edge Node Sharing","source":"GSMA OPG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Background GSMA OPG thanks SA WG6 for the LS on edge node sharing considering the mapping of GSMA OP and 3GPP EDGEAPP architecture. The OP is a conceptual model specifying the behaviour of edge computing systems that share resources among their subscribers. An OP is described in terms of roles, such as Service Resource Management, Federation Management, and Capabilities Exposure, but specific functional entities are not mandated. An OP manages Cloud and Network Resources, on which applications can be deployed for subscribers and which can be shared with partner OPs. The focus of the OP model is sharing resources between edge computing systems owned by different Operators who do not share a trust domain, and providing an edge computing model to applications without excessive complexity. {. . .}","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"TSG SA, SA WG2","lsoriginalls":"OPG_103_Doc_03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220728.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220731","title":"LS from ITU-T SG11: LS on status of draft Recommendation Q.Sig_Req_ETS_IMS_roaming 'Signalling requirements for emergency telecommunication service in IMS roaming environment'","source":"ITU-T SG11","contact":"Xiaojie Zhu","contact-id":88418,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement aims to inform ITU-T Study Group 2, 3GPP TSG SA, 3GPP TSG SA WG2, 3GPP TSG SA WG6, 3GPP TSG CT about the latest progress on the draft Recommendation Q.Sig_Req_ETS_IMS_roaming.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSGB SA, SA WG2, SA WG6, TSG CT","Cc":"","lsoriginalls":"SG11-LS15","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220731.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220732","title":"LS from ITU-T SG13: LS on the approval of a new ITU-T Supplement on use cases for autonomous networks","source":"ITU-T SG13","contact":"Marco Carugi","contact-id":31658,"tdoctype":"LS in","for":"Information","abstract":"This LS informs about the approval of the first ITU-T SG13 document about autonomous networks, 'Use cases for autonomous networks'.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10140,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSAG, ITU-T SGs, 3GPP, GSMA, IEEE, TMF, IETF, IRTF, ISO\/IEC, ...","Cc":"","lsoriginalls":"SG13-LS5","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220732.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220733","title":"LS from ITU-T SG13: LS on the consent of Recommendation ITU-T Y.3181 (ex-Y.ML-IMT2020-sandbox): 'Architectural framework for Machine Learning Sandbox in future networks including IMT-2020'","source":"ITU-T SG13","contact":"Marco Carugi","contact-id":31658,"tdoctype":"LS in","for":"Information","abstract":"This LS informs about the consent of Recommendation ITU-T Y.3181 (ex-Y.ML-IMT2020-sandbox) 'Architectural framework for Machine Learning Sandbox in future networks including IMT-2020'.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSAG, ITU-T SGs, 3GPP, GSMA, IEEE, TMF, IETF, IRTF, ISO\/IEC, ...","Cc":"","lsoriginalls":"SG13-LS6","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220733.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220734","title":"LS from ITU-T SG13: LS on initiation of new work item ITU-T Y.IMT2020-NFC-req 'Use cases and requirements for network function communication between 5G Public Networks and Non Public Networks in IMT-2020'","source":"ITU-T SG13","contact":"Marco Carugi","contact-id":31658,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs about the initiation of new work item 'Use cases and requirements for network function communication between 5G Public Networks and Non Public Networks in IMT-2020' in Q20\/13.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG16, ITU-T SG20, 3GPP","Cc":"","lsoriginalls":"SG13-LS7","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220734.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220735","title":"LS from O-RAN WG10: LS on O-RAN - UML models and tools to be used by 3GPP SA5","source":"O-RAN WG10","contact":"Marek Michalak","contact-id":86149,"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 10 (WG10) is developing an O-RAN Operations and Maintenance Interface Specification that defines an O1 interface and associated Management Services (MnS) for Fault, Configuration, Performance, File Management and Software Management for O-RAN compliant network functions (NF). The O-RAN WG10 recognizes the value of SA WG5 defined SBMA and is committed to follow SA WG5 specifications as much as possible. During development of WG10 documents we have identified specific areas where we were able to refer to 3GPP documents. For further alignment, WG10 is interested in finding common practice for development of UML models\/diagrams. O-RAN WG10 recognizes that SA WG5 includes UML diagrams into published specifications. While there are FORGE publications with Stage 3 solutions sets, we were not able to locate machine readable UML representation of the NRMs made available in a similar way or to identify which tool(s) have been used to create the diagrams contained in the published specifications. We would like to ask SA WG5 for guidance regarding potential reuse of UML models and diagrams, whether they are accessible to other groups for use in defining and describing extensions to the SA WG5 models. Additionally, O-RAN WG10 would like to ask if SA WG5 has current or planned procedures and tool(s) that should be used to improve the efficiency of generating and maintaining UML diagrams in their documents.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA, TSG RAN","lsoriginalls":"S2022002","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220735.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220736","title":"LS from O-RAN WG9: LS on O-RAN - Transport Network Slicing Enhancement IM\/DM TS 28.541","source":"O-RAN WG9","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. The O-RAN WG9 would like to follow SA WG5 specifications as much as possible. During development of Transport Network Management model for network slicing use case we have found NRM (IM\/DM and IOC definitions) defined by SA WG5 useful and aligned with our work. O-RAN WG9 recognizes that the subject of Network Slicing NRMs has been extensively discussed in 3GPP and would like to ask for information on SA WG5 NRM stage 2 in TS 28.541 clause 6.3.18.2 EP_Transport . We see an opportunity in supporting flexible use cases and addressing virtual nature of RAN and Core subsystems with potential to have a link to the transport model while following the methodology of linking MANO class definitions. O-RAN WG9 is working on detailed solutions for slicing use-cases (O-RAN.WG9.XTRP-MGT.0-v04.0) defined in WG1 Network Slicing Task Group (NSTG). The TN models WG9 is investigating within this activity are defined IETF NETMOD WG (https:\/\/datatracker.ietf.org\/doc\/html\/draft-ietf-teas-ietf-network-slice-nbi-yang). A logical connection \/ attachment point between EP_Transport in 3GPP NRM and an object class in IETF model is required in order to support the cross-domain (RAN, Transport, Virtualization, Core) management of network slice following an example depicted on Fig. 2 on this (https:\/\/datatracker.ietf.org\/doc\/draft-contreras-teas-3gpp-ietf-slice-mapping-00). The existing Transport Domain coordination procedure in TS 28.531 clause 7.9 may need to be extended.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10180,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA, TSG RAN","lsoriginalls":"S2022003","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220736.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220737","title":"LS from CT WG1: LS on V2X policy or ProSe policy request during registration procedure","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 has discussed the possible solutions to support that the UE requests for V2X policy and\/or 5G ProSe policy during registration procedure, but cannot reach the consensus. Due to the time frame for Rel-17, CT WG1 will not pursue this V2X\/ProSe policy request during registration procedure in Rel-17.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10200,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG CT, TSG SA, CT WG3, CT WG4, CT WG6","lsoriginalls":"C1-225451","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220737.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220738","title":"LS from RAN WG3: LS on the scope of resource efficiency for MBS reception in RAN sharing scenario","source":"RAN WG3","contact":"Aijuan Liu","contact-id":43714,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 is discussing resource efficiency for MBS reception in RAN sharing scenarios as requested by the WID in RP-213568 and has identified that the scope of that work task is not restricted with regards to the type of the MBS session (broadcast \/ multicast), while being aware that respective ongoing studies in SA WG2 for Release18 have been conducted for broadcast MBS sessions only.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10210,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"SA WG2, TSG SA","lsoriginalls":"R3-225229","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220738.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220739","title":"LS from SA WG2: LS Out on LS on slice list and priority information for cell reselection and Random Access","source":"SA WG2","contact":"Jinguo Zhu","contact-id":78054,"tdoctype":"LS in","for":"Action","abstract":"SA WG2 is tasked by TSG SA#96 to further work on NR_Slice-Core at Q3 on clarifying the Random access behaviour and how the NSAG priority is formed. Additionally, the sentence describing how Cell Reselection is disabled if the NSAG priorities are not sent needs also be clarified. SA WG2 has discussed the aspects above and agreed the attached CR. Action: SA WG2 kindly asks TSG SA, TSG CT, TSG RAN, RAN WG2, and RAN WG3 to take the above information into account.","secretary_remarks":"Noted. Working agreement #55 is withdrawn (i.e. is unchallenged)","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG CT, TSG RAN, RAN WG2, RAN WG3, CT WG1","Cc":"","lsoriginalls":"S2-2207698","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220739.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220740","title":"LS from SA WG2: Reply LS on 5G ProSe security open items","source":"SA WG2","contact":"Jung Je Son","contact-id":96448,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 appreciate SA for the decision and reply LS on 5G ProSe security open items. In their LS, SA indicated that SA has agreed that SA WG2 and SA WG3 should work on PDU Session Secondary Authentication in Rel-18 as per normal 3GPP working procedures. Related to this, SA WG2 expects SA WG3 to take the lead on the PDU Session Secondary Authentication work that it was not possible to complete during Rel-17. SA WG2 requests that SA WG3 keeps SA WG2 informed of their progress. SA WG2 expects that any work related to architecture and procedures in this area will be performed via collaboration between the 2 WGs.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10220,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG3","Cc":"TSG CT, CT WG1, CT WG3, CT WG4, CT WG6","lsoriginalls":"S2-2207838","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220740.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220741","title":"LS from SA WG2: LS on response to LS on parameters preconfigured in the UE to receive MBS service","source":"SA WG2","contact":"meng li","contact-id":91637,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 would like to thank TSG CT for their 'LS on parameters preconfigured in the UE to receive MBS service' and would like to provide the response: Regarding the questions from CT: Question 1: Which parameters can be preconfigured in the UE to receive MBS service? Question 2: How are these parameters used by the UE? SA WG2 answer: SA WG2 did not reach consensus to answer the questions from TSG CT and also could not agree CRs on this topic.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10230,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT, CT WG1","Cc":"CT WG4, SA WG4, RAN WG2, TSG SA, CT WG6","lsoriginalls":"S2-2207888","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220741.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220742","title":"LS Reply on Reply LS on 5G ProSe security open items","source":"SA WG3","contact":"Samir Ferdi","contact-id":72165,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to thank SA for their LS on 5G ProSe security open items. SA WG3 has discussed it and would like to indicate the following reached agreements. SA decision: - SA asks SA WG3 and CT WGs to remove PDU Session Secondary Authentication from Rel-17 specifications. SA WG3 agreement: SA WG3 has agreed to the attached CR S3-222400 to remove the support for PDU Session Secondary Authentication from TS 33.503 Rel-17 specification. SA decision: - SA has agreed that SA WG2 and SA WG3 should work on PDU Session Secondary Authentication in Rel-18 as per normal 3GPP working procedures. SA WG3 agreement: SA WG3 has agreed to the attached draftCR S3-222262 and WID S3-222366 to work on PDU Session Secondary Authentication in Rel-18. Action: SA WG3 kindly asks SA, SA WG2 to take the above information into account.","secretary_remarks":"CC#1: Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-06 13:13:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"TSG CT, CT WG1, CT WG3, CT WG4, CT WG6","lsoriginalls":"S3-222434","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220742.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220743","title":"LS from SA WG5: LS on customer acceptation of limited QoS degradation to save energy in the network","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 has started its Release 18 study on energy efficiency and energy saving in 5G networks. In this context, SA WG5 is discussing the following potential new use case for energy saving in 5G networks: {. . .} To capture such expectations from NSCs, GSMA NG.116 (Generic Network Slice Template) may have to be updated. In return, NSCs should be able to receive, from their NSPs, information about actual Energy Consumption (EC) savings attributable to their decision to accept limited QoS degradation. SA WG5 has started and continues working on how to define the EC of 5G network functions and network slices and on the methodology to collect necessary measurements. SA WG5 kindly asks NGMN GFN to consider this potential new use case for energy saving in 5G networks. Until now, it has been considered that network operators may deploy various energy saving mechanisms in their networks to reduce their energy footprint, with the constant constraint that no QoS degradation is allowed, i.e. energy saving functionalities activation shall have no impact of the QoS delivered to customers. This potential new use case shows how energy savings in telecommunication networks (respectively services) would not be a network operator (resp. service provider) only concern, but can now be a Customer (e.g. Verticals) concern as well, and that all of them can draw benefits from such a proposal.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10240,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"NGMN GFN, GSMA NG","Cc":"TSG SA","lsoriginalls":"S5-224100","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220743.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220744","title":"LS from SA WG5: Reply LS on DN energy efficiency data analytics","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank SA WG6 for your LS on DN energy efficiency data analytics. SA WG5 would like to reply to SA WG6 questions as follows: SA WG6 question Q1: Is SA WG5 defining Energy Efficiency (EE) KPIs for the enablement layer functions (like EDGEAPP, SEAL) and EE KPIs for the 3rd party applications \/ edge applications? If the answer is yes, how SA WG5 is expected to derive requirements for defining such EE KPIs? SA WG5 reply: SA WG5 would like to highlight that the Energy Efficiency (EE) of any entity of the mobile network (e.g. gNB, 5GC Network Function, network slice, etc.) is defined as the ratio between the Performance of this entity and the Energy Consumption (EC) of this entity. How to define the Performance of an entity is specific to each type of entity; it can be based on traffic volume, number of connected UEs, number of sessions, etc. SA WG5 has defined the Performance of many entities of the 3GPP mobile network. Performance measurements for EDGEAPP functions are defined in TS 28.552 clauses 5.14 and 5.15. Wrt. the Energy Consumption (EC) of an entity of the mobile network, this has been (and continues to be) addressed within SA WG5. In case of Physical Network Function (PNF), SA WG5 leverages on ETSI EE 202 336-12. In case of Virtualized Network Function (VNF), SA WG5 has defined EC KPIs based on the mean vCPU usage of underlying virtual compute resources, collected from ETSI NFV MANO. In Rel-18, SA WG5 will include additional metrics than vCPU usage and will extend its scope from VM-based VNFs to include also containerized VNFs. SA WG5 thinks that enablement layer functions (like EDGEAPP, SEAL) and 3rd party applications \/ edge applications may be treated as aforementioned entities of the mobile network and are, consequently, in the scope of SA WG5. Therefore, SA WG5 expects that SA WG6 can provide SA WG5 with use cases and requirements for EE KPIs \/ analytics. Based on this, SA WG5 can work on corresponding solutions. SA WG6 question Q2: Does MDAS or any other management service provide analytics\/data on EE for the edge\/cloud resources? SA WG5 reply: Though this is in SA WG5 scope, this has not been done in Rel-17. However, this can be addressed in our Release 18 work. Again, SA WG5 would appreciate that SA WG6 provides SA WG5 with use cases and requirements for EE KPI(s) \/ analytic(s), based on which SA WG5 will work on corresponding solutions. SA WG6 question Q3: If the answer to Q2 is yes, is the exposure of energy data\/analytics to 3rd party \/ applications defined as part of SA WG5, and what parameters are expected to be exposed? SA WG5 reply: SA WG5 has defined APIs to collect performance measurements and KPIs specified in TS 28.552 and TS 28.554, including EE KPIs and analytics; the solution is generic and applies to any kind of management data. SA WG5 thinks that, based on operator s policies, such APIs may be exposed to third parties. How such APIs can be exposed to 3rd parties is still under study within SA WG5. SA WG6 question Q4: Is the understanding of SA WG5 that the energy measurement and analytics for external DNs \/ 3rd party applications lies within the coverage of SA WG5; hence any mechanism needs to be specified there? SA WG5 reply: Yes, it is SA WG5 understanding. Please also see our reply to SA WG6 question Q1 and Q3. Reference documents are: o Management and orchestration; 5G end to end Key Performance Indicators (KPI). Available at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3415 o Management and orchestration; 5G performance measurements. Available at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3413","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10250,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG1, TSG SA","lsoriginalls":"S5-224342","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220744.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220745","title":"LS on Reply on initiation new work item 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 Study Group 2 for the information on initiation new work item M.fidtom Framework of intent driven telecom operation and management. SA WG5 is interested in intent driven management topics. 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). SA WG5 has now worked on its two Release 18 study items related to intent driven management for mobile network based on R17 work: Study on enhanced intent driven management services for mobile network and Study on intent-driven management for network slicing, corresponding draft TRs are TR 28.912 (Study on enhanced intent driven management services for mobile networks) and TR 28.836 (Study on intent-driven management for network slicing).","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T Study Group 2","Cc":"TSG SA, TM Forum AN, IETF NMRG, ITU-T SG13","lsoriginalls":"S5-225599","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220745.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220746","title":"LS from SA WG5: Reply LS on UML models and tools to be used by 3GPP SA WG5","source":"SA WG5","contact":"Deepanshu Gautam","contact-id":81664,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks O-RAN for the LS on UML models and tools to be used by SA WG5 and would like to provide the responses as follows: Question 1: Guidelines for other organizations such as O-RAN Alliance to reuse and extend SA WG5 defined UML representations of 3GPP NRMs Answer 1: Regarding whether the other organizations such as O-RAN Alliance s intent to reuse and extend SA WG5 defined UML representations of 3GPP NRMs, it is possible. If you have been considering reproduction of any text from 3GPP Technical Specifications (TSs), we advise that O-RAN documents instead refer to the relevant content in the respective 3GPP TS(s) to avoid any IPR issues. Question 2: Common tool(s) for generating and maintaining information and data models and UML diagrams in SA WG5 documents Answer 2: As per the 3GPP drafting rules defined in TR 21.801 following tools are allowed for creating Graphics in a 3GPP specification. SA WG5 adhere to such guidelines. Microsoft Visio Microsoft Word built-in drawing tools For Unified Modelling Language (UML) graphics: Eclipse Papyrus In addition to above, SA WG5 has been also using PlantUML Question 3: Methodologies such as use of repositories or other mechanisms for maintaining machine readable UML representation Answer 3: SA WG5 does not maintain a repository for UML diagram\/representations codes. In some cases PlantUML is used and corresponding codes are typically included as annex","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"O-RAN","Cc":"TSG RAN, TSG SA","lsoriginalls":"S5-225602","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220746.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220747","title":"LS from SA WG5: LS reply to TM Forum, MEF and GSMA on overall architecture for network slice ordering, provisioning and assurance","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank GSMA, TM Forum and MEF for your replies (respectively S5-222140, S5-222142 and S5-225017) to SA WG5 original LS S5-215530. In its study on network slice capability exposure (FS_NSCE), SA WG5 continues to elaborate the overall architecture for network slice ordering, provisioning and assurance please see non-normative TR 28.824 clause 5.5. SA WG5 would like to invite GSMA, TM Forum and MEF to provide your feedback on this.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10270,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TM Forum, MEF, GSMA","Cc":"TSG SA","lsoriginalls":"S5-225604","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220747.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220748","title":"LS from SA WG6: LS on Clarification of Edge Node Sharing","source":"SA WG6","contact":"Yanmei Yang","contact-id":37039,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 has specified edge enabling architecture (EDGEAPP) in 3GPP TS 23.558 in Rel.17. During Rel.18, eEDGEAPP study has captured Key Issue #22 (clause 4.22) in 3GPP TR 23.700-98 v1.0.1. This Key Issue is based on GSMA OPG requirements for Edge Node Sharing. In Edge Node Sharing context, there are two separate actors or business entities defined by SA WG6 PLMN operator and Edge Computing Service Provider (ECSP). It is possible that PLMN Operator and ECSP are same organization. For Edge Node Sharing aspects, SA WG6 mainly refer the clauses 3.3.5, 3.5.4.3.3, Annex A.2.1 and Annex A.2.2 specified in GSMA OPG Operator Platform Telco Edge Requirements (v2.0) GSMA.OPG.02. {. . .}","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10280,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-05 07:10:44","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPG","Cc":"TSG SA, SA WG2","lsoriginalls":"S6-222004","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220748.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220750","title":"LS from ETSI ISG IPE: Liaison Statement announcing publication of IPE-012: IPv6 based Blockchain","source":"ETSI ISG IPE","contact":"Latif Ladid","contact-id":86673,"tdoctype":"LS in","for":"Information","abstract":"ISG IPE is pleased to announce the latest Group Report (ETSI GR IPE 012) on IPv6 based Blockchain published this August and believe that this could be of interest to your committee: https:\/\/www.etsi.org\/deliver\/etsi_gr\/IPE\/001_099\/012\/01.01.01_60\/gr_IPE012v010101p.pdf. {. . .} Actions: ISG IPE invite any interested parties to provide feedback.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10290,"status":"noted","reservation_date":"2022-08-30 08:43:21","uploaded":"2022-09-09 09:06:51","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TC CABLE, TC CYBER, TC INT WG AFI, TC MSG, TC SmartM2M, TC LI, ISG NIN, ISG ENI, ISG ZSM, ISG NFV, ISG F5G, oneM2M, ETSI Board, TSG CT, TSG SA, 3GPP OP and 3GPP PCG, GAIA-X, ITU-T SG17, SG15 SG11 SG 13, ITU-T SG20, ISO\/IEC JTC 1 SC6 WG7, GSMA, MEF, O","Cc":"","lsoriginalls":"IPE(22)000062","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220750.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220969","title":"LS from SA WG6: Reply LS to OPAG_34_Doc_07_OPAG_LS ETSI-3GPP-Network integration","source":"SA WG6","contact":"Basavaraj (Basu) Pattan","contact-id":61285,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 would like to thank GSMA OPAG for the LS, and sharing the draft Operator Platform's (OP) Network Integration Support APIs definition document that includes SBI-NR and NEF NBI usage for SBI-NR. SA WG6 thanks OPAG for taking into account the work of SA WG6 (3GPP TS 23.558, and corresponding stage 3 work by CT WG3 in 3GPP TS 29.558), namely the definition of Application Relocation API and Confirm User Location API. SA WG6 believes these APIs should be listed as NBI APIs (and not SBI-NR) in clause 1.1 (Table 1) and in clause 1.7, of the Operator Platform's (OP) Network Integration Support APIs definition document, since these APIs are not directly exposed by the core network, but rather at the Edge Enablement Layer (EEL) in reference to the EDGEAPP architecture, which is mapped to OP as specified in Annex D.2 of 3GPP TS 23.558. Further, SA WG6 would like to bring to OPAG s attention that: 1) Network capabilities (some of which are considered in your current document) are also available via EES, where EES may re-expose the network capabilities of the 3GPP core network to the EAS(s) via NB APIs as specified in clause 8.7.3 of 3GPP TS 23.558 with additional EEL abstraction 2) Furthermore, you may like to consider the additional EES capabilities that are available to Edge Application Server (EAS) via NBI APIs as specified in clause 8.6 of 3GPP TS 23.558, in meeting the OP requirements. SA WG6 agrees that collaboration among SDOs (3GPP, ETSI ISG MEC, and GSMA) is essential to avoid market fragmentation. As part of Release 18, SA WG6 is currently studying on enhancements to architecture for enabling Edge Applications in 3GPP TR 23.700-98, which includes additional NBI APIs in new R18 functionality e.g. to support federation and roaming. Should you have any queries or further clarifications on these APIs, SA WG6 is happy to elaborate and provide more information.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10300,"status":"noted","reservation_date":"2022-09-09 09:00:27","uploaded":"2022-09-09 09:06:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPAG","Cc":"TSG SA, SA WG2, SA WG3, SA WG5, ETSI ISG MEC, GSMA OPG","lsoriginalls":"S6-222337","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220969.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220970","title":"Forward on S6-222332, LS on Network federation interface for Telco edge consideration","source":"SA WG6","contact":"Niranth Amogh","contact-id":39608,"tdoctype":"LS in","for":"Action","abstract":"Background: GSMA OPG has developed PRD for Operator Platform Telco Edge Requirements which specifies architectural requirement and a corresponding reference architecture for Operator Platform. GSMA OPAG is developing the API specifications for interfaces or the Operator Platform. GSMA OPG, 3GPP and ETSI MEC ISG are coordinating to develop a single harmonized system architecture for edge computing. In this context, SA WG6, SA WG2 and SA WG5 have received the attached LS from GSMA OPAG about East West Bound Interface (EWBI) APIs PRD for feedback. The EWBI APIs PRD may have impacts to the edge computing work for Rel.18 in SA and CT WGs and hence a coordinated response to GSMA OPAG is required. SA WG6 is currently reviewing the EWBI APIs PRD and may provide detailed technical response for December Plenary to enable a coordinated LS response by TSG SA to GSMA OPAG. SA WG6 asks SA WG2, SA WG3 and SA WG5 to review the EWBI PRD and provide any technical response to TSG SA by December Plenary for a coordinated LS response by TSG SA to GSMA OPAG. SA WG6 asks SA to create a coordinated response, if necessary, based upon the inputs to the December plenary from the SA WGs. Action: SA WG6 asks SA to create a coordinated response, if necessary, based upon the inputs to the December plenary from the SA WGs.","secretary_remarks":"Consolidated response to be developed by TSG SA. Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10030,"status":"noted","reservation_date":"2022-09-09 09:00:27","uploaded":"2022-09-09 09:06:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG5, SA WG2, SA WG3","Cc":"CT WG4, CT WG3, CT WG1, TSG CT","lsoriginalls":"S6-222543","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220970.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220971","title":"LS from SA WG6: Reply LS to Network federation interface for Telco edge consideration","source":"SA WG6","contact":"Samar Shailendra","contact-id":93216,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 would like to thank GSMA OPAG for the LS, the draft EWBI APIs interface definition document and the YAML file. SA WG6 has noted the interface definition document and the YAML file and we are currently studying the impact of the same on Edge Enabler Layer involving multiple ECSPs in Release 18 (see TR 23.700-98). Should we have any queries post our analysis, we will revert to GSMA OPAG for further clarifications. SA WG6 acknowledges that collaboration among SDOs (3GPP, ETSI ISG MEC, and GSMA) is essential to avoid market fragmentation. As part of Release 18, SA WG6 also intends to develop an external TR to capture alignment aspects of EDGEAPP with ETSI MEC and GSMA OP.","secretary_remarks":"Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10310,"status":"noted","reservation_date":"2022-09-09 09:00:27","uploaded":"2022-09-09 09:06:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPAG","Cc":"TSG SA, SA WG2, SA WG3, SA WG5, ETSI ISG MEC, GSMA OPG","lsoriginalls":"S6-222557","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_97E_Electronic_2022-09\/Docs\/SP-220971.zip","group":"SP","meeting":"SP-97-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]