[{"name":"S2-180009","title":"LS from GSMA: Liaison Statement on defining a common value for SPID for Unmanned Aircraft","source":"GSMA","contact":"Barbara Pareglio","contact-id":63010,"tdoctype":"LS in","for":"Information","abstract":"Summary: The GSMA Drone Interest Group, part of the IoT Programme, has studied different possibilities on how to be able to support the identification of Unmanned Aircraft (UA) by leveraging existing capabilities of mobile networks. A primary goal is to enable the mobile operators to provide the right quality of services for UA operations, which would enable them to support their customers. Introduction Mobile operators might need to recognise and distinguish a UA from a traditional device mainly in order to provide the right service optimisation for proper operation of the UA and to ensure the least interference to the other users. Description The GSMA Drone Interest Group that using a commonly defined value of the Subscriber Profile ID (SPID) would facilitate Mobile Network Operators (MNO) to recognise a device being an Unmanned Aircraft. When a user acquires a Subscriber Identity Module (SIM) with the intention of using it in a UA, or when a cellular module with an embedded SIM is i","secretary_remarks":"Postponed S2-178308 from SA WG2#124. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:35:40","revisionof":"S2-178308","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2, RAN WG3","Cc":"","lsoriginalls":"DIG Doc 003","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180009.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180011","title":"LS from SA WG4: Latest Technical Specification on Framework for Live Uplink Streaming","source":"SA WG4","contact":"Nikolai Leung","contact-id":38562,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 would like to thank SA WG2 for their response LS to SA WG4's initial LS on the status and progress of the Live Uplink Streaming (FLUS) work item, including your initial assessment that no immediate issues have been identified in the FLUS technical specification TS 26.238 v0.1.1. During the S4#96 meeting, SA WG4 completed the FLUS technical spec (v0.3.0) as attached in this LS. Given that the SA WG2 LS requested SA WG4 to keep SA WG2 informed on further progress of the FLUS work as appropriate, we are providing the latest version of the specification for your information, and would like to request any comments from SA WG2 on this document. Action: SA WG4 kindly asks SA WG2 to take the above information into account, and provide any inputs on the Rel-15 TS 26.238.","secretary_remarks":"Postponed S2-178388 from SA WG2#124. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178388","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG1, CT WG1","lsoriginalls":"S4-171395","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180011.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180012","title":"Reply LS on Certification\/License and Identification of Aerial Vehicles","source":"SA WG1","contact":"Edward Hall","contact-id":43958,"tdoctype":"LS in","for":"Action","abstract":"As part of a liaison exchange between RAN WG2 and SA WG2, SA WG1 has observed the following question by RAN WG2 and answer by SA WG2: RAN WG2 Question: Specifically, for certification\/license\/authorization issue, RAN WG2 thinks that is out of the RAN WG2 expertise and would kindly like to consult SA WG2 whether it is feasible to signal 'certificate\/licence\/authorization' information of a UE to be used as an aerial UE from CN to the eNB. SA WG2 Response: Certification\/licensing aspects related to devices, SA WG2 understands that it is not SA WG2 responsibility. SA WG2 can provide means to indicate if a user is allowed to have such devices, if such devices are identified as a 3GPP 'UE' belonging to a subscriber associated with an operator's PLMN. Such information, depending on RAN WG2 investigation and its requirement(s) can be provided as part of user's subscription information but the actual certification\/licensing aspects are outside of SA WG2 expertise. SA WG1 discussed this topic an","secretary_remarks":"Postponed S2-178408 from SA WG2#124. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178408","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2","Cc":"SA WG3, GSMA IoT Drone Interest Group","lsoriginalls":"S1-174512","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180012.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180037","title":"LS from RAN WG2: Reply LS on Certification\/License and Identification of Aerial Vehicles","source":"RAN WG2","contact":"Dawid Koziol","contact-id":68362,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 and SA WG1 for their LSs related to certification\/license and identification of Aerial Vehicles. Based on the provided feedback, RAN WG2 has further discussed this topic and agreed the attached Text Proposal for UE Identification for TR 36.777. In particular, it was agreed that: Permission for a user to function as an aerial UE in the 3GPP network can be identified via subscription information. This subscription information is passed to RAN via S1 signalling from the MME. The eNB may use this information together with capability indication to identify an aerial UE, perform the necessary control and apply the relevant functions. RAN WG2 understanding is that signalling mentioned above would be an authorization information, similar to the one provided for ProSe or V2X. Based on SA WG1 feedback, RAN WG2's understanding is that in Rel-15 this information would be limited to subscription related information while aspects relating to certification\/licensing","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG1, RAN WG3","Cc":"-","lsoriginalls":"R2-1714248","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180037.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180053","title":"LS from TSG SA: LS on URLLC","source":"TSG SA","contact":"Adrian Neal","contact-id":31227,"tdoctype":"LS in","for":"Action","abstract":"TSG SA thanks SA WG2 for their LS on QCIs for URLLC. TSG SA understands that there is urgency to determine whether the SA WG1 requirements of 1 ms latency with 1-10-6 Reliability for packets up to 256 Octets should form the basis for the definition of a URLL service characteristic, or the RAN request that one URLLC service with PDB of 1ms with reliability of 10-5 Packet error and loss rate for packets of maximum size of 32 octets is defined, in alignment with the ITU-R target for IMT-2020. TSG SA has decided that for Release 15 the KPIs for URLLC defined in TS 22.261 need to be reconciled with the expected RAN capabilities and system capabilities. TS 22.278 will also be impacted. TSG SA has identified that service requirements for EPS are in TS 22.278. TSG SA requests that SA WG1 documents the KPIs to be supported by EPS (including 5G Option 3) into TS 22.278. RAN has indicated that at the late stage of Release 15 completion, their design targets will not be able to be changed, and the","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2017-12-23 10:57:07","uploaded":"2017-12-23 10:57:29","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2","Cc":"TSG RAN, RAN WG1, RAN WG2","lsoriginalls":"SP-171079","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180053.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180476","title":"Discussion paper: UE Wi-Fi MAC Address in WLAN Measurement Information","source":"Comtech Telecommunications Incorporated, AT&T, Cisco, Qualcomm","contact":"Khiem Tran","contact-id":60055,"tdoctype":"discussion","for":"Discussion","abstract":"Abstract of the contribution: This contribution discusses required changes in LPP of including UE WLAN MAC address to support Emergency Services location. It includes a proposed way forward by attaching an included LS from SA WG2 to RAN WG2.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2018-01-16 00:09:13","uploaded":"2018-01-16 00:55:05","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180476.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180773","title":"LS from GSMA PACKET: LS on the definition of the Mx functionality in support of the S8HR architecture","source":"GSMA PACKET","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"GSMA NG PACKET thanks SA WG2 and CT WG1 for their LS replies on using the Mx reference point for SRVCC in S8HR architecture. Following the discussion on this option, GSMA NG PACKET has identified the need for defining SRVCC for S8HR (MSC server enhanced and ATCF) based on the Mx reference point. Action: GSMA PACKET kindly requests SA WG2 to specify stage 2 details for SRVCC using the Mx reference point in support of the S8HR architecture (MSC server enhanced and ATCF) and CT WG1 to define the stage 3 details in the relevant specifications.","secretary_remarks":"This LS was postponed. Revised at S2#126 in S2-181430.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"revised","reservation_date":"2018-01-19 11:26:56","uploaded":"2018-01-19 11:27:22","revisionof":"","revisedto":"S2-181430","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"-","lsoriginalls":"PACKET_96_113","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180773.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181137","title":"LS from GSMA Packet IoTTF: LS reply to SA WG2 on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"GSMA Packet IoTTF","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"GSMA Packet IoTTF thanks SA WG2 for reply liaison statement on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic. IoTTF intended to: - Identify traffic coming from Cat. M1\/M2 LTE UEs regardless if they initiate\/receive traffic with or without any means of CIOT optimisations. The following identifications are out of scope: - Identify the volume of data sent in Coverage Enhancement Mode A and Coverage Enhancement Mode B regardless of the UE category that supports the Coverage Enhancement Mode, IoTTF understood that Coverage Enhancement Mode A, Coverage Enhancement Mode B, and Low Access Priority Indicator could not differentiate LTE-M traffic because they could be used for non-IoT UEs. GSMA needs to differentiate Mobile IoT traffic, both LTE-M and NB-IoT, from traditional user traffic. This is motivated by the operators' desire to apply different charging models to traffic from LTE-M devices and NB-IoT devices plus the requirements for identification and transparency wh","secretary_remarks":"This LS was postponed Revised at S2#126 in S2-181432.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:53","revisionof":"","revisedto":"S2-181432","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5","Cc":"-","lsoriginalls":"IOTTF17 Doc003","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181137.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]