[{"name":"SP-190003","title":"Draft LTI in reply to LS on Strategies and policies for the deployment of broadband in developing countries","source":"TSG SA","contact":"Erik Guttman","contact-id":18782,"tdoctype":"LS out","for":"Endorsement","abstract":"For 3GPP review: in: TSG SA feedback LS before: 22\/02\/2019 to: 3GPP PCG","secretary_remarks":"For endorsement for forwarding to PCG for approval and transmission. Endorsed by correspondence and forwarded to PCG","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10180,"status":"endorsed","reservation_date":"2019-02-19 08:44:06","uploaded":"2019-02-19 08:44:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP PCG","Cc":"","lsoriginalls":"RP-190004","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190003.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190004","title":"LS from ITU-D SG1: Strategies and policies for the deployment of broadband in developing countries","source":"ITU-D SG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"ITU-D Study Group 1 Rapporteur Group for Question 1\/1 is working on the 'Strategies and policies for the deployment of broadband in developing countries', including 5G (IMT-2020), and would like to collaborate with 3GPP. The scope of work of Question 1\/1 and its objectives can be seen at: https:\/\/www.itu.int\/net4\/ITU-D\/CDS\/sg\/rgqlist.asp?lg=1&sp=2018&rgq=D18-SG01-RGQ01.1&stg=1 We would like to benefit from 3GPP's experience on 5G (IMT-2020) and receive information related with the working area of Question 1\/1. Especially on the following areas; - Information on 3GPP's 5G activities including standardization work. - Information on SDN\/NFV related work for 5G and the importance of SDN\/NFV for the 5G networks and developing countries. - Importance of 5G for the developing countries and use cases. - Policies and regulations that promote increased high-speed, high-quality mobile broadband network connectivity (5G) in developing countries. - Guidelines and standards for the transition from n","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2019-02-19 09:29:45","uploaded":"2019-02-19 09:33:48","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"","lsoriginalls":"SG1RGQ\/REP\/1","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190004.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190005","title":"LS from JCA-IMT2020: LS on Invitation to update the information in the IMT2020 roadmap","source":"JCA-IMT2020","contact":"Scott Mansfield","contact-id":42415,"tdoctype":"LS in","for":"Action","abstract":"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 elaborations 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 addi","secretary_remarks":"Postponed","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10280,"status":"postponed","reservation_date":"2019-02-19 09:29:48","uploaded":"2019-02-19 09:33:48","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU SGs, external IMT-2020 liaison partners","Cc":"","lsoriginalls":"JCA-IMT2020-LS05","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190005.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190006","title":"LS from GSMA: User Plane Security for 5GC Roaming","source":"GSMA","contact":"Scott Bailey","contact-id":71585,"tdoctype":"LS in","for":"Action","abstract":"5GJA welcomes the Release 15 specifications for the SEPP in 3GPP to protect the HTTP-based signalling via the N32 reference point between VPMN and HPMN when both PMNs are using the service-based 5G Core Network. Based on discussion in 5GJA#5 on 7th November 2018, 5GJA also sees a need for security enforcement between UPFs in the VPMN and HPMN via the N9 reference point, to protect the PMN core network. This applies to the Roaming 5G System architecture - Home Routed scenario. The PMN needs to distinguish valid incoming traffic on N9 that belongs to a successfully initiated subscriber session through N32, from any other traffic, where the PMN would only accept the former. 5GJA expects that a solution is flexible enough to allow different levels of protection, ranging from no protection at all, to providing only integrity protection, and to providing integrity protection and confidentiality. Any solution proposed, must take into account impacts to processing capabilities and end-to-end d","secretary_remarks":"Response drafted in SP-190234. Final response in SP-190252","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10310,"status":"replied to","reservation_date":"2019-02-19 09:29:48","uploaded":"2019-02-19 09:33:48","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2, SA WG3","Cc":"","lsoriginalls":"5GJA05_118","lsreply":"SP-190252","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190006.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190007","title":"LS from 5GAA WG4: LS on V2X specification visibility in 3GPP","source":"5GAA WG4","contact":"Philippe Reininger","contact-id":35013,"tdoctype":"LS in","for":"Action","abstract":"5GAA thanks 3GPP for their efforts and work on V2X, particularly for continuing this work in 5G. 5GAA noticed that in the past the 3GPP standardisation of features relevant to vertical industries, like LTE-V2X, was embedded within general technical specifications. Whilst this approach fits well with principles of radio standard specification, the easy identification of vertical features like V2X would greatly facilitate discussions with regulators, other SDOs, OEMs, manufacturers, etc. 5GAA see with the anticipated establishment of the V2X Phase 3 WI a unique opportunity to encourage 3GPP to further highlight its involvement with the automotive industry, as vertical. As such, the 5GAA would like to facilitate the visibility of the automotive related features, various solutions are possible as example: - Have an overall normative dedicated Stage 2 which describes NR-V2X; - Compilation document similar to what was done for NB IoT in Compilation of all Features related to CIoT [RP-161801]","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10360,"status":"noted","reservation_date":"2019-02-19 10:53:32","uploaded":"2019-02-19 10:54:42","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG SA, TSG CT","lsoriginalls":"5GAA_S-190040","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190007.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190008","title":"LS from GSMA 5GJA: HTTP\/s SMS roaming interface evolution","source":"GSMA 5GJA","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Introduction: The GSMA 5G Joint Activity (5GJA) is responsible for all 5G related items and topics within the Networks Group (NG) domain. The GSMA 5GJA will work in cooperation with GSMA working groups, GSMA program, as well as external organizations. The scope of the GSMA 5GJA includes, but is not limited to, the following topics: \u00b7 ? UNI for operator-provided communication services (i.e. Voice, Video, messaging) over 5G ? Guidelines for technical aspects of deployment of 5G. ? Guidelines for 5G roaming and interconnection. Background: GSMA NG welcomes the Release 15 specifications for the SEPP in 3GPP to protect the HTTP-based signalling via the N32 reference point between VPMN and HPMN when both PMNs are using the service-based 5G Core Network. Based on discussion in 5GJA#5 on 7 November 2018, GSMA 5GJA also see a need for SMS roaming interface to benefit from this security improvement. By also including the SMS roaming interface based on HTTP\/S to compliment the MAP and Diameter in","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10350,"status":"noted","reservation_date":"2019-02-19 10:53:32","uploaded":"2019-02-19 10:54:42","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"CT WG4","lsoriginalls":"5GJA5_120","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190008.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190009","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":"Action","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":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10290,"status":"noted","reservation_date":"2019-02-19 10:53:32","uploaded":"2019-02-19 10:54:42","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, 3GPP, ETSI TC NTECH","Cc":"","lsoriginalls":"ls73-11","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190009.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190010","title":"LS from ITU-T SG12: LS on Draft new Recommendation E.RQST - KPI targets for mobile networks","source":"ITU-T SG12","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement is to inform you that the ITU-T Study Group 12 (performance, QoS and QoE) is currently undertaking the development of a new Recommendation to define guidance on the definition of KPI targets for cellular mobile networks with a link with QoS as perceived by end users of services such as voice and data. Many of the identified KPIs and targets to be used in the current draft of the planned new recommendation are originating from work undertaken and technical specifications produced within your working group. Therefore, we request your support and advice on this ongoing work item, whose text has been attached to the present liaison statement. We would be pleased to enter in a fruitful collaboration on this document in the future and will keep you informed of any new revision.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2019-02-19 10:53:32","uploaded":"2019-02-19 10:54:42","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG1, SA WG5","Cc":"","lsoriginalls":"oLS68-td722R2","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190010.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190011","title":"LS from RAN WG1: Reply LS on RAN Impact analysis due to TSN","source":"RAN WG1","contact":"Karri Ranta-aho","contact-id":64268,"tdoctype":"LS in","for":"Information","abstract":"RAN WG1 would like to thank SA WG2 for the LS on RAN Impact analysis due to TSN. RAN WG1 has discussed feasibility and scalability impacts of identified TSN Time synchronization solutions. 2. Feasibility aspects: Deterministic RAN-UE delay required by Solution #17 presents feasibility challenges. RAN WG1 has not identified any feasibility related issues with the other solutions. 3. Scalability aspects: Regarding scalability aspect, SA WG2 asked: 'In addition, SA WG2 would like to request feedback on the scalability on the radio interface for solutions that require transport of gPTP time synchronisation messages using per-UE unicast transport over the air.' The scalability of per-UE unicast is affected by several factors, including the payload size, the frequency the payload needs to be transmitted, SINR geometry of the cell, and the overall deployment. - If the payload size is small, scalability can be achieved more easily than if the payload size is large. - If the payload does not ne","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10210,"status":"noted","reservation_date":"2019-02-19 10:53:32","uploaded":"2019-02-19 10:54:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"FS_NR_IIOT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, RAN WG3, TSG SA","lsoriginalls":"R1-1901442","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190011.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190013","title":"LS from SA WG3: LS on User Plane Security for 5GC Roaming","source":"SA WG3","contact":"Alex Leadbeater","contact-id":71428,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to inform TSG SA that SA WG3 has reviewed the liaison statement from GSMA 5GJA on User Plane Security for 5GC Roaming in SP-181202 \/ S3-190019 and the subsequent Action: set by TSG SA plenary at SA#82 on SA WG3 and SA WG2 to provide guidance to SA on technical solutions to address the issues raised by GSMA. SA WG3 has agreed to extend the scope of the existing study FS_SBA-SEC in the attached S3-190464 to address binding of signalling sessions to N9 sessions and develop the necessary N9 security function to achieve this. SA WG3 consider that this may require a function equivalent to the SEPP used on N32 to be standardised on N9. SA WG3 also considers that work with SA WG2 may be needed to identify any necessary 5GC architecture changes within R16 timescales. The need for any SEPP equivalent N9 functional would be subject to the conclusions of the extended FS_SBA-SEC study. Furthermore, SA WG3 has agreed to add a recommendation to TS 33.501 R15 in attached S3-190408, t","secretary_remarks":"This will be taken into account in the response to GSMA and was then noted.","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10340,"status":"noted","reservation_date":"2019-02-19 10:53:32","uploaded":"2019-02-19 10:54:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"TSG CT, CT WG4","lsoriginalls":"S3-190409","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190013.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190017","title":"LS from SA WG6: Reply LS on Cooperation on Generic Slice Template definition","source":"SA WG6","contact":"Juergen Rurainsky","contact-id":66405,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 would like to thank GSMA for bringing this important topic, the definition of the Generic Slice Template (GST) and Network Slice Type (NEST), to our attention. Public Protection and Disaster Relief (PPDR) operators in SA WG6 confirm the interest to include their perspective and are looking forward to collaborating with GSMA on this topic. SA WG6 plans to analyse the potential of network slicing to enhance Mission Critical services in the ongoing SA WG6 'Study on Mission Critical Services support over 5G System'. Although there are no current plans for SA WG6 to define GST or NEST recommendations, future efforts within SA WG6 could lead to additional feedback to the GSMA request.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10200,"status":"noted","reservation_date":"2019-02-19 10:53:33","uploaded":"2019-02-19 10:54:42","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA5GJA","Cc":"TSG SA","lsoriginalls":"S6-190243","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190017.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190019","title":"LS from JCA-IoT and SC&C: Request to update the IoT and SC&C Standards Roadmap and the list of contact points","source":"ITU-T JCA-IoT and SC&C","contact":"Hyoung Jun Kim","contact-id":46093,"tdoctype":"LS in","for":"Action","abstract":"At the twentieth meeting of the ITU-T Joint Coordination Activity on Internet of Things and Smart Cities and Communities (JCA-IoT and SC&C), which was held in Wuxi, 6 December 2018 it was agreed to request all JCA-IoT and SC&C contacts to update their contact information. At the aforementioned meeting of the JCA-IoT and SC&C it was also agreed to request all contacts to submit their updates to the IoT and SC&C standards roadmap (free download) (Attachment 1). The IoT and SC&C standards roadmap includes a list of IoT and SC&C related standards (both approved and under development) from relevant standards developing organizations (SDOs) and ITU. The IoT and SC&C standards roadmap is a powerful tool to support the efficient coordination of IoT and SC&C -related standardization activities within ITU-T Study Groups and other SDOs. The JCA-IoT and SC&C hosts the IoT standards roadmap in its homepage and maintains it by issuing updates at each JCA-IoT and SC&C meeting. We would appreciate you","secretary_remarks":"Postponed","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10300,"status":"postponed","reservation_date":"2019-02-19 10:53:33","uploaded":"2019-02-19 10:54:42","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"External bodies","Cc":"","lsoriginalls":"ls38_jca-iotscc-o-057","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190019.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190048","title":"LS from RAN WG2: Reply LS on RAN Impact analysis due to TSN","source":"RAN WG2","contact":"Zhenhua Zou","contact-id":73815,"tdoctype":"LS in","for":"Information","abstract":"1. Overall Description: RAN WG2 would like to thank SA WG2 for the LS on RAN impacts analysis due to TSN. RAN WG2 has discussed feasibility and scalability impacts of identified TSN Time synchronization solutions and has come to the following conclusions. Feasibility aspects: Deterministic gNB-UE delay required by Solution #17 presents feasibility challenges. Solution #28.X1 seems similar to Solution #17 and the same feasibility concerns applies to it. Otherwise, all other solutions seem feasible from RAN WG2 perspective, although the details of each solution are not known from the TR 23.734. Additionally, RAN WG2 would prefer that the User Plane AS protocol stack does not need to interpret\/understand information inside (g)PTP packet. Solution #19 is not preferred since it seems to have significant impact due to (g)PTP time-stamping in the User Plane AS protocol stack. On the other hand, Solution #28.X2, Solution #11 Option 2, Solution #11 Option 3 and Solution #11 Option 4 can be cand","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10220,"status":"noted","reservation_date":"2019-03-06 15:08:57","uploaded":"2019-03-06 16:03:43","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG1, RAN WG3, TSG RAN, TSG SA","lsoriginalls":"R2-1902369","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190048.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190052","title":"LS from RAN WG3: LS on Completion of X2 TNL Address Discovery for EN-DC","source":"RAN WG3","contact":"Luis Lopes","contact-id":47178,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 has been working on completion of the X2 TNL Address Discovery feature for EN-DC, which enables an eNB to initiate an X2 interface towards an en-gNB, based on UE reports and without manual configuration. This is the EN-DC equivalent of the Automatic Neighbour Relations feature in LTE. The agreed solution in RAN WG3 involves steps similar to those in LTE, whereby a container ('SON Configuration Transfer') is sent by the initiating eNB towards the MME and is relayed across the S10 interface (if needed), and then sent down to the target eNB, with a response then following the reverse path. The MME does not need to process the container apart from extracting the information required to identify a target eNB (and\/or MME in case S10 relaying is required). In EN-DC, the main difference is that one of the RAN endpoints is an en-gNB (i.e. the container is further relayed within RAN), and additional information is provided to the MME to aid routing. In addition, RAN WG3 has agreed to ena","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10230,"status":"noted","reservation_date":"2019-03-06 15:08:57","uploaded":"2019-03-06 16:03:43","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG4, TSG CT","Cc":"TSG RAN, TSG SA","lsoriginalls":"R3-191119","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190052.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190056","title":"LS on Information on MEC work on 5G","source":"Samsung R&D Institute UK","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 have asked SA to send an LS to ETSI ISG MEC as the information to be sent might need to include approved SA WG2 and SA WG6 study items related to this.","secretary_remarks":"Revised to SP-190228.","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10380,"status":"revised","reservation_date":"2019-03-07 14:38:17","uploaded":"2019-03-07 18:01:47","revisionof":"","revisedto":"SP-190228","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI ISG MEC","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190056.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190143","title":"LS from ETSI ISG PDL: LS to various organisations on the start of ISG PDL activities","source":"ETSI ISG PDL","contact":"Diego Lopez","contact-id":57145,"tdoctype":"LS in","for":"Action","abstract":"Overall description: The Industry Specification Group Permissioned Distributed Ledgers (ISG PDL) has recently started its activities, with the commitment to work in analysing and providing the foundations for the operation of permissioned distributed ledgers, and the ultimate purpose of creating an open ecosystem of industrial solutions to be deployed by different sectors, fostering the application of these technologies, and therefore contributing to consolidate the trust and dependability on information technologies supported by global, open telecommunications networks. The ETSI ISG PDL starts from already available experiences in the field of permissioned distributed ledgers, seeking for the definition of open and well-known operational mechanisms to: - Validate participant nodes. - Scale up ledgers to accommodate more nodes at reasonable throughput. - Decide consensus among the participant nodes. - Publish and execute operations regarding the recorded transactions. - Facilitate the","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2019-03-12 14:34:43","uploaded":"2019-03-12 15:04:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Various organisations","Cc":"","lsoriginalls":"PDL(19)000_009r1","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190143.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190144","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 LS on Reporting All Cell IDs in 5G. RAN WG3 has discussed the matter and enabled a mechanism for Dual Connectivity with 5G, equal to the existing mechanism for LTE and 5G stand-alone: When needed, the Secondary Node reports the secondary serving cell (PSCell) information to the Master Node when the secondary serving cell is selected and then, when it changes; the Master Node reports it then back to the Core Network. There were doubts whether this solution causes excessive signaling in the RAN. A possible mitigation to this drawback is to add a flag from the Core Network to indicate whether PSCell shall be reported. This can be added as an enhancement to the current solution.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10270,"status":"noted","reservation_date":"2019-03-12 14:34:47","uploaded":"2019-03-12 15:04:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3LI","Cc":"TSG SA, SA WG2, SA WG3, TSG RAN, TSG CT, CT WG1, CT WG3, ETSI TC LI","lsoriginalls":"R3-191111","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190144.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190146","title":"LS from SA WG2: LS on Information on MEC work on 5G","source":"SA WG2","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"LS in","for":"Action","abstract":"SA WG2 received an LS from ETSI ISG MEC on Information on MEC work on 5G (MEC(18)000529r1 \/ S2 1901415). SA WG2 believes that the LS relates to SA WG6 and SA WG2 study items that will be sent to TSG SA Meeting #83 for approval. Thus, SA WG2 would like to respectfully asks TSG SA Plenary to review the attached LS from ETSI ISG MEC and take appropriate actions. Action: SA WG2 asks TSG SA to consider the information above and take appropriate actions.","secretary_remarks":"Response drafted in SP-190228. Final response in SP-190251","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10370,"status":"replied to","reservation_date":"2019-03-12 14:34:48","uploaded":"2019-03-12 15:04:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG5, SA WG6","lsoriginalls":"S2-1902907","lsreply":"SP-190251","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190146.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190147","title":"LS from SA WG2: LS on EPS Additional RRM Policy Index","source":"SA WG2","contact":"Chris Pudney","contact-id":1122,"tdoctype":"LS in","for":"Information","abstract":"In December 2018 at SA#82, TSG SA allocated SA WG2 meeting time to the new EPS work described in the SA WG2-endorsed discussion paper S2-1813443. SA WG2 have now approved the related Change Request (CR 3499r2) to TS 23.401 in S2-1902869. One use case underlying this CR is documented in the attached slides set in S2-1901970. Due to the foreseen impacts on RAN (3), perhaps RAN (2) and CT (4) specifications feedback from TSG RAN and TSG CT and highlighted WGs is welcome.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10420,"status":"noted","reservation_date":"2019-03-12 14:34:48","uploaded":"2019-03-12 15:04:57","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, RAN WG3, RAN WG2, TSG CT, CT WG4","Cc":"TSG SA","lsoriginalls":"S2-1902908","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190147.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190204","title":"Discussion on LS on EPS Additional RRM Policy Index","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":68028,"tdoctype":"discussion","for":"Decision","abstract":"Proposal: As described in the discussion part of this document, there are various points which should be discussed and agreed in RAN WGs. As there is still ample time to complete release 16, it is proposed that TSG SA#83 holds the approval of SA WG2 CR S2-1902869 (which is 23.401 CR 3499 on 'Subscriber RRM Group as additional parameter to SPID\/RFSP' in SP-190175) until RAN WG2 and RAN WG3 have had an opportunity to analyse the feature proposal subject of the LS in SP-190147.","secretary_remarks":"A note was added to this report under approval of the CR pack and this was then noted.","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10430,"status":"noted","reservation_date":"2019-03-14 10:17:56","uploaded":"2019-03-15 10:14:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190204.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190211","title":"LS from CT WG4: Reply LS on Completion of X2 TNL Address Discovery for EN-DC","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 thanks RAN WG3 for their LS on Completion of X2 TNL Address Discovery for EN-DC. CT WG4 is fine with the approach preferred by RAN WG3 introducing a new container ('EN-DC SON Configuration Transfer'). CT WG4 will update the GTPv2 specification accordingly.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10240,"status":"noted","reservation_date":"2019-03-15 10:19:17","uploaded":"2019-03-15 10:19:46","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, TSG RAN","Cc":"SA WG2, TSG CT, TSG SA","lsoriginalls":"C4-190589","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190211.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190216","title":"LS from GSMA: LS Reply to 3GPP RAN on Work Status of 5GSI","source":"GSMA","contact":"John Humbert","contact-id":72762,"tdoctype":"LS in","for":"Information","abstract":"Introduction: GSMA Future Networks Programme 5G Status Indicator (5GSI) Task Force is providing 3GPP an update on the status of the work the task force is doing. The task force has had a total of 15 conference calls since July 2018, focussed on the 3 areas of work identified by the LS received from 3GPP: - Definition of the 1-bit indicator upperLayerIndication - Recommendation for a default behaviour of Open Market Devices - Determine the need for and define any additional necessary bits The following is an update on each of the topics.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10440,"status":"noted","reservation_date":"2019-03-18 02:12:35","uploaded":"2019-03-18 02:13:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG SA, TSG CT","lsoriginalls":"5GSI#15 Doc 004","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190216.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190226","title":"LS from TSG CT: Reply LS on Completion of X2 TNL Address Discovery for EN-DC","source":"TSG CT","contact":"Lionel Morand","contact-id":25150,"tdoctype":"LS in","for":"Information","abstract":"TSG CT thanks RAN WG3 for their LS on Completion of X2 TNL Address Discovery for EN-DC. TSG CT would like to inform RAN WG3 that TSG CT has endorsed the feedback from CT WG4 in their reply LS (CP-190180) and the attached CR (CP-190170) has been approved at TSG CT#83. This CR updates the GTPv2 specification (TS 29.274) to enhance the Configuration Transfer Tunnel procedure to support TNL Address discovery via the S1 interface or via inter-system signalling for EN-DC.","secretary_remarks":"Noted","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10250,"status":"noted","reservation_date":"2019-03-19 04:33:01","uploaded":"2019-03-19 04:34:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, TSG RAN","Cc":"TSG SA, SA WG2","lsoriginalls":"CP-190187","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190226.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190228","title":"[Draft] LS on Information on MEC work on 5G","source":"Samsung R&D Institute UK","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 have asked SA to send an LS to ETSI ISG MEC as the information to be sent might need to include approved SA WG2 and SA WG6 study items related to this.","secretary_remarks":"Revision of SP-190056. LATE DOC: Rx 20\/03, 09:00. Response to SP-190146. Revised to SP-190235.","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10390,"status":"revised","reservation_date":"2019-03-19 04:33:01","uploaded":"2019-03-20 07:58:10","revisionof":"SP-190056","revisedto":"SP-190235","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI ISG MEC","Cc":"SA WG2, SA WG6","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190228.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190234","title":"Reply LS on User Plane Security for 5GC Roaming","source":"TSG SA","contact":"Alex Leadbeater","contact-id":71428,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA 5GJA. CC: SA WG3, SA WG2","secretary_remarks":"Response to SP-190006. Revised to SP-190252.","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10320,"status":"revised","reservation_date":"2019-03-20 07:56:32","uploaded":"2019-03-21 05:47:09","revisionof":"","revisedto":"SP-190252","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190234.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190235","title":"[Draft] LS on Information on MEC work on 5G","source":"TSG SA","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 have asked SA to send an LS to ETSI ISG MEC as the information to be sent might need to include approved SA WG2 and SA WG6 study items related to this.","secretary_remarks":"Revision of SP-190228. Revised to SP-190251.","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10400,"status":"revised","reservation_date":"2019-03-20 07:56:32","uploaded":"2019-03-21 05:47:09","revisionof":"SP-190228","revisedto":"SP-190251","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI ISG MEC","Cc":"SA WG2, SA WG5, SA WG6","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190235.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190251","title":"LS on Information on MEC work on 5G","source":"TSG SA","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"To: ETSI ISG MEC. CC: SA WG2, SA WG5, SA WG6. Attachments: SA WG2 and SA WG6 SIDs","secretary_remarks":"Revision of SP-190235. Approved","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10410,"status":"approved","reservation_date":"2019-03-21 05:44:01","uploaded":"2019-03-21 05:47:09","revisionof":"SP-190235","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-190146","lsto":"ETSI ISG MEC","Cc":"SA WG2, SA WG5, SA WG6","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190251.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-190252","title":"Reply LS on User Plane Security for 5GC Roaming","source":"TSG SA","contact":"Alex Leadbeater","contact-id":71428,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA 5GJA. CC: SA WG3, SA WG2","secretary_remarks":"Revision of SP-190234. Approved.","agenda_item_sort_order":12,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10330,"status":"approved","reservation_date":"2019-03-21 05:44:01","uploaded":"2019-03-21 05:47:09","revisionof":"SP-190234","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-190006","lsto":"GSMA","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_83\/Docs\/SP-190252.zip","group":"SP","meeting":"SP-83","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]