[{"name":"SP-180629","title":"LS from ESOA: Liaison ESOA (EMEA Satellite Operators Association) on 5G for Satellite Systems","source":"ESOA","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Introducing ESOA: The EMEA Satellite Operators Association (ESOA) has been the voice of Europe's satellite operators since March 2002 and in 2015, it expanded to cover operators in the EMEA region. ESOA is the world's only CEO-driven satellite association and leads a coordinated and impactful response to the global challenges and opportunities the commercial satellite communications sector faces. Today, the Association represents all satellite operators from the EMEA region and other companies that engage in satellite-related activities. It offers a unified voice for the world's largest satellite operators and important regional operators towards all international, regional and national organisations and regulators. Through a minimal infrastructure providing ubiquitous coverage, satellites allow communications across national boundaries, without discriminating on the basis of economic differences between nations. Overall, satellite operators and their services represent two thirds of t","secretary_remarks":"Noted","agenda_item_sort_order":10,"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":"2018-08-08 12:23:05","uploaded":"2018-08-08 12:27:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1 and  SA2","Cc":"TSG RAN","lsoriginalls":"Liaison Statement ESOA 3GPP","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180629.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180630","title":"LS from ETSI ISG NFV: LSout to various organisations on usage of NFV Specifications","source":"ETSI ISG NFV","contact":"Diego Lopez","contact-id":57145,"tdoctype":"LS in","for":"Action","abstract":"ETSI ISG NFV is assessing the use and adoption of the Group Specification and Group Reports that have been produced by the ISG. To realize this task, the ISG has an ongoing work item (DMI\/NFV-EVE015) covering the gathering of information across diverse industry stakeholders (including standardization bodies, among which your organization is included). More information about the NFV-EVE015 miscellaneous item is available on the following link: https:\/\/portal.etsi.org\/webapp\/WorkProgram\/Report_WorkItem.asp?WKI_ID=53588 In this context, ETSI ISG NFV would like your organisation to identify: - which ETSI NFV specifications are used in the course of your activities, - which ETSI NFV specifications are not used (when they could be), and why, and - which type of specifications or technical work are perceived as missing and should be developed (stage 3, \u2026) All ETSI NFV Specifications drafts are available in the ISG Open Area (http:\/\/docbox.etsi.org\/ISG\/NFV\/Open\/). Officially published ETSI NFV","secretary_remarks":"Noted","agenda_item_sort_order":10,"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":"2018-08-08 12:23:05","uploaded":"2018-08-08 12:27:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP, BBF, TM Forum, MEF, ONF, ETSI ZSM, ETSI MEC","Cc":"","lsoriginalls":"NFV(18)000145r3","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180630.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180632","title":"LS from TSG RAN: LS on 3GPP Interface transport protocol port number assignment","source":"TSG RAN","contact":"Georg Mayer","contact-id":9175,"tdoctype":"LS in","for":"Information","abstract":"TSG RAN would like to thank IANA and IETF for the assignment of numbers for 3GPP specific protocols and applications. During the last 20 years, 3GPP was granted about 13 port allocations for transport port protocols used over 3GPP interfaces which today are widely deployed and used for many different scenarios. Examples for those are RNSAP, S1, Xn, F1, \u2026 Recently, IANA rejected the request for a new transport protocol port number designated for the E1 interface. The E1 interface is part of the NR logical architecture for 5G. 3GPP understands that IANA is rethinking its policy for assigning SCTP port numbers. However, 3GPP is currently finalising the new 5G radio access, including network and interface aspects, for which imminent deployments are foreseen. The continued cooperation of IANA to support and facilitate 5G adoption by following past practices, will be highly appreciated.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2018-08-08 12:23:05","uploaded":"2018-08-08 12:27:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IETF, IANA","Cc":"TSG SA, TSG CT, RAN WG3, CT WG1","lsoriginalls":"RP-181421","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180632.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180635","title":"LS from OMA DMSE: LwM2M v1.1 Release Approval","source":"OMA DMSE","contact":"Padmakumar Subramani","contact-id":69258,"tdoctype":"LS in","for":"Information","abstract":"This liaison is provided to announce the Approval of the Lightweight Machine 2 Machine version 1.1 (LwM2M v1.1) specifications. The Device Management and Service Enablement Working Group at OMASpecWorks would like to raise awareness as well as encourage incorporation of the v1.1 specifications in your work. The goal of the LwM2M v1.1 specifications is to provide benefit across the industry for device management as well as for service enablement. Requested Action(s): The OMASpecWorks DMSE WG encourages the addressed organizations to incorporate LwM2M v1.1 into the relevant IoT areas of Device Management and Service Enablement. Organizations such as GSMA, oneM2M and OMASpecWorks IPSO WG have defined the necessary objects to enable multiple service needs on top of LwM2M. The OMA Naming Authority (OMNA) which is the object registry can be referred to for those objects http:\/\/www.openmobilealliance.org\/wp\/OMNA\/LwM2M\/LwM2MRegistry.html as well the LwM2M core objects. OMASpecWorks would like","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2018-08-09 08:18:26","uploaded":"2018-08-09 08:21:10","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG RAN, TSG CT, AIOTI, BBF, Eclipse, ETSI, ETSI SmartM2M, Fairhair Alliance, GCF, Global Platform, GSMA, ITU-T, IETF, IETF IoT Directorate, IETF Core, IIC, LoRA Alliance, OGC, OCF, OMS, oneM2M, Thread, TTA, W3C, WBA, WFA, Zigbee Alliance","Cc":"","lsoriginalls":"OMA-LS_1089","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180635.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180636","title":"LS from BBF: Response to SA WG2 liaison S2-183036 on 'general status of work'","source":"BBF","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Dear colleagues, BBF has progressed its study of converged wireline-wireless networks that use the 5G Core Network (5GC). As a follow-up to liaison LIAISE-120 which contained a first set of results, please find attached two documents that reflect the current state of our study work on FMC. The documents are SD-420R2 and 'BBF WWC WA Recommendations and request for Feedback from SA WG2'. The latter document, an extract of SD-420R2, is designed to highlight specific items BBF would appreciate being taken into account by 3GPP and would be interested in receiving feedback upon. Our reason for liaising both is that SD-420R2 is intended to provide context and the extract is intended to provide focus. Please note that SDs are BBF internal study documents and are not published and thus must not be used as references. BBF would like to advise 3GPP that we have decided to focus on three service models to be supported by three deployment scenarios (integration, interworking, FWA). These are elabor","secretary_remarks":"Noted","agenda_item_sort_order":10,"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":"2018-08-14 12:31:24","uploaded":"2018-08-14 12:35:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"SA WG3, SA WG5","lsoriginalls":"LIAISE-208","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180636.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180668","title":"LS from 5GAA WG2: LS on Requirements to enable Predictive QoS for Automotive industry","source":"5GAA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"5GAA WG2 NESQO work item applied an iterative method on the following 6 uses cases with an intention to identify requirements for Rel-16 in order to support Predictive QoS: 1. RT Situation Awareness and High Definition Map (Hazardous Location Warning) 2. Software Update 3. Tele-Operated Driving 4. High-Density Platooning 5. Advanced Safety (Lane Merge) 6. Infotainment Based on the iterative analysis applied, 5GAA was able to formulate requirements for predictive QoS use for V2X Predictive QoS is already under study in SA WG2, more specifically UC12 ('NWDA-Assisted predictable network performance') of TR 23.791 v0.4.0. 5GAA believes that the identified requirements can be considered as part of FS_eNA and\/or FS_eV2XARC. In this respect, with the timely capturing of NESQO requirements, 5GAA believes that the automotive industry will get desired predictive QoS feature standardised in Rel-16 time frame. As notified earlier, the NESQO work will continue till Q1 2019 and if required, 5GAA may","secretary_remarks":"Noted","agenda_item_sort_order":10,"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":"2018-08-16 13:40:34","uploaded":"2018-08-16 13:40:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG1","Cc":"TSG SA","lsoriginalls":"5GAA_A-180265","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180668.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180683","title":"LS from ETSI TC DECT: Interworking of DECT technology with 3GPP networks","source":"ETSI TC DECT","contact":"Guenter Kleindl","contact-id":580,"tdoctype":"LS in","for":"Action","abstract":"ETSI TC DECT is working on the evolution of the DECT family of standards (DECT, DECT ULE). DECT is part of the IMT-2000 family of standards called IMT-2000 FDMA\/TDMA and is so far the only IMT standard available for license-exempt or de-licensed operation in IMT bands. ETSI TC DECT is currently following two parallel development paths: DECT evolution and DECT-2020. DECT evolution is an update of the DECT standard to improve support of applications regarding latency, data-rate, and reliability based on the latest existing chipsets. DECT-2020 updates the air interface to OFDM FDMA\/TDMA and aims especially on support for URLLC and mMTC use cases in end-user deployed and operated networks. ETSI DECT-2020 is a candidate for being part of the IMT-2020 family of standards. We noted that 3GPP has running activities to interwork or integrate non-3GPP networks to its eco-system. As you may be aware DECT has interworking profiles available for interworking with GSM and UMTS networks. Because DECT","secretary_remarks":"Response drafted in SP-180886. Final response in SP-180924","agenda_item_sort_order":10,"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":"replied to","reservation_date":"2018-08-28 10:52:57","uploaded":"2018-08-28 10:54:08","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2","lsoriginalls":"DECT(18)000106","lsreply":"SP-180924, SP-180924","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180683.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180794","title":"LS from CT WG4 chairman: LS on API specification and API version number maintenance","source":"CT WG4","contact":"Lionel Morand","contact-id":25150,"tdoctype":"LS in","for":"Action","abstract":"The following API versioning model has been agreed in the 3GPP TS 29.501, providing the guidelines for the design of SBI API in the 5GC. The API version numbers shall consist of at least 4 fields, following a MAJOR.RELEASE.MINOR.PATCH pattern, in which the MAJOR, MINOR and PATCH field values are set according to the Semantic Versioning Specification [17] with exceptions for 3GPP releases under development. Optionally, additional fields can be added after the fourth field. At the first publication of the 3GPP Technical Specification defining the API, the version number of the API shall be set to '1. Rn.0.0', where n is the number of the 3GPP release. Some questions were raised on the handling of this API version and the consequence for the API specification management. After discussion, a set of recommendations has been reached between CT WG3 and CT WG4 regarding the handling of 5GC API specifications and the API version numbers. These recommendations are provided. Recommendation 1: In","secretary_remarks":"Noted","agenda_item_sort_order":10,"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-09-03 06:45:51","uploaded":"2018-09-03 08:18:23","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","lsoriginalls":"C4-186602","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180794.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180795","title":"LS from SA WG2: LS reply to BBF Response to 3GPP SA2 liaison S2-183036 on \u2018general status of work\u2019","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":72921,"tdoctype":"LS in","for":"Action","abstract":"SA WG2 would like to thank BBF for the LS to 3GPP on status of work (BBF LIAISE-208 \/ S2-188252). {SA WG2 provide replies to the BBF questions}.","secretary_remarks":"Noted","agenda_item_sort_order":10,"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":"2018-09-03 06:45:51","uploaded":"2018-09-03 08:18:23","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"FS_5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"TSG SA, SA WG3, SA WG5","lsoriginalls":"S2-189038","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180795.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180841","title":"[DRAFT] LS on global collaboration for 5G standardisation for maritime commercial and safety fields in 3GPP","source":"SyncTechno Inc.","contact":"Hyounhee Koo","contact-id":65247,"tdoctype":"LS out","for":"Approval","abstract":"Drafted LS on global collaboration for 5G standardisation for maritime commercial and safety fields in 3GPP","secretary_remarks":"Revised to SP-180882.","agenda_item_sort_order":10,"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":"revised","reservation_date":"2018-09-04 08:38:56","uploaded":"2018-09-05 06:18:40","revisionof":"","revisedto":"SP-180882","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"MARCOM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IALA","Cc":"SA WG1, TSG RAN, TSG CT","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180841.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180856","title":"LS from ETSI: LS on Joint ETSI - OSA Workshop: Open Implementations & Standardization","source":"ETSI","contact":"Olivier Genoud","contact-id":58316,"tdoctype":"LS in","for":"Information","abstract":"Overall Description: ETSI wishes to bring the training session and workshop described in the attached Collective Letter to the attention of relevant 3GPP groups, and solicits presentations and demonstrations of suitable 5G related material. Follow the hyperlinks in the attachment for further information. Action: Please take note of the ETSI-OSA workshop on open implementation and standardization and please encourage 3GPP members to contribute to the workshop.","secretary_remarks":"Noted","agenda_item_sort_order":10,"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":"noted","reservation_date":"2018-09-05 07:21:13","uploaded":"2018-09-05 07:21:44","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, RAN WG1, RAN WG2, RAN WG3, RAN WG4, RAN WG5, TSG CT, CT WG1, CT WG3, CT WG4, CT WG6, TSG SA, SA WG3, SA WG5, SA WG6","Cc":"","lsoriginalls":"LS_cover_ETSI_CL3463","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180856.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180857","title":"LS from SA WG1: LS on the information of the 3GPP standardization applicable to maritime usage and the request of the additional maritime related information","source":"SA WG1","contact":"Hyounhee Koo","contact-id":65247,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 would like to inform IALA that 3GPP have developed 3GPP technical report and are working on a 3GPP technical specification to be applicable to maritime usage. The goal is to have the requirements as part of 3GPP Release 16, which is currently predicted to be ready in December 2019. SA WG1 has created the technical report, 3GPP TR 22.819 'Feasibility Study on Maritime Communication Services over 3GPP System' which studies use cases and collects potential requirements. SA WG1 is now working on the technical specification 3GPP TS 22.119 that will contain the normative requirements. As part of this work, SA WG1 would like to ask IALA to provide feedbacks or inputs on the following information: - minimum value of the communication range for the direct vessel to vessel communication - status of legacy communication methods used for the navigation - status of legacy communication methods used by equipment inside a vessel If possible, SA WG1 would appreciate a response before the next m","secretary_remarks":"Noted","agenda_item_sort_order":10,"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-09-05 07:21:13","uploaded":"2018-09-05 07:21:44","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"MARCOM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IALA","Cc":"TSG SA","lsoriginalls":"S1-182760","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180857.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180866","title":"LS from GSMA: LS to 3GPP RAN and 3GPP SA on 5G Indicator Requirements","source":"GSMA","contact":"Mark A. Lipford","contact-id":36056,"tdoctype":"LS in","for":"Information","abstract":"Introduction: GSMA Future Networks Programme would like to congratulate 3GPP on the recent completion of Release 15 and NR. This is a huge achievement for 3GPP and for the mobile industry. As part of GSMA's work on 5G the GSMA Future Networks Programme recently activated a new Task Force to look at the Release 15 specifications and to review the requirements GSMA provided to 3GPP on 5G Indicator (R2-1713952\/S2-178933). Overview: The GSMA 5G Status Indicator (hereinafter called '5GSI') Task Force has discussed the update to 3GPP TS36.331 which adds the 1-bit 5G Indicator 'upperLayerIndication' information element to SIB2. Based on the six states and four configuration scenarios identified in the GSMA requirements (R2-1713952\/S2-178933), the GSMA 5GSI Task Force has agreed that the requirements set forth in that contribution have been discussed in the 3GPP Release 15 specifications. The GSMA 5GSI Task Force does not have any additional requirements at this moment, although the discussion","secretary_remarks":"Noted","agenda_item_sort_order":10,"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":"2018-09-06 13:31:37","uploaded":"2018-09-06 13:37:55","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA","Cc":"SA WG2, SA WG1, RAN WG2, CT WG1 , TSG CT","lsoriginalls":"5GSI#04 Doc 003","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180866.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180871","title":"LS from WBA Testing & Interoperability Workgroup: MAC randomization impacts","source":"WBA Testing & Interoperability Workgroup","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Dear WBA Partners, Currently, iOS, Android, and Windows anonymize the MAC address during probe requests while still using the true MAC address when connecting to the network. Further addressing the need of user privacy, in Android P new development (ref), Android plans to create a unique, anonymous MAC for each SSID that the device connects to: 'Connected mode randomization is a developer feature only and would be default off for Android P. Our main goal this year is to get a soak time in the industry and get feedback from partners such as yourself who depend on mac address identifier. It gives time for the ecosystem to adapt to new behavior once we roll out in subsequent releases as default behavior. {...} Specific request: WBA would like to recommend further discussion within the operator and vendor community to minimize the impact of implementing MAC randomization. The team may also approach device makers to propose revising certain aspects of randomization, which may help to resolv","secretary_remarks":"Noted","agenda_item_sort_order":10,"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-09-08 05:11:38","uploaded":"2018-09-08 05:17:53","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Industry Partners (ITU, Wi-Fi Alliance, GSMA, 3GPP, IEEE, ATIS, IETF)","Cc":"","lsoriginalls":"MAC Randomization Impacts Assessment T&I 20180905","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180871.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180872","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":"SA WG3-LI and SA WG3 were asked to consider this LS and provide information to TSG SA#82. This LS was then postponed.","agenda_item_sort_order":10,"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":"postponed","reservation_date":"2018-09-10 00:37:59","uploaded":"2018-09-10 00:38:51","revisionof":"","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":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180872.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180876","title":"LS from NGMN Alliance: LS to 3GPP on the 5G interoperability framework","source":"NGMN Alliance","contact":"Jongmun Lee","contact-id":60599,"tdoctype":"LS in","for":"Action","abstract":"Intention of the LS and required actions NGMN is pleased to inform the recipients of this liaison statement that the first version of the Interoperability Testing Framework has been published. The document will be maintained, and future versions are anticipated to reflect further forward-looking interoperability testing methodologies to facilitate harmonized understanding 5G specifications. The testing framework builds on and extends the deployment scenarios and parameter definitions defined for 5G in 3GPP Rel-15. The framework covers testing aim and scope, list of the related standard, test parameters, testing procedures and success criteria and is jointly developed by more than 20 of the leading operators, vendors and research institution worldwide and supported by all operator partners within the NGMN Alliance. NGMN kindly requests the recipients of this liaison to consider the 5G testing framework document as a baseline for securing end to end interoperability in 5G System and to a","secretary_remarks":"Noted","agenda_item_sort_order":10,"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-09-10 23:17:40","uploaded":"2018-09-10 23:19:59","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA","Cc":"","lsoriginalls":"NGNM_LS_180910","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180876.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180877","title":"LS from TSG CT: LS on Control Plane Solution for Steering of Roaming in 5GS","source":"TSG CT","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Action","abstract":"TSG CT has received the attached LS from GSMA, asking several questions on the control plane solution for steering of roaming in 5GS. TSG CT requests CT WG1, CT WG4 and CT WG6 to provide answers for the technical questions in the LS which are within the scope of their respective ToR and to send these answers to TSG CT via LS by TSG CT#82.","secretary_remarks":"Noted","agenda_item_sort_order":10,"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":"2018-09-11 04:59:47","uploaded":"2018-09-11 05:04:17","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4, CT WG6","Cc":"TSG SA, SA WG3","lsoriginalls":"CP-182234","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180877.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180878","title":"LS from TSG CT: Reply LS on API specification and API version number maintenance","source":"TSG CT","contact":"Lionel Morand","contact-id":25150,"tdoctype":"LS in","for":"Action","abstract":"TSG CT thanks CT WG4 for the LS on API specification and API version number maintenance (CP-182196\/C4-186602). TSG CT has discussed the recommendations listed in the LS and has reached the following conclusions: On the recommendation 1: TSG CT welcomes the proposal to submit a single CR per API to update the API version number. It is up to TSG SA to agree on an update of CR template to include a specific check-box (e.g. 'API impacts') on CR cover page. On the recommendation 2: TSG CT agrees on a principle to define a specific freezing date for API specifications, as for ASN.1, three months after the deep freeze of the stage 3. On the recommendation 3: The need for a separate OpenAPI file containing a copy of the normative annex of the specification has been discussed. TSG CT considers as useful to create separate OpenAPI files, validated by 3GPP, and to store these OpenAPI files in a centralized way. These separate files would be for information and the Annex of each specification cont","secretary_remarks":"Noted","agenda_item_sort_order":10,"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-09-11 04:59:48","uploaded":"2018-09-11 05:04:17","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, CT WG3, TSG SA, SA WG5, SA WG6","Cc":"","lsoriginalls":"CP-182239","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180878.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180882","title":"[DRAFT] LS on global collaboration for 5G standardisation for maritime commercial and safety fields in 3GPP","source":"SyncTechno Inc.","contact":"Hyounhee Koo","contact-id":65247,"tdoctype":"LS out","for":"Approval","abstract":"Drafted LS on global collaboration for 5G standardisation for maritime commercial and safety fields in 3GPP","secretary_remarks":"Revision of SP-180841. LATE DOC: Rx 12\/09, 13:20. Noted","agenda_item_sort_order":10,"ainumber":"6","ainame":"General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-09-12 01:51:17","uploaded":"2018-09-12 08:47:54","revisionof":"SP-180841","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"MARCOM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IALA","Cc":"SA WG1, TSG RAN, TSG CT","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180882.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180886","title":"[DRAFT] Reply LS to ETSI TC DECT on Interworking of DECT technology with 3GPP networks","source":"TSG SA","contact":"Erik Guttman","contact-id":18782,"tdoctype":"LS out","for":"Approval","abstract":"To: ETSI TC DECT","secretary_remarks":"Response to SP-180683. Revised to SP-180906.","agenda_item_sort_order":10,"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":"revised","reservation_date":"2018-09-12 07:10:19","uploaded":"2018-09-13 08:17:53","revisionof":"","revisedto":"SP-180906","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TC DECT","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180886.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180906","title":"[DRAFT] Reply LS to ETSI TC DECT on Interworking of DECT technology with 3GPP networks","source":"TSG SA","contact":"Erik Guttman","contact-id":18782,"tdoctype":"LS out","for":"Approval","abstract":"To: ETSI TC DECT","secretary_remarks":"Revision of SP-180886. Revised to SP-180915.","agenda_item_sort_order":10,"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":"revised","reservation_date":"2018-09-13 07:56:43","uploaded":"2018-09-14 03:57:54","revisionof":"SP-180886","revisedto":"SP-180915","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TC DECT","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180906.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180915","title":"[DRAFT] Reply LS to ETSI TC DECT on Interworking of DECT technology with 3GPP networks","source":"TSG SA","contact":"Erik Guttman","contact-id":18782,"tdoctype":"LS out","for":"Approval","abstract":"To: ETSI TC DECT","secretary_remarks":"Revision of SP-180906. Revised to SP-180924.","agenda_item_sort_order":10,"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":"revised","reservation_date":"2018-09-14 01:17:25","uploaded":"2018-09-14 03:57:54","revisionof":"SP-180906","revisedto":"SP-180924","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TC DECT","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180915.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-180924","title":"[DRAFT] Reply LS to ETSI TC DECT on Interworking of DECT technology with 3GPP networks","source":"TSG SA","contact":"Erik Guttman","contact-id":18782,"tdoctype":"LS out","for":"Approval","abstract":"To: ETSI TC DECT","secretary_remarks":"Revision of SP-180915. Approved","agenda_item_sort_order":10,"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":"approved","reservation_date":"2018-09-14 03:36:03","uploaded":"2018-09-14 03:57:54","revisionof":"SP-180915","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-180683","lsto":"ETSI TC DECT","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_81\/Docs\/SP-180924.zip","group":"SP","meeting":"SP-81","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]