[{"name":"S2-1903439","title":"Updating NG-RAN with new temporary identity after new 5G-GUTI allocation","source":"NEC","contact":"Toshiyuki Tamura","contact-id":17921,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that When a UE is assigned a new 5G-GUTI over non-3GPP access and the UE is RRC-INACTIVE mode over 3GPP access at NG-RAN then the NG-RAN should be updated with a UE identity derived from the new 5G-GUTI.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13770,"status":"noted","reservation_date":"2019-04-02 01:06:21","uploaded":"2019-04-02 03:04:16","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1204.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903439.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903440","title":"Updating NG-RAN with new temporary identity after new 5G-GUTI allocation","source":"NEC","contact":"Toshiyuki Tamura","contact-id":17921,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Specify that When a UE is assigned a new 5G-GUTI over non-3GPP access and the UE is RRC-INACTIVE mode over 3GPP access at NG-RAN then the NG-RAN should be updated with a UE identity derived from the new 5G-GUTI.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13780,"status":"noted","reservation_date":"2019-04-02 01:10:09","uploaded":"2019-04-02 03:04:16","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1205.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903440.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903543","title":"Correction to UE Activity Procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Fix the sentence in step 1b.","secretary_remarks":"Wrong TS number on Cover sheet. Revised in parallel session to S2-1904579.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13790,"status":"revised","reservation_date":"2019-04-02 07:17:18","uploaded":"2019-04-02 14:49:52","revisionof":"","revisedto":"S2-1904579","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1226.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903543.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903744","title":"Corrections on some MM procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 4.2.2.2.3: Correct the refered steps in step 2. 4.2.2.3.2: Correct the figure. 4.2.6: Clarify which text is for NG-RAN and which text is for N3IWF. 4.2.7.2.1: Substitute 'without a GUAMI or with a GUAMI not associated with the 5G-AN node' to 'GUAMI and 5G-S-TMSI or with a GUAMI associated with the AMF not usable by the 5G-AN node'","secretary_remarks":"Revised in parallel session to S2-1904580.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13810,"status":"revised","reservation_date":"2019-04-02 11:11:48","uploaded":"2019-04-02 13:55:19","revisionof":"","revisedto":"S2-1904580","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1278.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903744.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903745","title":"SMF actions on rejection of PDU Session or QoS flows during Handover and Service Request procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is aligned into Handover and Service Request procedure with a simple description that: If a PDU Session is indicated as a rejected PDU Session by the Target NG-RAN with an indication that the PDU session was rejected because User Plane Security Enforcement is not supported in the Target NG-RAN and the User Plane Enforcement Policy indicates 'Required' as described in clause 5.10.3 of TS 23.501 [2], the SMF triggers the release of this PDU Session. In all other cases of PDU Session rejection, the SMF can decide whether to release the PDU Session or to deactivate the UP connection of this PDU Session. If only partial a part of QoS Flows of a PDU Session are accepted by the Target NG-RAN, the SMF may shall initiate the PDU Session Modification procedure to remove the non-accepted QoS Flows from the PDU Session(s) after the handover procedure is completed.","secretary_remarks":"Revised in parallel session to S2-1904581.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13840,"status":"revised","reservation_date":"2019-04-02 11:11:49","uploaded":"2019-04-02 13:55:19","revisionof":"","revisedto":"S2-1904581","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1279.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903745.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904579","title":"Correction to UE Activity Procedure","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Fix the sentence in step 1b.","secretary_remarks":"Revision of S2-1903543. Agreed in parallel session This was Block approved","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13800,"status":"agreed","reservation_date":"2019-04-15 10:42:12","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903543","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1226.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904579.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904580","title":"Corrections on some MM procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 4.2.2.2.3: Correct the refered steps in step 2. 4.2.2.3.2: Correct the figure. 4.2.6: Clarify which text is for NG-RAN and which text is for N3IWF. 4.2.7.2.1: Substitute 'without a GUAMI or with a GUAMI not associated with the 5G-AN node' to 'providing any UE identities (i.e. a GUAMI or a 5G-S-TMSI), or the UE provides a GUAMI or a 5G-S-TMSI but the 5G-AN node cannot associate such identity to any of its connected AMFs'","secretary_remarks":"Revision of S2-1903744. Revised in parallel session to S2-1904705.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13820,"status":"revised","reservation_date":"2019-04-15 10:42:13","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903744","revisedto":"S2-1904705","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1278.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904580.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904581","title":"SMF actions on rejection of PDU Session session or QoS flows during Handover and Service Request procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is aligned into Handover and Service Request procedure with a simple description that: If a PDU Session is indicated as a rejected PDU Session by the Target NG-RAN with an indication that the PDU session was rejected because User Plane Security Enforcement is not supported in the Target NG-RAN and the User Plane Enforcement Policy indicates 'Required' as described in clause 5.10.3 of TS 23.501 [2], the SMF triggers the release of this PDU Session. In all other cases of PDU Session rejection, the SMF can decide whether to release the PDU Session or to deactivate the UP connection of this PDU Session. If only partial a part of QoS Flows of a PDU Session are accepted by the Target NG-RAN, the SMF may shall initiate the PDU Session Modification procedure to remove the non-accepted QoS Flows from the PDU Session(s) after the handover procedure is completed.","secretary_remarks":"Revision of S2-1903745. Agreed in parallel session This was Block approved","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13850,"status":"agreed","reservation_date":"2019-04-15 10:42:14","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903745","revisedto":"S2-1905669, S2-1905719","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1279.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904581.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904705","title":"Corrections on some MM procedures","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 4.2.2.2.3: Correct the refered steps in step 2. 4.2.2.3.2: Correct the figure. 4.2.6: Clarify which text is for NG-RAN and which text is for N3IWF. 4.2.7.2.1: Substitute 'without a GUAMI or with a GUAMI not associated with the 5G-AN node' to 'providing any UE identities (i.e. a GUAMI or a 5G-S-TMSI), or the UE provides a GUAMI or a 5G-S-TMSI but the 5G-AN node cannot associate such identity to any of its connected AMFs'","secretary_remarks":"Revision of S2-1904580. Agreed in parallel session This was Block approved","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13830,"status":"agreed","reservation_date":"2019-04-15 10:44:01","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904580","revisedto":"S2-1905745","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1278.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904705.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]