[{"name":"SP-200634","title":"LS from IALA: Liaison Note to TSG SA - Request for information","source":"IALA","contact":"Hyounhee Koo","contact-id":65247,"tdoctype":"LS in","for":"Action","abstract":"Introduction: The International Association of Marine Aids to Navigation and Lighthouse Authorities (IALA) focuses on the maritime domain, particularly Aids to Navigation (AtoN), including Vessel Traffic Services (VTS), and their associated communication systems. 3GPP is becoming an important element in digital communications, including the exchange of digital data. IALA would like to thank TSG SA for their appointment of a liaison between IALA and 3GPP currently fulfilled by Ms Hyounhee Koo (koo@synctechno.com). IALA would like to invite Ms. Koo to participate at the ENAV26 meeting scheduled from 28 September to 2 October at the IALA HQ to provide an update on 3GPP developments and assist in the drafting of relevant IALA documentation related to 3GPP. It is noted by IALA that 3GPP has a work item focusing maritime communication services over 3GPP Systems in Release 16 called 'MARCOM'. IALA 3GPP interest: At the fifteenth meeting of the Joint IMO\/ITU Experts Group on Maritime radiocommunication matters (8 to 12 July 2019, IMO Headquarters, London) IALA was requested to report to IMO in respect of 3GPP developments. The report of the meeting (IMO document NCSR7\/12) records this decision in paragraph 8.9: 8.9 During the ensuing discussion, the delegations that took the floor recognized that these were relevant developments and that IMO should be more proactive and get involved in the work of the 3rd Generation Partnership Project (3GPP). Noting that IALA had been approached already by 3GPP, the Group invited IALA to keep IMO informed of future developments. In response to this, IALA provided an information paper to IMO (NCSR7 INF.6). This document was developed from the IALA perspective on the operational aspects of the developments in 3GPP that may be of interest to the members of NCSR7. In document SP-191366, 3GPP provided a liaison to IALA noting proposed amendments to the NCSR document. The paper was not addressed at NCSR7 plenary, according to the standard procedures of IMO. IALA will prepare an updated input for NCSR8 and would welcome input from 3GPP in the preparation of that document. Given this request, and IALA's own role in the development of AtoN and VTS technology, IALA closely following the development of maritime services within 3GPP. IALA would therefore like to register an interest in the work of 3GPP, particularly the maritime vertical domain. Action requested: The TSG SA is requested to: 1. Inform IALA which 5G enabling technologies that are specified in the 3GPP Release 16 technical specification which could be applicable in the maritime domain. 2. Inform IALA of ongoing 5G standardization works in 3GPP Release 17 which could be applicable in the maritime domain. 3. Advise IALA regarding appropriate inputs [to support] development of 3GPP Release 17 for use within the maritime domain. 4. Advise IALA on the schedule for future meetings and other opportunities for input relevant to the maritime domain (such as MARCOM) allowing adequate time to prepare inputs.","secretary_remarks":"Postponed SP-200310 from SA#88E. Response drafted in SP-200655. Final response in SP-200877","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10210,"status":"replied to","reservation_date":"2020-08-21 07:08:55","uploaded":"2020-08-21 07:11:50","revisionof":"SP-200310","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"","lsoriginalls":"C71-11.5.1","lsreply":"SP-200877","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200634.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200638","title":"LS from ITU-T JCA-IMT2020: LS on Invitation to update the information in the IMT2020 roadmap","source":"ITU-T JCA-IMT2020","contact":"Scott Mansfield","contact-id":42415,"tdoctype":"LS in","for":"Action","abstract":"The ITU-T Joint Coordination Activity for IMT2020 (JCA IMT2020) thanks all that have replied to previous requests for input on IMT-2020 related standardization work. The current online version of the roadmap is available from the JCA-IMT2020 website. The Objective: of the roadmap is to support IMT-2020 standardization coordination. IMT-2020 is an important topic for our industry, and many standardization-related activities are held in various entities. The JCA is progressing this work in a form of roadmap of IMT2020 standardization. JCA-IMT2020 will keep updating this roadmap, and therefore we solicit your information about updates. If you send us the latest information of your activity related to 5G as well as Network Function Virtualization (NFV), programmable networks, self-managed networks, slicing (including orchestration and capability exposure), fixed-mobile convergence (FMC) and Information-Centric Networking (ICN), machine learning and other activities that are strongly related to IMT 2020, we will reflect it in the next roadmap update, which will be performed online soon after the next JCA IMT2020 meeting. Please submit your updates using the template to be found in appendix below. Should you wish to communicate any additional information about your specifications and projects, we invite you to do so. In addition, if not done yet, we invite the ITU-T Study Groups, SDOs, fora to nominate a representative to this group. JCA-IMT2020 anticipates having its next meeting in 2021, modalities and exact date\/timing will be fix and communicated later. We invite your inputs\/updates to the roadmap.","secretary_remarks":"Response drafted in SP-200856. Final response in SP-200887","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10290,"status":"replied to","reservation_date":"2020-08-21 07:08:55","uploaded":"2020-08-25 08:54:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SGs, External IMT-2020 liaison partners","Cc":"","lsoriginalls":"JCA-IMT2020-O-015-R1_LS08","lsreply":"SP-200887","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200638.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200646","title":"LS from TM Forum: TM Forum implementation experiences 3GPP NRM Models","source":"TM Forum","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Several TM Forum Members have participated in a series of 5G related Proof of Concept Catalyst projects beginning in 2016. These Catalyst have generally focused on 5G enabled services that are exposed to industry vertical applications, such as media, emergency services, remote maintenance, etc. The common elements of these Catalysts have been captured by the Open Digital Architecture (ODA) Production team into a model for exposing 5G Enabled services in GB999 ODA Production Implementation Guidelines v4.0 The essential elements in this work for 5G implementation are captured in IG1211 ODA 5G Management Implementation Guidelines v1.0. The key elements are: - Use of TMF909 API Suite Specification for NaaS v3.0.1 for 5G enabled exposed services. - Mapping from operations domains exposing NaaS API using TM Forum Information Framework (SID) Customer Facing Service (CFS) models to resource level models from 3GPP as realised by 5G vendors. The Business rationale and requirements for this approach are documented in IG1194 Focus on Services not Slices v1.0.1 Which also covers the use of the GSMA GST \/ NeST attributes. Liaison Many of our Communication Service Providers have been asking for practical guidance on how to integrate OSS\/BSS solutions based on TM Forum Management standards with Resource level solutions emerging from network technology focused SDO including 3GPP for 3\/4\/5G technologies. This has stimulated the production of the documents listed below for which SA WG5 feedback would be appreciated and for which focussed joint liaison work might be required for onward evolution of TM Forum and 3GPP assets. The two pieces of detailed modelling work are attached in: - IG1217 Resource Inventory of 3GPP NRM for Service Assurance v1.0 which describes how to practically map from 3GPP Network Resource Models (NRM) to TM Forum information models (SID) and Open APIs (REST) with JSON data models using Resource Inventory as an exemplar. - IG1211 ODA 5G Management Implementation Guidelines v1.0 which provides guidelines for five implementation questions that have arisen from members and extends IG1217 to cover concepts such as models for Resource Functions to model Network Slice and Network Slice Subnet with associated JSON representations. These impact three current 3GPP documents: - TS 28.620 Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM) (Release 15) - TS 32.107 Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) (Release 15) - TR 28.805 Study on management aspects of communication services (Release 16) And there are impacts on the GSMA GST slicing model which are referenced in TR 28.805. {. . .} We look forward to your feedback and the opportunity to collaborate further though direct discussion. Regards, Cecilia Ortega Lagos TM Forum","secretary_remarks":"CC#2: This was Block Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10320,"status":"noted","reservation_date":"2020-08-21 07:08:55","uploaded":"2020-09-04 06:07:34","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG5","Cc":"","lsoriginalls":"Liaison 3GPP SA5 TM Forum SID and NRM Models","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200646.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200647","title":"LS from SA WG2: LS on mandatory support of full rate user plane integrity protection for 5G","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS in","for":"Action","abstract":"SA WG2 thanks SA for their LS on mandatory support of full rate user plane integrity protection for 5G. SA WG2 would like to inform SA that SA WG2 fulfilled SA's request to mandate UE support of full rate user plane integrity protection for architecture option 2 in Release 16 via the agreement of the attached Release 16 CRs. Regarding support of full data rate user plane integrity protection for other architecture options in Release 17, SA WG2 expects SA WG3 to take the lead on specifying solutions for other architecture options and will update their specification after SA WG3 agrees normative requirements. Action: SA WG2 asks SA group to take the information above into account.","secretary_remarks":"CC#2: This was Block Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10330,"status":"noted","reservation_date":"2020-08-21 07:08:55","uploaded":"2020-09-04 06:07:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"CT WG1, SA WG3, RAN WG2, RAN WG3, TSG RAN, TSG CT","lsoriginalls":"S2-2006181","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200647.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200648","title":"LS on mandatory support of full rate user plane integrity protection for 5G","source":"CT WG1","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks TSG SA for their LS on mandatory support of full rate user plane integrity protection for 5G. CT WG1 would like to inform TSG SA that CT WG1 fulfilled TSG SA's request to mandate UE support of full rate user plane integrity protection for architecture option 2 in Release 16 via the agreement of the attached Release 16 CR. Regarding support of full rate user plane integrity protection for other architecture options in Release 17, CT WG1 expects SA WG3 to take the lead on specifying solutions for other architecture options and will update their specification after SA WG3 agrees normative requirements. Action: CT WG1 asks TSG SA group to take the information above into account.","secretary_remarks":"CC#2: This was Block Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10340,"status":"noted","reservation_date":"2020-08-21 07:08:55","uploaded":"2020-09-08 05:16:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG CT, TSG RAN, RAN WG3, RAN WG2, SA WG3, SA WG2","lsoriginalls":"C1-205392","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200648.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200650","title":"LS from RAN WG2: Response LS to TSG SA on mandatory support of full rate user plane integrity protection for 5G","source":"RAN WG2","contact":"Axel Klatt","contact-id":20567,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank TSG SA#88-e for their LS on 'mandatory support of full rate user plane integrity protection for 5G' [SP-200617] and the decision for which architecture options the requirement shall apply from Rel-16 onwards. RAN WG2 has discussed the request from SA#88-e and concluded that the requirement shall apply for NR connected to 5GC (aka Architecture Option 2) and further that it applies for NR-DC (handled in RAN terminology under the MR-DC framework), which has no explicit 'Option notation'. As RAN WG2 concluded based on company input that NR-DC would absolutely make sense considering the request from SA and the technical challenges are negligible once the UE implemented support for full rate UPIP for SA Option 2; based on this technical analysis RAN WG2 also decided to apply the mandatory full rate UPIP for NE-DC with MN terminated bearers as technically this is similar to NR-DC and covered in RAN WG2 already under the MR-DC framework. NE-DC with SN terminated bearers (i.e. in the eNB) should be subject to the further work in SA WG3 for Rel-17 and should consequently being covered in their new WI. RAN WG2 agreed during it's RAN WG2#111e meeting two CRs to reflect the UE requirements for Rel-16 in TS 38.300 [R2-2008513] and TS 37.340 [R2-2008639]. Regarding the addition of NE-DC with MN terminated bearers into the agreement, RAN WG2 would like to advise CT WG1 and SA WG2 to check their related changes to their specifications for any cross-WG inconsistency. To conclude corresponding work for other Architecture options in Rel-17, RAN WG2 will wait for the outcome of the discussions in SA WG3, looking forward receiving related requirements. Action: RAN WG2 asks TSG SA, CT WG1, SA WG2, SA WG3, TSG RAN and TSG CT to take the decisions above of RAN WG2 into account and note that the request by SA#88e has been accomplished for Rel-16. It should be especially noted that based on the discussions in RAN#111e NR-DC and NE-DC with MN terminated bearers are also already part of the agreement in RAN WG2.","secretary_remarks":"CC#2: This was Block Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10350,"status":"noted","reservation_date":"2020-08-21 07:08:55","uploaded":"2020-09-08 05:16:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, CT WG1, SA WG2, SA WG3, TSG CT, TSG RAN","Cc":"RAN WG3","lsoriginalls":"R2-2008643","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200650.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200651","title":"LS from RAN WG3: Reply LS on mandatory support of full rate user plane integrity protection for 5G","source":"RAN WG3","contact":"Luis Lopes","contact-id":84588,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to thank TSG SA for the LS on mandatory support of full rate user plane integrity protection for 5G. RAN WG3 has analysed the agreed CR to TS 33.501 in SP-200628 and thinks that this does not impact RAN WG3 specifications. Regarding release 17, RAN WG3 intends to wait for SA WG3 to analyse the impact on security requirements and architecture. RAN WG3 will follow up based on SA WG3's conclusions. Action: RAN WG3 kindly asks TSG SA, TSG RAN, TSG CT, SA WG2, SA WG3, RAN WG2, and CT WG1 to take the above information into account, and inform RAN WG3 of further progress on this topic.","secretary_remarks":"CC#2: This was Block Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10360,"status":"noted","reservation_date":"2020-08-21 07:08:55","uploaded":"2020-09-08 05:16:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG RAN, TSG CT, CT WG1, SA WG2, SA WG3, RAN WG2","Cc":"","lsoriginalls":"R3-205653","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200651.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200652","title":"LS from SA WG2: LS on RAN impact of FS_5MBS Study","source":"SA WG2","contact":"Meng Li","contact-id":81192,"tdoctype":"LS in","for":"Action","abstract":"SA WG2 has been discussing on Rel-17 FS_5MBS solutions since SA WG2 #135 meeting in TR 23.757, and captured several proposed solutions. SA WG2 would like to kindly inform RAN WG2 and RAN WG3 the following interim agreements in SA WG2: - SA WG2 will develop means to provide QoS requirements for an MBS Session to RAN nodes. - SA WG2 agrees that for N3 transport of the shared delivery method of MBS data, GTP-U tunnelling using a transport layer IP multicast method and shared N3 (GTP-U) Point-to-Point tunnel shall be supported from MB-UPF to NG-RAN nodes. This tunnel can use either IP multicast transport (NG-RAN sends IGMP\/MLD Join\/Leave to a multicast router) or point-to-point unidirectional N3 tunnels from MB-UPF to NG-RAN nodes. For unicast transport there shall be 1-1 mapping between MBS Session and GTP-U tunnel towards a RAN node, and for multicast transport there shall be 1-1 mapping between MBS Session and the GTP-U tunnel. - SA WG2 agreed that the UE shall be able to receive on-going data of a multicast MBS session while in CM-CONNECTED state. - Based on SA plenary decisions, Key Issue #5 ('Support of Broadcast TV Video and Radio communication services') is out of scope of Rel-17. {. . .}","secretary_remarks":"Response drafted in SP-200810. Final response in SP-200884","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10160,"status":"replied to","reservation_date":"2020-08-21 07:08:55","uploaded":"2020-09-08 05:21:13","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG RAN, RAN WG2, RAN WG3","Cc":"","lsoriginalls":"S2-2006044","lsreply":"SP-200884","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200652.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200654","title":"LS from CT WG1: LS on the stage 2 aspects of MINT","source":"CT WG1","contact":"Sang Min Park","contact-id":62105,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has discussed a WID proposal for CT aspects of Minimization of Service Interruption (MINT-CT) in the CT WG August meetings, in order to support the service requirements specified for Rel-17. The WID on MINT-CT includes a study phase on both stage-2 and stage-3 aspects. CT WG1 is also planning to define end-to-end call flow regarding registration after selection of a disaster roaming PLMN in the stage-2 specification owned by CT WG1. CT WG1 would like to ask TSG SA if there is any concern on this approach. CT WG1 expects any feedback on this way forward until the next WG meeting so that both study phase and normative phase can progress within Rel-17 timeframe. Action: CT WG1 kindly asks TSG SA to take the information above into account and to provide feedback.","secretary_remarks":"Response drafted in SP-200775. Final response in SP-200880","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10240,"status":"replied to","reservation_date":"2020-08-21 07:08:55","uploaded":"2020-09-08 10:21:20","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG CT, SA WG2, SA WG3, CT WG3, CT WG4","lsoriginalls":"C1-205332","lsreply":"SP-200880","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200654.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200655","title":"[DRAFT] Reply LS on request for information from IALA","source":"SyncTechno Inc.","contact":"Hyounhee Koo","contact-id":65247,"tdoctype":"LS out","for":"Approval","abstract":"This contribution is the reply liaison on request information from IALA.","secretary_remarks":"Response to SP-200634. MCC will need to revise to remove 'draft'. Revised to SP-200877.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10220,"status":"revised","reservation_date":"2020-09-01 12:50:54","uploaded":"2020-09-01 12:52:28","revisionof":"","revisedto":"SP-200877","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"MARCOM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IALA, 3GPP SA WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200655.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200774","title":"Discussion on the WI MINT","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"discussion","for":"Endorsement","abstract":"Discussion paper for LS from CT WG1 (C1-205332) on the stage 2 aspects of MINT","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10250,"status":"noted","reservation_date":"2020-09-08 02:17:53","uploaded":"2020-09-09 07:40:26","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"MINT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200774.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200775","title":"[DRAFT] Reply LS on the stage 2 aspects of MINT","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on the stage 2 aspects of MINT (CT WG1 LS, C1-205332)","secretary_remarks":"Response to SP-200654. CC#1: A revision will be provided based on the comments received. SP 200775_rev3 was approved. (This will be cleaned up and revised into a new TD number by MCC). Revised to SP-200880.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10260,"status":"revised","reservation_date":"2020-09-08 02:22:58","uploaded":"2020-09-09 07:40:26","revisionof":"","revisedto":"SP-200880","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"MINT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"TSG CT, SA2, SA3, CT3, CT4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200775.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200809","title":"Discussion on support for broadcast in Rel-17 MBS","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Endorsement","abstract":"Proposal: The scope of Rel-17 5MBS SID remains as it is (i.e. NR broadcast is included), and no further down-scoping or prioritization is needed.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2020-09-09 03:42:50","uploaded":"2020-09-09 08:57:48","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200809.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200810","title":"[DRAFT] Reply LS on RAN impact of FS_5MBS Study","source":"Huawei [SA]","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG RAN, SA WG2. CC: RAN WG2, RAN WG3","secretary_remarks":"Response to SP-200652. SP 200810_Rev2 was approved. (To be revised into a new TD number by MCC). Revised to SP-200884.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10180,"status":"revised","reservation_date":"2020-09-09 03:42:50","uploaded":"2020-09-09 08:57:48","revisionof":"","revisedto":"SP-200884","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, SA WG2","Cc":"RAN WG2, RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200810.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200814","title":"The Importance of Maintaining Broadcast Services in Rel-17 NR MBS","source":"CBN, ABS, ABP, China Telecom, China Unicom, IRT, Reliance Jio","contact":"Shuang Li","contact-id":83306,"tdoctype":"discussion","for":"Decision","abstract":"Broadcast is essential to NR MBS - SA WG2 is debating whether broadcast (for other use cases than the ones excluded already for Rel-17) should be further down-scoped in Rel-17 for remaining broadcast requirement in the SID. Some companies have provided solutions on broadcast (which are documented in the TR). SA WG2 sent an LS to SA asking the above question. - NR MBS with only multicast is just a feature improving network efficiency. With Broadcast, NR MBS creates new business models serving more scenarios, as well as enabling the 5G refarming of the broadcast-dedicated spectrum in many countries. - Down-scoping broadcast will cause NR MBS incapable to deal with emerging demand in many new businesses for 5G NR. NR Broadcast: Enable new business cases - Public Services - Government and public service entities have urgent demand for 5G-enabled innovative ways of communicating with citizens. Broadcast shall be adopted to more efficiently deliver real-time emergency multi-media notifications to a wide variety of devices under the scope of public safety (like disaster warning, security, pandemic control, etc.). - Multimedia Live Streaming in crowed activities(Concerts\/Sport Games) - Innovative broadcast services like Multi-angle live viewing, game statistics broadcasting, XR enhanced viewing, etc. Broadcast mode is essential for such highbitrate-high-concurrency services. CBN is planning to showcase innovative NR MBS broadcast services in Beijing Olympic Winter Games 2022. - Massive IoT - Identical content needs to be distributed to a massive number of devices like smart home appliances. It is inefficient to use unicast\/multicast for this, but ideal for broadcast. It makes OTA (over-the-air) firmware upgrades\/group messaging\/etc. much more efficient. - V2X - Broadcast enables vehicles to efficiently communicate with the network and its surroundings, making the network to more efficiently deliver real-time information, such as software and traffic updates, as well as the emergency Multimedia notifications to the vehicle driver\/passengers.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10280,"status":"noted","reservation_date":"2020-09-09 09:27:33","uploaded":"2020-09-09 09:51:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200814.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200856","title":"[DRAFT] Reply to LS on Invitation to update the information in the IMT2020 roadmap","source":"Samsung","contact":"Erik Guttman","contact-id":18782,"tdoctype":"LS out","for":"Approval","abstract":"To: .ITU-T JCA-IMT2020","secretary_remarks":"Created at meeting. Response to SP-200638. MCC will need to revise to remove 'draft'. Revised to SP-200887.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10300,"status":"revised","reservation_date":"2020-09-16 08:32:39","uploaded":"2020-09-17 05:03:10","revisionof":"","revisedto":"SP-200887","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T JCA-IMT2020","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200856.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200871","title":"LS from TSG RAN: Reply LS on RAN impact of FS_5MBS Study","source":"TSG RAN","contact":"Simone Provvedi","contact-id":36483,"tdoctype":"LS in","for":"Action","abstract":"Regarding the following question, that SA WG2 asked RAN to feedback on: SA WG2 is debating whether broadcast (i.e. without the network's awareness about UEs receiving broadcast contents and for other use cases than the ones excluded already for Rel-17) should be further down-scoped in Rel-17 for remaining broadcast requirement in the SID. Some companies have provided solutions on broadcast (which are documented in the TR). SA WG2 would like to ask SA, RAN, RAN WG2 and RAN WG3 for feedback on broadcast support in Rel-17. RAN would like to clarify that NR-based broadcast is within the scope of RAN WI for NR MBS in Rel-17, as per the WID approved in RP-201038. According to the discussion at RAN#89e, it is concluded that the scope of RAN WI for NR MBS in Rel-17 is kept as was. RAN would like to ask TSG SA and SA WG2 to take the above answer into account.","secretary_remarks":"Related to incoming LS in SP-200652. CC#4: This LS was noted.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10200,"status":"noted","reservation_date":"2020-09-18 11:37:42","uploaded":"2020-09-18 11:39:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"RAN WG2, RAN WG3","lsoriginalls":"RP-202086","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200871.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200877","title":"Reply LS on request for information from IALA","source":"TSG SA","contact":"Hyounhee Koo","contact-id":65247,"tdoctype":"LS out","for":"Approval","abstract":"To: IALA, SA WG1","secretary_remarks":"Revision of SP-200655. Approved","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10230,"status":"approved","reservation_date":"2020-09-19 07:23:24","uploaded":"2020-09-19 07:25:07","revisionof":"SP-200655","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"MARCOM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-200634","lsto":"IALA, SA WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200877.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200880","title":"Reply LS on the stage 2 aspects of MINT","source":"TSG SA","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: TSG CT, SA WG2, SA WG3, CT WG3, CT WG4","secretary_remarks":"Revision of SP-200775_Rev3. Approved","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10270,"status":"approved","reservation_date":"2020-09-19 07:23:25","uploaded":"2020-09-19 07:25:07","revisionof":"SP-200775","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"MINT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-200654","lsto":"CT WG1","Cc":"TSG CT, SA WG2, SA WG3, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200880.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200884","title":"Reply LS on RAN impact of FS_5MBS Study","source":"TSG SA","contact":"Wanqiang Zhang","contact-id":77712,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG RAN, SA WG2. CC: RAN WG2, RAN WG3","secretary_remarks":"Revision of SP-200810_Rev2. Approved","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10190,"status":"approved","reservation_date":"2020-09-19 07:23:29","uploaded":"2020-09-19 07:25:07","revisionof":"SP-200810","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-200652","lsto":"TSG RAN, SA WG2","Cc":"RAN WG2, RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200884.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-200887","title":"Reply to LS on Invitation to update the information in the IMT2020 roadmap","source":"TSG SA","contact":"Erik Guttman","contact-id":18782,"tdoctype":"LS out","for":"Approval","abstract":"To: .ITU-T JCA-IMT2020","secretary_remarks":"Revision of SP-200856. Approved","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10310,"status":"approved","reservation_date":"2020-09-19 07:23:29","uploaded":"2020-09-19 07:25:07","revisionof":"SP-200856","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-200638","lsto":"ITU-T JCA-IMT2020","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_89E_Electronic\/Docs\/SP-200887.zip","group":"SP","meeting":"SP-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]