[{"name":"S6-190891","title":"LS on LI Impacts for LMR-LTE Interworking study","source":"SA3-LI","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-04-24 10:03:47","uploaded":"2019-04-24 12:20:45","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-190891.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-190925","title":"LS reply on PCF and NEF discovery for Edge Computing","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-05-09 09:15:01","uploaded":"2019-05-09 09:30:23","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-190925.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-190926","title":"Observations on standards and technical constraints from 3rd MCX remote Plugtests","source":"ETSI CTI","contact":"Saurav Arora","contact-id":62621,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2019-05-09 09:19:26","uploaded":"2019-05-09 09:30:23","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\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-190926.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191047","title":"NGMN 5G End-to-End Architecture Framework.","source":"NGMN Alliance","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Discussion","abstract":"1. About the NGMN Alliance\nThe NGMN Alliance is an industry organization of leading world-wide Telecom Operators, Vendors and Research Institutes (see www.ngmn.org) and was founded by international network operators in 2006. Its objective is to ensure that the functionality and performance of next generation mobile network infrastructure, service platforms and devices will meet the requirements of operators and, ultimately, will satisfy end user demand and expectations. The NGMN Alliance will drive and guide the development of all future mobile broadband technology enhancements with a focus on 5G. The targets of these activities are supported by the strong and well-established partnership of worldwide leading operators, vendors, universities, and successful co-operations with other industry organisations.\n\n2. NGMN 5G Work-Programme, Requirements and Architecture \nIn September 2017 and in February 2018, the first version and the second version of the NGMN End-to-End Architecture Framework was published, building on and developing end-to-end architecture principles from the 2015 5G White Paper, which can support the standardisation and subsequent availability of 5G for 2020 and beyond. \n\n3. Intention of the LS and required actions\nNGMN is pleased to inform the recipient of this liaison statement for information sharing on the interim third version (v3.0) of the NGMN 5G End-to-End Architecture Framework that includes requirements together with descriptions and concepts associated with new topics.\n\nThe new topics include: \n?\tAutonomic networking\n?\tDistributed Ledger Technology\n?\tMinimization or avoidance of tunnelling\n?\tNetwork automation\n\nFurther enhancement, consideration, and review in the articulation of the related requirements together with updates that include security aspects, URLLC, and network data layer is planned for the final version in September 2019.\n\nThis NGMN liaison is intended for information sharing in terms of the new topics that have been introduced in the attached document. Please take this into account in the 5G architecture considerations.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":104700,"status":"noted","reservation_date":"2019-05-24 21:44:54","uploaded":"2019-05-24 21:57:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-191047.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191054","title":"LS on ETSI Plugtest standards Issues","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Discussion","abstract":"1\t. Overall description\nCT1 have received reports from ETSI Plugtest 2 and ETSI Plugtest 3 regarding issues they have noted regarding 3GPP mission critical standards. CT1 intends to see that each of these issues is addressed appropriately and has performed a preliminary review of the issue statements to determine which 3GPP working group could take the lead in understanding and resolving each issue.\nThe table in the annex of this LS provides that preliminary review and indicates which issues could benefit from analysis by SA6 and SA3. CT1 requests SA6 and SA3 to:\n * 1.\texamine this table and determine whether you agree with our preliminary determination of the lead 3GPP working group for each issue,\n * 2.\tto inform CT1 whether SA6 and SA3 are willing to accept leadership on the issues indicated, and\n * 3.\tto provide any additional input on any of these issues regarding leadership or a technical response.\n\nIt is the intention of CT1 to gather technical responses for each issue and provide these responses to ETSI Plugtest.\nCT1 appreciates the assistance of SA6 and SA3 in helping to resolve these issues and thus to advance the usability of mission critical services.\n\n2. \tActions\nTo SA6 and SA3\nACTION: \t3GPP TSG CT WG1 respectfully asks SA6 and SA3 to perform the three actions noted.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":9265,"status":"postponed","reservation_date":"2019-05-24 21:45:00","uploaded":"2019-05-24 21:57:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-191054.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191055","title":"LS on clarification for usage of MC Service emergency state for MCData service","source":"CT1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1\t. Overall description\nTS 23.282 subclause 7.10 together with TS 23.280 subclause 10.10 only provide for MCData emergency alert initiation and MCData emergency alert cancel procedures (both for on-network and off-network) to MCData users. \nThese clauses leave unspecified several aspects regarding what should occur after completion of this procedure. For example, in TS 23.280 subclause 10.10.1.2.1, the statement in step 5 of the procedures says \u201cMC service group calls made to this MC service group by the MC service client 1 will be sent as emergency calls until the emergency state on the MC service client 1 is cancelled.\u201d However, in TS 23.282 there are no procedures for MCData emergency calls of any kind (group or individual). Similarly, in TS 23.280 subclause 10.10.1.2.1, there is the statement \u201cThis procedure will place the MC service client in the MC service emergency state if the MC service client is not already in that state.\u201d But in TS 23.282 there is no mention of the emergency state for an MCData client, nor what effect this condition could have on subsequent MCData calls once in this state.\nCT1 would like to ask SA6:\nQ1. Should the bearers of an MCData session, while the MCData client is in an emergency state, have elevated priority (and\/or pre-emption handling)?\nQ2. There are no procedures in TS 23.282 that allow for elevated priority in emergency data communications. Should File Distribution (FD) sessions and\/or Short Data Service (SDS) sessions somehow be marked as being in an emergency state and\/or be enabled for preferential (emergency) treatment by the system for delivery? \nQ3. If the answer to Q2 is YES, please provide the SA6 detail procedures to accomplish this through specification.\nQ4. If answer to Q2 is NO, please explain the rationale for excluding MCData from emergency handling in TS 23.282, especially in light of the reference to such treatment in TS 23.280 clause 10.10.1.2.1 step 5 from above.\nIn addition, please provide any other clarifications and\/or details for the usage of the emergency state by the MCData client within the MCData service.\n2\t. Actions\nTo 3GPP TSG SA WG6 \nACTION: \t3GPP TSG CT WG1 kindly asks 3GPP TSG SA WG6 group to provide answers and clarifications on the usage of MCData emergency state within the MCData service.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":105500,"status":"postponed","reservation_date":"2019-05-24 21:45:00","uploaded":"2019-05-24 21:57:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-191055.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-191142","title":"LS reply on SCEF support for V2XAPP procedures","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nSA2 thanks SA6 for their LS on SCEF support for V2XAPP procedures and would like to reply as follows:\n-\tThe exposure of network status reports is already supported by the SCEF via the T8 interface, therefore the existing SCEF\/T8 based procedures defined in TS 23.682 and TS 29.122 can be reused.\n-\tThe monitoring of QoS by a 3rd party application server is partially supported by the SCEF using a status information message for bearer-level events. The SCEF does not support the real-time monitoring of AS session QoS. \n\n2. Actions:\nTo SA6 group.\nACTION: \tSA2 kindly asks SA6 to take the answer into account.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":114200,"status":"noted","reservation_date":"2019-05-24 21:46:16","uploaded":"2019-05-24 21:57:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_031_Bruges\/Docs\/S6-191142.zip","group":"S6","meeting":"S6-31","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]