[{"name":"SP-200635","title":"LS from ITU-R WP 5D: LIAISON STATEMENT TO RIT\/SRIT PROPONENTS ON THE COMPLETION AND CONCLUSIONS OF STEPS 5 TO 7 OF THE IMT-2020 PROCESS FOR THE FIRST RELEASE OF NEW RECOMMENDATION ITU-R M.[IMT-2020.SPECS]","source":"ITU-R WP 5D","contact":"Sergio Buonomo","contact-id":79388,"tdoctype":"LS in","for":"Information","abstract":"This liaison is to update you on the progress and results on Working Party 5D Meeting #35e particularly with regard to the completion of Steps 5-7 of the IMT-2020 process and the decisions on which of the candidate technology submissions have move forward to Step 8. ITU-R Working Party 5D (WP 5D) thanks the RIT\/SRIT Proponents and the GCS Proponents for their work regarding the submissions for IMT-2020 under the IMT-2020 development process. WP 5D has previously informed the relevant External Organizations of the detailed schedule for finalization of the first release of new Recommendation ITU-R M.[IMT-2020.SPECS] 'Detailed specifications of the radio interfaces of IMT-2020' in prior liaison related to two IMT-2020 Documents (IMT-2020\/20, IMT-2020\/21). WP 5D notes, for the IMT-2020 process, that it does not anticipate any major adjustments to the planned schedule for the completion of the Recommendation and Step 8 in year 2020 as planned, absent further unanticipated COVID-19 disruptions. It is advised to monitor the WP 5D webpage for any adjustments to dates for either physical or virtual (e-meetings).","secretary_remarks":"CC#1: This was block noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2020-08-21 07:08:55","uploaded":"2020-08-25 08:54:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP Proponents, ETSI TC DECT, DECT Forum","Cc":"GCS Proponents","lsoriginalls":"5D_TD_159R1","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200635.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200636","title":"LS from ITU-R WP5D: LIAISON STATEMENT TO TRANSPOSING ORGANIZATIONS ON THE COMPLETION OF STEP 8 OF IMT-2020 PROCESS FOR THE FIRST RELEASE OF NEW RECOMMENDATION ITU-R M.[IMT-2020.SPECS]","source":"ITU-R WP5D","contact":"Sergio Buonomo","contact-id":79388,"tdoctype":"LS in","for":"Information","abstract":"This liaison is to update you on the progress and results on Working Party 5D Meeting #35e particularly with regard to the completion of Steps 5-7 of the IMT-2020 process and the decisions on which of the candidate technology submission have moved forward to Step 8. It also identifies specific actions required by a Transposing Organizations with regard to the upcoming tasks, necessary contribution, and actions in the Step 8 work and the associated obligations and the respective timelines. ITU-R Working Party 5D (WP 5D) thanks the RIT\/SRIT Proponents and the GCS Proponents for their work regarding the submissions for IMT-2020 under the IMT-2020 development process. WP 5D has previously informed the relevant External Organizations of the detailed schedule for finalization of the first release of new Recommendation ITU-R M.[IMT-2020.SPECS] 'Detailed specifications of the radio interfaces of IMT-2020' in prior liaison related to two IMT-2020 Documents (IMT-2020\/20, IMT-2020\/21). WP 5D notes, for the IMT-2020 process, that it does not anticipate any major adjustments to the planned schedule for the completion of the Recommendation and Step 8 in year 2020 as planned, absent further unanticipated COVID-19 disruptions. It is advised to monitor the WP 5D webpage for any adjustments to dates for either physical or virtual (e-meetings).","secretary_remarks":"CC#1: This was block noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2020-08-21 07:08:55","uploaded":"2020-08-25 08:55:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP SDOs","Cc":"RIT\/SRIT PROPONENTS","lsoriginalls":"5D_TD_163R1e_IMT-2020.","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200636.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200637","title":"LS from ETSI ISG E4P: Request for information exchange","source":"ETSI ISG E4P","contact":"Edgar Guillot","contact-id":17853,"tdoctype":"LS in","for":"Information","abstract":"1. Introduction to ETSI ISG E4P: In the context of a pandemic with a transmittable virus such as SARS-CoV-2, digital contact tracing systems can be used to alert people of a potential risk of infection due to having been in close contact with an infected person. The ETSI ISG E4P (Europe for Privacy-Preserving Pandemic Protection) has been created to develop a framework and consistent set of specifications for contact tracing systems using proximity detection methods. Membership (see link) has grown to about 40 organizations since the ISG launched on 26th May 2020. The framework and specifications will be designed to ensure data privacy and to facilitate the development of interoperable applications and platforms. The working plan of E4P is to produce a comparison between existing systems and four related specifications in a short timeframe. The four specifications will describe the requirements for contact tracing systems (especially privacy preservation), the device-based proximity detection mechanisms, the back-end notification mechanisms and an interoperability framework across multiple systems. The first specifications will be available soon, before end of 2020, so as to be applicable to the existing needs. 2. Exchanging information: With this liaison letter, ETSI ISG E4P would like to inform your members about our work plan, which is visible here: https:\/\/portal.etsi.org\/\/tb.aspx?tbid=890&SubTB=890#\/ ETSI ISG E4P would like to kindly invite your organization to share any information that could support the development of the E4P work. In case your organization would like to discuss collaborations, or to highlight work in your group, please contact the Chairman of ETSI ISG E4P.","secretary_remarks":"CC#1: This was block noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2020-08-21 07:08:55","uploaded":"2020-08-25 08:54:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Bluetooth SIG, TSG SA, GSMA TSG","Cc":"","lsoriginalls":"E4P(20)000_022","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200637.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200639","title":"LS from TM Forum Autonomous Networks: Introduction of TM Forum Autonomous Network project and Coordination Proposal","source":"TM Forum Autonomous Networks","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"General: There is a growing interest across many Communication Service Providers (CSPs) and their suppliers into the opportunities presented by Autonomous Networks (AN) and Services to substantially improve operational efficiency and enable service innovations through intelligence-driven self-operating of networks and services. TM FORUM started an official project on Autonomous Networks Project (ANP) since July 2019. The scope of the project consists of: - User stories\/use cases - Vision & roadmap - Business requirements and architecture - Technical architecture The vision of Autonomous Networks in TM FORUM: - The long term vision is to provide innovative ICT infrastructure, capabilities and services with 'Zero X' (zero wait, zero touch, zero trouble, zero friction) experience for the users of vertical industries and consumers through Self-X capabilities (self-serving, self-fulfilling, self-assuring), which makes them simpler to consume by the users, and leaves the implementation complexity with the providers. - Autonomous Networks are likely to evolve step by step according to different autonomous levels, with corresponding services and capabilities. The framework of Autonomous Networks consists of '3-layer, 4-closed-loop' which cover from business operation layer to the network layer, i.e. - 3-layers: business operations layer, service operations layer and resource operations layers, and - 4-closed loops: resource closed loop, service closed loop, business closed loop and more importantly user closed loop from an E2E user perspective. TM FORUM Autonomous network project had published the following documents: 1. Whitepaper: 'Autonomous Networks: Empowering Digital Transformation For Telecoms Industry', May 2019 2. IG1193 'Cross-Industry Autonomous Networks - Vision and Roadmap v1.0', October 2019 3. IG1218 'Autonomous Networks Business Requirements & Architecture v1.0', July 2020, which defined basic concept, vision, framework, autonomous network levels, user stories category, business requirements, architecture and capabilities, as well as example use cases for Autonomous Networks. Further detailed information can be found in attached publications. TM FORUM Next steps: - TM FORUM is now working on the enhanced version of Autonomous Networks Business Requirements & Architecture 1.1 and Autonomous Networks Technical Requirements & Architecture 1.0, and Whitepaper R2.0. All of them are targeted to be published in Oct 2020. - -TM FORUM is seeking the Cross SDO collaboration, starting from this information sharing Liaison and planning a Multi-SDO collaboration workshop in Oct 2020. Cross-SDO collaboration proposal: We noticed that recently Autonomous Network initiatives are being progressed in multiple SDOs. We believe that alignment on Autonomous Network concept, vision, framework and key topics, and discussion on the responsibility and collaboration for the future works would best guide the industry to progress in a coordinated way on this topic. Given that AN initiatives are being progressed in multiple SDO, it would be beneficial for the industry to hold a Cross SDO workshop to review activities, identify key topics and gaps across multiple SDOs towards an industry collaboration ecosystem on Autonomous Networks. Invitation to Cross-SDO Collaboration Workshop on Autonomous Networks: TM Forum is willing to organize a virtual workshop in the last week of September (29th or 30th) to kick off the collaboration discussion on the Autonomous Network. We invite representatives from your organization to the virtual workshop, share information on autonomous network related work in your organization, and also your suggestions on future collaborations. The suggested virtual workshop objectives are: 1. Share information and ideas on the vision, key points and activities of each organizations developing AN solutions using their unique domain skills. 2. Discuss the gaps and key topics in industry activities for reaching industry consensus an","secretary_remarks":"CC#1: This was block noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2020-08-21 07:08:55","uploaded":"2020-08-25 08:54:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI, SA WG5, GSMA, NGMN, CCSA TC7","Cc":"TSG SA","lsoriginalls":"Liaison AN results ETSI GSMA 3GPPv2","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200639.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200640","title":"LS from IETF: Re: LS on need for Multi-Path QUIC for ATSSS","source":"IETF","contact":"Lars Eggert","contact-id":43655,"tdoctype":"LS in","for":"Information","abstract":"Thank you for your input to our specifications. Multipath capabilities for QUIC are currently under active discussion in the IETF's QUIC WG. Several individual proposals have been made, but the group is also considering whether the already-specified connection migration capabilities are sufficient to cover the majority of use cases. We encourage 3GPP to contribute their requirements for QUIC multipath capabilities in an Internet-Draft, especially if the already-specified connection migration capabilities are deemed insufficient. 3GPP's active involvement in any multipath QUIC standardization would be the best way to remain informed of the progress of any such work in the IETF. Kind regards, Mark Nottingham, Lucas Pardue and Lars Eggert, QUIC Working Group chairs","secretary_remarks":"CC#1: This was 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":"2020-08-21 07:08:55","uploaded":"2020-08-25 08:54:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2","lsoriginalls":"LS_from_IETF","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200640.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200641","title":"LS from IETF DRIP: Drone Remote ID Protocol Working Group (DRIP)","source":"IETF DRIP","contact":"Eric Vyncke","contact-id":29424,"tdoctype":"LS in","for":"Information","abstract":"Information of the DRIP working group can be found on the following web page: https:\/\/datatracker.ietf.org\/wg\/drip\/about\/ This is where the latest version of the charter can be found - reminded in the following section as well as the status an progress of the WG documents we detail in the following section. Charter for Working Group Civil Aviation Authorities (CAAs) worldwide have initiated rule making for Unmanned Aircraft Systems (UAS) Remote Identification (RID). CAAs currently promulgate performance-based regulations that do not mandate specific techniques, but rather cite industry-consensus technical standards as acceptable means of compliance. One key standard is ASTM International (formerly the American Society for Testing and Materials) WK65041 [1]. This technical specification defines UAS RID message formats, and transmission methods. Network RID defines a set of information for UAS to be made available globally via the Internet. Broadcast RID defines a set of messages for UAS to send locally one-way over Bluetooth or Wi-Fi. WK65041 does not address how to populate\/query registries, how to ensure trustworthiness of information, nor how to make the information useful. DRIP's goal is to specify how RID can be made trustworthy and available in both Internet and local-only connected scenarios, especially in emergency situations. Some UAS operate in environments where the network or the devices or both are severely constrained [2] in terms of processing, bandwidth (e.g., Bluetooth 4 beacon payload is 25 bytes long), or battery life, and DRIP aims to function in these environments. The specifications produced by the WG will need to balance public safety authorities' need to know trustworthy information with UAS operators' and other involved parties' privacy. The working group will primarily leverage Internet standards (including HIP, EPP, RDAP, and DNS) and infrastructure as well as domain name registration business models. The WG will track and align with the requirements being developed by regulatory authorities, e.g., the International Civil Aviation Organization the European Union Aviation Safety Agency (EASA) delegated [3] and implementing [4] regulations, and the US Federal Aviation Administration (US FAA) [5]. The working group will work on the following items: - Requirements: the WG is expected to provide an informational document that lists the technical requirements for applying IETF protocols to the UAS Remote Identification (UAS RID) - that is the system for identifying Unmanned Aircraft (UA) during flight by other parties. These requirements also include showing that new or adapted identifiers from existing protocols conform and meet the specifications to be certified as a UAS RID. - Architecture: the WG will propose a standard document that describes the architecture that address the technical requirements and that will attempt to re-use protocols or architectures already standardized at the IETF. - Protocol design: while the primary purpose of DRIP WG is to leverage existing protocols, the specificities of the UAS environment are likely to require existing protocols to be extended or new protocols to be designed. The WG will focus on getting these protocols or extensions standardized, coordinating with other WGs relevant for the protocol(s) in question on the most appropriate home for any given piece of work.","secretary_remarks":"CC#1: This was 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":"2020-08-21 07:08:55","uploaded":"2020-08-25 08:54:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"","lsoriginalls":"LSs_from_IETF_9June2020","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200641.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200642","title":"LS from ITU-R WP5A: LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS ON ITS Connected Automated Vehicles (CAV)","source":"ITU-R WP5A","contact":"Uwe Loewenstein","contact-id":11941,"tdoctype":"LS in","for":"Information","abstract":"ITU-R Working Party (WP) 5A has initiated its work on Question ITU-R 261\/5 'Connected Automated Vehicles (CAV)' and a working document is being developed, see Annex 16 to Document 5A\/85. Section 3 of this initial draft of the working document contains references to the related ITU-R texts. Working Party 5A kindly requests the interested external organizations to provide material on the description, architecture, applications, technologies, and operational scenarios of CAVs and the radiocommunication requirements for CAVs. The next meeting of Working Party 5A is scheduled for 9-20 November 2020 and the deadline for contributions is 16:00 hours UTC, 2 November 2020.","secretary_remarks":"CC#1: This was 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":"2020-08-21 07:08:55","uploaded":"2020-08-25 08:54:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXTERNAL","Cc":"","lsoriginalls":"5A_TEMP_29_R1","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200642.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200643","title":"LS from TSG RAN: Reply LS to RP-200030 on relevant 3GPP Specs for PC5 Sidelink","source":"TSG RAN","contact":"Philippe Reininger","contact-id":35013,"tdoctype":"LS in","for":"Information","abstract":"TSG RAN would like to thank 5GAA for the information on the ITU-T Data Base related to the Collaboration on ITS Communication Standards. TSG RAN notices that the SA WG3 TS 33.536 is missing from the list provided by 5GAA. TSG RAN prefers to remove the internal TRs from the list which are 3GPP internal documents. The TSG RAN clarifies that the relevant stage-3 specs can be found in the stage-2 references and adds some key stage-3 specifications.","secretary_remarks":"CC#1: This was 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":"2020-08-21 07:08:55","uploaded":"2020-08-25 08:54:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"5GAA WG4","Cc":"TSG SA","lsoriginalls":"RP-201285","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200643.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200644","title":"LS from TSG RAN: Reply LS to GSMA_5GSI_28_Doc003 = RP-193053 on 5G indicator enhancement","source":"TSG RAN","contact":"Damiano Rapone","contact-id":65295,"tdoctype":"LS in","for":"Information","abstract":"TSG RAN would like to make the GSMA Network Group (NG) aware of the completion of the activities as requested by the GSMA 5GSI in their LS Reply in RP-193053 sent to RAN#86 in December 2019 (5GSI#28 Doc 003). Within the Ls Reply there was a request for 3GPP to take into consideration the new requirements when defining specifications that impact the display of the 5G status indicator. In order to implement these requirements from GSMA, TSG RAN agreed on introducing enhancements to the existing 5G indicator handling based on the upperLayerIndication bit in the E-UTRA SIB2 and tasked RAN WG2 to introduce further changes to the E-UTRA RRC specification (TS 36.331), please refer to 'LS on 5G Indicator' from RAN to RAN WG2 in RP-193265. During the RAN WG2#110-e meeting the Rel-16 CR to TS 36.331 in R2-2006081 (attached) was agreed and provided to RAN#88e within the RP-201166 CR pack, where the changes suggested in RP-193265 are specified from Rel-16 onwards. It is worth to note that the implementation of this CR from Rel-15 will not cause interoperability issues.","secretary_remarks":"CC#1: This was 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":"2020-08-21 07:08:55","uploaded":"2020-08-25 08:54:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA Network Group (NG)","Cc":"TSG SA, TSG CT","lsoriginalls":"RP-201358","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200644.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200645","title":"LS from ITU-T SG13: LS\/o on information about consent of Machine Learning related ITU-T Recommendation Y.3176","source":"ITU-T SG13","contact":"Leo Lehmann","contact-id":30314,"tdoctype":"LS in","for":"Information","abstract":"ITU-T SG13 would like to inform you that the new ITU-T Machine Learning related Recommendations Y.3176 'Machine learning marketplace integration in future networks including IMT-2020' (Ref. SG13-TD314\/PLEN) was consented at the ITU-T SG13 virtual meeting held on 20-31 July 2020. ITU-T SG13 looks forward for future collaboration on topics related to machine learning in future networks including IMT-2020.","secretary_remarks":"CC#1: This was 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":"2020-08-21 07:08:55","uploaded":"2020-08-25 08:54:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU SGs, TSG SA, ETSI ISG ENI, IETF NMRG, ISO\/IEC JTC1\/SC42, ISO\/IEC JTC1\/SC29, NGMN","Cc":"","lsoriginalls":"SG13-LS160","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200645.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200649","title":"LS from CT WG4: LS on AUSF\/UDM discovery based on SUCI information","source":"CT WG4","contact":"Yue Song","contact-id":57977,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 has analyzed the issue of insufficient length of Routing Indicator within SUCI, see attached discussion paper in C4-204078 for details. The current 4 digits of the Routing Indicator enables only 10 K ranges of subscriptions, which may not provide enough granularity and flexibility for moving subscriptions across UDRs not controlled by the same AUSF\/UDM, for operators with a large number of subscriptions (e.g. 100 K users per range for a PLMN with 1 billion subscriptions). CT WG4 agreed that the above limitation should be addressed. CT WG4 has also discussed the solution proposed in C4-204339 (attached) for solving this problem, enabling to use the Home Public Key ID as an additional parameter (that allows to encode e.g. a 5th digit, in addition to the key ID on 4 bits) for the discovery of the AUSF\/UDM. CT WG4 would be fine in principle to specify this solution in Rel-17, provided corresponding stage-2 requirements are agreed first.","secretary_remarks":"CC#1: This was 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":"2020-08-21 07:08:55","uploaded":"2020-09-08 05:16:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG CT, TSG SA, SA WG3","lsoriginalls":"C4-204337","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200649.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200653","title":"LS from SA WG5: LS reply to LS on M.resm-AI \u201cRequirements for energy saving management of 5G RAN system with AI\u201d","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 (Telecom Management), thanks ITU-T Q5\/2 for your LS on M.resm-AI 'Requirements for energy saving management of 5G RAN system with AI'. In its Release 16, SA WG5 has worked on use cases and requirements for a) the collection of measurements in the NG-RAN so as to be able to calculate the NG-RAN EE KPI and b) the optimization of this EE KPI by saving the energy of the NG-RAN. The resulting specification is TS 28.310 (Energy efficiency of 5G) (https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3550) In its Release 17, SA WG5 has started: - a (non-normative) study item on new aspects of EE for 5G networks, aiming to study the definition of new Energy Efficiency (EE) KPIs, and means to measure them, from various aspects including in case of multi-RAT sites, of 5G RAN sharing, of 5G Core Network, of standardized network slice types (eMBB, URLLC, mIoT, V2X), of Virtualized Network Functions, etc. The draft TR 28.813 can be found at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3743; - a (normative) work item on enhancements of EE for 5G networks, to enhance \/ complement existing 3GPP Technical Specifications, based on outcomes from the aforementioned study item. Besides, SA WG5 has an ongoing Rel-17 study on enhancement of Management Data Analytics Service (MDAS), whose outcomes are captured in TR 28.809 (https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3694), where a use case, potential requirements and potential MDAS-based solutions for energy saving in 5G networks are described. Management Data Analytics, in conjunction with AI and ML techniques, brings intelligence and automation to the network service management & orchestration. Finally, SA WG5 would like to highlight that the 3GPP management of 5G networks is specified in terms of Management Services (MnS) such as e.g. Provisioning MnS, Fault Supervision MnS, Performance Assurance MnS, etc. MnS producers expose APIs; authorized consumers may consume MnSs. The Service-based Management Architecture (SBMA) replaces the traditional NMS-EMS-NE architecture (cf. TS 28.533 'Management and orchestration; Architecture framework' - https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3416). SA WG5 kindly requests ITU-T Q5\/2 to take the above information into account and provide any feedback if needed. SA WG5 also kindly requests ITU-T Q5\/2 to keep us informed of the progress of your work on M.resm-AI 'Requirements for energy saving management of 5G RAN system with AI'.","secretary_remarks":"CC#1: This was 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":"2020-08-21 07:08:55","uploaded":"2020-09-08 05:31:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T Q5\/2","Cc":"3GPP SA, 3GPP RAN3, ITU-R WP 5D","lsoriginalls":"S5-204516","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200653.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]