[{"name":"SP-211246","title":"LS from ETSI TC LI: Reply LS on PSCELL ID availability in SGW CDR","source":"ETSI TC LI","contact":"Carmine Rizzo","contact-id":52778,"tdoctype":"LS in","for":"Information","abstract":"ETSI TC LI would like to thank SA WG5 for the LS (S5-214069) on PSCELL ID availability in SGW CDR replying to ETSI TC LI request in providing the same capability in allowing the CSPs to comply with the Retained Data Regulations. ETSI TC LI gladly confirms that the above added functionality fulfils the Retained Data related requirements by allowing the CSPs to have access to the PSCELL ID information at a later time.","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:36","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA, SA WG2, RAN WG3, SA WG3-LI","lsoriginalls":"LI(21)P58049r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211246.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211247","title":"LS from APT: APT REPORT ON EMERGING CRITICAL APPLICATIONS & USE CASES OF IMT FOR INDUSTRIAL, SOCIETAL AND ENTERPRISE USERS","source":"AWG28\/OUT03 (Rev.1)","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"The AWG is developing a working document towards an APT Report on 'EMERGING CRITICAL APPLICATIONS & USE CASES OF IMT FOR INDUSTRIAL, SOCIETAL AND ENTERPRISE USERS' The scope of the report is on new\/emerging critical applications and use cases of IMT-Advanced and IMT-2020 for industrial, societal and enterprise users, both 4G LTE and NR. Current draft working document being developed in the AWG is enclosed for reference. As SA WG6 (SA WG6) is the application enablement and critical communication applications group for critical applications of IMT, AWG would kindly invite the 3GPP to provide relevant materials, use cases and any other related material that would facilitate in completion of this Report. AWG would appreciate 3GPP to provide any feedback before the next 29th APT Wireless Group (AWG-29) meeting, scheduled in March\/April 2022, if any. For technical queries please contact: Mr. Bharat Bhatia ITU-APT Foundation of India +91 9810173737 Email: Bharat.bhatia@itu-apt.org AWG will keep 3GPP informed of the progress and outcomes of relevant studies in future AWG meetings. Mr. Le Van Tuan Chairman APT Wireless Group","secretary_remarks":"CC#1: Clarify which WGs can provide response information. CC#4: To be forward to SA WG1 - please provide input till March. This LS was postponed and will be forwarded to SA WG1 by MCC.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10030,"status":"postponed","reservation_date":"2021-11-16 10:00:36","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG6","Cc":"","lsoriginalls":"AWG28\/OUT03 (Rev.1)","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211247.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211248","title":"LS from MEF Forum: Liaison informing about Publication of Standard MEF 84 Network Slice Service and Attributes","source":"MEF Forum","contact":"Nan Chen","contact-id":62083,"tdoctype":"LS in","for":"Information","abstract":"We would like to inform you about the publication of Standard MEF 84 Network Slice Service and Attributes. This standard specifies Network Slicing in the context of MEF Lifecycle Service Orchestration (LSO) and MEF Services. Key concepts of Network Slicing, Network Slices and Network Services are described. Network Services as defined in this Standard enables Service Providers to offer Network Slices in the Service Provider domain as Services to Subscribers in the Customer domain. The focus is on the Subscriber visible aspects of the Service Provider's internal Network Slices. MEF Standards are available at: https:\/\/www.mef.net\/learn\/mef-technical-standards-sdks\/","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:36","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP, BBF, ETSI ISGs ENI; NEF; ZSM, GSMA, IETF, ITU-T, NGNM, ONF, TMF","Cc":"","lsoriginalls":"LS00319_001","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211248.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211249","title":"LS from ETSI ISG RIS: Formation of a new ETSI ISG for Reconfigurable Intelligent Surfaces (RIS)","source":"ETSI ISG RIS","contact":"Arman Shojaeifard","contact-id":89567,"tdoctype":"LS in","for":"Information","abstract":"Overall description: ETSI's new Industry Specification Group on Reconfigurable Intelligent Surfaces (RSI) was officially launched on the 30th September 2021 with a kick-off meeting (KoM). The ISG RIS mission is to explore RIS and its applications across the wide spectrum of use cases and deployments and identify any specification needs that may be required, thus paving the way for future standardization of the technology (notably within 3GPP). {. . .} ETSI ISG RIS activities and deliverables will be complementary to existing ETSI work, and relationships with other ETSI bodies and the wider industry will be established to avoid duplication, maximize synergies and act to ensure broad industry adoption. Further information on the ISG RIS terms of reference, work programme, planned deliverables, and other documentations are available through the ISG portal:","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:36","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA, ITU-R, ETSI ISGs, CCSA TC5","Cc":"","lsoriginalls":"RIS(21)001003r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211249.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211250","title":"LS from RAN WG3: Reply LS on Guidelines on Port Allocation for New 3GPP Interfaces","source":"RAN WG3","contact":"Gino Masini","contact-id":23120,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks CT WG4 for the latest information and status report on the port number allocation solutions. Solutions #1-4, 8 all have varying impacts on implementations and\/or deployments, and have dependencies on the operator's infrastructure, including transport infrastructure. In general, they are not considered feasible. Solutions #3, 5 which affect the transport network layer, including SCTP, are also unfeasible. RAN WG3 prefers not to impact transport layer implementations, given that SCTP is today the basis for all RAN WG3-defined interfaces. We acknowledge the possible drawback of Solution #6, as described in Sec. 4.4.3 of TR 29.941. RAN WG3 understands that implementations are responsible for resolving any collisions. We would ask CT WG4 to keep us informed of any updates on this. RAN WG3 confirms that static port number allocation by 3GPP (Solution #6 in TR 29.941) and port allocation via OAM (Solution #7 in TR 29.941) shall be the way forward.","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:36","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"RAN WG2, SA WG4, CT WG3, SA WG5, SA WG2, TSG SA, TSG CT, TSG RAN","lsoriginalls":"R3-216233","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211250.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211251","title":"LS from SA WG2: LS on use of inclusive terminology for Time Synchronization","source":"SA WG2","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"LS in","for":"Information","abstract":"As communicated in LS SP-201144, 3GPP is replacing the occurrences of non-inclusive terminology (i.e. Master, Slave, Whitelist, Blacklist) from all Rel-17 3GPP Technical Specifications and 3GPP Technical Reports. 3GPP TS 23.501 and TS 23.502 have been using the same terminology as used in IEEE specifications for describing the Time Synchronization functionality specified for 5G System. SA WG2 has technically endorsed the attached CRs to replace 'Master'\/'Slave' with 'Leader'\/'Follower' along with a clarification Note regarding the mapping between 3GPP and IEEE terminology. SA WG2 plans to send attached CRs to TSG SA#94-e (Dec, 2021) for final approval.","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:37","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IEEE 1588 WG","Cc":"IEEE 802.1 WG, TSG SA","lsoriginalls":"S2-2107800","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211251.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211252","title":"LS from SA WG2: LS on MINT functionality for Disaster Roaming","source":"SA WG2","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 thanks TSG SA and CT WG1 for their respective LS, (SP-210581 \/ S2-2105307) and (C1-213908 \/ S2-2105249). According to the WID on MINT approved SA#92-e meeting (Target Date: December, 2021), SA WG2 has specified the normative work since SA WG2#146-e meeting, SA WG2 made the following agreements in SA WG2#147E: NOTE 1: The AUSF and the UDM are configured with Disaster Condition via OAM based on operator policy and the request by the government agencies. Based on this local configuration, the AUSF can execute authentication of the UE, and the UDM can provides the subscription data for a Disaster Roaming service to the AMF. NOTE 2: The AMF is recommended to provide the Disaster Roaming service indication to AUSF\/UDMs if the HPLMN is from a different country. For AUSF\/UDMs of HPLMNs of the same country the detection can be based on home operator policy and local configuration. Editor's note: The details of authentication are determined by SA WG3, including whether the Disaster Roaming service indication is needed. Disaster Roaming service indication may be removed, e.g. based on the feedback. Editor's note: It is FFS if Disaster Roaming indication needs to be provided from AMF to SMF, and further in charging related information. This will be evaluated based on the feedback from SA WG3 and SA WG5. SA WG2 respectfully asks SA WG3 and SA WG5 to provide their feedback on above agreements. SA WG2 respectfully asks SA WG3, SA WG5, CT WG1, CT WG4, CT WG6, and RAN WG2 to take above information into consideration and to update their specifications accordingly, if deemed necessary.","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:37","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, SA WG5, CT WG1, CT WG4, CT WG6, RAN WG2","Cc":"TSG SA, TSG CT, TSG RAN","lsoriginalls":"S2-2108172","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211252.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211253","title":"LS from SA WG2: Reply LS on EPS support for IoT NTN in Rel-17","source":"SA WG2","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 would like to thank TSG RAN for their reply LS on EPS support for IoT NTN in Rel-17 and to provide the following comments on TSG RAN requests: - TSG SA, SA WG2 to reconsider supporting new functionality to support discontinuous coverage; SA WG2 Comment: SA WG2 is attempting at resolving the issue of discontinuous coverage in Rel-17 but has yet to conclude how. SA WG2 has not yet updated the WID. - TSG SA, SA WG2, CT and CT WG1 to ensure WUS is not excluded. SA WG2 Comment: No explicit disabling of WUS functionality will be specified by SA WG2.","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:37","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, TSG SA, CT WG1, TSG CT, TSG RAN","Cc":"CT WG4, CT WG3, RAN WG3","lsoriginalls":"S2-2108176","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211253.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211254","title":"LS from SA WG3: Reply to LS on support of PWS over SNPN","source":"SA WG3","contact":"Bo Holm Bjerrum","contact-id":80370,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank SA WG1 for the information regarding introducing PWS in SNPN's. In R12, SA WG3 studied security for PWS for PLMN's in TR 33.969 and concluded not to continue with the normative work for PWS security. SA WG3 assume SA WG1 has evaluated requirements from regulators and not identified any differences between a PLMN and SNPN operated network in relation to PWS. If differences exist, SA WG3 would like to ask SA WG1 to provide the added\/updated requirements, such that security for PWS for SNPN's can be reevaluated.","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:37","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG2, CT WG1, RAN WG2, RAN WG3, TSG SA, TSG CT, TSG RAN","lsoriginalls":"S3-213609","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211254.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211255","title":"LS from SA WG3: LS on reply to SA6 about new SID on Application Enablement for Data Integrity Verification Service in IOT","source":"SA WG3","contact":"Markus Staufer","contact-id":88693,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank SA WG6 for sending LS S6-211496. Since the LS and SA WG3's answer relates to a requirement made by SA WG1, SA WG3 provides a common reply to the kind attention of SA WG6 and SA WG1. In LS S6-211496 (S3-212444) SA WG6 has informed SA WG3 about a new study (S6-211481) proposed in SA WG6 on the application layer support of the service for data integrity verification in IOT based on the stage 1 requirements in TS 22.261. SA WG3 could not agree, if the intention of the SA WG1 requirement was providing an 'additional ability to provide data integrity protection service between an application on UE and an Application Server' as stipulated in S6-211481. SA WG3 sees a potential contradiction with the SA WG1 requirement, which restricts the scope of the integrity protection service to data exchange between network and application server. SA WG3 can provide feedback and guidance on security aspects on a service for data integrity verification as soon as more detailed information about use cases, scope and intention of the data integrity verification service is available. Therefore, SA WG3 kindly asks SA WG6 and SA WG1 to provide this information as an input to SA WG3. Specifically, SA WG3 asks for information and clarification with respect to: - Is the scope of the integrity verification service end to end protection on application layer, or does the integrity verification service address the integrity of the link between 5GC and the application server? - To what extent is the UE and specifically the USIM or UICC involved in the data integrity verification service? Due to the expected security impact related to data integrity and authenticity under the remit of SA WG3, SA WG3 kindly suggests that the SA WG6 study on a data integrity verification service waits for clarification between SA WG6 and SA WG3 and between SA WG1 and SA WG3.","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:37","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6, SA WG1","Cc":"TSG SA","lsoriginalls":"S3-214337","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211255.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211256","title":"Reply LS on LS on MINT functionality for Disaster Roaming","source":"SA WG3","contact":"Dongjoo Kim","contact-id":84882,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank SA WG2 for the LS(S3-213874\/S2-2108172) on MINT functionality for Disaster Roaming. SA WG3 would like to inform SA WG2 that the MINT functionality must ensure that a VPLMN cannot single-handedly trick the HPLMN into considering the VPLMN as providing the disaster roaming. With this in mind, OAM configuration in the HPLMN seems important. SA WG3 would also like to inform SA WG2 that SA WG3 will continue to analyse further security impact caused by Disaster Roaming service indication and will keep SA WG2 informed when there is progress.","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:37","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG RAN, TSG CT, TSG SA, RAN WG2, CT WG6, CT WG4, CT WG1, SA WG5","lsoriginalls":"S3-214342","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211256.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211257","title":"LS from SA WG5: Reply LS to GSMA on new whitepaper E2E Network Slicing Architecture","source":"SA WG5","contact":"Kai Zhang","contact-id":66365,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank GSMA NG for their LS on New Whitepaper: 'E2E Network Slicing Architecture'. SA WG5 supports the intention of the whitepaper to show guidance of the entire industry ecosystem, for operators, vendors and service providers to be able to consider common solutions of network slicing. SA WG5 provides the following feedback on the whitepaper: - Regarding 2.4 SLA\/SLS attributes for Network Slicing o Besides the alignment work of attributes between Service Profile in 3GPP TS 28.541 and GST NG.116 is proceeding at the present time, Service Profile can be translated to corresponding requirements for dedicated domains. For example, 5GC SliceProfile is used to carry 5GC domain requirements, NG-RAN SliceProfile is used to carry NG-RAN domain requirements, and TN requirements are translated and provided to TN domain. Please see 3GPP TS 28.541 for further information on the relation between GSMA GST, ServiceProfile and SliceProfile. - Regarding the figure of High level diagram of O&M domain in 5.4 O&M o Why is there TMF638 Inventory Mgmt illustrated in RAN Mgmt domain and CN Mgmt Domain? SA WG5 thinks the intent of TMF638 Inventory Mgmt API is to provide a consistent\/standardized mechanism to query and manipulate the Service inventory in E2E Network & Service Mgmt Domain, not for a dedicated domain like RAN Mgmt domain or CN Mgmt domain. - Regarding the figure of 3GPP NRM for 5G network in 5.4.1 SA WG5 o JSON is listed as one kind of Solution Sets in the figure. However, in SA WG5 Rel-17 work, JSON has been replaced by YAML. 3GPP NRM Stage 3 Solution Sets are YAML and YANG.","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:37","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG","Cc":"TSG SA, SA WG2, TSG RAN","lsoriginalls":"S5-215083","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211257.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211258","title":"LS from SA WG5: LS to 3GPP OPs on Multi-SDO Autonomous Networks (AN) formal cooperation proposal","source":"SA WG5","contact":"Thomas Tovinger","contact-id":3654,"tdoctype":"LS in","for":"Information","abstract":"Background: SA WG5 has been working on standards to support management of automation already since 4G\/LTE with Self Organizing Networks (SON), and since last year several studies and work items for 5G related to Autonomous Networks (AN) have been started (e.g., Closed loop automation, Autonomous Network Levels, Intent driven management, Management Data Analytics, SON, etc.). Autonomous Networks standardisation has also lately become a very 'popular' topic in practically all SDOs\/organisations defining management standards within their respective areas: 3GPP, ETSI, GSMA, ONAP, NGMN, CCSA, IEEE, IETF, ITU-T and TM Forum. Therefore, TM Forum last year launched a global joint effort by coordinating all these SDOs\/organisations to try to harmonise all AN-related standards as much as possible, to enable increased interoperability between products implementing the different standards. This cooperation project started with a series of conference calls and email exchanges as well as a project website where meeting minutes and other documents such as technical contributions could be stored. SA WG5 also joined these discussions from the start, as we believe it would be a great advantage if we could share all the experience and definitions that we have in the automation\/AN area with the other SDOs, thus increasing the possibility that they would reuse SA WG5's definitions to a large extent. However, so far there is no formally signed cooperation agreement (including IPR policy for this project and how to publish any jointly produced documents like a White Paper); therefore, until now we have not submitted any technical contributions from SA WG5 to this project. In order to resolve this issue, TM Forum has recently prepared a first draft proposal on how such a cooperation agreement could look like and sent it with an LS to all participating SDOs for comments and agreement if possible, or update proposals if necessary, to be able to sign the cooperation agreement. This is the attached LS S5-215480, and therein, the cooperation agreement is the embedded document entitled 'DRAFT Multi SDO Participant Agreement'. The proposed IPR policy and Antitrust Policy & Guidelines (based on TM Forum's policies) are found in the link 'By-laws of TM Forum' in the body text of the LS (note: not in the embedded document). This cooperation agreement and related IPR policy \/ Antitrust Policy comprise legally formal text that neither SA WG5's delegates nor leadership are able to judge and decide whether it would be legally correct to sign. We therefore kindly ask the OPs, on recommendation from the SA leadership, to analyse this and take a decision on whether it can be signed for 3GPP or if some changes of the participation agreement description would be needed before signing.","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:37","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP PCG and Organizational Partners (OPs)","Cc":"TSG SA","lsoriginalls":"S5-215484","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211258.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211259","title":"LS from SA WG5: Reply to TM Forum on Intent Management","source":"SA WG5","contact":"Volodymyr Malashnyak","contact-id":87599,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 wishes to thank TM Forum for the 'Reply 3GPP LS S5-213522 to TM Forum on Intent Management' and we would like to give the following feedback and comments: Re: Action: 1 'TM Forum kindly asks SA WG5 to take the above information into account in Release 17 and provide feedback on our IG1253 documents': - After looking at IG1230 and IG1253 set of documents published by TM Forum we see the benefit to share understanding of Intent-driven concept between SA WG5 and TM Forum specified in IG1230 v.1.1.0 Sec 6.5. - At the next MSDO meeting discussing topic 'Intent-driven Interaction' we propose to discuss what the issues would be if SA WG5 and\/or any other SDO join efforts with TM Forum to work on specification of Intent-driven MnS or Intent-base API and discuss how those issues can be resolved. Re: Action: 2 'Please keep TM Forum informed of the progress of SA WG5 work related to intent-driven management': The work around Intent Management including Intent-driven MnS, Intent Management, Operations and Intent Modelling is ongoing in SA WG5 working group since 2018 with target completion date of normative work in December 2021. In order to eliminate the need for adaptation between solutions defined by TM Forum and 3GPP, we propose to start a discussion about how to align standardization activities around Intent API, and Intent management and modelling. Proper scoping and timing for cooperation shall be considered to avoid any delay of 3GPP Rel-17 standardization work. Question 1: There are 3 intent driven occurrence, 29 intent-driven occurrence, 3 intent-based occurrences in TMF IG1230. It would be better to clarify which intent concept TM Forum is addressing. Intent-based networking seems is published by IETF. It would be better to clarify the relation also in MSDO. Question 2: Is it possible to use CRUD (Create, Read, Update, Delete) operations (described in 3GPP TS 28.532, cl.11.1.1.1) to support methods described by TM Forum for Intent Life-Cycle management procedures in IG1253C, cl.3 and cl.4?","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:37","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TM Forum","Cc":"TSG SA","lsoriginalls":"S5-215486","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211259.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211260","title":"LS from SA WG5: LS 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":7599,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to inform TM Forum, MEF and GSMA that we have started a Release 17 study on network slice management capability exposure. SA WG5 is currently working on two main use cases for the ordering and provisioning of network slices. {. . .} SA WG5 would like to collect your feedback on the above statements. It should be noted that the Assurance part of the network slice is not yet addressed. Candidate APIs shall be identified, for interface types listed here above. SA WG5 is also thinking about new use cases in which the Network Slice Customer (NSC) could be willing to have access to more technical information concerning the network slice, than only the information exposed via the Network Slice Provider (NSP) product catalogue at BSS level. Such use cases are still under investigation. Finally, SA WG5 is also studying whether and how intent-based management may be used in this architecture, in particular when abstraction is required between the two sides of interfaces, and when multiple APIs are candidate for the same purpose. SA WG5 would be happy to collaborate further on all this with TMF, MEF and GSMA.","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:37","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TM Forum, MEF, GSMA","Cc":"TSG SA","lsoriginalls":"S5-215530","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211260.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211261","title":"LS from SA WG5: LS to ITU-T SG2 on autonomous network levels","source":"SA WG5","contact":"Xi Cao","contact-id":54217,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank ITU-T SG2 for your LS on initiation of a new work item M.il-AITOM 'Intelligence Levels of AI enhanced Telecom Operation and Management'(S5-214045\/SG2-LS195-TD1437R1) informing SA WG5 about the initiation of a new work item on Intelligence Levels of AI enhanced Telecom Operation and Management. SA WG5 would also like to inform ITU-T SG2 that SA WG5 is now working on autonomous network levels, the study output is captured in TR 28.810 (the latest released version is TR 28.810 V17.0.0), and the normative work is ongoing, the output will be captured in TS 28.100 (the latest version is draft TS 28.100 V0.6.0).","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:37","uploaded":"2021-11-17 08:23:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITUT SG2","Cc":"TSG SA","lsoriginalls":"S5-215539","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211261.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211262","title":"LS from CT WG1: Reply LS on EPS support for IoT NTN in Rel-17","source":"CT WG1","contact":"Marko Niemi","contact-id":16608,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 would like to thank TSG RAN, RAN WG2 and SA WG2 for their LSs on EPS support for IoT NTN in Rel-17. Considering support for discontinuous coverage: CT WG1#132e and 133e discussed and assumes that SA WG2 and RAN\/RAN WG2 should first discuss on the topic and decide whether new functionality needs to be introduced. CT WG1 will align with the decision. Considering support for WUS (response to C1-216539\/S2-2108176): CT WG1 confirms that WUS is not excluded from CT WID. Action: CT WG1 kindly asks groups to consider response given and provide feedback if necessary.","secretary_remarks":"CC#1: This LS was noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2021-11-16 10:00:37","uploaded":"2021-11-25 16:07:01","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2, TSG CT, TSG RAN, TSG SA","Cc":"CT WG4, RAN WG3","lsoriginalls":"C1-217258","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211262.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211263","title":"LS from SA WG1: Reply to LS on support of PWS over SNPN","source":"SA WG1","contact":"Betsy Covell","contact-id":86567,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 would like to thank SA WG3 for their LS on PWS over SNPN. In response to SA WG3 request to provide any added\/updated PWS requirements, SA WG1 confirms there are no new PWS requirements specific to NPNs.","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:37","uploaded":"2021-11-25 16:07:01","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2, CT WG1, RAN WG2, RAN WG3, TSG SA, TSG CT, TSG RAN","lsoriginalls":"S1-214049","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211263.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211264","title":"Reply LS on EPS support for IoT NTN in Rel-17","source":"SA WG2","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS in","for":"Action","abstract":"As a follow-up to the LS from SA WG2#147e in S2-2108176, SA WG2 would like to inform it has concluded to support discontinuous coverage in Rel-17 as documented in the attached CR. SA WG2 has also updated the WID accordingly as shown in attachment. The agreed solution assumes corresponding functionality in RAN WG2 and CT WG1 specifications. Please note that the support of discontinuous coverage may be further studied in Rel-18. SA WG2 would appreciate feedback on these aspects as necessary. Action: SA WG2 would like to ask TSG RAN, RAN WG2, CT, CT WG1 and TSG SA to take note of the information above.","secretary_remarks":"CC#1: If WID in SP-211306 is approved either an LS could be sent or reported to the relevant groups. CC#4: This LS was noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2021-11-16 10:00:37","uploaded":"2021-11-25 16:07:01","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, TSG SA, CT WG1, TSG CT, TSG RAN","Cc":"CT WG4, CT WG3, RAN WG3","lsoriginalls":"S2-2109344","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211264.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211265","title":"LS from ITU-T SG3: LS on ongoing work within ITU-T Study Group 3 (SG3) on new Technical Report on 'IMT2020-Related Policy Considering MVNOs'","source":"ITU-T SG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"ITU-T Study Group 3 (SG3), Tariff and accounting principles and international telecommunication\/ICT economic and policy issues, thanks the former Focus Group on Machine Learning for Future Networks including 5G (FG-ML5G) for their comments on STUDY_IMT2020MVNOs, a Technical Report on 'IMT2020-Related Policy Considering MVNOs', which SG3 studied with interest. SG3 is interested on the situation of the deliverables of FG-ML5G and their status in Study Group 13. Please inform us accordingly. Further, SG3 is seeking your guidance from a technical perspective on this draft Technical Report so that we can make progress. We kindly seek your cooperation to assist us with a mapping of your Recommendation ITU-T Y.3111 (09\/2017), IMT-2020 network management and orchestration framework, to the scope of our report. We further request 3GPP and other organizations to share with us relevant use cases on the subject matter to enhance the progress of the work item. SG3 plans to discuss the attached contribution (SG3-C337) further during its next SG3 meeting (Virtual, 13 to 17 December 2021). To help inform our discussion and progress the work, we welcome any feedback you may have on this contribution or on the work item overall. SG3 looks forward to your input and to continued collaboration and cooperation on this topic.","secretary_remarks":"CC#2: 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":"2021-11-16 10:00:37","uploaded":"2021-11-25 16:07:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG13","Cc":"ITU-D SG1, ITU-T SG3 RGs, 3GPP","lsoriginalls":"SG3-LS99","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211265.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211267","title":"LS from SA WG5: Reply LS on Prioritized Vehicle to Cloud Technical Solutions (Automotive Edge Computing Consortium (AECC))","source":"SA WG5","contact":"Lan Zou","contact-id":35534,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank Automotive Edge Computing Consortium (AECC) for the LS about Prioritized Vehicle to Cloud Technical Solutions. SA WG5 is currently responsible for: ? Management and Orchestration, which covers aspects such as operation, assurance, fulfillment and automation, including management interaction with entities external to the network operator (e.g. verticals). ? Charging, which covers aspects such as Quota Management and Charging Data Records (CDRs) generation, related to end-user and service-provider. {. . .} All documents are available at: https:\/\/www.3gpp.org\/DynaReport\/TSG WG--S5.htm SA WG5 is looking forward to further information exchange with AECC if needed.","secretary_remarks":"CC#2: 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":"2021-11-25 10:50:39","uploaded":"2021-12-01 09:41:57","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Automotive Edge Computing Consortium (AECC)","Cc":"SA WG1, SA WG2, SA WG6","lsoriginalls":"S5-216412","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211267.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211268","title":"LS from SA WG5: Reply LS on updating the readme.md file in 3GPP Forge","source":"SA WG5","contact":"Lan Zou","contact-id":35534,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank CT WG3 and CT WG4 for the LS on updating the readme.md file in 3GPP Forge. SA WG5 supports the initiative to (re-)organize the 'README.md' to better reflect the content of forge. SA WG5 is currently maintaining the 'SA WG5 - Management & Orchestration and Charging \/ Management and Orchestration APIs' in https:\/\/forge.3gpp.org\/rep\/sa5\/MnS as the focal point to access SA WG5 developed stage 3 work. SA WG5 OAM develops two solution sets including yang-models and OpenAPI. There are three readme.md files so far kept in SA WG5 forge folder: 1. Readme.md under link https:\/\/forge.3gpp.org\/rep\/sa5\/MnS provides the overall introduction of forge for 'Management and Orchestration - TSG SA Working Group 5 (SA WG5)' 2. Readme.md under link https:\/\/forge.3gpp.org\/rep\/sa5\/MnS\/tree\/Rel17-draft\/OpenAPI provides the introduction of the SA WG5 OpenAPIs. SA WG5 OpenAPI forge repository includes two categorizes of information: Network Resource Models (NRM) and Management Services (MnS). The use of SA WG5 OpenAPI needs to combine the MnS and selected NRM for the corresponding management. 3. Readme.md under link https:\/\/forge.3gpp.org\/rep\/sa5\/MnS\/tree\/Rel17-draft\/yang-models provides the introduction of all SA WG5 YANG modules and submodules. SA WG5 Charging is currently maintaining the charging APIs including TS32291_Nchf_ConvergedCharging.yaml and TS32291_Nchf_ConvergedCharging.yaml in the 5G APIs https:\/\/forge.3gpp.org\/rep\/all\/5G_APIs as following, SA WG5 may consider further reorganization of Charging part if needed. 1. Readme.md under link https:\/\/forge.3gpp.org\/rep\/all\/5G_APIs\/blob\/master\/README.md provides the introduction of CHF (Charging Function). SA WG5 welcome opinions or suggestions from CT groups for the organization of SA WG5 forge repository.","secretary_remarks":"CC#2: 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":"2021-11-25 10:50:39","uploaded":"2021-12-01 09:41:57","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3, CT WG4","Cc":"TSG SA, TSG CT, CT WG1, SA WG4","lsoriginalls":"S5-216413","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211268.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211269","title":"LS from SA WG5: LS on MANO performance measurements accuracy to estimate VNF energy consumption","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599,"tdoctype":"LS in","for":"Information","abstract":"3GPP TSG WG5 (Telecom Management), a.k.a. SA WG5, thanks ETSI NFV for your LS on MANO performance measurements accuracy to estimate VNF energy consumption. SA WG5 would like to inform ETSI NFV that our Rel-17 study on new aspects of EE for 5G networks and Rel-17 work item on enhancements on EE for 5G networks have been completed at this meeting and that we have planned to continue working on these aspects during our Release 18. Both a new study and work item have been proposed and discussed within SA WG5. Pending SA approval at its December meeting, the Release 18 work on energy efficiency of 5G network will start on January 2022. SA WG5 may need further interactions with ETSI NFV to progress on these topics during our Release 18 timeframe. Also, SA WG5 will keep ETSI NFV informed of any progress from our side.","secretary_remarks":"CC#2: 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":"2021-11-25 10:50:39","uploaded":"2021-12-01 09:41:57","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI NFV","Cc":"TSG SA","lsoriginalls":"S5-216419","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211269.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211353","title":"Reply LS on Inclusive language for ANR","source":"SA WG5","contact":"xiaoli Shi","contact-id":84838,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks RAN WG2 for the LS R2-2108869 on Inclusive language for ANR. Considering the inconsistencies, corresponding relationship of RAN related references are replaced with 'exclude-list' in the TS 28.541, and there would be no issues due to the terms are not fully aligned.","secretary_remarks":"CC#2: 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":"2021-12-01 10:59:46","uploaded":"2021-12-01 11:03:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3, TSG RAN, TSG SA","lsoriginalls":"S5-216197","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211353.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211410","title":"LS from SA WG3: Reply LS on LS on MINT functionality for Disaster Roaming","source":"SA WG3","contact":"Dongjoo Kim","contact-id":84882,"tdoctype":"LS in","for":"Information","abstract":"This is a follow-up LS of S3-214342, which was a reply LS on the LS(S3-213874\/S2-2108172) on MINT functionality for Disaster Roaming. SA WG3 has discussed the security aspect on the inclusion of the Disaster Roaming indication and concluded there is no additional security issue caused by the indication. SA WG3 believes the indication is not used in AKA procedure. Thus, SA WG3 would like to request SA WG2 to make their own decision on whether to support the indication or not based on the use cases, and keep SA WG3 informed on the progress. SA WG3 will then update the specification under SA WG3 control accordingly.","secretary_remarks":"CC#2: 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":"2021-12-02 08:17:40","uploaded":"2021-12-02 08:25:37","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG RAN, TSG CT, TSG SA, RAN WG2, CT WG6, CT WG4, CT WG1, SA WG5","lsoriginalls":"S3-214416","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211410.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211411","title":"LS on LTE User Plane Integrity Protection","source":"SA WG3","contact":"Tim Evans","contact-id":49202,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to inform that the work on integrity protection for user plane in EPS has been completed except for the following issue which is in the remits of RAN groups and hence left open. SA WG3 has decided to use LTE algorithms for integrity protection of the user plane. However, SA WG3 did not decide on using either LTE or NR algorithm code points for signalling to the UE which integrity algorithm to use. SA WG3 does not see any security issue with choosing either of the alternatives. This is because the algorithms are identical and can be mapped to each other. Therefore, SA WG3 kindly requests the RAN groups to take the final decision in this matter and inform SA WG3. To complete the work, SA WG3 has agreed on the attached CRs.","secretary_remarks":"CC#2: 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":"2021-12-02 08:17:41","uploaded":"2021-12-02 08:25:37","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, RAN WG2","Cc":"TSG RAN, TSG SA","lsoriginalls":"S3-214462","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211411.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211412","title":"LS from ITU-R WP5D: Development of a draft new Report ITU-R M.[IMT.INDUSTRY] -Applications of IMT for specific societal, industrial and enterprise usages","source":"ITU-R WP5D","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"'Applications of IMT for specific societal, industrial and enterprise usages'. The scope of this draft new Report ITU-R M.[IMT.INDUSTRY] addresses, inter alia, the usage, technical and operational aspects and capabilities of IMT for meeting specific needs of societal, industrial and enterprise usages. Current preliminary draft working document being developed in the WP 5D is enclosed for reference (TEMP\/463Rev.2 published as 5D\/886 (Annex 3.3)). This work has been initiated under Question ITU-R 262\/5. WP 5D would like to invite the External Organizations to provide information on industrial and enterprise on its usage, applications, required capabilities, technical and operational aspects, and any other related material that would facilitate in completion of this Report. External Organizations are invited to provide material preferably to the 40th meeting of WP 5D but no later than 41st meeting of WP 5D, as appropriate. Working Party 5D looks forward to collaborating with External Organizations on this matter. Working Party 5D will keep the External Organizations informed of the progress and outcomes of relevant studies in future WP 5D meetings.","secretary_remarks":"CC#1: Clarify which WGs can provide response information. CC#4: To be forward to SA WG1 - please provide input till March. This LS was postponed and will be forwarded to SA WG1 by MCC.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10040,"status":"postponed","reservation_date":"2021-12-02 09:05:12","uploaded":"2021-12-02 09:07:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXTERNAL ORGANIZATIONS","Cc":"","lsoriginalls":"ITU_R_WP5D_TEMP_464rev3","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211412.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211413","title":"LS from ITU-T SG2: LS on new work item TR.SPN, 'spoofing using national numbers'","source":"ITU-T SG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"During the ITU-T Study Group 2 (SG2) meeting, Question 3\/2 held a meeting on 9 November 2021, at which discussions took place on contribution C362 (Egypt), relating to spoofing using national numbers. The contribution provided a technical solution to avoid spoofing using national numbers. The solution is based on using a firewall on an international gateway to block all international calls with national numbers except for roaming subscribers. Therefore, no national number with international format should call unless it is a real roamer number. Q3\/2 created a new work item, a Technical Report on spoofing using national numbers (TR.SPN). The objective of this new Technical Report is to study the technical and security aspects that Member States and operators may face while applying this solution. (Please refer to the A.13 justification at SG2-TD90R1\/PLEN.) Q3\/2 would welcome comments and views on these documents, and kindly requests that you provide us with the technical and security aspects that may be considered. Attach: - SG2-C362, 'Spoofing using national number'. - SG2-TD090R1\/PLEN, 'A.13 justification for the new work item TR.SPN: 'Spoofing using national number'","secretary_remarks":"CC#2: 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":"2021-12-02 12:06:50","uploaded":"2021-12-02 14:38:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-SG11, SG17, 3GPP, GSMA","Cc":"","lsoriginalls":"SG2-LS222-TD1512","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211413.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211414","title":"LS from ITU-T JCA-IMT2020: LS on Invitation to update the information in the IMT2020 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 (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. Should you wish to communicate any additional information about your specifications and projects, we invite you to do so. 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 July 2022 alongside the ITU-T SG13 meeting 4 - 15 July 2022, place TBC. We invite your inputs\/updates to the roadmap.","secretary_remarks":"CC#1: This LS was noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2021-12-02 12:06:50","uploaded":"2021-12-03 08:12:29","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU SGs, External IMT-2020 liaison partners","Cc":"","lsoriginalls":"JCA-IMT2020-O-019","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211414.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211484","title":"LS from 5GAA: LS on 3GPP Rel-18 items","source":"5GAA","contact":"Maxime Flament","contact-id":79037,"tdoctype":"LS in","for":"Action","abstract":"5GAA has submitted its contribution [RWS-210360] with most relevant evolution topics of the automotive sector to the TSG RAN Rel-18 workshop. Those topics were identified through a survey amongst 5GAA members. 5GAA appreciates that many of those topics are currently reflected in Rel-18 draft WIDs. 5GAA has identified a mapping of the topics provided in RWS-210360 with potentially corresponding RAN draft WIDs as outcome of the October 2021 discussions:. The green marked topics are considered by 5GAA to be addressed by some of the aspects in the listed draft WIDs, while the remaining topics could not be identified within the draft Rel-18 WIDs currently available. Alignment of those topics between RAN and SA work is important and should be part of the 3GPP internal alignment process. Actions to TSG RAN: 5GAA understands that Rel-18 will address many topics of different industry sectors. 5GAA would like to encourage 3GPP to keep the green marked topics within the Rel-18 scope during the Rel-18 packaging at RAN#94e and if 3GPP workload allows, also to consider including some of the black marked topics to the appropriate WIs.","secretary_remarks":"Action is to TSG RAN. CC#2: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10320,"status":"noted","reservation_date":"2021-12-03 08:12:01","uploaded":"2021-12-03 08:19:54","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA","Cc":"","lsoriginalls":"5GAA_S-210187","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211484.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211578","title":"LS from GSMA OPAG: Reply LS on edge computing definition and integration","source":"GSMA OPAG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Introduction: GSMA OPG Operator Platform API Group (OPAG) would like to thanks TSG SA, SA WG2, SA WG5, and SA WG6 delegates as well as ETSI ISG MEC members for attending the webinar on the mapping of SDO specifications to APIs to be exposed or used by the Operator Platform to realise its required interfaces. For delegates that were unable to attend, OPAG would like to inform that a recording of the webinar as well as the slides used are now available, see [3]. Discussion: The OPAG would like to invite feedback to that mapping at the joint workshop that has been planned for 21st January 2022, see [2], targeting a conclusion of that mapping allowing work to close the gaps identified to start shortly after. Actions: Based on the mapping presented during the webinar, the OPAG wishes to continue the multi-party discussion with ETSI ISG and 3GPP. For this a follow-up workshop has been agreed on 21 January 2022, 13:00-15:00 GMT [2], for 3GPP and ETSI to provide feedback based on OPAG mapping and review\/discuss\/align. GSMA wishes to invite all delegates of the involved groups to join this workshop.","secretary_remarks":"CC#2: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10330,"status":"noted","reservation_date":"2021-12-13 08:15:55","uploaded":"2021-12-13 08:16:24","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI ISG MEC, TSG SA, SA WG2, SA WG5, SA WG6","Cc":"ETSI ISG NFV","lsoriginalls":"OPAG_04_Doc_02","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211578.zip","group":"SP","meeting":"SP-94-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]