[{"name":"S2-1905666","title":"Correction on Location reporting procedures","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. for Xn-HO, the information of location report shall be included in the Handover request from S-RAN to T-RAN if there is any, while for N2-HO, for the S-RAN, the information of location report should not be included in the Handover required message. 2. The AMF could request the location info of a certain UE via either the location report control message, or the existing N2 messages as speficied by RAN WG3.","secretary_remarks":"Revised in parallel session to S2-1906587.","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12780,"status":"revised","reservation_date":"2019-05-07 10:48:38","uploaded":"2019-05-07 13:36:33","revisionof":"","revisedto":"S2-1906587","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1424.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905666.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905668","title":"SMF actions on rejection of PDU Session session or QoS flows during N2-based handover for R15","source":"Huawei, HiSilicon, Ericsson?, OPPO?","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. In addition, other changes have been included as followings: 1. It is proposed to change the wording 'List of PDU Sessions Rejected with for each PDU Session N2 SM Information including a rejection Cause ' into 'List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element'. 2. The IEs of 'AN Tunnel Info' and 'List of accepted QoS Flows for the PDU Sessions whose UP connections are activated' are contained in the N2 SM information of each PDU Session To Be Switched.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-1906585.","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12720,"status":"revised","reservation_date":"2019-05-07 10:48:39","uploaded":"2019-05-07 13:36:33","revisionof":"","revisedto":"S2-1906585","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1434.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905668.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905719","title":"Clarification on the misleading IE for the rejected PDU sessions by RAN","source":"Huawei, HiSilicon, Ericsson?, OPPO?","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: 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. In addition, other changes have been included as followings: 1. It is proposed to change the wording 'List of PDU Sessions Rejected with for each PDU Session N2 SM Information including a rejection Cause ' into 'List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element'. 2. The IEs of 'AN Tunnel Info' and 'List of accepted QoS Flows for the PDU Sessions whose UP connections are activated' are contained in the N2 SM information of each PDU Session To Be Switched.","secretary_remarks":"Revision of S2-1904581 from S2#132. Confirm Sources! Revised in parallel session to S2-1906586.","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12750,"status":"revised","reservation_date":"2019-05-07 11:15:50","uploaded":"2019-05-07 13:36:33","revisionof":"S2-1904581","revisedto":"S2-1906586","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1279.0,"crrevision":3.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905719.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905745","title":"Corrections on some MM procedures","source":"Huawei, HiSilicon, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"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' Rev3 4.2.2.2.3: Step 2 changed such that initial AMF may perform 9a i.e. authentication or also 9b SMC","secretary_remarks":"Revision of S2-1904705 from S2#132. Agreed in parallel session. This was Block approved","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12820,"status":"agreed","reservation_date":"2019-05-07 11:32:50","uploaded":"2019-05-07 14:25:58","revisionof":"S2-1904705","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1278.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190413","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905745.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905782","title":"Correction on Direct Forwarding Path Availability","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change the text to say: 1. The Direct Forwarding Path Availability is included in the Handover Required message by the source RAN node to indicate that the direct forwarding path is available for the handover. 2. If the Direct Forwarding Path Availability is not included in the N2 SM information, then the SMF decides the applicability of the indirect data forwarding based on the connectivity between source and target.","secretary_remarks":"Revised in parallel session to S2-1906588.","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12680,"status":"revised","reservation_date":"2019-05-07 13:42:14","uploaded":"2019-05-07 13:48:22","revisionof":"","revisedto":"S2-1906588","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1451.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905782.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905786","title":"Correction on Direct Forwarding Path Availability","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Change the text to say: 1. The Direct Forwarding Path Availability is included in the Handover Required message by the source RAN node to indicate that the direct forwarding path is available for the handover. 2. If the Direct Forwarding Path Availability is not included in the N2 SM information, then the SMF decides the applicability of the indirect data forwarding based on the connectivity between source and target.","secretary_remarks":"Revised in parallel session to S2-1906589.","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12700,"status":"revised","reservation_date":"2019-05-07 13:46:35","uploaded":"2019-05-07 13:48:22","revisionof":"","revisedto":"S2-1906589","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1452.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905786.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906585","title":"SMF actions on rejection of PDU Session session or QoS flows during N2-based handover for R15","source":"Huawei, HiSilicon, Ericsson?, OPPO?","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. In addition, other changes have been included as followings: 1. It is proposed to change the wording 'List of PDU Sessions Rejected with for each PDU Session N2 SM Information including a rejection Cause ' into 'List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element'. 2. The IEs of 'AN Tunnel Info' and 'List of accepted QoS Flows for the PDU Sessions whose UP connections are activated' are contained in the N2 SM information of each PDU Session To Be Switched.","secretary_remarks":"Revision of S2-1905668.","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":14690,"status":"revised","reservation_date":"2019-05-15 17:19:49","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905668","revisedto":"S2-1906630","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1434.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906585.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906586","title":"Clarification on the misleading IE for the rejected PDU sessions by RAN","source":"Huawei, HiSilicon, Ericsson?, OPPO?","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: 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. In addition, other changes have been included as followings: 1. It is proposed to change the wording 'List of PDU Sessions Rejected with for each PDU Session N2 SM Information including a rejection Cause ' into 'List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element'. 2. The IEs of 'AN Tunnel Info' and 'List of accepted QoS Flows for the PDU Sessions whose UP connections are activated' are contained in the N2 SM information of each PDU Session To Be Switched.","secretary_remarks":"Revision of S2-1905719.","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":14710,"status":"revised","reservation_date":"2019-05-15 17:19:49","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905719","revisedto":"S2-1906631","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1279.0,"crrevision":4.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906586.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906587","title":"Correction on Location reporting procedures","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. for Xn-HO, the information of location report shall be included in the Handover request from S-RAN to T-RAN if there is any, while for N2-HO, for the S-RAN, the information of location report should not be included in the Handover required message. 2. The AMF could request the location info of a certain UE via either the location report control message, or the existing N2 messages as speficied by RAN WG3.","secretary_remarks":"Revision of S2-1905666.","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":14730,"status":"revised","reservation_date":"2019-05-15 17:19:50","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905666","revisedto":"S2-1906629","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1424.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906587.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906588","title":"Correction on usage of Direct Forwarding Path Availability during handovers","source":"Samsung, Ericsson","contact":"Jungshin Park","contact-id":65750,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change the text to say: 1. The Direct Forwarding Path Availability is included in the Handover Required message by the source RAN node to indicate that the direct forwarding path is available for the handover. 2. If the Direct Forwarding Path Availability is not included in the N2 SM information, then the SMF decides the applicability of the indirect data forwarding based on the connectivity between source and target.","secretary_remarks":"Revision of S2-1905782. Agreed in parallel session. This was Block approved","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12700,"status":"agreed","reservation_date":"2019-05-15 17:19:52","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905782","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1451.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190402","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906588.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906589","title":"Correction on usage of Direct Forwarding Path Availability during handovers","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Change the text to say: 1. The Direct Forwarding Path Availability is included in the Handover Required message by the source RAN node to indicate that the direct forwarding path is available for the handover. 2. If the Direct Forwarding Path Availability is not included in the N2 SM information, then the SMF decides the applicability of the indirect data forwarding based on the connectivity between source and target.","secretary_remarks":"Revision of S2-1905786. Agreed in parallel session. This was Block approved","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12720,"status":"agreed","reservation_date":"2019-05-15 17:19:53","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905786","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1452.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-190402","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906589.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906629","title":"Correction on Location reporting procedure","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. for Xn-HO, the information of location report shall be included in the Handover request from S-RAN to T-RAN if there is any, while for N2-HO, for the S-RAN, the information of location report should not be included in the Handover required message. 2. The AMF could request the location info of a certain UE via either the location report control message, or the existing N2 messages as speficied by RAN WG3.","secretary_remarks":"Revision of S2-1906587. Agreed in parallel session. This was Block approved","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12810,"status":"agreed","reservation_date":"2019-05-16 17:57:10","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1906587","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1424.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190413","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906629.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906630","title":"SMF actions on rejection of PDU Session session or QoS flows during N2-based handover for R15","source":"Huawei, HiSilicon, Ericsson, OPPO","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. In addition, other changes have been included as followings: 1. It is proposed to change the wording 'List of PDU Sessions Rejected with for each PDU Session N2 SM Information including a rejection Cause ' into 'List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element'. 2. The IEs of 'AN Tunnel Info' and 'List of accepted QoS Flows for the PDU Sessions whose UP connections are activated' are contained in the N2 SM information of each PDU Session To Be Switched.","secretary_remarks":"Revision of S2-1906585. Agreed in parallel session. This was Block approved","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12750,"status":"agreed","reservation_date":"2019-05-16 17:57:11","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1906585","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1434.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190402","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906630.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906631","title":"SMF actions on rejection of PDU Session session or QoS flows during Handover and Service Request procedures","source":"Huawei, HiSilicon, Ericsson, OPPO","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: 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. In addition, other changes have been included as followings: 1. It is proposed to change the wording 'List of PDU Sessions Rejected with for each PDU Session N2 SM Information including a rejection Cause ' into 'List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element'. 2. The IEs of 'AN Tunnel Info' and 'List of accepted QoS Flows for the PDU Sessions whose UP connections are activated' are contained in the N2 SM information of each PDU Session To Be Switched.","secretary_remarks":"Revision of S2-1906586. Agreed in parallel session. This was Block approved","agenda_item_sort_order":25,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12780,"status":"agreed","reservation_date":"2019-05-16 17:57:12","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1906586","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1279.0,"crrevision":5.0,"crcategory":"A","tsg_crp":"SP-190401","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906631.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]