[{"name":"SP-180927","title":"LS from GSMA: LS Reply on Control Plane Solution for Steering of Roaming in 5GS","source":"GSMA","contact":"David Hutton","contact-id":33294,"tdoctype":"LS in","for":"Action","abstract":"Introduction: GSMA Wholesale Agreements & Solutions (WAS) Working Group thank 3GPP for their Liaison Statement on 5G Steering of Roaming. The liaison statement has been discussed within the Wholesale Agreements (WAGREE) and Wholesale Solutions (WSOLU) groups to analyse the commercial impacts of the 5G Steering of Roaming Control Plane Solution. Please note that further responses from GSMA groups responsible for Fraud and Security and Technical aspects may provide further feedback. Discussion: GSMA WSOLU\/WAGREE have analysed the liaison statement and the attached change requests and have the following questions for clarifications and related concerns of commercial impacts related to the 5G steering of roaming control plan solution. 1. Can 3GPP clarify the justification for developing an alternative SoR solution to the current mechanisms that are deployed in commercial networks to date? Deploying new solutions in network deployments does have associated commercial costs. 2. In terms of c","secretary_remarks":"Postponed SP-180872 from TSG SA#81. Response drafted in SP-181194. Final response in SP-181244","agenda_item_sort_order":11,"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":"replied to","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:27:58","revisionof":"SP-180872","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG CT, SA WG3, CT WG1, CT WG4, CT WG6","Cc":"","lsoriginalls":"WSOLU 34_007","lsreply":"SP-181244","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180927.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180934","title":"LS from 5GAA WG2: LS Reply to 3GPP on Time-Criticality of In-Advance QoS Notification","source":"5GAA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"5GAA WG2 would like to thank SA WG2 for the LS response to 3GPP (S2-185846\/S2-1810867) on the following aspects: 1. Regarding REQ.6 and REQ.7 {...}. 2. Regarding time-criticality {...}. 3. Regarding REQ.2 and REQ.3.","secretary_remarks":"Noted","agenda_item_sort_order":11,"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":"noted","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:27:59","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG1, TSG SA","lsoriginalls":"5GAA_A-180328","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180934.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180935","title":"LS from GSMA: Cooperation on Generic Slice Template definition","source":"GSMA","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"The GSMA 5G Joint Activity would like to draw your attention to the document that defines and provides a description of the Generic Slice Template (GST). The GST is a set of attributes (e.g. supported throughput, supported functionality, provided application programming interfaces (APIs), etc.) that characterize any slice. It contains the attribute names, definitions and units. These attributes can be used by vendors, mobile network operators and slice customers, in addition to other proprietary attributes, if custom slices are desired. By filling the GST with values for all or a subset of the attributes it is possible to describe the structure of a network slice. A GST filled with values is called Network Slice Type (NEST). A NEST serves many purposes: - Vendors can use a NEST to define the features of their products - Vertical Industry customers (slice customers) can use a NEST as a reference to understand the contractual agreements with the network operator - Network operators (slic","secretary_remarks":"Noted","agenda_item_sort_order":11,"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":"noted","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:27:59","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"TSG SA, SA WG1, SA WG2, SA WG3, RAN WG3, SA WG5","lsoriginalls":"5GJA05_110","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180935.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180936","title":"LS from IEEE 802.11: IEEE 802.11 study results benchmarking 802.11ax capabilities to meet Indoor Hotspot test environment defined by IMT-2020","source":"IEEE 802.11","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"The IEEE 802.11 WG would like to kindly inform you of the results of the studies documented in [1], [3], [4], and [5] regarding benchmarking of IEEE P802.11ax [1] capabilities in the Indoor Hotspot environment defined by IMT-2020 ([6], [7]). The IEEE 802.11WG believes these studies conclusively show that: ? P802.11ax [1] meets the salient IMT-2020 requirements for the Indoor Hotspot environment, including mobility. The IEEE 802.11 WG invites you to consider these results in the context of ongoing work regarding WLAN interworking with 3GPP systems, and looks forward to a continued, productive exchange of information.","secretary_remarks":"Noted","agenda_item_sort_order":11,"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":"noted","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:27:59","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"IEEE 802 EC, IEEE 802.1 WG, WFA, WBA","lsoriginalls":"2018-11-20-3GPP-11ax","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180936.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180937","title":"LS from ISO TC204 WG16: Liaison Request between 3GPP SA & ISO TC204 WG16","source":"ISO TC204 WG16","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"ISO TC204 WG16 is a standards development organization within the Intelligent Transportation Solutions Technical Committee TC204 focused on wireless communciations enabling V2X as well as defining the ITS Station Architecture. The ITS Station Architecture facilitates usage of multiple communication mediums on a singular platform thus providing a communications agnostic system for V2X services. ISO TC204 WG16 is developing international standards ISO 17515-2 Intelligent transport systems -- Communications access for land mobiles (CALM) -- Evolved universal terrestrial radio access network (EUTRAN) -- Part 2: Device to device communications (D2D) and ISO 17515-3 Intelligent transport systems -- Evolved-universal terrestrial radio access network -- Part 3: LTE-V2X. These standards will enable use of LTE-D2D and LTE-V2X as ITS station access technologies by referencing specifications from 3GPP. ISO 17515-2 and ISO 17515-3 will specify details of the 'Communication Adaptation Layer' (CAL) a","secretary_remarks":"Response drafted in SP-181200. Final response in SP-181228","agenda_item_sort_order":11,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10470,"status":"replied to","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:27:59","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"","lsoriginalls":"2018-11-20-3GPP-11ax","lsreply":"SP-181228, SP-181228","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180937.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180938","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":"This LS was postponed.","agenda_item_sort_order":11,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10520,"status":"postponed","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:00","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_82\/Docs\/SP-180938.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180939","title":"LS from IALA ENAV22: Reply to LS on the information of the 3GPP standardization applicable to maritime usage and the request of the additional maritime related information","source":"IALA ENAV22","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Introduction IALA would like to thank SA WG1 for their liaison regarding the work of 3GPP (ENAV22 10.3.5). This reply liaison is to provide IALA feedback on the three questions posed by SA WG1. IALA's feedbacks on three SA WG1's questions IALA reviewed the questions posed by SA WG1. IALA is pleased to provide the following responses: 1 Minimum value of the communication range for the direct vessel to vessel communication ? In terms of ship to ship communications, VHF range is normally considered to be line of site, noting digital communications has slightly larger range. For digital communications ranges of 20-30 NM can be expected. For satellite-based communications, range would be expected to be global, noting specific requirements for polar regions. 2 Status of legacy communication methods used for the navigation ? If legacy communication methods used for the navigation means ship to ship, ship to shore, and shore to ship communication, communication technologies are identified in t","secretary_remarks":"Noted","agenda_item_sort_order":11,"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":"noted","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"TSG SA","lsoriginalls":"ENAV22-12.1.19","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180939.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180940","title":"LS from JCA-IMT2020: LS on Invitation to update the information in the IMT2020 roadmap","source":"JCA-IMT2020","contact":"Maurice Pope","contact-id":648,"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":"This LS was postponed.","agenda_item_sort_order":11,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10530,"status":"postponed","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:00","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_82\/Docs\/SP-180940.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180943","title":"LS from ETSI CTI Plugtests: Observations on standards and technical constraints from 2nd MCPTT Plugtests","source":"ETSI CTI Plugtests","contact":"Maurice Pope","contact-id":648,"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 to MCPTT Standards: Missing, erroneous or ambiguous definition of procedures in 3GPP's MCPTT TSs. - Technical constraints: Related to implementation issues, not covered by the standards, but which need to be faced by MCX vendors in most deployments. The reader should note that 3GPP TS approved in December 2017 (mostly 14.4.0) were considered for the second Plugtests event and some fields may have changed or have been already solved. The 2nd MCPTT 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 been sta","secretary_remarks":"Noted","agenda_item_sort_order":11,"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":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6, CT WG1, SA WG3","Cc":"TSG CT, TSG SA","lsoriginalls":"LS_from_2ndMCPTTPlugtests_To_CT1-SA6","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180943.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180944","title":"LS from CT WG1: Reply LS on Control Plane Solution for Steering of Roaming in 5GS","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks CT for their LS on Control Plane Solution for Steering of Roaming (CP-SoR) in 5GS in CP-182234\/C1-186301. Please find the answers to the questions in the GSMA LS below: {...}","secretary_remarks":"Noted","agenda_item_sort_order":11,"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":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT","Cc":"SA WG3, CT WG4, CT WG6, TSG SA","lsoriginalls":"C1-186841","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180944.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180945","title":"LS from CT WG1: LS on Observations from 2nd MCPTT Plugtests","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 have received your liaison 'Observations on standards and technical constraints from 2nd MCPTT Plugtests' (C1-186346) and wish to extend our appreciation for this input to our work. CT WG1 member companies have begun to work on the problems noted in your liaison. We wish to inform you that several fixes were applied at the current meeting (CT WG1 Meeting 112bis), and more fixes are expected at upcoming meetings. We welcome this input. We also would note that the delegates at Plugtest are probably the experts most familiar with the problems found and the solutions that may apply. Accordingly, it would be most efficient if the 3GPP member companies present in Plugtest directly prepare change requests to 3GPP specifications and bring them to the appropriate 3GPP working groups as direct company contributions. While Plugtest reports from ETSI CTI are indeed welcome, such direct company contributions are likely to produce specifications with the correct solutions most quickly. CT WG1","secretary_remarks":"Noted","agenda_item_sort_order":11,"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":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:01","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI CTI","Cc":"TSG CT, TSG SA, SA WG3, SA WG6","lsoriginalls":"C1-186964","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180945.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180956","title":"LS from SA WG3: Reply LS on Control Plane Solution for Steering of Roaming in 5GS","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"In TSG SA#81 meeting, SA WG3 were asked to consider the LS from GSMA in S3-183285\/SP-180872 and provide information to SA#82, so that TSG SA#82 will gather the final resulting reply for GSMA (c.f., draft SA#81 Meeting report (AP 81\/1)\/SA WG3 chairman's report on last SA plenary (S3-183203)). SA WG3 answers the GSMA questions as follows: 3. Security a. GSMA WAS requires that the VPLMN does not have visibility of PLMN list. Can 3GPP confirm that the PLMN list is encrypted and the contents are not visible to the VPLMN? Visibility of this PLMN list by the VPLMN does have significant commercial implications. [SA WG3 answer] -> There are two possible data types transported as specified by CT WG1 in 3GPP TS 24.501 and it is up to the HPLMN as to which type is used:- - If 'list type' value '1' then the roaming list is in clear and visible to the VPLMN. For this data type the List is generated by the UDM and terminates in the ME. This list is integrity protected so alteration in transit can be","secretary_remarks":"Noted","agenda_item_sort_order":11,"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":"noted","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-SEC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, CT WG1","Cc":"CT WG4, CT WG6, TSG CT","lsoriginalls":"S3-183715","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180956.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180958","title":"LS from SA WG5: LS reply to ITU-T SG13 on draft Recommendation Y.3103","source":"SA WG5","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks ITU-T SG13 for their LS on consent of draft Recommendation Y.3103 (formerly Y.IMT2020-BM) (SG13-LS63), which describes business roles, business role-based models and best practice use cases in IMT-2020 from different relevant perspectives. SA WG5 would like to inform ITU-T SG13 about the definition of business roles for 5G networks and network slicing management in Rel-15 TS 28.530 (Management and orchestration; Concepts, use cases and requirements) - clause 4.8 (http:\/\/www.3gpp.org\/ftp\/\/Specs\/archive\/28_series\/28.530\/). {...}","secretary_remarks":"Noted","agenda_item_sort_order":11,"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":"noted","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NETSLICE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITUT SG13","Cc":"TSG SA, ITUT SG2, ITUT SG11, ITUT SG15, ITUT SG16, ITUT SG20, SA WG1, NGMN, ETSI ISG NFV","lsoriginalls":"S5-186320","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180958.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180961","title":"LS from SA WG5: Reply LS on Reply LS from CT to SA5 on API specification and API version number maintenance","source":"SA WG5","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks CT for their LS on API specification and API version number maintenance. SA WG5 OAM would like to get the written proposal on the API specification and API version number to be able to consider what impacts it would have to the work in SA WG5 OAM. SA WG5 Charging has already considered the 'Principles and Guidelines for Services Definition' TS 29.501 during their stage 3 work on 5G API. SA WG5 CH expects any new recommendations and guidelines further clarified and concluded by CT WGs to be reflected in a new version of this specification, which could also be considered as much as possible, whenever no issue is identified during the implementation.","secretary_remarks":"Noted","agenda_item_sort_order":11,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10550,"status":"noted","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT","Cc":"CT WG4, CT WG3, TSG SA, SA WG6","lsoriginalls":"S5-187336","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180961.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180962","title":"LS from ITU-T WP 1\/13: LS on consent of Recommendation Y.3103 (formerly Y.IMT2020-BM)","source":"ITU-T WP 1\/13","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"ITU-T SG13 thanks SA WG5 for your reply to our LS on consent of Recommendation Y.3103 (formerly Y.IMT2020-BM) including information on your relevant work. ITU-T SG13 has read and considered TS 28.530. We understand from the scope of TS 28.530 that it specifies 'concepts, use cases and requirements for management of network slicing' and defines roles from network slicing management point of view. ITU-T Y.3103 defines roles, role-based models and best practice use cases of IMT-2020 from business point of view. Because of their different points of view, TS 28.530 and Y.3103 address different models. Regarding the slice related terminology, in ITU-T IMT-2020 related Recommendations we do not use the term 'subnet' in order to avoid confusion with the term commonly used in IP networking. SG13 looks forward to continue collaboration with SA WG5 in the future.","secretary_remarks":"Noted","agenda_item_sort_order":11,"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":"noted","reservation_date":"2018-11-27 13:02:42","uploaded":"2018-12-04 13:28:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5, ITU-T SG2, ITU-T SG11, ITU-T SG15, ITU-T SG16, ITU-T SG20, TSG SA, SA WG1, NGMN, ETSI ISG NFV","Cc":"","lsoriginalls":"SG13-LS80","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-180962.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181146","title":"LS from CT WG1: LS on questions from ISO TC204 WG16 regarding V2X message family and L3 protocol data unit types","source":"CT WG1","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Action","abstract":"It has come to the attention of CT WG1 that ISO TC204 WG16 sent an LS on 'Liaison Request between TSG SA & ISO TC204 WG16' to SA requesting information on the following points: - Definition of 'V2X message family' and 'L3 protocol data unit types'. We understand that we can refer to C51 specification TS 24.386, but a diagram or map would be helpful Since TS 24.386 is within CT WG1's remit, CT WG1 would like to provide SA with the following information as input into SA's answer to ISO TC204 WG16 {...} Action: CT WG1 asks SA to take the above information into account for their answer to ISO TC204 WG16.","secretary_remarks":"Noted","agenda_item_sort_order":11,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10500,"status":"noted","reservation_date":"2018-12-04 05:07:32","uploaded":"2018-12-04 13:59:29","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2","lsoriginalls":"C1-188592","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181146.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181149","title":"LS from SA WG2: Reply LS on ISO 17515-3 comment resolution","source":"SA WG2","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS in","for":"Action","abstract":"SA WG2 is made aware of the ISO TC204 WG16 LS on ISO 17515-3 comment resolution (Liaison Request between TSG SA & ISO TC204 WG16: S2-1812443) to TSG SA. Within the LS, there are specific questions raised for SA WG2 and CT WG1 to answer. Regarding the question from ISO TC204 WG16, SA WG2 would like to provide the answer as follows: Question: The use of PSID\/ITS-AID in determining Layer 2 destination ID. ISO TC204 experts are divided on whether the ITS-AID is used as a lower layer address (which would be problematic) or a 3GPP mapping is used. We request a detailed explanation for L2 ID and its configurable mapping table. SA WG2 answer: The use of L2 ID is specified in 3GPP TS 23.285, and is available from 3GPP website http:\/\/www.3gpp.org\/ftp\/\/Specs\/archive\/23_series\/23.285. Specifically, the relationships between ITS-AID and the destination L2 ID are explained in clause 4.4.1.1.2. The ITS-AID is not used directly as a lower layer address (the destination L2 ID). They are of different fo","secretary_remarks":"Noted","agenda_item_sort_order":11,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10510,"status":"noted","reservation_date":"2018-12-04 05:07:32","uploaded":"2018-12-04 13:59:29","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"CT WG1","lsoriginalls":"S2-1812848","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181149.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181194","title":"[DRAFT] Reply LS on Control Plane Solution for Steering of Roaming in 5GS","source":"Samsung R&D Institute UK","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA NG, GSMA NG SIGNAL, GSMA WAS, GSMA FASG. CC: TSG CT, SA WG3, CT WG1, CT WG4, CT WG6","secretary_remarks":"Response to SP-180927. Revised to SP-181227.","agenda_item_sort_order":11,"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":"revised","reservation_date":"2018-12-06 15:12:58","uploaded":"2018-12-06 15:51:00","revisionof":"","revisedto":"SP-181227","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG, GSMA NG SIGNAL, GSMA WAS, GSMA FASG","Cc":"TSG CT, SA WG3, CT WG1, CT WG4, CT WG6","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181194.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181200","title":"Reply LS on ISO 17515-3 comment resolution","source":"QUALCOMM Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"Responds to LS from ISO TC204 WG16. To: ISO TC204 WG16. CC: CT WG1, SA WG2","secretary_remarks":"Response to SP-180937. Revised to SP-181228.","agenda_item_sort_order":11,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10480,"status":"revised","reservation_date":"2018-12-06 16:54:12","uploaded":"2018-12-06 18:16:23","revisionof":"","revisedto":"SP-181228","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"V2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ISO TC204 WG16","Cc":"CT WG1, SA WG2","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181200.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181201","title":"LS from CT WG4: Reply LS on API specification and API version number maintenance","source":"CT WG4","contact":"Lionel Morand","contact-id":25150,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks TSG CT for the Reply LS on API specification and API version number maintenance (CP-182239\/C4-187297). Based on the TSG CT\/TSG SA feedback, CT WG3 and CT WG4 have further reconsidered the API version number pattern and the related version control mechanism used for the APIs used over the Service-Based Interfaces (SBI). It has been concluded to remove the release field ('Rn') from API version numbers in order to follow more closely the principles of the Semantic Versioning. A set of rules, illustrated with examples, have been provided to understand how and when increment each version field while maintaining the compatibility with the existing 3GPP working procedures. In particular, it has been clarified the support of backward (in)compatible changes within a release and across multiple releases. The agreed CR (C4-188645) is attached to this LS. CT WG3 and CT WG4 have followed the CT recommendation regarding the need for separate OpenAPI files. At each plenary, a separate O","secretary_remarks":"Noted","agenda_item_sort_order":11,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10540,"status":"noted","reservation_date":"2018-12-06 18:20:55","uploaded":"2018-12-06 18:30:42","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT, TSG SA","Cc":"CT WG3, SA WG5, SA WG6","lsoriginalls":"C4-188646","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181201.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181202","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":"This LS was postponed.","agenda_item_sort_order":11,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10560,"status":"postponed","reservation_date":"2018-12-06 18:51:17","uploaded":"2018-12-06 18:51:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2, SA WG3","Cc":"","lsoriginalls":"5GJA05_118","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181202.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181207","title":"LS from GSMA: LS Reply to 3GPP RAN on Work Status of 5GSI","source":"GSMA","contact":"Mark A. Lipford","contact-id":36056,"tdoctype":"LS in","for":"Information","abstract":"1 Introduction: GSMA Future Networks Programme 5G Indicator Task Force is providing 3GPP an update on the status of the work the group is doing. The task force has had a total of 10 conference calls since July 2018, focused on the 3 areas of work identified by the LS received from 3GPP (reference). - Definition of the 1-bit indicator upperLayerIndication - Determine the need for and define any additional necessary bits - Recommendation for a default behaviour of Open Market Devices. The following is an update on each of the topics. 2 Work Status: The task force has been actively working primarily on several topics that are germane to 5G Indication in order to address the three aspects identified by 3GPP in their liaison to GSMA. 2.1 Definition of the 1-bit indicator: The group is discussing what the upperLayerIndication bit means and when should it be used. Several proposals have been submitted on the definition. The 5GSI is converging on a definition, but has not reached a consensus.","secretary_remarks":"Noted","agenda_item_sort_order":11,"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":"noted","reservation_date":"2018-12-07 14:13:13","uploaded":"2018-12-07 14:13:38","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG SA, TSG CT","lsoriginalls":"5GSI10 Doc 003","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181207.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181212","title":"LS from IEEE P802.11: IEEE 802.11 study results benchmarking 802.11ax capabilities to meet Indoor Hotspot test environment defined by IMT-2020","source":"IEEE P802.11","contact":"Sindhu Verma","contact-id":57333,"tdoctype":"LS in","for":"Information","abstract":"This document presents the self-evaluation of 802.11ax vis-\u00e0-vis the IMT-2020 minimum requirements for the Indoor Hotspot test environment of the eMBB usage scenario [2]. The self-evaluation follows the methodology specified in [2]. This document is a summary of the results presented to IEEE 802.11 in [3], [4] and [5] with some additional observations. R6 includes minor modifications of editorial nature suggested during the AANI SC session, Monday, November 12, PM2. R7 corrects the dates of references 4, 5 and 5 6 and clarifies reference 7.","secretary_remarks":"Noted","agenda_item_sort_order":11,"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":"2018-12-10 08:42:17","uploaded":"2018-12-10 08:42:43","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"IEEE 802 EC, IEEE 802.1 WG, WFA, WBA","lsoriginalls":"2018-11-20-3GPP-11ax","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181212.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181226","title":"LS from TSG CT: LS on request from SA for consolidation of CT WGs responses to LS from GSMA WSOLU\/WAGREE in SP-180872","source":"TSG CT","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"As per the request from TSG SA recorded in the draft SA#81 meeting report: Steering of Roaming (SoR) activity, related to the LS from GSMA (SP-180872), will continue in diverse WGs. In TSG CT, replies will come from CT WGs to be gathered by TSG CT. (SP-180877). In TSG SA, by SA WG3 and SA WG3LI, to be sent to TSG SA. TSG SA#82 will gather the final resulting reply for GSMA. (This was achieved by giving SA WG3 and SA WG3-LI this Action: item in the TSG SA#81 report). Please find the consolidation by TSG CT of the LS replies from the CT WG1 WG and the CT WG6 WG on the questions posed by GSMA WSOLU\/WAGREE on the topic of steering of roaming:. Action: TSG CT asks TSG SA to use the above approved consolidated CT input in the LS response back to GSMA WSOLU\/WAGREE on steering of roaming.","secretary_remarks":"Noted","agenda_item_sort_order":11,"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":"2018-12-13 08:20:43","uploaded":"2018-12-13 08:47:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"","lsoriginalls":"CP-183240","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181226.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181227","title":"[DRAFT] Reply LS on Control Plane Solution for Steering of Roaming in 5GS","source":"TSG SA","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA NG, GSMA NG SIGNAL, GSMA WAS, GSMA FASG. CC: TSG CT, SA WG3, CT WG1, CT WG4, CT WG6","secretary_remarks":"Revision of SP-181194. Revised to SP-181244.","agenda_item_sort_order":11,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10450,"status":"revised","reservation_date":"2018-12-13 08:20:43","uploaded":"2018-12-14 07:18:10","revisionof":"SP-181194","revisedto":"SP-181244","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG, GSMA NG SIGNAL, GSMA WAS, GSMA FASG","Cc":"TSG CT, SA WG3, CT WG1, CT WG4, CT WG6","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181227.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181228","title":"Reply LS on ISO 17515-3 comment resolution","source":"TSG SA","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"To: ISO TC204 WG16. CC: CT WG1, SA WG2, SA WG6, SAE CV2X TC","secretary_remarks":"Revision of SP-181200. Approved","agenda_item_sort_order":11,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10490,"status":"approved","reservation_date":"2018-12-13 08:20:43","uploaded":"2018-12-14 07:18:10","revisionof":"SP-181200","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"V2XARC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-180937","lsto":"ISO TC204 WG16","Cc":"CT WG1, SA WG2","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181228.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-181244","title":"Reply LS on Control Plane Solution for Steering of Roaming in 5GS","source":"TSG SA","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA NG, GSMA NG SIGNAL, GSMA WAS, GSMA FASG. CC: TSG CT, SA WG3, CT WG1, CT WG4, CT WG6. Attachments: SP-181226, SP-180956","secretary_remarks":"Revision of SP-181227. Approved","agenda_item_sort_order":11,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10460,"status":"approved","reservation_date":"2018-12-14 06:50:07","uploaded":"2018-12-14 14:37:54","revisionof":"SP-181227","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-180927","lsto":"GSMA NG, GSMA NG SIGNAL, GSMA WAS, GSMA FASG","Cc":"TSG CT, SA WG3, CT WG1, CT WG4, CT WG6","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_82\/Docs\/SP-181244.zip","group":"SP","meeting":"SP-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]