[{"name":"SP-190278","title":"LS from NGMN Alliance: 5G Extreme Requirements","source":"NGMN Alliance","contact":"Klaus Moschner","contact-id":59428,"tdoctype":"LS in","for":"Information","abstract":"NGMN Task Force on 5G Extreme Requirements: NGMN has recognised the need to gain deeper understanding in what impact new services will have on the future network architecture, both for the radio access and for the entire end-to-end network. Therefore, a task force on 5G Extreme Requirements was kicked off in May 2017. The new requirements are referred to as 'extreme' since they go far beyond the boundaries of the traditional targets that have been the main driver for network design until today, and the focus of this work is the case when very high reliability and low latency are required at the same time. This task force has the objective of answering the following questions: 1) To which extent can the 5G extreme services be delivered on existing deployments? 2) What modifications, if any, are required in the radio access network and\/or in the core network to deliver the 5G extreme services? 3) How sensitive are the deployment models to the requirements? By relaxing the targets, does t","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG RAN, ETSI ISG NGP, 5GAA","Cc":"","lsoriginalls":"190329 Liaison NGMN_3GPP_5G_Ext_Req.","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190278.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190279","title":"LS from CT WG1: LS on Equivalent SNPN","source":"CT WG1","contact":"Lin Shu","contact-id":43310,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 is working on the Stand-alone Non-Public Network (SNPN) selection in stage 2 TS 23.122 and could not reach a consensus on whether equivalent SNPNs need to be supported. CT WG1 would like to ask SA WG2: Is there requirement to support equivalent SNPNs?","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG1, TSG SA","lsoriginalls":"C1-192780","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190279.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190280","title":"LS from CT WG4: Reply LS on Protected LI Parameters in N4","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 thanks SA WG3-LI for their LS on Protected LI Parameters in N4. CT WG4 has been working on N4 protocol extensions for a N4-based LI_T3 interface in 5GC based on the following stage 2 requirements from SA WG3-LI in TS 33.127 v15.0.0: 6.2.3 LI for SMF\/UPF 6.2.3.1 Architecture [\u2026] When interception of communication contents is required, the CC-TF present in the SMF sends a trigger to the CC-POI present in the UPF over the LI_T3 interface which can be based on N4 functionalities (between SMF and UPF) with LI specific security measures applied. The following CT WG4 29.244 CR approved at CT#83 started to define these protocol extensions. 2019-03 CT#83 CP-190032 0213 1 Legal Interception support for 5GC SMF\/UPF 15.5.0 C4-191435 (CR 0234 29.244 Rel-15 Lawful Interception in 5GC, submitted to CT WG4#90 and postponed according to SA WG3-LI LS) was meant to complete this work. This work is similar in principles to the PFCP protocol extensions CT WG4 has specified from Rel-14 onwards for CU","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"LI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3LI","Cc":"TSG CT, TSG SA, SA WG3","lsoriginalls":"C4-191529","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190280.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190281","title":"LS from CableLabs: Residential use case for 5G Core with fixed broadband access","source":"CableLabs","contact":"Jennifer Andreoli-Fang","contact-id":59177,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 delegates: CableLabs would like to thank 3GPP for progressing the release 16 5WWC work item towards specification completion. This work item enables the connectivity to 5GC with hybrid-fibre coaxial (HFC) access network technologies specified by CableLabs. Many devices (e.g, laptops, security cameras, etc) today that use the HFC access network do not support 3GPP access technologies and the NAS (Network Access Stratum). Furthermore, these devices do not use 3GPP credentials to access the HFC networks. CableLabs works with its member operators to identify priority use cases for the 3GPP 5G Core with the HFC access network. One use case of interest is for the operator's 5G core network to service the existing devices behind the HFC residential GW or enterprise GW. There devices do not have 3GPP RAT, NAS, or 3GPP credentials. It is important to support customer devices within the context of wireline access. Support for such devices will allow the 5G core to provide services to wide","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"TSG SA, SA WG2, SA WG3","lsoriginalls":"CableLabs LS to 3GPP SA1 May 2019","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190281.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190282","title":"Ls from Broadband Forum: Response to 3GPP SA2 liaison S2-1902902 on LS on updating the status of 5WWC normative work","source":"Broadband Forum","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Dear colleagues, BBF would like to thank SA WG2 for the update on current status and the provided specification. BBF will consider it during the normative work and will provide feedback and comments as soon the work progressed. {...} Other issues: BBF has considered roaming as a solution for wholesale of fixed access. Our operator community considers current L2 wholesale BBF solutions sufficient for their needs. We have not identified requirements for 3GPP supporting roaming for WWC scenarios in Release 16 timeframe. BBF has done a survey on the business need to support 5G bridged RG among the BBF operators. BBF plans to share the result of our analysis and any derived requirements in a separate LS for your SA WG2#132 meeting.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2, SA WG3","Cc":"","lsoriginalls":"LIAISE-288","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190282.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190283","title":"LS from NGMN: NGMN 5G End-to-End Architecture Framework","source":"NGMN","contact":"Feifei Lou","contact-id":61172,"tdoctype":"LS in","for":"Information","abstract":"NGMN 5G Work-Programme, Requirements and Architecture: In September 2017 and in February 2018, the first version and the second version of the NGMN End-to-End Architecture Framework was published, building on and developing end-to-end architecture principles from the 2015 5G White Paper, which can support the standardisation and subsequent availability of 5G for 2020 and beyond. Intention of the LS and required actions: NGMN is pleased to inform the recipient of this liaison statement for information sharing on the interim third version (v3.0) of the NGMN 5G End-to-End Architecture Framework that includes requirements together with descriptions and concepts associated with new topics. The new topics include: - Autonomic networking - Distributed Ledger Technology - Minimization or avoidance of tunnelling - Network automation Further enhancement, consideration, and review in the articulation of the related requirements together with updates that include security aspects, URLLC, and netwo","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA, SA WG2, SA WG3, SA WG5, SA WG6","Cc":"","lsoriginalls":"Liaison_NGMN_P1_to_3GPP","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190283.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190284","title":"LS from ETSI CTI: Observations on standards and technical constraints from 3rd MCX remote Plugtests","source":"ETSI CTI","contact":"Saurav Arora","contact-id":62621,"tdoctype":"LS in","for":"Information","abstract":"As a result of the Plugtests event activities some issues in 3GPP Technical Specifications (TSs) and related standards were identified together with practical deployment problems that may demand some clarification or feedback from the related SDOs. We have classified those aspects into the following two categories: - Observations on 3GPP Standards: Missing, erroneous or ambiguous definition of procedures in 3GPP's MCS TSs. - Technical constraints: Related to implementation issues, not covered by the standards, but which need to be faced by MCS vendors in most deployments. The reader should note that 3GPP TS approved in December 2017 (mostly 14.4.0) were considered for the second and third Plugtests event and some fields may have changed or have been already solved. The third MCX Plugtests event team wants to thank all the participants in the Plugtests for kindly sharing the following lessons learned. Specific actions towards pushing this feedback to relevant TSGs in 3GPP have already b","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:57","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6, CT WG1, SA WG3","Cc":"TSG CT, TSG SA","lsoriginalls":"LS_from_3rdMCXPlugtests","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190284.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190285","title":"LS from ITU-T SG11: LS on Amendment for ITU-T Q.731.3 on new functionalities to the calling line identification presentation","source":"ITU-T SG11","contact":"Cheng Li","contact-id":72701,"tdoctype":"LS in","for":"Information","abstract":"ITU-T SG11 would like to inform ITU-T SG2, 3GPP and ETSI TC NTECH that ITU-T SG11 develops an amendment for ITU-T Q.731.3: Stage 3. Description for number identification supplementary services using signalling system No.7 \u2014 calling line identification presentation. This Amendment defines new functionalities to the calling line identification presentation. The document will be proposed for consent at the next ITU-T SG11 meeting (Geneva, 6-15 March 2019). In this regard, ITU-T SG11 would appreciate your comments and views on the current draft. The output document which contains the latest baseline text of Amendment 1 for ITU-T Q.731.3 is available in SG11-TD607\/GEN. ITU-T SG11 looks forward to collaborating with you on this subject.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, 3GPP, ETSI TC NTECH","Cc":"","lsoriginalls":"SG11-LS73","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190285.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190286","title":"LS from SA WG2: Conclusion on 5G CIoT user plane small data solution","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 has re-discussed whether to introduce system support for User Plane CIoT 5GS Optimization with long eDRX (i.e. solution 19 in TR 23.724) in Rel-16 for eMTC\/NB-IoT or system support for RRC Inactive with long eDRX (based on e.g. solution 7 and solution 24 in TR 23.724) in Rel-16 for eMTC and NB-IoT. SA WG2 concluded to only introduce system support for User Plane CIoT 5GS Optimization with long eDRX (i.e. solution 19 in TR 23.724) in Rel-16 for eMTC\/NB-IoT. SA WG2 would like to ask RAN WG2 if RAN WG2 intends to support RRC Inactive with short eDRX (sleep cycles up to the NAS transmission timer) for eMTC and\/or NB-IoT connected to 5GC in Rel-16?","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, RAN WG2, RAN WG3","Cc":"TSG SA, TSG CT","lsoriginalls":"S2-1904025","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190286.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190287","title":"LS from SA WG2: Response LS on reporting all cell IDs in 5G","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 thanks RAN WG3 and SA WG3-LI on the LS on reporting all cell IDs in 5G. SA WG2 reviewed the now approved RAN WG3 CRs (RP-190201, RP-190202 for 5GC and RP-190555 for EPC) and discussed alignment CRs for TS 23.401 and TS 23.502. SA WG2 would like to highlight some system level aspects that came up during the SA WG2 discussion: - Concerns were mentioned in SA WG2 about the potential signalling impact to the CN (MME or AMF) when the reporting of the Secondary Cell (PScell) is always performed (i.e. when 'legacy' cell reporting is activated) and no means are provided in MME or AMF to selectively activate reporting of PScell only when required. SA WG2 would like to ask SA WG3-LI whether signalling optimisation via selective activation of reporting PScell would be acceptable for SA WG3-LI. - SA WG2 would also like to highlight that Carrier Aggregation (CA) also involves more than one cell. CA was standardised in release 10 and while there are some strict requirements on the cells (e.g.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10140,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3LI","Cc":"RAN WG3, TSG SA, SA WG3, SA WG5, TSG RAN, TSG CT, CT WG1, CT WG3, CT WG4, ETSI TC LI","lsoriginalls":"S2-1904819","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190287.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190288","title":"LS from SA WG2: LS Reply to 3GPP on Time-Criticality of In-Advance QoS Notification","source":"SA WG2","contact":"Dario Serafino Tonesi","contact-id":43468,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 thanks 5GAA WG2 for their reply LS on Time-Criticality of In-Advance QoS Notification and would like to notify that the attached CR documents Solution 29 of TR 23.786 which has been selected as the basis for normative work to enable in-advance notification for application adjustment. The normative work for such solution is in progress.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eV2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"5GAA WG2","Cc":"SA WG1, TSG SA","lsoriginalls":"S2-1904824","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190288.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190290","title":"LS from SA WG3: LS on Reply LS on Nudr Sensitive Data Protection","source":"SA WG3","contact":"Tim Evans","contact-id":49202,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank CT WG4 for the reply LS on Nudr Sensitive Data Protection. SA WG3 acknowledges that SA WG2 has introduced the concept of stateless network functions (such as UDM) (potentially) separate from function-less storage: UDR. With respect to the storing and handling of credential data this could lead to the storage in the UDR as described in 3GPP TS 29.505 and the handling in (a separate) UDM\/ARPF as described in 3GPP TS 33.501. SA WG3 has defined ARPF as the entity to handle all cryptographic functions, cryptographic parameters and keys associated with the generation of authentication vectors. As deployment options, the ARPF may contain a secure environment such as an HSM (Hardware Security Module) which shall be dedicated for ARPF use only. There is no standardized interface between UDM and ARPF in Rel-15. The credentials used by the ARPF for authentication are critical to the security of the 5G system and must be kept secure. TS 33.501 defines the subscriber cred","secretary_remarks":"Response drafted in SP-190539. Final response in SP-190581","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10160,"status":"replied to","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, SA WG2","Cc":"TSG SA","lsoriginalls":"S3-191629","lsreply":"SP-190581","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190290.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190291","title":"LS from SA WG3LI: LS on Protected LI Parameters in N4","source":"SA WG3LI","contact":"Alex Leadbeater","contact-id":71428,"tdoctype":"LS in","for":"Information","abstract":"SA WG3-LI has noted that CT WG4 is considering work to support LI triggering over the N4 interface. SA WG3-LI recognises that the proposed change is intended to meet the Release 15 LI requirements, and would like to thank CT WG4 delegates for working towards this. SA WG3-LI would like to make the following observations: - All LI interfaces, including the triggering interfaces (LI_T2, LI_T3) between the LI functions within the SMF and UPF, must meet the requirements stated in TS 33.126. - In particular, the interface must not reveal information about which sessions or subscribers are the subject of LI to any function which is not a specific LI function ('non-detectability'). This includes any part of the SMF or UPF outside the LI Triggering Function (TF) or Point of Interception (POI). - All mechanisms for managing and securing LI functions should be assessed and considered by SA WG3-LI. TS 33.128 currently realises the LI_T2\/LI_T3 triggering interface using a dedicated secure channel,","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"LI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"TSG CT, TSG SA, SA WG3","lsoriginalls":"S3i190254","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190291.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190292","title":"LS from SA WG3LI: Response LS on reporting all Cell IDs in 5G","source":"SA WG3LI","contact":"Alex Leadbeater","contact-id":71428,"tdoctype":"LS in","for":"Information","abstract":"SA WG3-LI would like to thank RAN WG3 for the reply LS on Reporting All Cell Ids in 5G in Tdoc R3-191111. SA WG3-LI understanding is that every change in the primary cell of secondary group will be reported by RAN to the CN. However, it was unclear to SA WG3-LI whether the primary cell of secondary group will be included as additional location information available when the Mobility Management events are handled by the MME\/AMF and that changes of the primary cell of secondary group will be handled in the MME as location update and in the AMF as mobility registration update. SA WG3-LI requires that for every UE; - Whenever the primary cell of the primary group changes (including initial attach \/ registration), both the primary cell of the primary group and the primary cell of the secondary group (if assigned) needs to be reported to the MME\/AMF. - Whenever the primary cell of the secondary group changes (including initial attach to secondary group), both the primary cell of the primary","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10180,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"LI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG2","Cc":"SA WG3, TSG CT, CT WG1, CT WG3, ETSI TC LI, TSG SA, TSG RAN","lsoriginalls":"s3i190265","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190292.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190293","title":"LS from SA WG3LI: Reply on LS on Protected LI Parameters in N4","source":"SA WG3LI","contact":"Alex Leadbeater","contact-id":71428,"tdoctype":"LS in","for":"Information","abstract":"SA WG3-LI thanks CT WG4 for their LS on Protected LI Parameters in N4, in C4-190259. With regard to the Action: to SA WG3-LI 'CT WG4 kindly asks SA WG3-LI group to report further guidance to CT WG4, as soon as possible, on whether CT WG4 should pursue or revert its work on N4 to support LI in 5GC in Rel-15, and to update their specifications in one way or the other accordingly', SA WG3-LI would like to provide the following guidance. SA WG3-LI kindly requests CT WG4 to not pursue any work on N4 enhancements to support LI at the current time and to please revert any CRs already agreed by CT WG4. SA WG3-LI will advise CT WG4 if any further work on N4 enhancements for LI is required in the future.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2019-05-15 15:12:49","uploaded":"2019-05-22 12:15:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"LI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"TSG CT, TSG SA, SA WG3, ETSI TC LI","lsoriginalls":"S3i190283","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190293.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190324","title":"LS from NGMN: NGMN Liaison Statement on the 5G Proof of Concept","source":"NGMN","contact":"Feifei Lou","contact-id":61172,"tdoctype":"LS in","for":"Information","abstract":"NGMN 5G Trial and Testing Initiative with the Proof of Concept (PoC) phase: In June 2016, NGMN Board approved a Project devoted to 5G Trial & Testing. The mission of the Trial and Test Initiative can be summarized as below: - Enable global collaboration of testing activities to support an efficient, successful, and in-time 5G technology and service introduction ? Consolidate contributions and report on industry progress in order to ensure the development of globally aligned 5G technology and service solutions - Identify, test, and promote new business opportunities and use-cases with industry stakeholders (e.g. from vertical industries). The Proof of Concept phase is a part of the 5G Trial and Testing Initiative. It aimed at demonstrating that basic 5G functionality and performance are achievable with prototypes involving proprietary pre-standard equipment. The PoC experiments were performed both in lab and also in small- to medium-scale outdoor environments within 2018. The testing ha","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10200,"status":"noted","reservation_date":"2019-05-22 12:46:29","uploaded":"2019-05-22 13:26:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA, ETSI MEC ISG, O-RAN Alliance, GTI, 5GAA, 5G-ACIA","Cc":"","lsoriginalls":"20190520_LS NGMN 5G TTI PoC","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190324.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190326","title":"LS from RAN WG3: Response LS on reporting all Cell IDs in 5G","source":"RAN WG3","contact":"Krzysztof Kordybach","contact-id":68359,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 would like to thank SA WG3-LI for the response LS on reporting all Cell IDs in 5G. RAN WG3 has discussed the request and concluded as follows: Action: SA WG3-LI asks RAN WG3 to confirm that every change in the primary cell of secondary group will be reported by RAN to the CN. The solution that RAN WG3 designed at RAN WG3 #103 meeting enables providing PCell and PSCell whenever either of them changes. Action: SA WG3-LI asks RAN WG3 to note that in order to preserve the non-detectability of LI, any signaling over non-LI specific interfaces shall be the same regardless of whether or not the subscriber is an LI target, and to take any Action: seen needed from signaling load perspective. The solution that RAN WG3 designed at RAN WG3 #103 meeting enables reporting every change of PCell or PSCell so that the signaling is the same for all users. This is executed though at the expense of very heavy signaling.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10210,"status":"noted","reservation_date":"2019-05-22 12:46:29","uploaded":"2019-05-22 13:26:04","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3LI, SA WG2","Cc":"SA WG3, TSG CT, CT WG1, CT WG3, ETSI TC LI, TSG SA, TSG RAN","lsoriginalls":"R3-193111","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190326.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190501","title":"LS from NGMN Alliance: NGMN Operators' Release 17 RAN Priorities","source":"NGMN Alliance","contact":"Feifei Lou","contact-id":61172,"tdoctype":"LS in","for":"Information","abstract":"Intention of the LS and required actions NGMN is pleased to inform TSG RAN about NGMN operators' joint position on Rel-17 RAN priorities that includes continuation of Rel-16 work and new topics for Rel-17. As many operators are launching 5G from 2019 and onwards, experiences from the launches and the live networks will drive the need for additional 3GPP work, and 3GPP should reserve capacity for this. In addition, remaining capacity should support the work for future services and enhancements. From NGMN operators' perspective, workload balance between corrections\/improvements and enhancements\/new requirements should be guaranteed. To avoid inability to take account of live deployment findings or overloading working groups, we suggest that 3GPP allocate ~30% capacity to address feedback from initial deployments and to agree on this reserved capacity in the June plenary meeting. The other items that NGMN would like to have prioritised (with examples in consideration) are: ? URLLC: needed","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10220,"status":"noted","reservation_date":"2019-05-30 15:14:52","uploaded":"2019-05-30 16:19:15","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG SA","lsoriginalls":"Liaison_NGMN_to_3GPP_R17 priorities","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190501.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190502","title":"LS from RAN WG2: Reply LS for Conclusion on 5G CIoT user plane small data solution","source":"RAN WG2","contact":"Veera Prasada Kadiri","contact-id":72325,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks SA WG2 for their LS on Conclusion on 5G CIoT user plane small data solution. Following SA WG2's agreement, RAN WG2 will introduce support for User Plane CIoT optimisations for NB-IoT and eMTC when connected to 5GC. RAN WG2 discussed whether to support RRC-Inactive with short eDRX (sleep cycles up to the NAS transmission timer) for eMTC and\/or NB-IoT connected to 5GC in Rel-16 and reached the following conclusions: - RRC-INACTIVE state in NB-IoT connected to 5GC is not supported. - RRC-INACTIVE state with short eDRX cycles is optionally supported for eMTC connected to 5GC with capability signalling. - FFS if EDT in RRC-INACTIVE state is not supported in Rel-16. - UP optimization solution is supported for both eMTC and NB-IoT connected to 5GC with capability signalling.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10230,"status":"noted","reservation_date":"2019-05-30 15:14:52","uploaded":"2019-05-30 16:19:15","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"FS_CIoT_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3","Cc":"TSG SA, TSG CT, TSG RAN","lsoriginalls":"R2-1908202","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190502.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190503","title":"LS from SA WG2: LS on IMS voice over 5GS","source":"SA WG2","contact":"Mario Madella","contact-id":23765,"tdoctype":"LS in","for":"Information","abstract":"The 5G System is defined in 3GPP TS 23.501 Rel-15 as follows 5G System: 3GPP system consisting of 5G Access Network (AN), 5G Core Network and UE. In 3GPP Rel-15 the 5G AN is comprised of 3GPP accesses (NG-RAN) and untrusted non-3GPP accesses, where NG-RAN is defined as follows NG-RAN: A radio access network that supports one or more of the following options with the common characteristics that it connects to 5G Core: 1) Standalone New Radio. 2) New Radio is the anchor with E-UTRA extensions. 3) Standalone E-UTRA. 4) E-UTRA is the anchor with New Radio extensions. SA WG2 expects\/understands that an IMS Profile for Voice, Video and Messaging over 5GS will be developed by GSMA, including all the accesses that make up the 5G AN, as defined in 3GPP and reported above.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10240,"status":"noted","reservation_date":"2019-05-30 15:14:52","uploaded":"2019-05-30 16:19:15","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GJA, GSMA NG","Cc":"SA WG1","lsoriginalls":"S2-1906791","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190503.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190504","title":"LS from SA WG2: Reply LS on PARLOS RAN impacts","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 thanks RAN, RAN WG2 and RAN WG3 for their LS responses for PaRLOS RAN impacts. Based on feedback from RAN WGs, TSG RAN and CT WG1, SA WG2 discussed further the restriction indicated in the LS from RAN and RAN WG2 that the number of spare cause value and spare bits in LTE connection set up procedure is very limited and indicating RLOS in establishment cause is not feasible. SA WG2, further to the solutions indicated in LS S2-1901077, discussed the possibility that an indication for RLOS is provided in LTE RRC msg.5 'RRCConnectionSetupComplete' which SA WG2 understands does not have the same size limitations as RRC msg.3. Such RLOS indication could assist in MME selection and potentially overload control procedures. SA WG2 drafted the attached CR to TS 23.401 that describes this solution that is agreed from SA WG2 point of view. SA WG2 would like to ask RAN, RAN WG2 and RAN WG3 whether an RLOS indicator can be added in LTE RRC msg.5 'RRCConnectionSetupComplete' in Rel.16. If this","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10250,"status":"noted","reservation_date":"2019-05-30 15:14:52","uploaded":"2019-05-30 16:19:15","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, RAN WG2, RAN WG3","Cc":"CT WG1, TSG SA","lsoriginalls":"S2-1906806","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190504.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190505","title":"LS from SA WG6: LS on application layer support for V2X services","source":"SA WG6","contact":"Niranth Amogh","contact-id":39608,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 has finalized the following Release 16 stage 2 normative specifications which support V2X application layer: 1. 3GPP TS 23.286 'Application layer support for V2X services; Functional architecture and information flows' (see attachment). 2. 3GPP TS 23.434 'Service Enabler Architecture Layer for Verticals; Functional architecture and information flows' (see attachment). 3GPP TS 23.434 has specified the (Service Enabler Architecture Layer) SEAL services (e.g. group management, location management, network resource management) which can be commonly used by any vertical application layer including V2X application layer. 3GPP TS 23.286 has specified V2X application enabler layer functions (e.g. V2X service discovery, V2X service continuity, file distribution, application level location tracking, V2X message delivery). Where necessary these functions utilize SEAL services. SA WG6 has also agreed on a new study for enhancements to application layer support for V2X services considering 5","secretary_remarks":"Revised to add attachments in SP-190530.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10260,"status":"revised","reservation_date":"2019-05-30 15:14:52","uploaded":"2019-05-30 16:19:15","revisionof":"","revisedto":"SP-190530","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"V2XAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"5GAA WG2, ETSI TC ITS, SA WG2X TC, NGMN Alliance V2X TaskForce","Cc":"TSG SA","lsoriginalls":"S6-191237","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190505.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190530","title":"LS from SA WG6: LS on application layer support for V2X services","source":"SA WG6","contact":"Niranth Amogh","contact-id":39608,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 has finalized the following Release 16 stage 2 normative specifications which support V2X application layer: 1. 3GPP TS 23.286 'Application layer support for V2X services; Functional architecture and information flows' (see attachment). 2. 3GPP TS 23.434 'Service Enabler Architecture Layer for Verticals; Functional architecture and information flows' (see attachment). 3GPP TS 23.434 has specified the (Service Enabler Architecture Layer) SEAL services (e.g. group management, location management, network resource management) which can be commonly used by any vertical application layer including V2X application layer. 3GPP TS 23.286 has specified V2X application enabler layer functions (e.g. V2X service discovery, V2X service continuity, file distribution, application level location tracking, V2X message delivery). Where necessary these functions utilize SEAL services. SA WG6 has also agreed on a new study for enhancements to application layer support for V2X services considering 5","secretary_remarks":"Revision of SP-190505. Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LS's - proposed to note","tdoc_agenda_sort_order":10270,"status":"noted","reservation_date":"2019-06-04 15:17:29","uploaded":"2019-06-04 15:46:52","revisionof":"SP-190505","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"V2XAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"5GAA WG2, ETSI TC ITS, SA WG2X TC, NGMN Alliance V2X TaskForce","Cc":"TSG SA","lsoriginalls":"S6-191237","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_84\/Docs\/SP-190530.zip","group":"SP","meeting":"SP-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]