[{"name":"SP-221006","title":"LS from 5G ACIA: 5G Edge Computing Use Cases & Requirements","source":"5G ACIA","contact":"Andreas Mueller","contact-id":81087,"tdoctype":"LS in","for":"Information","abstract":"5G-ACIA has produced an internal report on edge computing use cases and requirements for industrial 5G networks and it is now working on a whitepaper about the various edge deployment options and architectural considerations for the edge components. This 5G-ACIA internal technical report aims at identifying and understanding industrial edge use-cases, their requirements concerning the edge computing infrastructure, and the related communication requirements. The service requirements are analyzed in 3GPP TS 22.104 which is consulted for comparison and gap analysis for edge related requirements. The following use-cases that attribute to the gaps with existing 3GPP Standards documents are described below in a nutshell. The first table describes use case title and the corresponding KPI\/parameters that might be modified\/added. The second table identifies 3GPP document section that might require modifications. {. . .} Actions: 5G-ACIA kindly asks 3GPP to take note of the identified gaps and limitations in Rel-18 specifications for considerations and inform if there are any related activities to address these issues in the ongoing or future 3GPP studies to cover.","secretary_remarks":"CC#3: Block 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-11-24 08:56:23","uploaded":"2022-11-29 09:29:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG CT, TSG RAN","Cc":"SA WG1","lsoriginalls":"2022_09_06_LS_004","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221006.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221007","title":"LS from IETF LPWAN WG: Liaison statement from the IETF LPWAN WG to 3GPP","source":"IETF LPWAN WG","contact":"Alexander Pelov","contact-id":56390,"tdoctype":"LS in","for":"Action","abstract":"We write to 3GPP to expose new IETF work (https:\/\/datatracker.ietf.org\/doc\/draft-ietf-lpwan-schc-over-nbiot\/) on the application of the SCHC protocol (RFC 8724\/8824) on NB IOT. This document is currently under IETF Last Call till October 7th, 2022, and it should be submitted to the IESG evaluation for final approval on October 27th, 2022. All comments are welcome until the ballot of 20 October, to be sent to the last-call@ietf.org mailing list, or exceptionally to iesg@ietf.org instead. SCHC provides a deep compression of the IPv6 packets at Layer-3 and above, and enables new capabilities such as IPv6 and CoAP signaling in highly constrained network like LP-WANs where it was previously considered impossible. SCHC also provides a fragmentation mechanism that would not necessarily be used in the case of NB-IOT. The new work at the IETF LPWAN Working Group provides informational considerations on how SCHC could be used over the Radio link and the No-Access Stratum. It also provides a normative description of the usage of SCHC over the Non-IP Data Delivery service. We foresee a potential of collaboration and cross referencing between our IETF specifications and 3GPP standards and seek advice and feedback.","secretary_remarks":"CC#3: Block noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2022-11-24 08:56:23","uploaded":"2022-11-29 09:29:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"","lsoriginalls":"LS_from_IETF_1796","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221007.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221009","title":"LS from GSMA OPAG: 3GPP TR 23.700-98 V1.2.0 Analysis","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 working on the analysis of 3GPP TR 23.700-98 V1.2.0 (2022-09) to understand its relationship to Federation, Edge Sharing and Roaming and the work GSMA OPAG is doing. 2 Enhanced Application Architecture The target architectures to be analysed are presented in the sections 6.1 and 6.2 of the 3GPP TR 23.700-98 V1.2.0 (2022-09). GSMA OPAG identified that these architectures might be related to the proposed solutions for the following key issues: Key Issue #6: Edge services support across ECSPs. Key Issue #9: Enhancement of dynamic EAS instantiation triggering. Key Issue #10: Support for roaming UEs. Key Issue #17: Discovery of a common EAS. Key Issue #20: Method of supporting federated EAS service Key Issue #22: EAS discovery in Edge Node sharing scenario Considering the description in the 3GPP TR 23.700-98, it is clear that the EDGE-10 interface has an important role in the proposed architectures and solutions, for example: Solution #5: ECS enhancement to discover EESs via other ECSs to support edge services across ECSPs. Solution #14: V-ECS Discovery via the H-ECS. As a part of the analysis, GSMA OPAG would like to understand if 3GPP EDGE-10 interface can be endorsed as part of the OPAG EWBI. However, we could not find a formal definition for EDGE-10 interface in 3GPP specifications. 3 Conclusion and actions GSMA OPAG kindly ask SA WG6 to provide a detailed description of the services and capabilities offered by the EDGE-10 interface and its relation to Federation, Edge Sharing and Roaming scenarios. GSMA OPAG would also like to understand whether SA WG6 is considering the EWBI defined in GSMA PRD OPG.04 for the realisation of the Edge-10 interface.","secretary_remarks":"CC#3: Block 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-11-24 08:56:23","uploaded":"2022-11-29 09:29:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"OPG","Cc":"TSG SA, SA WG6","lsoriginalls":"OPAG_41_Doc_04","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221009.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221011","title":"LS from GSMA OPG: LS reply to 3GPP SA2 on shared EHE and HR PDU session with SBO in V-PLMN","source":"GSMA OPG","contact":"Magnus Olsson","contact-id":74324,"tdoctype":"LS in","for":"Information","abstract":"GSMA OPG thanks SA WG2 for the LS on shared EHE and HR PDU session with SBO in V-PLMN. Firstly, GSMA OPG would like to clarify that 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":"CC#3: 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-11-24 08:56:24","uploaded":"2022-11-29 09:29:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5","Cc":"TSG SA","lsoriginalls":"OPG_112_Doc_03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221011.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221012","title":"LS from ITU-R WP5D: DEVELOPMENT OF A NEW REPORT ITU-R M.[IMT.MULTIMEDIA] Capabilities of the terrestrial component of IMT-2020 for multimedia communications","source":"ITU-R WP5D","contact":"Uwe Loewenstein","contact-id":11941,"tdoctype":"LS in","for":"Information","abstract":"Working Party (WP) 5D would like to thank 3GPP for their liaison statement (Doc. 5D\/1531) and to inform 3GPP that the working document of the new Report ITU-R M.[IMT.MULTIMEDIA] has been updated. The material provided by 3GPP in Document 5D\/1531 has been considered for incorporation in the working document (Document 5D\/1555 (Annex 3.3)). 3GPP is further invited to provide additional information, if any, preferably no later than towards the 43rd meeting of WP 5D, which is scheduled to be held from 31 January to 9 February 2023 (contribution deadline, 24 January, 16:00 UTC). Working Party 5D is looking forward to continuing fruitful cooperation with 3GPP on the new Report ITU-R M.[IMT.MULTIMEDIA]. The finalization of the development of this Report is planned for the 44th meeting of WP 5D, scheduled for 13 22 June 2023.","secretary_remarks":"CC#3: 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-11-24 08:56:24","uploaded":"2022-11-29 09:29:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"","lsoriginalls":"R19-WP5D-221010-TD-0746","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221012.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221013","title":"LS from ITU-T SG3: LS\/r on feedback to ITU-T SG 3 regarding the Technical Report on IMT2020-Related Policy Considering MVNOs under development in Question 3 of SG3","source":"ITU-T SG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"ITU-T Study Group 3 (SG3) welcomes initial feedback from ITU-T Study Group 13 (SG13) on STUDY_IMT2020MVNOs and invites additional input from SG13, as well as 3GPP and ITU-D Study Group 1 Question 4\/1.","secretary_remarks":"CC#3: 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-11-24 08:56:24","uploaded":"2022-11-29 09:29:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG13, 3GPP, ITU-D SG1 Q4\/1","Cc":"","lsoriginalls":"SG3-LS14","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221013.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221015","title":"LS from SA WG2: Reply LS on the scope of resource efficiency for MBS reception in RAN sharing scenario","source":"SA WG2","contact":"Thomas Belling","contact-id":68266,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 thanks TSG RAN for the LS on the scope of resource efficiency for MBS reception in RAN sharing scenarios. TSG RAN wrote: TSG RAN considers that from technical point of view support of resource efficiency for MBS reception is beneficial regardless of the MBS session type (broadcast \/ multicast). TSG RAN suggests RAN WG3 to focus on the work on the broadcast service for resource efficiency improvement for MBS reception in RAN sharing scenario, and to further coordinate with SA WG2 on the applicability of the solution to multicast service when needed. Action To SA WG2 and SA: TSG RAN kindly asks SA WG2 and SA to take the above information into account for their further work and coordinate with RAN and RAN WG3 if needed. There is no Rel-18 study SA WG2 work on 5G MOCN network sharing for multicast: The SA WG2 SID SP-211645 only contains an objective to study 5G MOCN network sharing for broadcast: WT#1.2 Study feasible and efficient resource utilization for the same broadcast content to be provided to 5G MOCN network sharing scenarios (i.e., multiple CNs are connected to the same NG-RAN); The related key issue 2 in TR 23.700-47 is also restricted to broadcast. SA WG2 did not reach consensus on whether it is possible to add support of MOCN for multicast in Rel-18.","secretary_remarks":"CC#3: 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-11-24 08:56:24","uploaded":"2022-11-29 09:29:33","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"TSG SA, TSG RAN","lsoriginalls":"S2-2211171","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221015.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221018","title":"LS from SA WG5: Reply LS on possibility of providing per UE speed and orientation on FS_eNA_Ph3","source":"SA WG5","contact":"Deepanshu Gautam","contact-id":81664,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks SA WG2 for the LS on possibility of providing per UE speed and orientation and would like to provide the response as follows: Q: Can OAM system provide per UE level speed and orientation to NWDAF as defined in Table 6.27.1-1(Information collected from OAM) TR23.700-81 regarding proximity analytics? SA WG5 Answer: This is very much possible. NWDAF can invoke TraceJob (clause 4.3.30 of 28.622) using Generic Provisioning Management Service (Clause 11.1 of 28.532) to get Sensor Information as part of MDT data collection mechanism. The UE sensor information includes Barometric pressure, UE speed and UE orientation (clause 5.10.29 of 32.422).","secretary_remarks":"CC#3: 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-11-24 08:56:24","uploaded":"2022-11-29 09:29:33","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG SA","lsoriginalls":"S5-226547","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221018.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221019","title":"LS from SA WG5: LS reply to GSMA on LS on customer acceptance 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 would like to thank GSMA for your reply to SA WG5 original LS S5-224100. SA WG5 would like provide further clarifications on S5-224100: 1. SA WG5 expects NGMN GFN project to provide their feedback on the proposed new use case as it is described, e.g. in terms of relevance, acceptability and potential benefits for service providers and customers (e.g. Verticals); 2. Should NGMN GFN consider that the proposed use case is acceptable for service providers and may bring value, then the following question comes up: how can NSCs express their requirements wrt. accepteable QoS degradation in their communication with NSPs, i.e. during the network slice ordering phase and\/or during the operation phase of the network slice? 3. Upon the reception of such expectations expressed by NSCs, whatever decision(s) NSPs take (or not) to save energy in their network to satisfy NSC expectations is out of scope of this LS. Based on this, SA WG5 would like to provide the following answers to GSMA ENSWI questions: {. . .}","secretary_remarks":"CC#3: 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-11-24 08:56:24","uploaded":"2022-11-29 09:29:33","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG ENSWI","Cc":"NGMN GFN, TSG SA","lsoriginalls":"S5-227038","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221019.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221020","title":"LS from SA WG6: Reply LS on Re-use of CAPIF by ETSI MEC","source":"SA WG6","contact":"Martin Oettl","contact-id":68409,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks ETSI ISG MEC for further collaborating on CAPIF alignment with ETSI MEC and EDGEAPP. SA WG6 has discussed the topic and would like to answer ETSI ISG MEC s questions as following: Q1: ETSI ISG MEC would like feedback on whether SA WG6 believes that there would be the need to add stage 2 requirements to enable protocol-level additions fulfilling the sketched extensibility requirements (a), (b) and (c), or whether this is already covered by the existing CAPIF stage 2 requirements. A1: SA WG6 will study and specify any necessary stage 2 changes to meet the extensibility requirements for (a), (b) and (c) as provided in the LS (S6-222714\/ MEC(22)000451r6). Q2: ETSI ISG MEC would like to understand the feasible possible timelines and target release(s) for such additions. A2: SA WG6 view is that if any gaps are found in current CAPIF specification on this topic it can be addressed in Rel-18 timeframe. Q3: ETSI ISG MEC would like to understand the most appropriate mode of collaborating on this topic from the point of view of SA WG6. A3: After SA WG6 completes its study on this topic, any relevant specification update (if required) will be addressed in TS 23.222. Subsequently, the security related impacts for any enhancement in CAPIF can be addressed by SA WG3 and the stage 3 impacts for any protocol enhancements in CAPIF can be addressed by CT WG3. SA WG6 will provide further status updates once available.","secretary_remarks":"CC#3: 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-11-24 08:56:24","uploaded":"2022-11-29 09:29:33","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI ISG MEC, CT WG3","Cc":"TSG CT, TSG SA, SA WG3","lsoriginalls":"S6-223027","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221020.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221021","title":"LS from SA WG6: Reply LS on Clarification of Edge Node Sharing","source":"SA WG6","contact":"Sapan Shah","contact-id":76271,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks GSMA OPG for their reply LS on edge node sharing considering the mapping of GSMA OP and 3GPP EDGEAPP architecture. {. . .}.","secretary_remarks":"CC#3: 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-11-24 08:56:24","uploaded":"2022-11-29 09:29:33","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPG","Cc":"SA WG2, TSG SA","lsoriginalls":"S6-223506","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221021.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221023","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":"SA WG6 would like to thank GSMA OPAG for sending LS on 3GPP TR 23.700-98 V1.2.0 Analysis. SA WG6 has not yet analysed EWBI requirements in GSMA PRD OPG.04 in relation to EDGE-10, EDGE-9 and other SA WG6 interfaces. Below SA WG6 indicates its related KI and their solutions. SA WG6 would like to indicate that the solutions for KI#9, #17 and #20 as of now do not have federation aspects covered, however, SA WG6 will work on the use cases\/requirements from GSMA OPAG related to these KIs. Further, SA WG6 requests GSMA OPAG to provide their analysis on KI#9, #17 and #20 on relation with federation. SA WG6 would like to inform GSMA OPAG that there are several solutions discussed in the Rel-18 study which are related to above identified key issues as follows: Key Issue #6: Edge services support across ECSPs: o Solution #4, #5, #13, #43 Key Issue #10: Support for roaming UEs. o Solution #4, #5, #13, #14 Key Issue #22: EAS discovery in Edge Node sharing scenario o Solution #43, #44, #45 SA WG6 would like to request GSMA OPAG to consider above solution in their analysis too. Further, SA WG6 would like to inform that considering all solutions discussed in the study, there are multiple interfaces which can be considered at EWBI.","secretary_remarks":"CC#3: 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-11-24 08:56:24","uploaded":"2022-11-29 09:29:33","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPAG","Cc":"GSMA OPG, TSG SA","lsoriginalls":"S6-223613","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221023.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221024","title":"LS from ITU-T Working Party 1\/13: LS on the initiation of the new work item Y.AN-Arch-fw: 'Architecture Framework for Autonomous Networks'","source":"ITU-T Working Party 1\/13","contact":"Marco Carugi","contact-id":31658,"tdoctype":"LS in","for":"Information","abstract":"This Liaison Statement informs about the initiation of the new work item on 'Architecture Framework for Autonomous Networks'.","secretary_remarks":"CC#3: 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-11-24 08:56:24","uploaded":"2022-12-05 09:26:58","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSAG, ITU-T SGs, 3GPP, GSMA, IEEE, ETSI, TMF, IETF, IRTF, ISO\/IEC JTC1\/SC42, Linux Foundation Networking, LF AI & Data Foundation, O-RAN Alliance, NGMN","Cc":"","lsoriginalls":"SG13-LS37","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221024.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221025","title":"CAPIF extensions requested by ETSI ISG MEC","source":"SA WG6","contact":"Martin Oettl","contact-id":68409,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks ETSI ISG MEC for collaborating on CAPIF alignment. As indicated in the Reply LS on Re-use of CAPIF by ETSI MEC (S6-223027), SA WG6 is further elaborating necessary stage 2 changes to meet the extensibility requirements as indicated in the LS (S6-222714\/ MEC(22)000451r6) and agreed the attached CR0096 (Rel-18) against TS 23.222.","secretary_remarks":"CC#3: 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-11-24 08:56:24","uploaded":"2022-12-05 09:26:58","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3, ETSI ISG MEC","Cc":"SA WG3, TSG CT, TSG SA","lsoriginalls":"S6-223628","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221025.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221268","title":"LS from ITU-T JCA-IMT2020: LS on Invitation to update the information in the IMT-2020 and beyond roadmap","source":"ITU-T JCA-IMT2020","contact":"Scott Mansfield","contact-id":42415,"tdoctype":"LS in","for":"Action","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 March 2023 alongside the ITU-T SG13 meeting in Geneva. We invite your inputs\/updates to the roadmap.","secretary_remarks":"CC#3: 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-12-05 12:13:18","uploaded":"2022-12-05 12:17:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU study groups, External IMT-2020 liaison partners","Cc":"","lsoriginalls":"JCA-IMT2020-O-025-LS12","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221268.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221272","title":"LS from ITU-T SG13: LS on the new work item Y.Arch_NGNe_ncp 'Architectural evolution of NGN control plane by applying SDN technology'","source":"ITU-T SG13","contact":"Yuan Zhang","contact-id":93840,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement notifies about the creation of the new work item Y.Arch_NGNe_ncp in Q2\/13.","secretary_remarks":"Revised to add attachment in SP-221283","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10180,"status":"revised","reservation_date":"2022-12-06 08:49:58","uploaded":"2022-12-06 09:08:18","revisionof":"","revisedto":"SP-221283","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG11, SG15, 3GPP, ETSI","Cc":"","lsoriginalls":"SG13-LS43","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221272.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-221283","title":"LS from ITU-T SG13: LS on the new work item Y.Arch_NGNe_ncp 'Architectural evolution of NGN control plane by applying SDN technology'","source":"ITU-T SG13","contact":"Yuan Zhang","contact-id":93840,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement notifies about the creation of the new work item Y.Arch_NGNe_ncp in Q2\/13.","secretary_remarks":"CC#3: 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-12-07 09:54:29","uploaded":"2022-12-07 15:46:33","revisionof":"SP-221272","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG11, SG15, 3GPP, ETSI","Cc":"","lsoriginalls":"SG13-LS43","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_98E_Electronic_2022-12\/Docs\/SP-221283.zip","group":"SP","meeting":"SP-98-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]