[{"name":"S2-1908646","title":"LS from SA WG3-LI: Response LS on support of non-3GPP only UE and support for PEI in IMEI format","source":"SA WG3-LI","contact":"Koen Jaspers","contact-id":9291,"tdoctype":"LS in","for":"Information","abstract":"SA WG3LI kindly thanks SA WG2 for their LS on the support of non-3GPP only UE and support for PEI in IMEI format. SA WG3LI confirms the requirement to assign an equipment identifier for each UEs that accesses the 5GC via a non-3GPP access. In order to fulfil the LI requirements it is important that: a) The equipment identifier is reported to the Core Network. b) The equipment identifier is non-changeable. c) The equipment identifier is defined in a globally standardised format. The equipment identifier needs to be unique and in a standardised format. Although IMEI or IMEISV format fulfil these requirements, also other standards are acceptable. Action: SA WG3LI kindly asks SA WG2 group to specify the assignment of an equipment identifier to UEs using a non-3GPP access and ensure the LI requirements above are incorporated","secretary_remarks":"Postponed S2-1906846 from S2#134. Response drafted in S2-1909383. Final response in S2-1910679","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13730,"status":"replied to","reservation_date":"2019-09-16 19:37:37","uploaded":"2019-09-16 21:37:53","revisionof":"S2-1906846","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S3i190363","lsreply":"S2-1910679","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908646.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908705","title":"LS from SA WG3: Reply LS on support of non-3GPP only UE and support for PEI in IMEI format","source":"SA WG3","contact":"Alex Leadbeater","contact-id":71428,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 kindly thanks SA WG2 for their LS on support of non-3GPP only UE and support for PEI in IMEI format. SA WG3 has reviewed the LS and would like to provide the following guidance. SA WG3 is not aware of any specific regulatory difference between requirements for 3GPP and non-3GPP access to 3GPP core networks from a security perspective. Regulations require that the UE PEI is non-changeable but the format of the PEI is not mandated, with the exception that it needs to be in a globally standardised format (e.g. IMEI or IMEISV). SA WG3 also confirm that all existing requirements relating to non-changeability and trustworthiness shall apply equally to PEIs used for 3GPP and non-3GPP access, including possible use with the EIR to block non-3GPP only, stolen UEs. In addition SA WG3 note that any UE connecting to the 3GPP core network needs to comply with all UE security requirements as defined in TS 33.501, regardless of the method of access (3GPP or non-3GPP). Action: SA WG3 kindly asks SA WG2 to take the above answers to SA WG2 questions into account when completing SA WG2 work on non-3GPP only UE PEI format.","secretary_remarks":"Response drafted in S2-1909383. Final response in S2-1910679","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13740,"status":"replied to","reservation_date":"2019-09-16 19:37:38","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, CT WG4, SA WG3LI","lsoriginalls":"S3-192278","lsreply":"S2-1910679","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908705.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909382","title":"PEI format for non-3GPP devices","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An IEEE Extended Unique Identifier (EUI-64) is proposed as PEI for non-3GPP only UEs.","secretary_remarks":"Revised in parallel session to S2-1910338.","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13780,"status":"revised","reservation_date":"2019-10-02 23:15:32","uploaded":"2019-10-04 19:42:24","revisionof":"","revisedto":"S2-1910338","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1801.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909382.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909383","title":"[DRAFT] LS Response Reply LS on support of non-3GPP only UE and support for PEI in IMEI format","source":"Qualcomm communications-France","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. CC: CT WG1, CT WG4, SA WG3-LI. Attachments: S2-1909382.","secretary_remarks":"Response to S2-1908705 and S2-1908646. Revised in parallel session to S2-1910339.","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13750,"status":"revised","reservation_date":"2019-10-02 23:17:18","uploaded":"2019-10-04 19:42:24","revisionof":"","revisedto":"S2-1910339","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"CT WG1, CT WG4, SA WG3-LI","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909383.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909613","title":"Discussion on handover failure between 3GPP and non-3GPP accesses","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses how the network handles handover procedure between 3GPP access and non-3GPP access when the handover fails.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13810,"status":"noted","reservation_date":"2019-10-04 00:42:03","uploaded":"2019-10-04 09:45:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909613.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909614","title":"Clarification on handover failure between 3GPP and non-3GPP accesses","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. When the Request Type is 'Existing PDU Session' and the PDU Session Establishment procedure fails, the SMF notifies the failure by sending Nsmf_PDUSession_SMContextStatusNotify including Access Type of the PDU Session. 2. When the AMF received the handover failure notification from the SMF, the AMF updates Access Type of the PDU Session based on information from the SMF. 3. In case of HR roaming, the V-SMF notifies the handover failure to the H-SMF by triggering Nsmf_PDUSession_Update Request including Access Type of the PDU Session.","secretary_remarks":"Revised in parallel session to S2-1910340.","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13820,"status":"revised","reservation_date":"2019-10-04 00:42:03","uploaded":"2019-10-04 09:45:37","revisionof":"","revisedto":"S2-1910340","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1826.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909614.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909837","title":"Correction to the access authentication for untrusted non-3GPP access","source":"Motorola Mobility, Lenovo, BlackBerry UK Ltd.","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Changes are made so that the UE may connect to an untrusted non-3GPP access network by applying the 3GPP-based authentication procedure specified in TS 33.402, if the selected non-3GPP access network supports the SWa interface with one or more EPCs.","secretary_remarks":"Revised in parallel session to S2-1910341.","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13860,"status":"revised","reservation_date":"2019-10-04 15:10:36","uploaded":"2019-10-04 17:02:07","revisionof":"","revisedto":"S2-1910341","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1859.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909837.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910338","title":"PEI format for non-3GPP devices","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An IEEE Extended Unique Identifier (EUI-64) is proposed as PEI for non-3GPP only UEs.","secretary_remarks":"Revision of S2-1909382. Revised in parallel session to S2-1910371.","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13790,"status":"revised","reservation_date":"2019-10-19 05:40:24","uploaded":"2019-10-19 07:48:11","revisionof":"S2-1909382","revisedto":"S2-1910371","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1801.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910338.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910339","title":"[DRAFT] LS Response Reply LS on support of non-3GPP only UE and support for PEI in IMEI format","source":"Qualcomm communications-France","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. CC: CT WG1, CT WG4, SA WG3-LI. Attachments: S2-1909382.","secretary_remarks":"Revision of S2-1909383. Revised in parallel session to S2-1910679.","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13760,"status":"revised","reservation_date":"2019-10-19 05:40:25","uploaded":"2019-10-19 07:48:11","revisionof":"S2-1909383","revisedto":"S2-1910679","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"CT WG1, CT WG4, SA WG3-LI","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910339.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910340","title":"Clarification on handover failure between 3GPP and non-3GPP accesses","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. When the Request Type is 'Existing PDU Session' and the PDU Session Establishment procedure fails, the SMF notifies the failure by sending Nsmf_PDUSession_SMContextStatusNotify including Access Type of the PDU Session. 2. When the AMF received the handover failure notification from the SMF, the AMF updates Access Type of the PDU Session based on information from the SMF. 3. In case of HR roaming, the V-SMF notifies the handover failure to the H-SMF by triggering Nsmf_PDUSession_Update Request including Access Type of the PDU Session.","secretary_remarks":"Revision of S2-1909614. Revised in parallel session to S2-1910369.","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13830,"status":"revised","reservation_date":"2019-10-19 05:40:25","uploaded":"2019-10-19 07:48:11","revisionof":"S2-1909614","revisedto":"S2-1910369","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1826.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910340.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910341","title":"Correction to the access authentication for untrusted non-3GPP access","source":"Motorola Mobility, Lenovo, BlackBerry UK Ltd.","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Changes are made so that the UE may connect to an untrusted non-3GPP access network by applying the 3GPP-based authentication procedure specified in TS 33.402, if the selected non-3GPP access network supports the SWa interface with one or more EPCs.","secretary_remarks":"Revision of S2-1909837. Revised in parallel session to S2-1910370.","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13870,"status":"revised","reservation_date":"2019-10-19 05:40:26","uploaded":"2019-10-19 07:48:11","revisionof":"S2-1909837","revisedto":"S2-1910370","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1859.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910341.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910369","title":"Clarification on handover failure between 3GPP and non-3GPP accesses","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. When the Request Type is 'Existing PDU Session' and the PDU Session Establishment procedure fails, the SMF notifies the failure by sending Nsmf_PDUSession_SMContextStatusNotify including Access Type of the PDU Session. 2. When the AMF received the handover failure notification from the SMF, the AMF updates Access Type of the PDU Session based on information from the SMF. 3. In case of HR roaming, the V-SMF notifies the handover failure to the H-SMF by triggering Nsmf_PDUSession_Update Request including Access Type of the PDU Session.","secretary_remarks":"Revision of S2-1910340. Revised in parallel session to S2-1910677.","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13840,"status":"revised","reservation_date":"2019-10-19 05:40:51","uploaded":"2019-10-19 07:48:11","revisionof":"S2-1910340","revisedto":"S2-1910677","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1826.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910369.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910370","title":"Correction to the access authentication for untrusted non-3GPP access","source":"Motorola Mobility, Lenovo, BlackBerry UK Ltd.","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Changes are made so that the UE may connect to an untrusted non-3GPP access network by applying the 3GPP-based authentication procedure specified in TS 33.402, if the selected non-3GPP access network supports the SWa interface with one or more EPCs.","secretary_remarks":"Revision of S2-1910341. Agreed in parallel session This was Block approved","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13880,"status":"agreed","reservation_date":"2019-10-19 05:40:53","uploaded":"2019-10-19 07:48:11","revisionof":"S2-1910341","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1859.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191091","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910370.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910371","title":"TS 23.501: PEI format for non-3GPP devices","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An IEEE Extended Unique Identifier (EUI-64) is proposed as PEI for non-3GPP only UEs.","secretary_remarks":"Revision of S2-1910338. Agreed in parallel session This was Block approved","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13800,"status":"agreed","reservation_date":"2019-10-19 05:40:54","uploaded":"2019-10-19 07:48:11","revisionof":"S2-1910338","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1801.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191074","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910371.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910677","title":"Clarification on handover failure between 3GPP and non-3GPP accesses","source":"LG Electronics, Motorola Mobility, Lenovo","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. When the Request Type is 'Existing PDU Session' and the PDU Session Establishment procedure fails, the SMF notifies the failure by sending Nsmf_PDUSession_SMContextStatusNotify including Access Type of the PDU Session. 2. When the AMF received the handover failure notification from the SMF, the AMF updates Access Type of the PDU Session based on information from the SMF. 3. In case of HR roaming, the V-SMF notifies the handover failure to the H-SMF by triggering Nsmf_PDUSession_Update Request including Access Type of the PDU Session.","secretary_remarks":"Revision of S2-1910369. Agreed in parallel session This was Block approved","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13850,"status":"agreed","reservation_date":"2019-10-19 05:43:31","uploaded":"2019-10-19 07:48:16","revisionof":"S2-1910369","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1826.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-191091","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910677.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910679","title":"LS Response Reply LS on support of non-3GPP only UE and support for PEI in IMEI format","source":"SA WG2","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. CC: CT WG1, CT WG4, SA WG3-LI. Attachments: S2-1910371, S2-1910380","secretary_remarks":"Revision of S2-1910339. Agreed in parallel session This was Block approved","agenda_item_sort_order":22,"ainumber":"6.","ainame":"Non-3GPP access specific functionality and flows","tdoc_agenda_sort_order":13770,"status":"approved","reservation_date":"2019-10-19 05:43:33","uploaded":"2019-10-19 07:48:16","revisionof":"S2-1910339","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1908705","lsto":"SA WG3","Cc":"CT WG1, CT WG4, SA WG3-LI","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910679.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]