[{"name":"S2-2001831","title":"Clarification on the EBI context if target MME does not support EBI extension during 5GS to EPS mobility","source":"ZTE, Ericsson, Huawei, CATT","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF determines EBIs which cannot be transferred to EPS and retrieves the EPS bearer context(s) for the other EBIs from PGW-C+SMF. Rev3: Remove the description on how PGW-C+SMF returns PDN connection context(s) and keep alignment with 23.502 CR#1980 Cover sheet is also updated to reflect the actual change.","secretary_remarks":"Revision of agreed S2-2001131 from SA2#136AH. Revised to S2-2002443.","agenda_item_sort_order":20,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":11450,"status":"revised","reservation_date":"2020-02-13 14:52:42","uploaded":"2020-02-18 14:52:12","revisionof":"S2-2001131","revisedto":"S2-2002443","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2060.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2001831.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001877","title":"Not supporting 15 EPS bearers at 5GS to EPS mobility","source":"Ericsson, CATT","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: #1 At 5GS to EPS mobility, the AMF knows the target MME does not support 15 EPS bearers through local configuration; #2 If AMF has already allocated more than 8 EBI values, the AMF marks the EBI values as follows to ensure that not more than 8 EPS bearers will be transferred to the MME. The AMF first determines EBI values in range 1-4 as not to be transferred, which means the QoS Flows associated with those EBIs are not to be transferred to EPS. If there are still more than 8 EBI values, the AMF then determines EBI value(s) not to be transferred based on S-NSSAI, and ARP PL and PVI value(s). #3 If the AMF determines that all QoS flows of a PDU Session are not to be transferred to EPS, then AMF does not retrieve the corresponding PDN connection context. If the AMF determines that a PDU Session has some QoS Flows to be transferred, then the AMF attempts to retrieve the UE EPS PDN Connection, including the EBI list. Case-1 (V-)SMF returns the UE EPS Connection if the EBI associated with the default QoS Flowcan be transferred; Case-2 if EBI associated with the default QoS Flow can not be transferred (which is not expected to happen if ARP PVI is set appropriately, but just in case), the (V-)SMF does not return UE EPS PDN Connection, i.e. SM Context retrieval failed. #4 The AMF initiates PDU Session release PDU Sessions that are not transferred to the MME, including PDU Session(s) without SM context retrieval, or PDU Session(s) with failed SM Context retrieval. #5 For PDU Session transferred to the EPS, if there are EPS bearers mapped from QoS Flows that are not included in Modify Bearer Request, the PGW-C+SMF release those QoS Flows. Rev5: Alignment of wording, and statements in 4.11.1.2.1 steps 12-12c and 4.11.1.3.2 steps 15-15c are corrected to refer to PDU Session(s).","secretary_remarks":"Revision of agreed S2-2001680 from SA2#136AH. Revised to S2-2002444.","agenda_item_sort_order":20,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":11470,"status":"revised","reservation_date":"2020-02-15 00:47:47","uploaded":"2020-02-18 17:38:31","revisionof":"S2-2001680","revisedto":"S2-2002444","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1980.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2001877.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001937","title":"N26 based interworking procedure update to support LADN concept when UE moves from 5G to 4G","source":"China Mobile","contact":"Dan Wang","contact-id":72661,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: There is a pre-condition that in 4G , the LADN DNN is already subscribed by the UE to support the session continuity between 5G and 4G , and in general the SMF+PGW-C should allocate EBI for LADN PDU sessions. For 5G, a LADN PDU session has been established with using local UPF. In 4.11.1.2.1, step 2, for LADN DNN PDU sessions, AMF may judge the E-UTRAN's service area.If the target E-UTRAN's service area is in the interesting area which is local configured in AMF, the AMF should request the SM context corresponding to LADN PDU sessions, and then send relocation request to MME including this SM context. If AMF decides the E-UTRAN'service area is out of interesting area, AMF should release the SM context for LADN DNN PDU sessions. And in this case, the session continuity is not supported and a new PDN connectivity is required to be established with using a new PGW-U(out of campus)","secretary_remarks":"Revision of unhandled S2-2000847 from SA2#136AH. Noted","agenda_item_sort_order":20,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":11490,"status":"noted","reservation_date":"2020-02-17 01:59:21","uploaded":"2020-02-17 02:00:42","revisionof":"S2-2000847","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2065.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2001937.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002171","title":"Correction of the CN tunnel info at the target side","source":"Huawei, HiSilicon, CATT","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the CP always need the CN tunnel info ready. The interaction with UPF may be optional depending on the who allocate the CN tunnel info. Rev1: Clarify the PGW-C+SMF need communicate with the PGW-U+UPF to get the CN tunnel info. Undo the change related the CN tunnel info allocated by the PGW-C+SMF. Remove the NOTE2 as the CN tunnel info always need be allocated at the PGW-U+UPF. In step 7 of clause 4.11.1.2.2.3, the V-CN tunnel is provided to PGW-C+SMF. Remove the H-CN Tunnel Info at the step 11 of clause 4.11.2.2.3. Also this step is triggered after step 7, i.e. not need wait the response from SMF.","secretary_remarks":"Revision of agreed S2-2000368 from S2#136AH. Approved","agenda_item_sort_order":20,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":11500,"status":"agreed","reservation_date":"2020-02-18 09:30:13","uploaded":"2020-02-18 14:53:37","revisionof":"S2-2000368","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1996.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200079","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002171.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002210","title":"NSSAI in the HO request during inter RAT\/EPS interworking","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For this purpose, this CR proposes update step 9 of 23.502 Figure 4.11.1.2.2.2-1 to state AMF creates a temporary NSSAI and sends it to NG-RAN as part of HO request","secretary_remarks":"Revised to S2-2002445.","agenda_item_sort_order":20,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":11510,"status":"revised","reservation_date":"2020-02-18 12:13:17","uploaded":"2020-02-18 20:49:15","revisionof":"","revisedto":"S2-2002445","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2146.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002210.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002443","title":"Clarification on the EBI context if target MME does not support EBI extension during 5GS to EPS mobility","source":"ZTE, Ericsson, Huawei, CATT, Nokia, Nokia Shanghai Bell","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF determines EBIs which cannot be transferred to EPS and retrieves the EPS bearer context(s) for the other EBIs from PGW-C+SMF. Rev3: Remove the description on how PGW-C+SMF returns PDN connection context(s) and keep alignment with 23.502 CR#1980 Cover sheet is also updated to reflect the actual change.","secretary_remarks":"Revision R01 of S2-2001831. Approved","agenda_item_sort_order":20,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":11460,"status":"agreed","reservation_date":"2020-02-28 13:23:24","uploaded":"2020-02-29 09:46:33","revisionof":"S2-2001831","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2060.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-200078","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002443.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002444","title":"Not supporting 15 EPS bearers at 5GS to EPS mobility","source":"Ericsson, CATT, Huawei, Nokia, Nokia Shanghai Bell, Cisco","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: #1 At 5GS to EPS mobility, the AMF knows the target MME does not support 15 EPS bearers through local configuration; #2 If AMF has already allocated more than 8 EBI values, the AMF marks the EBI values as follows to ensure that not more than 8 EPS bearers will be transferred to the MME. The AMF first determines EBI values in range 1-4 as not to be transferred, which means the QoS Flows associated with those EBIs are not to be transferred to EPS. If there are still more than 8 EBI values, the AMF then determines EBI value(s) not to be transferred based on S-NSSAI, and ARP PL and PVI value(s). #3 If the AMF determines that all QoS flows of a PDU Session are not to be transferred to EPS, then AMF does not retrieve the corresponding PDN connection context. If the AMF determines that a PDU Session has some QoS Flows to be transferred, then the AMF attempts to retrieve the UE EPS PDN Connection, including the EBI list. Case-1 (V-)SMF returns the UE EPS Connection if the EBI associated with the default QoS Flowcan be transferred; Case-2 if EBI associated with the default QoS Flow can not be transferred (which is not expected to happen if ARP PVI is set appropriately, but just in case), the (V-)SMF does not return UE EPS PDN Connection, i.e. SM Context retrieval failed. #4 The AMF initiates PDU Session release PDU Sessions that are not transferred to the MME, including PDU Session(s) without SM context retrieval, or PDU Session(s) with failed SM Context retrieval. #5 For PDU Session transferred to the EPS, if there are EPS bearers mapped from QoS Flows that are not included in Modify Bearer Request, the PGW-C+SMF release those QoS Flows. Rev5: Alignment of wording, and statements in 4.11.1.2.1 steps 12-12c and 4.11.1.3.2 steps 15-15c are corrected to refer to PDU Session(s). Some ordering and reshuffling of the text to improve readability. Remove duplicated text.","secretary_remarks":"Revision R01 of S2-2001877. Approved","agenda_item_sort_order":20,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":11480,"status":"agreed","reservation_date":"2020-02-28 13:23:25","uploaded":"2020-02-29 09:46:33","revisionof":"S2-2001877","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1980.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-200079","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002444.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002445","title":"NSSAI in the HO request during inter RAT\/EPS interworking","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For this purpose, this CR proposes update step 9 of 23.502 Figure 4.11.1.2.2.2-1 to state AMF sends Allowed NSSAI to NG-RAN as part of HO request","secretary_remarks":"Revision R03 of S2-2002210. Approved","agenda_item_sort_order":20,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":11520,"status":"agreed","reservation_date":"2020-02-28 13:23:26","uploaded":"2020-02-29 09:46:33","revisionof":"S2-2002210","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2146.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200079","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002445.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]