[{"name":"SP-200895","title":"LS from ITU-R WP 5D: Invitation to IEGs to re-engage in Step 4 evaluation of the 'ETSI (TC DECT) and DECT Forum Proponent' and of the 'Nufront Proponent' candidate technology submissions for IMT-2020 under the \u2018Way Forward\u2019 Option 2 exceptional basis IMT-","source":"ITU-R WP 5D","contact":"Uwe Loewenstein","contact-id":11941,"tdoctype":"LS in","for":"Information","abstract":"Working Party (WP) 5D thanks the registered Independent Evaluation Groups for their active participation in the IMT-2020 process. As noted in the prior liaison dispatched via email on 15 July 2020 from Mr Sergio Buonomo, WP 5D at that time had indicated that: 'WP 5D takes this opportunity to express appreciation to the work carried out by the Independent Evaluation Groups and would welcome further opportunity in the future to engage with the IEGs who have been active in the IMT-2020 process evaluations.' Due to the previously unforeseen need to continue the evaluation of certain IMT-2020 candidate technology submissions, ITU-R is again seeking the engagement of the registered IEGs and their expertise. {. . .} Conclusion: WP 5D fully appreciates and understands that the IEGs have previously fulfilled their obligations under the Step 4 of the IMT-2020 process and that the previous Evaluation Group charters and\/or mandates may have expired and might need to be reinstated and\/or organized into the 2021 work plans of the IEG entity or their parent body or bodies. WP 5D hopes this 'Way Forward' Option 2 evaluation reset to Step 4 might be able to be accommodated by the IEG community under this one-time exceptional approach. Should an IEG need more information or have the need to discuss logistics or other details with ITU-R, they may coordinate through Mr Uwe Lowenstein, Counsellor for Study Group 5.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"INDEPENDENT EVALUATION GROUPS","Cc":"ETSI TC DECT, DECT FORUM","lsoriginalls":"5D_TD_201r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200895.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200896","title":"LS from ITU-R WP 5D: Development of a draft new Report ITU-R M.[IMT.C-V2X] - The use of the terrestrial component of IMT systems for Cellular-Vehicle-to-Everything","source":"ITU-R WP 5D","contact":"Uwe Loewenstein","contact-id":11941,"tdoctype":"LS in","for":"Information","abstract":"ITU-R Working Party (WP) 5D thanks contributing External Organizations for their reply liaison statement to WP 5D on C-V2X. WP 5D has further progressed its work on developing a working document towards a draft new Report ITU-R M.[IMT.C-V2X] 'The Use of the terrestrial component of IMT systems for Cellular-Vehicles-to-Everything'. WP 5D kindly requests the collaboration with External Organizations and seeks views and input, including but not limited to: - Use cases envisaged for C-V2X - Characteristics and Capabilities of C-V2X - Trial\/Deployment cases of C-V2X Working Party 5D looks forward External Organizations sharing information, preferably by its 37th meeting with a deadline for contribution set on 15th February 2021 (1600 UTC). Finally, WP 5D looks forward to continuing collaboration with External Organizations on this matter.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXTERNAL ORGANIZATIONS","Cc":"","lsoriginalls":"5D_TD_0206r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200896.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200897","title":"LS from ITU-R WP 5D: Future Technology Trends for the evolution of IMT towards 2030 and beyond","source":"ITU-R WP 5D","contact":"Uwe Loewenstein","contact-id":11941,"tdoctype":"LS in","for":"Information","abstract":"Considering the successful accomplishments by ITU for the evolution of IMT-2000, IMT Advanced and IMT-2020, similar actions are proposed for the evolution of IMT towards 2030 and beyond. The approach taken for IMT Advanced evolution towards IMT-2020 was to start with the work on the Report ITU-R M.2320 entitled 'Future technology trends of terrestrial IMT systems' (approved in 2014) to develop the evolution for IMT-Advanced. At its 34th meeting (19-26 February 2020), ITU R Working Party (WP) 5D decided to start study on future technology trends for the future evolution of IMT. It is planned for WP 5D to complete this study at the 41st WP 5D meeting in June 2022. A preliminary draft new Report ITU-R M.[IMT.FUTURE TECHNOLOGY TRENDS] will be developed and will consider related information from various external organizations and country\/regional research programmes. The scope of the new Report ITU-R M.[IMT.FUTURE TECHNOLOGY TRENDS] focuses on the following aspects: 'This Report provides a broad view of future technical aspects of terrestrial IMT systems considering the time frame up to 2030 and beyond. It includes information on technical and operational characteristics of terrestrial IMT systems, including the evolution of IMT through advances in technology and spectrally-efficient techniques, and their deployment.' For the development of this report, WP 5D invites the views of External Organizations on future technology trends for terrestrial IMT systems, including but not limited to the motivation on driving factors such as new use cases, applications, capabilities, technology trends and enablers. These technical inputs are intended for the timeframe towards 2030 and beyond and are proposed to be significantly advanced and different from that of IMT-2020. The draft structure of new Report ITU-R M.[IMT.FUTURE TECHNOLOGY TRENDS] is in Annex 1. Working Party 5D kindly requests the External Organizations to share their information prior to the 38th meeting of WP 5D, 6-18 June 2021. The deadline for input contributions to the 38th meeting is 31 May 2021. It is noted that the 39th meeting of WP 5D is scheduled for 4-15 October 2021, and additional inputs will also be recognised during this meeting as well. WP 5D looks forward to collaborating productively with External Organizations on this matter.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXTERNAL ORGANIZATIONS","Cc":"","lsoriginalls":"5D_TD_0219r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200897.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200898","title":"LS from GSMA 5GJA: LS response to TCCA on Public Safety","source":"GSMA 5GJA","contact":"Mari Melander","contact-id":37233,"tdoctype":"LS in","for":"Information","abstract":"Overall Description: GSMA 5GJA thanks TCCA for their LS response 'LS on Generic Slice Template with Public Safety Feedback' and appreciate the detail review of GST Baseline v0.16. GSMA 5GJA would like to inform TCCA about the latest GSMA PRD NG.116 'Generic Network Slice Template' v3.0 that is available on this link: https:\/\/www.gsma.com\/newsroom\/wp-content\/uploads\/\/NG.116-v3.0.pdf Response from 5GJA: ACTION 01: TCCA asks GSMA kindly to take the above information as well as the feedback provided with the revised document together with the cross-reference table into consideration. [GSMA 5GJA]: GSMA has published PRD NG.116 v3.0 and the link can be found in the Overall Description section. GSMA 5GJA has reviewed all comments provided in the document 'GST Baseline v0.16 v200310 cPublicSafety.docx' and is working on adding new attributes based on the requirement from TCCA. PRD NG.116 contains a list of NESTs that contains the minimum set of attributes needed to characterise a specific service\/slice. GSMA 5GJA would like to add a NEST for public safety once all values will be provided and agreed between GSMA 5GJA and TCCA. ACTION 02: TCCA asks GSMA kindly to respond to the clarification's requests \/ questions provided in the revised document. [GSMA 5GJA]: Some of the attributes were removed or modified and are not part of published NG.116. ACTION 03: TCCA asks GSMA kindly to inform TCCA about the next process steps and how TCCA could be part of it. [GSMA 5GJA]: GSMA 5GJA has reviewed comments and suggestions from TCCA and is working on implementing changes into the version of the document. We have prepared a draft version of NEST for public safety with some of the values provided by TCCA. The next step would be to review the draft NEST and provide missing information.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TCCA","Cc":"TSG SA, SA WG1, SA WG2, SA WG3, SA WG5, RAN WG6, RAN WG3","lsoriginalls":"5GJA14_121r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200898.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200899","title":"LS from NGMN Alliance Project P1: NGMN 5G End-to-End Architecture Framework (Phase-3)","source":"NGMN Alliance Project P1","contact":"Klaus Moschner","contact-id":59428,"tdoctype":"LS in","for":"Information","abstract":"Intention of the LS and required actions: NGMN is pleased to inform the recipient of this liaison statement for information sharing on the NGMN 5G End-to-End Architecture Framework (Phase-3) that includes requirements together with considerations and concepts emerging in the industry. This builds on the themes described in NGMN 5G End-to-End Architecture Framework (Phase-2) that was published in 2019 and shared subsequently. The topics of interest the NGMN 5G End-to-End Architecture Framework (Phase-3) include: The new topics and advancements of interest include: ? Autonomic Networking ? Network Data Layer ? Artificial Intelligence and Machine Learning ? Virtualization in the Radio Access Network ? Multi-access Edge Computing ? Distributed Ledger Technology ? Vertical Market ? End-to-End Security This NGMN liaison is intended for information sharing in terms of the new topics that have been introduced in the attached document.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2, SA WG5, SA WG6, TSG RAN, ETSI-MANO, ONAP","Cc":"","lsoriginalls":"201117 NGMN_liaison","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200899.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200900","title":"LS from ETSI JTC Broadcast: On ETSI TS 103 720 (5G Broadcast System for linear TV and radio services; LTE-based 5G terrestrial broadcast system)","source":"ETSI JTC Broadcast","contact":"Thomas Stockhammer","contact-id":60397,"tdoctype":"LS in","for":"Information","abstract":"JTC Broadcast would like to inform 3GPP TWG SA and RAN that draft TS 103 720 on '5G Broadcast System for linear TV and radio services; LTE-based 5G terrestrial broadcast system' has been submitted to ETSI JTC Broadcast as a final draft. The version is attached to this document. Publication is planned in December 2020. As a summary, the specification provides an implementation profile as a subset of Rel-16 3GPP specifications in order to provide a 5G Broadcast System for linear TV and radio services. In the context of this specification, JTC Broadcast has defined two 5G Broadcast Receiver categories as documented in clause 10 of the attached document. ETSI JTC Broadcast asks SA WG4 (SA WG4) to assign appropriate MBMS feature codes as documented in clause 11.9 of TS 26.346 (see also below). Currently values 27 and 28 have been used, but if 3GPP would like to provide other numbers or a reserved range for ETSI JTC Broadcast, we would be most grateful. Table 10.1-1 MBMS Feature Values for 5G Broadcast Receiver Categories MBMS Feature Value Service Capability References 27 Service that can be received by 5G Broadcast LTE-based Base receiver Clause 10.2 28 Service that can be received by 5G Broadcast LTE-based Main receiver Clause 10.3 We welcome timely feedback on this matter in order to complete our specification. Any other comments and feedback on the specification are most welcome.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG 4","Cc":"TSG SA, TSG RAN","lsoriginalls":"BROADCAST(20)000075r3","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200900.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200901","title":"LS from ETSI TC ITS: Open contribution or Review of initial Multi-Channel Operations study results, Mature Draft ETSI TR 103 439 from ETSI TC ITS - 'Intelligent Transport Systems (ITS); Multi-Channel Operation Study; Release 2'","source":"ETSI TC ITS","contact":"Niels Peter Skov Andersen","contact-id":718,"tdoctype":"LS in","for":"Information","abstract":"Draft LS from ETSI TC ITS to external SDOs e.g. 3GPP, IEEE, SAE, CEN\/ISO and ITU, European ITS interested organisations C2C-CC, 5GAA, C-ROADS and European projects ENSEMBLE, Concorda, C-ROADS's, InterCor, PROSPECT, XCYCLE, Imagine, AutoPilot, C-Mobile and SafetyCube to provide feedback on the STF 858 work realizing the Multi-Channel Operation (MCO) specifications for ITS with specific operation in the 5.9 GHz spectrum band with current focus on the MCO study mature document TR 103 439. Actions: ETSI TC ITS kindly asks the recipients to review the stable draft of TR 103 439 and to provide feedback and comments on its content. Please use the accompanying commenting form to submit your feedback and then send it to: Andrea.Lorelli@etsi.org. It is preferred to receive your feedback by the end of the year, 2020. The STF 585 expert team will review and consolidate the received comments. It is up to the team to decide if and how to incorporate received feedback into the deliverable. Upon request, STF 585 will provide feedback on the decision implemented for each of the comments.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA, IEEE, SAE V2X, C-SAE, ISO\/CEN, CITS","Cc":"","lsoriginalls":"ITS(20)040040","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200901.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200905","title":"LS from RAN WG3: Reply LS on energy efficiency","source":"RAN WG3","contact":"Angelo Centonza","contact-id":45800,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks SA WG5 for their Liaison Statement on energy efficiency. RAN WG3 confirms SA WG5's understanding that Energy Efficiency calculations for the gNB-DU are valid for cases where one gNB-CU may serve gNB-DUs at different sites. With regards to the following: 1. The existing EE KPI for NG-RAN, defined in TS 28.554, is calculated based on: a) Measuring PDCP Data Volumes (DV) at gNB-CU level, i.e. centrally, b) Measuring Energy Consumption (EC) at each site (at gNB-CU site and at each gNB-DU site), c) Collect all these measurements and calculate the EE KPI RAN WG3 would like to point out that if gNB-DUs are distributed in different sites, the metric above is not able to measure energy efficiency per site. SA WG5 also mentioned that: 2. According to our understanding of RAN WG3 TR 37.816, the EE KPI would be calculated based on: a) Measuring RLC Data Volumes for each gNB-DU of a given gNB, i.e. at each site b) Measuring Energy Consumption in the same way as in 1b) above. RAN WG3 would like to point out that the measurements in 1) and in 2), aggregated at gNB level, may not be the same because the measurement in 2) only takes into account the Energy Efficiency for each gNB-DU site. RAN WG3 has converged on the following agreements: In split gNB architecture Energy Efficiency measurements are calculated based on RLC SDU Data Volume measurements; non-split architecture is FFS Therefore, RAN WG3 would like to ask SA WG5 whether it is feasible to specify data volume reporting at RLC SDU level. RAN WG3 would also like to ask SA WG5 to evaluate whether the UL\/DL PDCP SDU Data Volume per interface measurements in clause 5.1.3.6.2.2 and clause 5.1.3.6.2.3 of TS 28.552 can be used to calculate the data volume consumed at a gNB-DU.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:25","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"RAN WG2, TSG SA","lsoriginalls":"R3-205657","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200905.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200906","title":"LS from Ericsson: Reply LS on on energy efficiency","source":"RAN WG3","contact":"Angelo Centonza","contact-id":45800,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks SA WG5 for their Reply LS on Energy Efficiency. On the basis of the reply from SA WG5 RAN WG3 has concluded that the measurement of Energy Efficiency at gNB level is sufficient and that no further enhancements to the standard are needed to achieve per gNB EE measurements. RAN WG3 therefore decided to close discussions on Energy Efficiency on the basis of the fact that all required measurement are already specified.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10140,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:26","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"RAN WG2, TSG SA","lsoriginalls":"R3-207014","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200906.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200907","title":"LS from RAN WG3: LS Reply on HO to congested cells","source":"RAN WG3","contact":"Yazid Lyazidi","contact-id":78235,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks TSG SA for their LS on HO to congested cells. RAN WG3 has reached the conclusion that the potential issue raised by some companies in the TSG SA LS can be mitigated by the current NR mechanisms in RAN (including the support for e.g. slicing) and by proper implementation of admission control; this may include setting a less demanding (but still appropriate for the service, if possible) AQP.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:26","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG SA","lsoriginalls":"R3-207182","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200907.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200908","title":"LS from SA WG4: LS reply on QoE Measurement Collection","source":"SA WG4","contact":"Gunnar Heikkil\u00e4","contact-id":31393,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 thanks SA WG5 for the LS on QoE Measurement Collection. In the LS, SA WG5 asks RAN WG2, RAN WG3 and SA WG4 to: - Implement the QoE Reference Id both inside and outside of the reporting container. - Implement temporary stop and restart of reporting. It is considered vital that QoE data is captured during time periods of RAN overload. However, there can be many consumers that frequently collects QoE data from many UEs. To not contribute to the RAN overload, the QMC reporting should be able to be temporarily stopped and restarted. As SA WG4 earlier informed (in our LS reply S4-200962), the QoE Reference Id has already been implemented in TS 26.114 and TS 26.247 in Rel-16. Regarding temporary stop and restart, SA WG4 agrees that this seems to be a useful functionality to handle temporary RAN overload. However, as we also stated in the above reply, SA WG4 believes that there should be no need for involving the application in this scenario. The temporary stop and restart is a generic service-agnostic functionality which can be handled directly at RAN level in the UE, whenever any temporary RAN overload is seen. SA WG4 thus decided to not implement this functionality at the application level.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5, RAN WG2, RAN WG3","Cc":"TSG SA, TSG RAN","lsoriginalls":"S4-201600","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200908.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200909","title":"LS from SA WG4: Reply LS On ETSI TS 103 720 (5G Broadcast System for linear TV and radio services; LTE-based 5G terrestrial broadcast system)","source":"SA WG4","contact":"Thomas Stockhammer","contact-id":60397,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 thanks ETSI JTC Broadcast for the LS on ETSI TS 103 720 (5G Broadcast System for linear TV and radio services; LTE-based 5G terrestrial broadcast system). SA WG4 has agreed a CR as attached (S4-201605) to TS 26.346. This CR should address your request. The CR will be sent to SA plenary for approval in December 2020. Should you have any more questions or comments, please contact SA WG4 on this matter.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI JTC Broadcast","Cc":"TSG SA, TSG RAN","lsoriginalls":"S4-201606","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200909.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200910","title":"LS from SA WG5: LS on QoE Measurement Collection","source":"SA WG5","contact":"Robert Petersen","contact-id":14104,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thank SA WG4 and RAN 2 for the LSs S4-200962 and R2-2005778. It is essential that handover is supported for QoE measurements. Without the WithinArea indication being implemented, the requirement to perform QoE Measurement Collection (QMC) in a specified area cannot be met. This is an essential requirement in Rel-16. The requirement is specified in TS 28.404 requirement REQ-EUSPC-CON-1. It is also specified in TS 26.114 clause 16.3.1 \/\/\/CellList. In TS 26.247 it is specified in clause 10.5 as LocationFilter. There is also the requirement that the measurements shall continue until the application session stops even if the UE goes outside the specified area. The requirement is mentioned in TS 26.247 clause 10.1 and in TS 26.114 clause 16.3. As there will be assurance and other automated functions using the QMC mechanism in 5G in Rel-17, the functionality to provide QoE Reference both inside and outside the container to enable multiple simultaneous measurements and the temporary stop\/restart QMCs are needed: - As multiple assurance and automation functions may need to have different QoE data from the same UE, multiple simultaneous QMCs from each UE is needed. - When multiple QMCs are ordered by different consumers, the reported data needs to be sent to different consumers. The base station needs to have a mapping of the QoE Reference and the consumer address. The base station should not need to open the report container and decode the data to find the QoE Reference. - It is considered vital that QoE data is captured during time periods of RAN overload. However, there can be many consumers that frequently collects QoE data from many UEs. To not contribute to the RAN overload, the QMC reporting should be able to be temporarily stopped and restarted.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, SA WG4","Cc":"TSG SA, TSG RAN","lsoriginalls":"S5-205347","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200910.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200911","title":"LS from SA WG5: Reply LS on TM Forum implementation experiences 3GPP NRM Models","source":"SA WG5","contact":"Lan Zou","contact-id":35534,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks TM Forum for their LS reply on TM Forum implementation experiences on 3GPP NRM Models. SA WG5 would like to inform TM Forum that 3GPP has adopted a Service Based Management Architecture (SBMA) for 5G networks, and the corresponding management services are specified in Rel-16. For an overview of all SA WG5's 5G related specifications, please refer to 3GPP TS (Technical Specification - normative) 32.103 section 11. SA WG5 would like to provide the following feedback: ? Regarding the modelling work, we would like to get more detailed information on the concrete impact to TS 28.620, TS 32.107. A list of issues and concrete examples would be helpful to better understand the potential gaps. ? For the network slicing models which are related to GSMA GST, SA WG5 has finalized the discussion for TR (Technical Report - Non normative) 28.805. The continuation of related standardization work is captured in TS 28.541 which includes the enhancement of 5G NR NRM, 5GC NRM and network slice NRM. And for network slice models, we have started the alignment with GSMA GST 3.0 from Rel-17. SA WG5 agrees that the cooperation with TMF is important and elaborated cooperation examples would benefit the industry. We have regular SA WG5 OAM rapporteur calls planned 15:00 CET~17:00 CET on Oct.29th, Nov. 5th and Nov. 12th to discuss various topics before our November meeting SA WG5#134e (16-25 Nov.2020). We would be happy to use one of those time slots for a joint call with TM Forum to discuss the details of this LS exchange.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10180,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:26","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TM Forum","Cc":"TSG SA","lsoriginalls":"S5-205348","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200911.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200912","title":"LS from SA WG5: Reply LS on energy efficiency","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks RAN WG3 for their LS reply on energy efficiency and would like to provide the following feedback: 1. With regard to the following (excerpt from R3-205657): ?RAN WG3 would like to point out that if gNB-DUs are distributed in different sites, the metric above is not able to measure energy efficiency per site.' ? In Release 16, SA WG5 did not aim to define per RAN site EE KPI. Instead, SA WG5 aimed at defining per gNB EE KPI, as per ETSI ES 203 228. 2. With regard to the following (excerpt from R3-205657): ?RAN WG3 would like to point out that the measurements in 1) and in 2), aggregated at gNB level, may not be the same because the measurement in 2) only takes into account the Energy Efficiency for each gNB-DU site.' ? SA WG5 agrees with this analysis. 3. With regard to the following (excerpt from R3-205657): ?RAN WG3 has converged on the following agreements: In split gNB architecture Energy Efficiency measurements are calculated based on RLC SDU Data Volume measurements; non-split architecture is FFS Therefore, RAN WG3 would like to ask SA WG5 whether it is feasible to specify data volume reporting at RLC SDU level. ' ? SA WG5 currently has no plan to define EE KPI per site either in its Rel-16 work item EE_5G or in its Rel-17 work item EE5GPLUS, therefore so far SA WG5 does not see the need to specify the performance measurements related to RLC SDU Data Volume for the EE KPI per gNB. SA WG5 thinks it's not within 3GPP scope to define any site EE KPI, as sites can be composed of various types of 'equipment', incl. belonging to the mobile network, fixed network, site equipment, edge computing, etc. 4. With regard to the following (excerpt from R3-205657): ?RAN WG3 would also like to ask SA WG5 to evaluate whether the UL\/DL PDCP SDU Data Volume per interface measurements in clause 5.1.3.6.2.2 and clause 5.1.3.6.2.3 of TS 28.552 can be used to calculate the data volume consumed at a gNB-DU.' ? The UL\/DL PDCP SDU Data Volume per interface measurements in clause 5.1.3.6.2.2 and clause 5.1.3.6.2.3 of TS 28.552 are measured at the gNB-CU-UP level, i.e. with no per gNB-DU split. Consequently, they can't be used to calculate the data volume consumed at a gNB-DU.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-27 11:05:26","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2, TSG SA","lsoriginalls":"S5-205357","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200912.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200913","title":"LS from SA WG2: Reply LS on AUSF\/UDM discovery based on SUCI information","source":"SA WG2","contact":"Jiang Yi","contact-id":56358,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 thanks CT WG4 for their LS. SA WG2 acknowledges the issue raised by CT WG4 and agrees the principle suggested in the incoming LS. SA WG2 has discussed the solution and endorsed the attached Rel-17 draft CRs allowing Home Network Public Key identifier as additional SUCI information to be used for AUSF\/UDM discovery.","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-30 15:47:24","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"TSG CT, TSG SA, SA WG3","lsoriginalls":"S2-2009207","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200913.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200914","title":"LS from SA WG2: LS on ATSSS Phase 2 conclusions","source":"SA WG2","contact":"Apostolis Salkintzis","contact-id":66021,"tdoctype":"LS in","for":"Information","abstract":"Further to our previous communication regarding the ATSSS Phase 2 requirements (see initial request from 3GPP at https:\/\/datatracker.ietf.org\/liaison\/1697\/ and the IETF reply at https:\/\/datatracker.ietf.org\/liaison\/1701\/), the SA WG2 would like to inform the QUIC WG of the following: {. . .}","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10200,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-11-30 15:47:24","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IETF QUIC Working Group","Cc":"TSG SA, The IETF chair@ietf.org","lsoriginalls":"S2-2009400","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200914.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200915","title":"LS from SA WG5: LS on Network Slice EE KPIs","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 (Telecom Management) has initiated its Rel-17 work item on enhancements of EE for 5G networks. One of the key objectives of this work item is the definition of EE KPIs for 3GPP standardized network slice types. SA WG5 would like to inform of the following achievements: during our SA WG5 e-meeting No. 134, the attached CR (S5-206370) has been agreed by SA WG5 (pending SA Plenary approval in December), to introduce new EE KPI definitions for network slices in TS 28.554. {. . .}","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10210,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-12-04 15:39:01","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI EE EEPS, ITUT Q6\/5","Cc":"TSG SA","lsoriginalls":"S5-206446","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200915.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200916","title":"LS from SA WG5: LS on Network Slice EE KPIs","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599,"tdoctype":"LS in","for":"Information","abstract":"TSG WG5 (Telecom Management) has initiated its Rel-17 work item on enhancements of EE for 5G networks. One of the key objectives of this work item is the definition of EE KPIs for 3GPP standardized network slice types. SA WG5 would like to inform of the following achievements: during our SA WG5 e-meeting No. 134, the attached CR (S5-206370) has been agreed by SA WG5 (pending SA Plenary approval in December), to introduce new EE KPI definitions for network slices in TS 28.554. {. . .}","secretary_remarks":"CC#1: Block Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS\u2019s - proposed to note","tdoc_agenda_sort_order":10220,"status":"noted","reservation_date":"2020-11-26 08:38:00","uploaded":"2020-12-04 15:39:01","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GJA","Cc":"TSG SA","lsoriginalls":"S5-206447","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_90E_Electronic\/Docs\/SP-200916.zip","group":"SP","meeting":"SP-90-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]