[{"name":"SP-210807","title":"LS from ITU-R WP5D: LIAISON STATEMENT TO GCS PROPONENTS AND TRANSPOSING ORGANIZATIONS ON THE PROVISION OF TRANSPOSITION REFERENCES AND CERTIFICATION C FOR DRAFT REVISION 5 OF RECOMMENDATION ITU-R M.2012","source":"ITU-R WP5D","contact":"Uwe Loewenstein","contact-id":11941,"tdoctype":"LS in","for":"Action","abstract":"Introduction: Working Party (WP) 5D thanks the relevant GCS Proponents for their successful work in regards to completion of the milestone identified by Item 8 of Table 1 for the draft Revision 5 of Recommendation ITU-R M.2012 'Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-Advanced (IMT-Advanced)' following the process in Document IMT-ADV\/31(Rev.1), 'Schedule for the Revision 5 Update of Recommendation ITU-R M.2012'. WP 5D wishes to inform the GCS Proponents and the Transposing Organizations that during its 38th e-meeting (7-18 June 2021) the specific technology updates for the draft Revision 5 of Rec. ITU R M.2012 (not including the detailed transposition references) were finalized and provisionally agreed. Request to supply transpositions references: WP 5D draws the attention of the Transposing Organizations of LTE-Advanced to the need for each Transposing Organization to provide the relevant transposition references for Section 2 of Annex 1 by the requested firm deadline of 1 September 2021. Request to supply Certification C: Each identified Transposing Organization is required to provide to ITU-R, the Certification C by 1 September 2021. The Certification C is outlined in Document IMT-ADV\/25(Rev.2) 'Procedure for the development of draft Revisions of Recommendation ITU-R M.2012' and Document IMT ADV\/24 (Rev.3) 'Process and The Use Of Global Core Specification (GCS), References And Related Certifications In Conjunction With Recommendation ITU-R M.2012'. Procedurally, the Certification C from each Transposing Organization should be directed to the Counsellor for ITU R Study Group 5 and not provided as inputs to WP 5D. The Counsellor will prepare as an input to the 39th meeting of WP 5D meeting a summary statement regarding the receipt of the Certification C documents. Completion of relevant business matters: As indicated, there is also the consequential step of, as necessary, the completion of relevant business matters by 1 September 2021 and the indication of compliance with ITU policy on IPR, as appropriate. These matters should be directly addressed between the Transposing Organization and the ITU as appropriate via the contact point of the Counsellor for Study Group 5. Closure of the draft Revision 5 with references in Working Party 5D: At its 39th e-meeting (4-15 October 2021), WP 5D intends to review and seek final agreement of the full consolidated draft Revision 5 of Rec. ITU-R M.2012 including the transposition references. It will then be forwarded to ITU-R Study Group 5 for consideration at its November 2021 meeting in accordance with the ITU-R approval process in Resolution ITU-R 1-8, especially \u00a7 A.2.6.2. WP 5D looks forward to the continued cooperation with the Transposing Organizations in these final steps on concluding this update of the IMT-Advanced terrestrial radio interfaces.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2021-08-03 08:09:50","uploaded":"2021-08-03 08:10:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GCS PROPONENTS AND TRANSPOSING ORGANIZATIONS","Cc":"","lsoriginalls":"5D_TD_0350_IMT-ADV","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210807.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210808","title":"LS from ITU-R WP5D: LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS ENGAGED IN RECOMMENDATION ITU-R M.2012 ON THE SCHEDULE FOR UPDATING RECOMMENDATION ITU-R M.2012 TO REVISION 6","source":"ITU-R WP5D","contact":"Uwe Loewenstein","contact-id":11941,"tdoctype":"LS in","for":"Information","abstract":"Working Party (WP) 5D thanks the relevant External Organizations for their on-going work in regard to the Revision 5 of Recommendation ITU-R M.2012 - Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-Advanced (IMT-Advanced) which will be available as a published ITU-R Recommendation. As formally announced in ITU-R Circular Letter 5\/LCCE\/93, WP 5D wishes to inform the relevant External Organizations that it is commencing the cycle for the development of the Revision 6 of Recommendation ITU-R M.2012 and provides a detailed schedule for Revision 6 of Recommendation ITU R M.2012. Background: This liaison provides guidance on the revision procedure and the detailed step-by-step schedule to External Organizations regarding updates of the terrestrial radio interfaces in the development of Revision 6 of Recommendation ITU-R M.2012 - Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-Advanced (IMT-Advanced). Procedure: The procedure outlined in Document IMT-ADV\/25(Rev.2) - Procedure for the development of draft revisions of Recommendation ITU-R M.2012 applies to the development of this Revision 6. Schedule: For the Revision 6 of Recommendation ITU-R M.2012 a completion date of the WP 5D meeting #44, currently planned for June 2023, has been chosen. WP 5D announces that the first formal meeting in the meeting cycle ('Meeting Y') of the development of Revision 6 of Recommendation ITU-R M.2012 will be WP 5D meeting #40, which is scheduled for 7-18 February 2022. As explained in the Circular Letter, it should be noted that new technology proposals for IMT Advanced will not be accepted in the updating of Recommendation ITU-R M.2012, applicable on a going forward basis beginning with this Revision 6. The detailed timeline for the Revision 6 of Recommendation ITU-R M.2012 which accommodates the currently planned\/anticipated schedule of meetings for WP 5D and Study Group 5 through the 2021 and 2023 time frame and some milestone activities\/actions may be found in Document IMT ADV\/32 - Schedule for Revision 6 of Recommendation ITU-R M.2012. The dates in Document IMT-ADV\/32 were developed considering not only the WP 5D and Study Group 5 dates but also with a view towards coordinating with the understood planned dates of the relevant External Organizations to the extent they were known . Some adjustment of these dates might be required to accommodate availability of facilities at specific venues in conjunction with the scheduling of the ITU-R WP 5D and Study Group 5 meetings. Every effort will be made to keep these dates as listed. As appropriate Document IMT-ADV\/32 will be updated to accommodate such date changes and further correspondence with the External Organization could be forthcoming throughout the update cycle as warranted by the circumstances. External Organizations are encouraged to consult the ITU-R IMT-Advanced web page (http:\/\/www.itu.int\/ITU-R\/go\/rsg5-imt-advanced\/) which may be updated dynamically to provide additional information. WP 5D looks forward to the continued cooperation with the External Organizations in the on-going work on the IMT-Advanced terrestrial radio interfaces.","secretary_remarks":"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-08-03 08:09:50","uploaded":"2021-08-03 08:10:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC","Cc":"","lsoriginalls":"5D_TD_0356_IMT-ADV","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210808.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210809","title":"LS from NGMN Alliance Project '5G TDD Uplink': NGMN Liaison Statement to 3GPP Plenary on 5G NR TDD Uplink Throughput","source":"NGMN Alliance Project '5G TDD Uplink'","contact":"Klaus Moschner","contact-id":59428,"tdoctype":"LS in","for":"Information","abstract":"Intention of the LS and required actions: In 2021 NGMN Alliance started a new project concerned about finding solutions for improving the 5G TDD Uplink in particular for use cases that are relevant for the vertical industries. This project studies the following - Deploying 5G TDD networks in a multi-operator context requires synchronized operation of adjacent networks and, in particular, the adoption among operators of a compatible frame structure to avoid any BS-BS and MS-MS interference and allow coexistence without the need for guard bands or additional filters supporting efficient spectrum usage. - To avoid potential interference situations and ensure an efficient spectrum usage, regulatory conditions are attached to spectrum rights. In Europe for example, common TDD frame structures at national level are defined for the 3400 - 3800 MHz frequency band (Band n78). Current frame structures consist of 8 timeslots in the downlink (DL) and 2 timeslots in the uplink (UL) which allows a maximum of 180 Mbit\/s peak throughput under optimum conditions in the uplink (with 100 MHz spectrum bandwidth, 2x2 UL MIMO and without UL carrier aggregation) and a minimum latency of 2 - 4 ms one-way in the RAN. The obligation to adopt the common national TDD frame structure can possibly be relaxed for local\/regional licensing, while obligations to avoid interference remain in place. - On the other hand, there's the need to account for licensees' commercial service needs and the great variety of 5G use cases. - In fact, when working with industries (e. g. manufacturing, entertainment, news production, autonomous vehicles), a much higher uplink capacity is often required. For example, in SA WG1 22.261 there are requirements for cloud rendering and virtual reality which range from 100Mbps up to perhaps Gbps per user in some potential cases; even at the lower end of this requirement support within the constraints discussed in the previous paragraph would be limited to a very small number of users. In other examples from the automotive sector, extracting data from cars on a test track, it would need to be in excess of 600 Mbit\/s. Other use cases require UL capacity, which exceeds the current capabilities, e.g. video surveillance with upload from multiple HD cameras. - Furthermore, among the frame structures that are defined for the NR by the 3GPP, currently only a limited subset has been realized by base station vendors, chipset vendors and device vendors. For both bands, n78 (3.5GHz) and n258 (26GHz), NGMN will appreciate, if base station vendors, chipset vendors and device vendors will also make available frame structures that provide a better balance between uplink and downlink throughput. - The scope of this NGMN project is to drive the study of both technical and regulatory solutions for lifting the current limitations to 5G NR uplink capacity, especially in the 3 400 - 3 800 MHz band and including consideration of the 26 GHz band, as appropriate. In addition, the project will correspondingly lobby with regulators as well as chipset and device vendors to represent the service capabilities drawbacks of current implementation limitations and work and act together to achieve the needed implementation flexibility for a more suitable distribution between uplink and downlink for Vertical Industries use cases. Additionally, alternative solutions will be studied together with the partners of the NGMN. Addressing TSG RAN Plenary: NGMN is looking for solutions to the 5G NR uplink challenge for the vertical industries, that are perceiving limitations in realizing their use cases as soon as their uplink requirements are in excess of the currently possible uplink throughput and response times in the public spectrum domain as allowed by current national regulations. NGMN will highly appreciate if 3GPP, as the relevant SDO working on such topic, continues to look for and specify solutions at the 5G NR interface, supporting high throughput uplink and low latenc","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2021-08-03 08:09:50","uploaded":"2021-08-03 08:10:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG SA, SA WG1","lsoriginalls":"210617 LS_from NGMN 5G TDD UL to RAN","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210809.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210810","title":"LS from ETSI TC ITS: Open contribution or Review of the general C-ITS architecture (EN 302 665) update related to MCO (Multi-Channel Operation), stable draft ETSI TS 103 696 from ETSI TC ITS - 'Intelligent Transport Systems (ITS); C-ITS architecture; Mult","source":"ETSI TC ITS","contact":"Paul Spaanderman","contact-id":86146,"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.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2021-08-03 08:09:50","uploaded":"2021-08-03 08:10:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA, IEEE, SAE V2X, ISO","Cc":"","lsoriginalls":"ITS(21)043023r3","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210810.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210811","title":"LS from MulteFire Alliance: LS on MulteFire PLMN-ID","source":"MulteFire Alliance","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Overall description: MFA would like to thank TSG SA for the reply to MFA liaison statement regarding the use of MFA PLMNID in 5G NR private networks. [TSG SA answer]: It is not within 3GPP mandate to give consent (or deny) to MFA or other organizations to use their PLMN-ID on 5G NR private networks. However, TSG SA can confirm that in current 3GPP specifications, there is no restriction to use any PLMN-ID for 5G NR private network using SNPN as defined in TS 23.501. The description and limitations for SNPNs are described in TS 23.501 and other related 3GPP specifications. Technically the MFA PLMN ID as one option can be broadcasted by 5G NR private networks, using SNPN, without changes to existing 3GPP specifications. 3GPP specification also allow other PLMN-ID options for 5G NR private network, using SNPN. In that respect : MFA acknowledges that according to the 3GPP reply that MFA PLMN ID can be broadcasted by 5G NR private networks. MFA would like to notify TSG SA, that since 3GPP decided to include standalone operation of NR in the unlicensed bands, MFA does not currently consider to work further on the standardization of NR for unlicensed bands. MFA can also confirm that it is dedicated to propagate 5G NR private networks as specified by 3GPP by helping to create a global market for them. Action: MFA would like to reply to TSG SA LS as above.","secretary_remarks":"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-08-03 08:09:50","uploaded":"2021-08-03 08:10:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG RAN, TSG CT","lsoriginalls":"MF LS to 3GPP June 2021.","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210811.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210812","title":"LS from TM Forum: Multi-SDO Autonomous Networks (AN) Formal Liaison: Request for review of Letter of Intent and report on the 21st of June Formal meeting Ref AN-SDO2021-08","source":"TM Forum","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Letter of Intent Review Request The M-SDO AN, Formal MSDO meeting#7 on 21st June 2021, reviewed a proposal for an MoU for the Autonomous Networks Multi-SDO Initiative. The objective is to formally establish those who are willing to contribute and be referenced in joint press releases. The meeting agreed to: 1. Rename the proposal as a Letter of Intent - a revised version is attached (which also addresses some concerns about the length of the opportunities list being too ambitious). 2. Request each participating SDO to provide a preliminary response on two questions: a. Do you have comments on the attached Letter of Intent proposal? b. Indicate when your SDO could formally agree to the Letter of Intent and provide some indication of your internal process that would need to be satisfied (will depend on each SDO internal procedures). We would be grateful for a response with the timeframe suggested at the workshop, I.e., within two weeks, 5th July 2021. At the meeting, we also reviewed a specific initial joint work proposal - WP02 Landscape and Roadmap for Autonomous Networks (Operations Focus) - as a practical example of work to perform under the Letter of Intent. Results of 21st June 2021 M-SDO AN Formal Liaison Meeting #7 The notes of this meeting are attached and are also available on the shared workspace at: - 2021-06-21 M-SDO AN Formal Liaison Meeting notes #7 We identified several actions, the main points being: - To set up a joint working paper area to address WP02 Landscape and Roadmap for Autonomous Networks (Operations Focus). - To schedule a discussion of a proposal for a joint paper based on the IEEE WP04 proposal: Overarching Blueprint of Common Operational Principles of Autonomic\/Autonomous Networks. - The meeting also identified that the meeting schedule that we agreed on has conflicts with a SA WG5 meeting in August. We decided to reschedule meetings as follows: - August 23rd meeting rescheduled to the 16th of August 2021. - August 30th meeting rescheduled to 6th of Sept 2021. - A copy of the revised meeting schedule for the Formal SDO meetings is attached in Annex B. We also identified a need to address the IPR arrangements for MSDO Joint White Papers. TM Forum took an Action: to come back to the MSDO Formal Group with an IPR proposal for discussion. Regards, Cecilia Ortega Lagos TM Forum","secretary_remarks":"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-08-03 08:09:50","uploaded":"2021-08-03 08:11:27","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI, GSMA, ONAP, NGNM, 3GPP, CCSA, IEEE, IETF, ITU-T","Cc":"","lsoriginalls":"MSDO_AN_Liasion LoI review 20210624.","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210812.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210813","title":"LS from ITU-R WP5D: LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS ON THE SCHEDULE FOR UPDATING RECOMMENDATION ITU-R M.2150 TO REVISION 'AFTER YEAR 2021","source":"ITU-R WP5D","contact":"Uwe Loewenstein","contact-id":11941,"tdoctype":"LS in","for":"Information","abstract":"Introduction: Working Party (WP) 5D thanks the relevant External Organizations for their work regarding Recommendation ITU-R M.2150 - 'Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-2020 (IMT-2020)'. As formally announced in ITU-R Circular Letter 5\/LCCE\/94, WP 5D wishes to inform the relevant External Organizations that it is commencing the cycle for the development of the Revision 'After Year 2021' of Recommendation ITU-R M.2150 and provides a detailed schedule for Revision 'After Year 2021' of Recommendation ITU R M.2150. Background: This liaison provides guidance on the revision procedure and the detailed step-by-step schedule to External Organizations regarding updates of the terrestrial radio interfaces in the development of Revision 'After Year 2021' of Recommendation ITU-R M.2150 'Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-2020 (IMT-2020)'. Procedure: The procedure outlined in document IMT-2020\/57 Procedure for the development of draft revisions of Recommendation ITU-R M.2150 applies to the development of this Revision 'After Year 2021'. Schedule: For the Revision 'After Year 2021' of Recommendation ITU-R M.2150, a completion date of the WP 5D meeting #44, currently planned for June 2023, has been chosen. WP 5D announces that the first formal meeting in the meeting cycle ('Meeting Z') of the development of Revision 'After Year 2021' of Recommendation ITU-R M.2150 will be WP 5D meeting #40, which is scheduled for 7-18 February 2022. While the deadline for receipt of 'complete' new candidate technology submissions is established in the schedule as WP 5D meeting No. 40, proponents of new candidate technology proposals are strongly encouraged to notify WP 5D at the meeting No. 39 (October 2021) of their intentions to submit so that the process, including the invitation for the registration of IEGs, could proceed in due time to support the downstream process timings. The detailed timeline for the Revision 'After Year 2021' of Recommendation ITU-R M.2150 which accommodates the currently planned\/anticipated schedule of meetings for WP 5D and Study Group 5 through the 2021 and 2023 time frame and some milestone activities\/actions may be found in Document IMT-2020\/58 Schedule for Revision 'After Year 2021' of Recommendation ITU-R M.2150. For convenience it is also enclosed to this liaison as Attachment. The dates in Document IMT-2020\/58 were developed considering not only the WP 5D and Study Group 5 dates but also with a view towards coordinating with the understood planned dates of the relevant External Organizations to the extent they were known . Some adjustment of these dates might be required to accommodate availability of facilities at specific venues in conjunction with the scheduling of the ITU-R WP 5D and Study Group 5 meetings. Every effort will be made to keep these dates as listed. As appropriate, Document IMT-2020\/58 may be updated to accommodate such date changes and further correspondence with the External Organization could be forthcoming throughout the update cycle as warranted by the circumstances. The Radiocommunication Bureau maintains the IMT-2020 section on the web page of WP 5D which may be updated dynamically to provide additional information on the revision activities and to facilitate the development of update and new proposals and the work (if necessary) of the evaluation groups. WP 5D looks forward to the continued cooperation with the External Organizations in the on-going work on the IMT-2020 terrestrial radio interfaces.","secretary_remarks":"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-08-03 08:09:50","uploaded":"2021-08-03 08:10:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GCS Proponents and Transposing Organizations, 3GPP, IEEE","Cc":"","lsoriginalls":"R19-WP5D-210607-TD-0353!!MSW-E_rev_out.","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210813.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210814","title":"LS from ITU-R WP5D: LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS Development of 'IMT Vision for 2030 and beyond'","source":"ITU-R WP5D","contact":"Uwe Loewenstein","contact-id":11941,"tdoctype":"LS in","for":"Action","abstract":"ITU-R has previously developed Recommendation ITU-R M.1645 (IMT Vision for 2010 and beyond) and then Recommendation ITU-R M.2083 (IMT Vision for 2020 and beyond). From the 37th meeting in March 2021, ITU-R Working Party 5D (WP 5D) has started to develop a draft new Recommendation on IMT Vision for 2030 and beyond. This Recommendation can be helpful to drive the industries and administrations to encourage further development of IMT for 2030 and beyond. This Recommendation will define the framework and overall objectives of the future development of IMT for 2030 and beyond, including the role that IMT could play to better serve the needs of the future society, for both developed and developing countries. For the development of this draft new Recommendation, WP 5D would like to invite the views of External Organizations on the IMT Vision for 2030 and beyond, including but not limited to, user and application trends, evolution of IMT, usage scenario, capabilities and framework and objectives. External Organizations are invited to submit material preferably to the 39th meeting of WP 5D but no later than the 41st meeting of WP 5D, as appropriate. Please check the WP 5D website for latest information of the coming WP 5D meetings: http:\/\/www.itu.int\/ITU-R\/go\/rwp5d. Working Party 5D looks forward to receiving views on the new Recommendation on IMT Vision for 2030 and beyond. WP 5D looks further forward to collaborating with External Organizations on this matter.","secretary_remarks":"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-08-03 08:09:50","uploaded":"2021-08-03 08:10:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXTERNAL ORGANIZATIONS","Cc":"","lsoriginalls":"R19-WP5D-210607-TD-0383!R1!MSW-E","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210814.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210815","title":"LS from ITU-T SG13: LS on the new work item ITU-T Y.NGNe-IBN-arch: 'Functional architecture of NGN evolution by adoption of Intent-Based Network'","source":"ITU-T SG13","contact":"Yuan Zhang","contact-id":85622,"tdoctype":"LS in","for":"Information","abstract":"During the ITU-T SG13 virtual meeting (5-16 July 2021) Q2\/13 (Next-generation network (NGN) evolution with innovative technologies including software-defined networking (SDN) and network function virtualization (NFV)) created a new work item on 'Functional architecture of NGN evolution by adoption of Intent-Based Network' (Y.NGNe-IBN-arch: TD621\/WP3). ITU-T Y.NGNe-IBN-arch aims to provide the general functional architecture of NGNe by adoption of the Intent-Based Network, specifies its functional entities and defines the detailed functionalities of these functional entities, and aims to continue the research of the Intent-Based Network especially concerning the implementation and realization in NGNe. ITU-T Q2\/13 would like to thank you for your attention, feedback and cooperation on this topic. In addition, please find below the A.1 justification form for the new work item Y.NGNe-IBN-arch.","secretary_remarks":"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-08-06 11:44:22","uploaded":"2021-08-06 11:48:14","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IETF, 3GPP","Cc":"","lsoriginalls":"SG13-LS221","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210815.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210816","title":"LS from 5GAA WG4: LS on MCO TS 103 696","source":"5GAA WG4","contact":"Leonardo Gomes Baltar","contact-id":86896,"tdoctype":"LS in","for":"Information","abstract":"5GAA thanks ETSI TC ITS for the invitation to comment on draft TS 103 696. 5GAA would like to share two high-level comments as follows. First, 5GAA would like to ask if all the content in clause 5 'Essentials' are essential of MCO architecture. For example, it is difficult to find the essentialness and relevance to MCO concept from the clauses 5.4.2 'C-ITS hybrid communication architecture' and 5.4.3 'C-ITS time and location in the C-ITS constellations'. Second, 5GAA would also like to ask if the opening topics of clause 7 on 'layers and planes', and 'SAPs and interfaces' are focused on MCO extensions, or general issues of Release-1 architecture. If the latter is the case, we would like to ask if it is in work scope of the STF 585.","secretary_remarks":"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-08-09 05:34:03","uploaded":"2021-08-09 05:34:34","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TC ITS, ETSI STF585","Cc":"TSG RAN, TSG SA, SAE V2X; C-SAE; ITU CITS","lsoriginalls":"5GAA_S-210137","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210816.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210817","title":"LS from GSMA NG: New Whitepaper: 'E2E Network Slicing Architecture'","source":"GSMA NG","contact":"Toshiyasu Wakayama","contact-id":57558,"tdoctype":"LS in","for":"Information","abstract":"INTRODUCTION: The GSMA, one of the Market Representation Partners of 3GPP, have a project concerning End to end Network Slicing under the Network Group (NG). The project aims to identify potential gaps in standards and input recommendations to the related organisations toward the realisation of Network Slicing architecture designed from an End-to-End (E2E) perspective. This E2E notion means network slicing capabilities need to be integrated across the different domains (e.g., device, access network, core network, transport network and network management system), so that Service Level Agreement based on customers' requirements can be guaranteed. The GSMA NG would like to inform related organisations that the GSMA Whitepaper NG.127 'E2E Network Slicing Architecture' has been published on gsma.com at : https:\/\/www.gsma.com\/newsroom\/resources\/ng-127-e2e-network-slicing-architecture-v1-0\/ . The intention of this whitepaper is to show guidance of the entire industry ecosystem; for operators, vendors and service providers to be able to consider common solutions of network slicing which have not been fully defined yet. The scope of this whitepaper is to provide the description of: 1. Blueprint of E2E Network Slicing Architecture, 2. Technology aspect, 3. Ongoing SDOs and open-source projects, which are snapshot based on current status of these standardization activities, typically activities of the 3rd Generation Partnership Project (3GPP) Release 17. Action: The GSMA NG kindly asks related organisations to take our whitepaper into consideration for their standardisation work on E2E network slicing as well as provide feedback on our whitepaper.","secretary_remarks":"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-08-16 11:45:08","uploaded":"2021-08-16 11:47:39","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN TSG SA, SA WG2, SA WG5, ...","Cc":"","lsoriginalls":"E2E-NS WP Publish LS","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210817.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210968","title":"LS from ETSI ISG IPE: Liaison from ISG IPE on IPv6 Enhanced Innovation Gap Analysis","source":"ETSI ISG IPE","contact":"Latif Ladid","contact-id":86673,"tdoctype":"LS in","for":"Information","abstract":"ISG IPE is pleased to inform you of the latest GR of ETSI ISG IPE (IPv6 Enhanced Innovation) on 'IPv6 Gap Analysis' published in August 2021. IPE expects that this could be of interest to your committee. This deliverable has the following goals: - Identify gaps of existing IPv6 standards in both ETSI and other SDOs that need to be resolved to accelerate IPv6-based innovations - Communicate the identified gaps and corresponding recommendations for improvement to suitable ETSI TCs \/ ISGs and other SDOs. The major findings of the document are: - IPv6 has made much progress in last 5 years. The 'user device - network - content' value chain is ready for the first time in history. IPv6 already represents about 45% of Internet users (Google + China statistics). - IPv6 is different from IPv4, not just by bigger address space. IPv6 has more advanced functionalities that should be considered during all stages of the IP network lifecycle: design, development, support, and maintenance. Negligence to do so may lead to a sub-optimal deployment. - It is possible to transition overlay\/services to IPv6 separately from underlay\/infrastructure. It creates the possibility to split IPv6 transition into several stages and make them more manageable. Service transition typically has higher priority than infrastructure migration because address shortage typically happens first. - IPv6 does not have critical gaps that may prevent IPv6 transition. Meanwhile, IPv6 has many standardization activities for new and advanced functionalities that are not available in IPv4. - IPv6 progress in different countries and companies is very different. Lack of IPv6 knowledge and capacity building were the main reasons for fast IPv6 adoption. - New services like 5G, Cloud, IoT, and SD-WAN raise new requirements for the networks: ubiquitous resilient connectivity, ultra-high bandwidth, deterministic quality, low latency, automation, and security. IPv6 enhanced innovations like Proactive ND, SRv6, iOAM and BIER over IPv6 are needed to meet such requirements. The conclusions are: - IPv6 is about addressing the future of the Internet. and of any organization. It is possible to postpone the IPv6 transition for many organizations, but it is not possible to avoid it. Therefore, it is better to plan for IPv6 as soon as possible to avoid unnecessary investment in IPv4. The IETF has already warned the Internet community to move to IPv6 as IPv4 will not be maintained in the future. - The move to IPv6-Only by 2025 has been launched by the US government policy in June 2021. - China has also published its single stack (IPv6-Only) policy in July 2021: https:\/\/www.theregister.com\/2021\/07\/26\/china_single_stack_ipv6_notice\/ - Section 5 analyses the typical technology challenges for IPv6 transition and concludes that IPv6 is fundamentally different from IPv4. Hence, it is important to account for the differences during the design, implementation, and support phases of the networking lifecycle. - Section 6 provides insight into the non-technical challenges. It is important to prepare the organizations, people, business processes, and tools for the transition to the new technology. - Section 7 has the overview of new technologies that are in development specifically for the requirements of new scenarios discussed in section 4. It is important to point out that IPv6 enhanced innovations discussed in section 7 do not have equivalents in IPv4. Hence, these requirements do not create the challenge for the transition from IPv4. - Following the proper guideline and best practices, IPv6 transition can be deployed almost for free. There are no general gaps that prevent this transition in any scenario. It is time to finalize the IPv6 transition plan to avoid unnecessary investments. It is key to request readiness for hardware and software at any refreshment cycle. ISG IPE invites interested parties to provide feedback.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2021-09-07 14:54:05","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TCs CABLE, CYBER, INT WG AFI, LI, MSG, SmartM2M, ETSI ISGs ENI, F5G, NFV, NIN, ZSM, ETSI Board, TSG CT, TSG SA, 3GPP PCG, oneM2M, ITU-T SG17, SG15, SG11, SG13, ITU-T SG20, ISO\/IEC JTC 1 SC6 WG7, GSMA, MEF, OMA, IEC SyC COMM, and the European Commissi","Cc":"","lsoriginalls":"IPE(21)000088","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210968.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210969","title":"LS from RAN WG2: Reply LS on Inclusive language for ANR","source":"RAN WG2","contact":"Mats Folke","contact-id":43898,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG5 for the LS on Inclusive language for ANR. RAN WG2 concludes the terminology chosen by SA WG5 differs from the terminology chosen by RAN WG2, where RAN WG2 has chosen to use the term 'exclude-list' to replace 'black-list'. RAN WG2 wonders if there would be issues if the terms are not fully aligned. RAN WG2 understands that RAN plenary (but not CT and SA plenary) appointed a contact person for cross-TSG coordination on this matter. Action: RAN WG2 asks SA and CT to consider appointing a coordinator for inclusive language to work together with the RAN coordinator for inclusive language on cross-TSG questions.","secretary_remarks":"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-09-07 14:54:05","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT, TSG SA, SA WG5","Cc":"RAN WG3, TSG RAN","lsoriginalls":"R2-2108869","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210969.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210970","title":"LS from RAN WG3: Reply LS on Inclusive Language for ANR","source":"RAN WG3","contact":"Gino Masini","contact-id":23120,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks SA WG5 for the LS on inclusive language for ANR. RAN WG3 has endorsed the attached CR, fixing ANR terminology and aligning toward RAN WG2's and RAN WG4's choice. The endorsed CR will be agreed by RAN WG3 at the end of Rel-17 according to the inclusive language way of working. RAN WG3 agrees that a common approach across WGs to align the replaced terminology seems beneficial. For your information, the attached discussion document was also discussed, and it was recommended to Specification Rapporteurs to improve alignment with other WGs where it makes sense.","secretary_remarks":"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-09-07 14:54:06","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5, RAN WG2","Cc":"TSG RAN, TSG SA, TSG CT","lsoriginalls":"R3-214289","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210970.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210971","title":"LS from RAN WG3: Response LS on PWS Support over SNPN","source":"RAN WG3","contact":"Philippe Godin","contact-id":68843,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA for the Reply LS on Support of PWS for NPN. RAN WG3 has endorsed the attached draft CR for TS 38.300, which removes the existing stage 2 restriction, from RAN WG3 point of view. RAN WG3 requests RAN WG2, as the group responsible for TS 38.300, to take this endorsement into account, and proceed as RAN WG2 sees fit (i.e. use this CR, merge or implement an equivalent RAN WG2 CR, if agreeable). RAN WG3 would also like to inform SA that no stage 3 changes have been considered essential at this point in RAN WG3 specifications. RAN WG3 may revisit this topic in rel-17 if any such changes are identified. Action: RAN WG3 respectfully requests TSG SA and RAN WG2 to take the above into account.","secretary_remarks":"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-09-07 14:54:06","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, RAN WG2","Cc":"SA WG1, SA WG2, SA WG3, TSG CT, CT WG1, TSG RAN","lsoriginalls":"R3-214402","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210971.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210972","title":"Reply LS on support of PWS over SNPN","source":"SA WG1","contact":"Edward Hall","contact-id":90585,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks CT WG1 for the LS and respond to the questions. Question-1 to SA WG1: Can an SNPN support emergency services but not support PWS, in a country where PWS is deployed? Yes; it is possible that, subject to regional or national regulatory requirements, an SNPN may support emergency services but not support PWS in a country where PWS is deployed. Question-2 to SA WG1: Is there a need for the UE to prioritize SNPNs supporting PWS over SNPNs not supporting PWS for SNPN selection: - when the UE is in limited service state and SNPN-1 supporting PWS and SNPN-2 not supporting PWS, are available; or - when the UE is not in limited service state, SNPN-1 supporting PWS and SNPN-2 not supporting PWS are available, and SNPN-1 and SNPN-2 are otherwise of the same priority for SNPN selection by the UE? No; there is no need for a UE to prioritise SNPNs supporting PWS over SNPNs not supporting PWS for SNPN selection in either scenario shown in Question 2.","secretary_remarks":"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-09-07 14:54:06","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"TSG RAN, TSG CT, TSG SA, RAN WG3, RAN WG2, SA WG3, SA WG2","lsoriginalls":"S1-213120","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210972.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210973","title":"LS from SA WG1: LS on Non-territorial emergency or distress call","source":"SA WG1","contact":"Erik Guttman","contact-id":18782,"tdoctype":"LS in","for":"Information","abstract":"3GPP has undertaken a study in the group SA WG1 to consider the regulatory implications of extra-territorial communications for telecommunications standards. 3GPP standards have regulatory requirements, specifically services such as emergency call, public warning system and lawful interception. In the course of this study, SA WG1 has considered how these regulatory services apply when a user and their user equipment is located beyond any territory, as a passenger in an aircraft that is not over sovereign territory. It is possible for a passenger with a mobile telecommunications terminal to access network communications. We would be grateful if you could provide or indicate references to guidelines or recommendations whether and how to handle emergency calls made by passengers in aircraft using telecommunications equipment. SA WG1 seeks to conclude their recommendations on regulatory aspects of non-terrestrial telecommunication at their November meeting this year. Please, if it is possible, provide feedback so that we can take it into account at that meeting.","secretary_remarks":"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-09-07 15:09:52","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ICAO","Cc":"TSG SA","lsoriginalls":"S1-213210","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210973.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210974","title":"Reply LS on UAS terminology alignment","source":"SA WG1","contact":"Qun Wei","contact-id":75001,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 thanks TSG SA for the LS requesting the alignment of UAS terminology in Rel-17 specifications of TS 22.125 about the change of term of 'Unmanned' to 'Uncrewed'. SA WG1 has agreed the corresponding alignment as attached CR. Action: SA WG1 respectfully asks TSG SA to take the above into consideration.","secretary_remarks":"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-09-07 15:09:52","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, SA WG6, SA WG3","lsoriginalls":"S1-213256","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210974.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210976","title":"LS from SA WG2: Rely LS to Liaison Statement on 5G & Wi-Fi RAN Convergence","source":"SA WG2","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 thanks WBA for the information on the 5G & Wi-Fi RAN Convergence activity and the related whitepaper. 3GPP has completed the Rel-17 normative work in the areas of ATSSS, Wireline access, Trusted and Untrusted Non-3GPP access defined in TS 23.501, TS 23.316, TS 23.502 and TS 23.503. SA WG2 would like to inform WBA that several Rel-18 proposals for improvements in the above areas are currently under discussion in SA WG2. However, the final decision on which of the potential proposals would be finally part of Rel-18 is under SA responsibility and currently is planned to be decided in December TSG SA plenary.","secretary_remarks":"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-09-07 15:09:52","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"WBA","Cc":"TSG SA","lsoriginalls":"S2-2106533","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210976.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210977","title":"LS on Reliable Data Service Serialization Indications in Rel-16","source":"SA WG2","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 thanks CT WG1 for their LS on Reliable Data Service Serialization Indications (S2-2105225\/C1-207769) and indicating that 'CT WG1 has agreed the RDSSI WID in Rel-17 to implement the Reliable Data Service Serialization Indication feature in stage 3, whereas the corresponding stage 2 requirements are in Rel-16.' SA WG2 would like to indicate that, in Rel-16, the Reliable Data Service Serialization Indication feature has been removed from TS 23.682, TS 23.501, and TS 23.502. The associated CRs are attached.","secretary_remarks":"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-09-07 15:09:52","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG3, TSG CT, TSG SA","lsoriginalls":"S2-2106536","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210977.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210978","title":"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 inform TSG RAN that in view of RAN#92e approval of a new Work Item (RP-211601) to introduce IoT NTN support in EPS in Rel-17, it has agreed the attached Rel-17 Work Item to be sent for approval to SA#93e\/Sep2021.","secretary_remarks":"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-09-07 15:09:52","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG CT, TSG SA","lsoriginalls":"S2-2106679","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210978.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210980","title":"Reply LS on OAuth2 misalignments between SA WG3 and CT WG4 specifications","source":"SA WG3","contact":"Anja Jerichow","contact-id":68341,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks CT for their LS on OAuth2 misalignments between SA WG3 and CT WG4 specifications. SA WG3 would like to inform that SA WG3 has followed the requested action. SA WG3 chose to handle Rel-15 and Rel-16 with the changes in the CR S3-213178 (with Rel-16 mirror CR in S3-213177), while handling Rel-17 with the changes in the CR S3-213189. The two baseline CRs for Rel-15 and Rel-17 are attached. Action: SA WG3 kindly asks TSG CT, CT WG4 and TSG SA to take this information into account.","secretary_remarks":"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-09-07 15:09:52","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, TSG CT","Cc":"TSG SA","lsoriginalls":"S3-213193","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210980.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210981","title":"LS on PSCELL ID availability in SGW CDR","source":"SA WG5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks ETSI TC LI for their reply LS on making PSCELL ID available at the SGW of EPC, and SA WG2 for their LS (S5-213031\/ S2-2100248) informing SA WG5 on availability of procedures for MME passing the PSCell ID information to SGW in Rel-17 TS 23.401. Based on availability of the PSCELL ID in the SGW by SA WG2 solution, SA WG5 has introduced this PSCELL ID in the Rel-17 SGW charging information and SGW-CDR definition in TS 32.251, with the corresponding stage 3 ASN.1 CDR agreed CR to TS 32.298 (S5-214068). SA WG5 would like to summarize for ETSI TC LI, about the availability of the PSCell Id in both 5GC and EPC CDRs for billing system, allowing CSPs to comply with Retained Data regulations, as follows. - 5GC: Rel-16 CHF CDRs for AMF specified in TS 32.256 with stage 3 TS 32.298 - EPC: Rel-17 SGW CDRs specified in TS 32.251 with stage 3 TS 32.298.","secretary_remarks":"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-09-07 15:09:53","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, ETSI TC LI","Cc":"RAN WG3, SA WG3LI, TSG SA","lsoriginalls":"S5-214069","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210981.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210982","title":"LS from SA WG5: LS on Multi-SDO Autonomous Networks (AN) Letter of Intent proposal","source":"SA WG5","contact":"Thomas Tovinger","contact-id":3654,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 wishes to thank TM Forum for the LS on Request for review of Letter of Intent and report on the 21st of June Formal meeting Ref AN-SDO2021-08, and we would like to give the following feedback and comments: As said at the MSDO meeting the 16th August, we would like the LoI to be more like statement of direction (like a press release) - without any binding commitment for some deliverables, and not to set too high expectations - any output documents e.g. Joint White Paper should be agreed by all participating SDOs case by case. We believe that the planned publications\/deliverable(s) Solutions\/specifications can only be published in each SDO following their applicable working procedures and IPR rules. We are happy to collaborate on harmonised definitions for AN, but it is each SDO's decision to update their respective definitions taking input proposals from this effort. We thought this would be the initial objective of this effort, and work beyond that can be then discussed and agreed after we have analysed the results of the first phase. At the current stage, we think the cooperation with participating organizations will need to be based on compatible IPR policies. We also need to check the response from '3GPP legal' before we can approve the LoI (especially regarding IPR rules, copyright, planned deliverables). Finally, some comments on the text in the first LoI proposal: - We feel that the description of state of the industry standards in clause 1 (The AN Challenge) is too negative - e.g. 'Existing 'silo' solutions have not yet demonstrated sufficient business value' and 'Lack of E2E view\/framework, no interoperability'. - '\u2026to build the next wave of intelligent and autonomous systems' in clause 4 sounds as if this multi SDO effort is aiming to deliver a new set of standards, like a new SDO.","secretary_remarks":"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-09-07 15:09:53","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TM Forum, ETSI, GSMA, ONAP, NGMN, TSG SA, IEEE, IETF, ITUT","Cc":"TSG SA","lsoriginalls":"S5-214514","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210982.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210983","title":"LS from SA WG5: LS reply to LS reply to 3GPP SA5 on Network Slice EE KPIs","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank GSMA 5GJA for your LS on the network slice EE KPI informing SA WG5 about the update of the definition of the energy efficiency attribute in NG.116 clause 3.4.7 according to the 3GPP TS 28.554. SA WG5 would also like to inform GSMA 5GJA that the energyEfficiency attribute has been introduced in TS 28.541 (https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3400), as an attribute of the ServiceProfile data type which captures the network slice related requirements that should be supported by the NetworkSlice instance(s) in the 5G network.","secretary_remarks":"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-09-07 15:09:53","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GJA","Cc":"TSG SA","lsoriginalls":"S5-214535","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210983.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210984","title":"LS from SA WG5: LS to ETSI NFV 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":"SA WG5 (Telecom Management) has an ongoing Rel-17 study on new aspects of Energy Efficiency (EE) for 5G networks. One of the key issues addressed in this study is the definition of the EE KPI for a 3GPP network function, which is the ratio between some characteristic performance measurement of the network function (not detailed here, on purpose), and the Energy Consumption (EC) of the network function. {. . .}","secretary_remarks":"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-09-07 15:09:53","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI NFV","Cc":"TSG SA","lsoriginalls":"S5-214607","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210984.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210985","title":"LS from ITU-T SG13 WP3: LS on information about draft Recommendation ITU-T Y.frd: 'Framework and Requirements of Network-oriented Data Integrity Verification Service based on Blockchain in Future Network'","source":"ITU-T SG13 WP3","contact":"Hee-Chang Chung","contact-id":6031,"tdoctype":"LS in","for":"Information","abstract":"ITU-T Study Group 13, Q1 is progressing development of a draft ITU-T Recommendation Y.frd ' Framework and Requirements of Network-oriented Data Integrity Verification Service based on Blockchain in Future Network' in the virtual meeting (5-16 July 2021). This Recommendation describes the reference architecture of the network-oriented DIVS in relation to the data integrity verification and network capability exposure. The draft text is attached and will be further developed in future Q1\/13 meetings. We thank you for your time and expertise, and look forward to cooperation and collaboration on this topic.","secretary_remarks":"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-09-07 15:09:53","uploaded":"2021-09-07 15:51:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG17, SA WG6","Cc":"Forwarded to TSG SA","lsoriginalls":"SG13-LS212","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-210985.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-211095","title":"LS from Automotive Edge Computing Consortium (AECC): LS on Prioritized Vehicle to Cloud Technical Solutions","source":"AECC","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Overall Description: The Automotive Edge Computing Consortium (AECC, https:\/\/aecc.org\/) was launched in February 2018 as a global consortium of automotive, telecommunication, cloud and mobility service companies. AECC is greatly interested in accelerating the deployment of automotive services based on network and distributed computing infrastructure. Such a goal is also achieved by identifying, developing and accessing functional and performance requirements of access networks and compute platforms, that are deemed important to enable prioritized and high-value automotive services. To this extent, AECC will require standardized solutions which are industry-wide aligned and introduced in the market. Use Case Development Working Group in AECC aims to develop use cases and requirements for the connected vehicles industry. The most relevant use case scenarios with 3GPP are intelligent driving, high-definition maps, vehicle-to-cloud cruise assist, and multi-tenant systems. Further details can be found in the attached AECC General Principle and Vision White Paper. Technical Solution Working Group in AECC focuses on developing and recommending technical solutions for the connected vehicles industry based on the requirements defined by the AECC service scenarios and use cases. The technical solution recommendations by AECC on edge data offloading, mobility service provider server selection and vehicle system reachability are in line with 3GPP Rel-17 work items. Also, AECC would like to share information about some new key issues that have been identified as important from connected vehicles industry perspective. The new key issues are access network selection, provisioning and configuration update and opportunistic data transfer. For AECC's recommendations to address these key issues, AECC would from a technical solution perspective recommend 3GPP in the Rel-18 development to study the technical gaps, and develop corresponding solutions for any identified one. For example, for key issue access network selection, a mechanism to expose information about network status to UE OS\/Apps layer. Further details can be found in the chapters 3.4.3, 3.5.3 and 3.6.3 of the attached Technical Report. Another track of work undertaking in the AECC Technical Solution Working Group is around distributed computing architecture. AECC has defined the preliminary service and architecture level requirements as well as an initial functional architecture for distributed computing in the context of automotive edge computing. AECC would ask 3GPP to kindly take AECC service requirements and system architecture into account in 3GPP Rel-18 specification development as well. More technical details can be found in the attached Distributed Computing White Paper. Action: AECC kindly invites 3GPP to review and provide feedback to the attached white papers and technical report.","secretary_remarks":"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-09-09 12:04:43","uploaded":"2021-09-10 07:42:37","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2, SA WG5, SA WG6","lsoriginalls":"AECC_3GPP_LS_final","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_93E_Electronic_2021_09\/Docs\/SP-211095.zip","group":"SP","meeting":"SP-93-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]