[{"name":"SP-220362","title":"LS from CT WG1: LS on spoofing using national numbers","source":"CT WG1","contact":"J\u00f6rgen Axell","contact-id":36534,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 would like to thank ITU-T SG2 for their incoming LS in SG2-LS222\/C1-220114 and would like to inform ITU-T SG2 about work performed in CT WG1. CT WG1 started in rel-14 (WI SPECTRE), and continued in rel-15 (WI eSPECTRE) to work on call spoofing prevention based on the work in IETF STIR WG. While ITU-T work is focussed on barring calls from potentially fraudulent sources, CT WG1 work has been focussed on ensuring that the originating identity can be verified at the terminating network and is based on the Identity header field specified in IETF RFC 8224, using PASSporTs defined in RFC 8588 and RFC 8946. The 3GPP solution has been specified in 3GPP TS 24.229 from rel-15. 3GPP currently has two ongoing WIs (TEI17_SAPES and SPECTRE_Ph3). TEI17_SAPES extends the mechanism for originating identity verification to also protect values in the Resource-Priority header field and the 'psap-callback' value in the Priority header field. SPECTRE_Ph3 is to enable signing of multiple PASSporTs using the same signing resource and to convey information about errors encountered during verification.","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-05-23 12:07:31","uploaded":"2022-05-23 12:29:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2","Cc":"TSG CT, TSG SA","lsoriginalls":"C1-223042","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220362.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220363","title":"LS from ETSI ISG MEC: LS to 3GPP on MEC Federation and interest to collaborate","source":"ETSI ISG MEC","contact":"Pekka Kuure","contact-id":68365,"tdoctype":"LS in","for":"Information","abstract":"Further to the joint workshop organized by GSMA Operator Platform Group (OPG), on 21\/01\/2022, ETSI MEC would like to reiterate their interest to collaborate with 3GPP to create consistent standards in avoidance of work duplication. ETSI MEC understand LS exchange to be the most suitable mechanism, coupled with common members participation and contribution in the relevant 3GPP groups. ETSI MEC considers the time is right to align efforts, starting from the alignment on the SDOs API mapping and work-split. This is expected to show complementary coverage of OP architecture and benefit the entire ecosystem, under the guidance from the OPG on the overall collaboration framework. In order for ETSI MEC to progress its work, such a technical alignment with 3GPP is considered timely (and also to some extent not only motivated by the GSMA needs for federation, even if this is a main driver). So, the present LS is not intended to substitute to any communication from GSMA (that we expect to arrive soon) on the collaboration, but for the sake of technical progress on the details of the standard alignment between ETSI MEC and 3GPP. ETSI ISG MEC would like to share the public location of the group s slides presented at the workshop (here) and inform 3GPP about the latest progress of our work, also described in the recent ETSI press release (here). In particular: The ISG has recently published the following deliverables: MEC 003 v3.1.1 (here), MEC 010-2 v2.2.1 (here) and MEC 021 v2.2.1 (here). The latest advances to these GS capture the MEC Architecture with variant for MEC Federation, bug fixing on MEC Application lifecycle management, and updates on Application Mobility Service API. ETSI GS MEC 040 work item on MEC Federation Enablement APIs is continuously evolving and each new iteration is being made available in the MEC Open Area (https:\/\/docbox.etsi.org\/ISG\/MEC\/Open) in a dedicated folder (here). Latest advances of MEC 040 include updates related to OP architecture, e.g.: registration of MEC system(s) to the federation, MEC Service discovery, Application package management, Application instance lifecycle management and also data type definition related to the information provided by MEC orchestrator as a part of the Registration of MEC system to the federation . All these updates are coherent with the approach proposed at the workshop (slides 4-10, here). Further clauses 6 and 7 are intended for normative API design, and will be added later, also based on the collaboration with GSMA. Also the ETSI GS MEC 011 drafts are available in a dedicated folder of the MEC Open Area (here), and it is another important enabler for MEC in the view of aligning with 3GPP, not only for federation purposes. The latest advance of MEC 011 includes the introduction of data type AppInfo representing the information provided by a MEC application instance as part of the 'application registration request' message. This data type is intended to allow registration of MEC applications, also for those where LCM is not performed by MEC system (e.g. EASs). Moreover, for the sake of progress in the normative work to address the GSMA OP requirements, we would like to propose some topics for collaboration with 3GPP groups: the synergy between Mp1 and EDGE-3 in SA WG6; clarification of the ETSI MEC specifications and their role for the OP-EWBI\/OP-NBI APIs; how to reuse existing specs from 3GPP and ETSI MEC, perhaps it will be useful that both SDOs will work together e.g. to bring an example of the proposed packaging approach (see ETSI MEC slides at the workshop), as this could help a common understanding, especially from OPG side; To summarize, ETSI ISG MEC is willing to foster a collaboration with SA WG6 on this topic and look forward to further coordination and alignment among the two standard bodies. We hope that the above information on our current and finalized work area would be helpful for your work, and in case needed, we are happy to provide further information.","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-05-23 12:07:31","uploaded":"2022-05-23 12:29:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"TSG SA, SA WG5, SA WG2, ETSI NFV, GSMA OPG, GSMA OPAG","lsoriginalls":"MEC(22)000127r5","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220363.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220365","title":"LS from SA WG3: Reply LS on Reply LS on MINT functionality for Disaster Roaming","source":"SA WG3","contact":"Dongjoo Kim","contact-id":84882,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks SA WG2 for the reply LS(S3 220499\/S2-2201514) on MINT functionality for Disaster Roaming. SA WG3 would like to inform SA WG2 that based on SA WG2 decision, SA WG3 agreed the attached CR for TS 33.501, which updates the initiation procedures of the primary authentication and corresponding services provided by AUSF and UDM.","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-05-23 12:07:31","uploaded":"2022-05-23 12:29:32","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG5, CT WG1, CT WG4, CT WG6, RAN WG2, TSG SA, TSG CT","lsoriginalls":"S3-220518","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220365.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220366","title":"LS from SA WG5: Reply LS to ITU-T on the first deliverable on use cases for autonomous networks from ITU FG-AN (ITU FG-AN)","source":"SA WG5","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank ITU-T for the information on the first deliverable on use cases for autonomous networks from ITU FG-AN. SA WG5 has the following questions for clarification regarding the content of Technical Specification Use cases for Autonomous Networks from ITU-T: 1. autonomous behavior is used many times in the document, and it s referring to evolution, exploration and adaption , we would like to clarify what could be the potential impact to the standardized interfaces when different autonomous behaviors are adopted. SA WG5 has specified concept of control loops in TS 28.535, whether there is any similarities with the autonomous behavior? 2. There are following two categories are used to categorize different use cases: o Cat 1: describes a scenario related to core autonomous behavior itself. o Cat 2: describes a scenario related to application of autonomous behaviour in the network. We would like to clarify the difference between the two categories and whether there is any potential overlapping between the two categories. SA WG5 would like also inform ITU-T that SA WG5 has discussed the autonomous networks related topics, the Rel-17 related use cases and solutions are captured in the following specifications which can be found in https:\/\/portal.3gpp.org\/Specifications.aspx?q=1&series=22&releases=all&draft=False&underCC=False&withACC=False&withBCC=False&numberNYA=False : TS 28.100 Management and orchestration; Levels of autonomous network TS 28.104 Management and orchestration; Management Data Analytics TS 28.535 Management and orchestration; Management services for communication service assurance; Requirements TS 28.536 Management and orchestration; Management services for communication service assurance; Stage 2 and stage 3 TS 28.313 Management and orchestration; Self-Organizing Networks (SON) for 5G networks TS 28.312 Management and orchestration; Intent driven management services for mobile networks TS 28.557 Management and orchestration; Management of Non-Public Networks (NPN); Stage 1 and stage 2 SA WG5 has just started Rel-18 work from Apr.2022. There are following study items and work items which are related to intelligence and automation: Self-Configuration of RAN NEs (work item) Study on enhancement of autonomous network levels (study item) Study on evaluation of autonomous network levels (study item) Study on enhanced intent driven management services for mobile networks (study item) Study on intent-driven management for network slicing (study item) Study on AI\/ ML management (study item) Study on Enhancement of the management aspects related to NWDAF (study item) Study on Fault Supervision Evolution (study item) SA WG5 is currently collaborating with TM Forum, ETSI and other related groups on autonomous networks and we are happy to collaborate and exchange more information with ITU-T in future meetings if needed.","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-05-23 12:07:31","uploaded":"2022-05-23 12:29:32","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, SG3, SG5, SG9, SG11, SG12, SG15, SG16, SG17, SG20, CITS, FG-AI4EE, FG-AI4NDM, FG-AI4AD, GSMA, IEEE, ETSI ISG ZSM, ETSI ISG NFV, ETSI TC INT, TM Forum, IETF, IRTF, Linux Foundation Networking, Open Networking Foundation, LF AI & Data Foundation,","Cc":"TSG SA","lsoriginalls":"S5-222560","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220366.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220367","title":"LS from SA WG5: LS on MINT functionality for Disaster Roaming","source":"SA WG5","contact":"Robert T\u00f6rnkvist","contact-id":35172,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks SA WG2 for their LS. There is currently no work item for MINT in SA WG5. Charging for roaming using home routed is already specified by SA WG5 and for roaming using local breakout there is an ongoing SA WG5 work item. The charging data records produced by the VPLMN is mainly used for interconnect charging and the records produced in HPLMN is mainly used for subscriber charging. In the case of Disaster Roaming service there would probably be special treatment of both the subscriber and interconnect records, therefore it is beneficial if these could be easily sorted based on a specific indication from VPLMN.","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-05-23 12:07:31","uploaded":"2022-05-23 12:29:32","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG SA, SA WG3, TSG CT, CT WG1, CT WG4, CT WG6, TSG RAN, RAN WG2","lsoriginalls":"S5-222575","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220367.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220368","title":"LS from SA WG5: Reply LS to GSMA NG ENSWI on overall architecture for network slice ordering, provisioning and assurance","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank GSMA NG ENSWI (E2E Network Slicing Work Item) for your reply LS on the overall architecture for network slice ordering, provisioning and assurance. The original SA WG5 LS (S5-215530) was sent out to several SDOs and\/or groups and SA WG5 is still waiting for replies from some of them. As soon as we have received and analyzed all replies, we will keep you updated of the progress of our work.","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-05-23 12:07:31","uploaded":"2022-05-23 12:29:32","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG ENSWI","Cc":"TSG SA","lsoriginalls":"S5-222814","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220368.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220369","title":"LS from SA WG5: Reply LS to TM Forum on overall architecture for network slice ordering, provisioning and assurance","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank TM Forum End to End Open Digital Architecture Project for your reply LS on the overall architecture for network slice ordering, provisioning and assurance. The original SA WG5 LS (S5-215530) was sent out to several SDOs and\/or groups and SA WG5 is still waiting for replies from some of them. As soon as we have received and analyzed all replies, we will keep you updated of the progress of our work.","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-05-23 12:07:31","uploaded":"2022-05-23 12:29:32","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TM Forum","Cc":"TSG SA","lsoriginalls":"S5-222815","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220369.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220370","title":"LS from SA WG6: Reply LS to ETSI MEC on MEC Federation and interest to collaborate","source":"SA WG6","contact":"Samar Shailendra","contact-id":91764,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks ETSI MEC ISG for their LS and appreciate their willingness to collaborate on common technical interest and alignment. SA WG6 has noted the ETSI MEC ISG specifications and carefully reviewed the questions. SA WG6 has identified a key issue (KI #5) on EDGEAPP and ETSI MEC alignment and considered various deployment options for convergence of EES and MEC Platform (Annex-B) in internal TR 23.700-98-051. SA WG6 is evaluating a CAPIF based deployment option to access APIs across two platforms (Sol #11) in above TR. However, the exact nature of alignment of Mp1 and EDGE-3 interfaces and mapping to OP interfaces is still an ongoing area of study. SA WG6 noted the ETSI MEC ISG specification on Federation (MEC 003 and MEC 040). Federation is currently an active study item under discussion at SA WG6. SA WG6 wants to thank ETSI MEC ISG for bringing these specifications into our notice. SA WG6 will liaise with ETSI MEC ISG and provide further updates about EDGEAPP work. SA WG6 intends to continue close collaboration with ETSI MEC ISG.","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-05-23 12:07:31","uploaded":"2022-05-23 12:29:32","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI ISG MEC","Cc":"TSG SA, SA WG2, SA WG3, SA WG5, ETSI NFV, GSMA OPG, GSMA OPAG","lsoriginalls":"S6-220931","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220370.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220372","title":"LS from ETSI TC ITS STF585: Open contribution or Review of the MCO set of specifications (TS 103 697, TS 103 141, TS 103 836-4-1, TS 103 695) for C-ITS Release 2","source":"ETSI TC ITS STF585","contact":"Paul Spaanderman","contact-id":86146,"tdoctype":"LS in","for":"Action","abstract":"The ETSI Specialist Task Force (STF) 585 is responsible for the 'Specifications of a Multi-Channel Operational (MCO) concept and related specifications within the domain of Intelligent Transportation Systems. The STF started its work in April 2020 under the guidance of ETSI TC ITS WG2 (Architecture and Cross Layer Working Group). The STF 585 is responsible for the development of six MCO related deliverables (table below) within the coming 2 years. {. . .} Actions: ETSI TC ITS kindly asks the recipients to review the stable drafts of TS 103 697, TS 103 141, TS 103 836-4-1 and TS 103 695. Please send your feedbacks and comments to Andrea.Lorelli@etsi.org preferably by 20 June 2022. As it is known that some organisations have their next meetings in July 2022, STF 585 team would still appreciate to receive comments from those organisations by the end of July. The STF 585 expert team will review and consolidate the received comments according to the provided template. It is up to the team to decide if and how to incorporate the received feedback into the deliverables. Upon request, STF 585 will provide feedback on the decision implemented for each of the comments.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2022-05-23 12:09:52","uploaded":"2022-06-01 10:46:34","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG TSG RAN, TSG SA, \u2026","Cc":"","lsoriginalls":"MCO LS","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220372.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220373","title":"LS from SA WG1: Reply LS on IMS emergency communication improvement-SM","source":"SA WG1","contact":"Bruno TOSSOU","contact-id":87444,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks GSMA NRG for their LS in S1-221184 Based on GSMA and ETSI request to support SMS over IMS for emergency service in case of roaming and supported for emergency numbers such as 112 and 911, SA WG1 updated for Release 18 TS 22.101 by creating a new section on Short Message Service over IMS to emergency centre which was agreed with the attached CR0583.","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-05-23 12:09:52","uploaded":"2022-06-01 10:46:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NRG","Cc":"CT WG1, SA WG2, ETSI EMTEL, TSG SA","lsoriginalls":"S1-221221","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220373.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220374","title":"LS from SA WG5: Reply LS on Issues Network Slice information delivery to a 3rd party","source":"SA WG5","contact":"Erik Guttman","contact-id":18782,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks SA WG6 for their LS and questions. SA WG5 clarifies to SA WG6 how network slice provisioning functionality defined by SA WG5 should be used. All of the questions from SA WG6 appear to assume that the NSCE server\/AF exposes an inventory of the already-existing network slice instances. SA WG5 notes that it is also possible to expose capabilities for allocating a new network slice instance(s). Network slice management is intended to be used as follows: a network slice customer requests allocation of a network slice, can view the status\/performance\/faults of this network slice, can reconfigure the network slice (based on the concluded contracts\/agreements and the access rights) and can deallocate the network slice. SA WG5 emphasizes that the management of a network slice should be available to any authorized entity.","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-05-23 12:09:52","uploaded":"2022-06-01 10:46:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG1, SA WG2","lsoriginalls":"S5-223516","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220374.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220375","title":"LS from SA WG6: LS on Alignment of EDGEAPP and ETSI MEC","source":"SA WG6","contact":"Roya Rezagah","contact-id":90163,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 has initiated work on the alignment of EDGEAPP and ETSI MEC as part of the Release 18 study of FS_eEDGEAPP and has captured one Key Issue (KI#5) in TR 23.700-98. In order to reach a common understanding of the alignment issue, SA WG6 would like to share its progress on the approach for such alignment. Furthermore, SA WG6 believes that such alignment work in SA WG6, would benefit from regular feedback and may require reciprocating action from ETSI MEC side.","secretary_remarks":"Related WID proposal in SP-220634. 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-05-23 12:09:52","uploaded":"2022-06-01 10:46:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI MEC ISG","Cc":"TSG SA","lsoriginalls":"S6-221436","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220375.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220376","title":"LS from ETSI ISG IPE: Liaison Statement announcing publication of IPE-002: IPv6 based Data Centers, Network and Cloud Integration","source":"ETSI ISG IPE","contact":"Latif Ladid","contact-id":86673,"tdoctype":"LS in","for":"Action","abstract":"ISG IPE is pleased to inform you of the latest GR from ETSI ISG IPE (IPv6 Enhanced Innovation) on IPv6 based Data Centers, Network and Cloud Integration published in April 2022 and believe that this could be of interest to your committee. https:\/\/www.etsi.org\/deliver\/etsi_gr\/IPE\/001_099\/002\/01.01.01_60\/gr_IPE002v010101p.pdf. Action: ISG IPE invite any interested parties to provide feedback.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2022-05-23 12:09:52","uploaded":"2022-06-01 13:43:45","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, 3GPP PCG, GAIA-X, ITU-T SGs, ISO\/IEC JTC, GSMA, MEF, OMA, IEC SyC COMM","Cc":"","lsoriginalls":"IPE(22)R15003","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220376.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220377","title":"LS from O-RAN WG9: LS on O-RAN Transport Network Slicing Enhancement IM\/DM TS28.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":10190,"status":"noted","reservation_date":"2022-05-23 12:09:52","uploaded":"2022-06-06 07:30:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA, TSG RAN","lsoriginalls":"S-2022003","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220377.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]