[{"name":"S2-1910854","title":"LS from CT WG3: LS on interface selection of GERAN, UTRAN and EUTRAN access","source":"CT WG3","contact":"Zhenning Huang","contact-id":60086,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is considering how to map the PCEF in EPC to the combination of SMF and UPF in 5GC in a way that will enable all required UE mobility scenarios between combinations of radio (GERAN\/UTRAN, EUTRAN, 5G-NR) and core (EPC, 5GC) technologies. There is an assumption that we have mobility between GERAN\/UTRAN and EUTRAN, and between EUTRAN and NR. But the mobility among GERAN\/UTRAN, EUTRAN and NR is not specified. It is specified in the introduction part of 3GPP TS 23.503 that the PCEF of 3GPP TS 23.203 is mapped to the combination of SMF and UPF in 5GC.There is no description on which interface should be used when UE is under GERAN\/UTRAN. How the SMF\/PGW-C could contain the full PCEF, and how the functionality could be provided is also not clearly defined. CT WG3 kindly asks SA WG2 to answer the following questions: Question 1: If the UE performs the initial attach procedure from EUTRAN, then it could perform mobility from EUTRAN to GERAN\/UTRAN and also from EUTRAN to NR. Which mobility cases can be supported among GERAN\/UTRAN, EUTRAN and NR? Question 2: Could the SMF\/PGW-C contain the PCEF, whereby the SMF\/PGW-C supports the PCEF functionality under 3GPP-EPS IP-CAN type? Question 3: Should the N7 interface be extended to support the GERAN\/UTRAN RAT type? If the N7 interface is extended to support the GERAN\/UTRAN RAT type, what is the impact on the Npcf from SA WG2 view?. Action: CT WG3 kindly asks SA WG2 to answer the above questions, and also consider updating their specs such as to bring necessary adaptation to Npcf.","secretary_remarks":"Postponed S2-1908666 from S2#135. Response drafted in S2-1911406. Final response in S2-1912509","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12810,"status":"replied to","reservation_date":"2019-10-30 08:52:10","uploaded":"2019-11-04 09:40:46","revisionof":"S2-1908666","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-193640","lsreply":"S2-1912509","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910854.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910972","title":"Adding direct forwarding during HO between EPS and 5GS","source":"ZTE, Ericsson","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding direct data forwarding support during mobility between EPS and 5GS","secretary_remarks":"Revision of endorsed\/postponed S2-1910314 from S2#135. Revised in parallel session to S2-1912117.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12780,"status":"revised","reservation_date":"2019-11-04 12:32:34","uploaded":"2019-11-08 15:24:13","revisionof":"S2-1910314","revisedto":"S2-1912117","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"},{"winame":"Direct_data_fw_NR-Core"}],"crnumber":1804.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910972.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911037","title":"Correction to EPS-5GS idle mobility with N26","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 4.11.1.3.2 5GS to EPS Idle mode mobility using N26 interface Remove the text related to timer in step 5a; add V-SMF and V-UPF in the figure; Step 5a, clarify the behaviour for non-roaming\/LBO roaming and home routed roaming; Add step 12a: PGW-C+SMF may perform SM Policy Association Modification e.g. due to RAT change; New step 15b&15c to show that AMF release the resource in V-SMF and V-SMF release resource in V-UPF. Clause 4.11.1.3.3 EPS to 5GS Mobility Registration Procedure (Idle and Connected State) using N26 interface In Figure 4.11.1.3.3, add V-SMF and V-UPF Step 14, remove the referenced steps from 17-20 as they're not applicable to EPS to 5GS mobility; Add step 14a and 14c for Nsmf_PDUSession_CreateSMContext for HR roaming; Add steps 14b and 14f for interaction between V-SMF and V-UPF; Add step 14c for interaction between PGW-C+SMF and (H-)UPF; Add step 14e optional PCF interaction; Add step 14f V-SMF informs V-UPF of the CN tunnel info of (H-)UPF; Add step 16a that the source MME deletes the resource in SGW. Add step 17a to show the optional AMF-PCF interaction for UE policy, which happens after Step 17 Registration Accept (note that 23.502CR1710 (S2-1910372) added a referenced to step 21b of clause 4.2.2.2.2 in Step 14 does not have a correct sequence). In text description, Step 14 is updated accordingly so that the figure and the text description is aligned; In step14, remove text 'and for Idle state mobility registration, release the resource of the CN tunnels for EPS bearers corresponding to the PDU session as well' as the CN tunnels are not released in the home routed roaming.","secretary_remarks":"Revised in parallel session to S2-1912118.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12810,"status":"revised","reservation_date":"2019-11-06 00:10:13","uploaded":"2019-11-08 04:33:34","revisionof":"","revisedto":"S2-1912118","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1875.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911037.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911209","title":"Correction on UE context handling during inter system mobility","source":"Samsung","contact":"Sangsoo Jeong","contact-id":81802,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the UE radio capability stored in the source CN node cannot be used during the (idle mode) inter-system mobility.","secretary_remarks":"Confirm Specification Number! Confirm CR Number! Confirm Spec version!. Revised in parallel session to S2-1912119.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12830,"status":"revised","reservation_date":"2019-11-07 10:54:15","uploaded":"2019-11-08 11:01:01","revisionof":"","revisedto":"S2-1912119","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1935.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911209.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911210","title":"Correction on UE context handling during inter system mobility","source":"Samsung","contact":"Sangsoo Jeong","contact-id":81802,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the UE radio capability stored in the source CN node cannot be used during the (idle mode) inter-system mobility.","secretary_remarks":"Confirm Specification Number! Confirm CR Number! Confirm Spec version!. Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12860,"status":"noted","reservation_date":"2019-11-07 10:56:48","uploaded":"2019-11-08 11:01:01","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3560.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911210.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911271","title":"EBI management for QoS flow.","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Decision","abstract":"This contribution discuss how to manage the EBI allocated to default QoS flow by AMF.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12870,"status":"noted","reservation_date":"2019-11-07 15:45:20","uploaded":"2019-11-08 16:06:59","revisionof":"","revisedto":"S2-2000367","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_136_Reno\/Docs\/S2-1911271.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911272","title":"EBI management for QoS flow","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change wording in clause 4.11.1.2.1 to enable handover of Non GBR bearers to 4G. Correct that the EBI of default QoS flow can not be revoked early than EBI of other QoS flow within the same PDU Session.","secretary_remarks":"Revised in parallel session to S2-1912120.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12880,"status":"revised","reservation_date":"2019-11-07 15:45:20","uploaded":"2019-11-08 16:06:59","revisionof":"","revisedto":"S2-1912120","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1894.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911272.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911273","title":"Number of EBIs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In case of mobility procedures involving target EPC nodes not supporting 15 EPS bearers, the QoS flow, which is associated with the not supported EPS Bearer ID value, shall not be transferred to EPC network and released at the 5GC side.","secretary_remarks":"Revised in parallel session to S2-1912121.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12920,"status":"revised","reservation_date":"2019-11-07 15:45:22","uploaded":"2019-11-08 16:06:59","revisionof":"","revisedto":"S2-1912121","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1941.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911273.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911274","title":"Number of EBIs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF indicate whether the target EPS network support 15 EPS bearer to PGW-C+SMF, based on that indication the PGW-C+SMF determine whether the QoS flow associated with not supported EPC Bearer ID value shall not be transferred to EPS network and released at the 5GC side. In the HR roaming case, the V-SMF transfer the 15 EPS supported or not indication to H-SMF. H-SMF release the non accepted QoS flow.","secretary_remarks":"Revised in parallel session to S2-1912122.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12960,"status":"revised","reservation_date":"2019-11-07 15:45:23","uploaded":"2019-11-08 16:06:59","revisionof":"","revisedto":"S2-1912122","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1895.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911274.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911297","title":"Correction of implementation of CR #1321","source":"Intel","contact":"Robert Zaus","contact-id":10799,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Re-insertion of the missing words","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12870,"status":"agreed","reservation_date":"2019-11-07 16:17:18","uploaded":"2019-11-07 16:27:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1945.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-191090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911297.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911406","title":"[DRAFT] Reply LS on interface selection of GERAN, UTRAN and EUTRAN access","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"LS out","for":"Approval","abstract":"Responds to CT WG3 LS stating that SMF\/UPF does not support mobility to and from GERAN\/UTRAN.","secretary_remarks":"Revision of S2-1910313 from S2#135. Response to S2-1910854. Revised in parallel session to S2-1912116.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12750,"status":"revised","reservation_date":"2019-11-08 03:02:41","uploaded":"2019-11-08 23:06:25","revisionof":"S2-1910313","revisedto":"S2-1912116","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"en5GPccSer"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"S2-1910854","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911406.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912116","title":"[DRAFT] Reply LS on interface selection of GERAN, UTRAN and EUTRAN access","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"LS out","for":"Approval","abstract":"Responds to CT WG3 LS stating that SMF\/UPF does not support mobility to and from GERAN\/UTRAN.","secretary_remarks":"Revision of S2-1911406. Revised in parallel session to S2-1912509.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12760,"status":"revised","reservation_date":"2019-11-20 19:43:35","uploaded":"2019-11-25 15:57:55","revisionof":"S2-1911406","revisedto":"S2-1912509","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"en5GPccSer"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"S2-1910854","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912116.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912117","title":"Adding direct forwarding during HO between EPS and 5GS","source":"ZTE, Ericsson","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding direct data forwarding support during mobility between EPS and 5GS Rev 3: replace 'CN tunnel' with 'tunnel' in the step 13 and 14 in the clause 4.11.1.2.2.2","secretary_remarks":"Revision of S2-1910972. Agreed in parallel session. Block approved","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12860,"status":"agreed","reservation_date":"2019-11-20 19:43:35","uploaded":"2019-11-25 15:57:55","revisionof":"S2-1910972","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"},{"winame":"Direct_data_fw_NR-Core"}],"crnumber":1804.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_136_Reno\/Docs\/S2-1912117.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912118","title":"Correction to EPS-5GS idle mobility with N26","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 4.11.1.3.2 5GS to EPS Idle mode mobility using N26 interface Remove the text related to timer in step 5a; add V-SMF and V-UPF in the figure; Step 5a, clarify the behaviour for non-roaming\/LBO roaming and home routed roaming; Add step 12a: PGW-C+SMF may perform SM Policy Association Modification e.g. due to RAT change; New step 15b&15c to show that AMF release the resource in V-SMF and V-SMF release resource in V-UPF. Clause 4.11.1.3.3 EPS to 5GS Mobility Registration Procedure (Idle and Connected State) using N26 interface In Figure 4.11.1.3.3, add V-SMF and V-UPF Step 14, remove the referenced steps from 17-20 as they're not applicable to EPS to 5GS mobility; Add step 14a and 14c for Nsmf_PDUSession_CreateSMContext for HR roaming; Add steps 14b and 14f for interaction between V-SMF and V-UPF; Add step 14c for interaction between PGW-C+SMF and (H-)UPF; Add step 14e optional PCF interaction; Add step 14f V-SMF informs V-UPF of the CN tunnel info of (H-)UPF; Add step 16a that the source MME deletes the resource in SGW. Add step 17a to show the optional AMF-PCF interaction for UE policy, which happens after Step 17 Registration Accept (note that 23.502CR1710 (S2-1910372) added a referenced to step 21b of clause 4.2.2.2.2 in Step 14 does not have a correct sequence). In text description, Step 14 is updated accordingly so that the figure and the text description is aligned; In step14, remove text 'and for Idle state mobility registration, release the resource of the CN tunnels for EPS bearers corresponding to the PDU session as well' as the CN tunnels are not released in the home routed roaming.","secretary_remarks":"Revision of S2-1911037. Agreed in parallel session. Block approved","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12890,"status":"agreed","reservation_date":"2019-11-20 19:43:36","uploaded":"2019-11-25 15:57:55","revisionof":"S2-1911037","revisedto":"SP-191115","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1875.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-191091","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912118.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912119","title":"Correction on UE context handling during inter system mobility","source":"Samsung","contact":"Sangsoo Jeong","contact-id":81802,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the UE radio capability stored in the source CN node cannot be used during the (idle mode) inter-system mobility.","secretary_remarks":"Revision of S2-1911209. Revised in parallel session to S2-1912505.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12840,"status":"revised","reservation_date":"2019-11-20 19:43:38","uploaded":"2019-11-25 15:57:55","revisionof":"S2-1911209","revisedto":"S2-1912505","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1935.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912119.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912120","title":"EBI management for QoS flow","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change wording in clause 4.11.1.2.1 to enable handover of Non GBR bearers to 4G. Correct that the EBI of default QoS flow can be revoked early than EBI of other QoS flow within the same PDU Session.","secretary_remarks":"Revision of S2-1911272. Revised in parallel session to S2-1912506.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12890,"status":"revised","reservation_date":"2019-11-20 19:43:39","uploaded":"2019-11-25 15:57:55","revisionof":"S2-1911272","revisedto":"S2-1912506","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1894.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912120.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912121","title":"Number of EBIs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In case of mobility procedures involving target EPC nodes not supporting 15 EPS bearers, the QoS flow, which is associated with the not supported EPS Bearer ID value, shall not be transferred to EPC network and released at the 5GC side.","secretary_remarks":"Revision of S2-1911273. Revised in parallel session to S2-1912507.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12930,"status":"revised","reservation_date":"2019-11-20 19:43:40","uploaded":"2019-11-25 15:57:55","revisionof":"S2-1911273","revisedto":"S2-1912507","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1941.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912121.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912122","title":"Number of EBIs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF indicate whether the target EPS network support 15 EPS bearer to PGW-C+SMF, based on that indication the PGW-C+SMF determine whether the QoS flow associated with not supported EPC Bearer ID value shall not be transferred to EPS network and released at the 5GC side. In the HR roaming case, the V-SMF transfer the 15 EPS supported or not indication to H-SMF. H-SMF release the non accepted QoS flow.","secretary_remarks":"Revision of S2-1911274. Revised in parallel session to S2-1912508.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12970,"status":"revised","reservation_date":"2019-11-20 19:43:41","uploaded":"2019-11-25 15:57:55","revisionof":"S2-1911274","revisedto":"S2-1912508","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1895.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912122.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912505","title":"Correction on UE context handling during inter system mobility","source":"Samsung","contact":"Sangsoo Jeong","contact-id":81802,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the UE radio capability stored in the source CN node cannot be used during the (idle mode) inter-system mobility.","secretary_remarks":"Revision of S2-1912119. Agreed in parallel session. Block approved","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12920,"status":"agreed","reservation_date":"2019-11-25 15:19:48","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912119","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1935.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_136_Reno\/Docs\/S2-1912505.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912506","title":"EBI management for QoS flow","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change wording in clause 4.11.1.2.1 to enable handover of Non GBR bearers to 4G. Correct that the EBI of default QoS flow can be revoked early than EBI of other QoS flow within the same PDU Session.","secretary_remarks":"Revision of S2-1912120. Revised in parallel session to S2-1912548.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12900,"status":"revised","reservation_date":"2019-11-25 15:19:49","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912120","revisedto":"S2-1912548","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1894.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912506.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912507","title":"Number of EBIs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In case of mobility procedures involving target EPC nodes not supporting 15 EPS bearers, the QoS flow, which is associated with the not supported EPS Bearer ID value, shall not be transferred to EPC network and released at the 5GC side.","secretary_remarks":"Revision of S2-1912121. Revised in parallel session to S2-1912546.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12940,"status":"revised","reservation_date":"2019-11-25 15:19:50","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912121","revisedto":"S2-1912546","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1941.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912507.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912508","title":"Number of EBIs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF indicate whether the target EPS network support 15 EPS bearer to PGW-C+SMF, based on that indication the PGW-C+SMF determine whether the QoS flow associated with not supported EPC Bearer ID value shall not be transferred to EPS network and released at the 5GC side. In the HR roaming case, the V-SMF transfer the 15 EPS supported or not indication to H-SMF. H-SMF release the non accepted QoS flow.","secretary_remarks":"Revision of S2-1912122. Revised in parallel session to S2-1912547.","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12980,"status":"revised","reservation_date":"2019-11-25 15:19:51","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912122","revisedto":"S2-1912547","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1895.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912508.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912509","title":"Reply LS on interface selection of GERAN, UTRAN and EUTRAN access","source":"SA WG2","contact":"Irfan Ali","contact-id":74090,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4","secretary_remarks":"Revision of S2-1912116. Agreed in parallel session. Block approved","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12770,"status":"approved","reservation_date":"2019-11-25 15:19:52","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912116","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"en5GPccSer"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1910854","lsto":"CT WG3","Cc":"CT WG4","lsoriginalls":"S2-1910854","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912509.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912546","title":"Number of EBIs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In case of mobility procedures involving target EPC nodes not supporting 15 EPS bearers, the QoS flow, which is associated with the not supported EPS Bearer ID value, shall not be transferred to EPC network and released at the 5GC side.","secretary_remarks":"Revision of S2-1912507. For e-mail approval","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12950,"status":"revised","reservation_date":"2019-11-25 15:20:55","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912507","revisedto":"S2-1912775","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1941.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912546.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912547","title":"Number of EBIs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF indicate whether the target EPS network support 15 EPS bearer to PGW-C+SMF, based on that indication the PGW-C+SMF determine whether the QoS flow associated with not supported EPC Bearer ID value shall not be transferred to EPS network and released at the 5GC side. In the HR roaming case, the V-SMF transfer the 15 EPS supported or not indication to H-SMF. H-SMF release the non accepted QoS flow.","secretary_remarks":"Revision of S2-1912508. For e-mail approval","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12990,"status":"available","reservation_date":"2019-11-25 15:20:57","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912508","revisedto":"S2-2000369","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1895.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912547.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912548","title":"EBI management for QoS flow","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change wording in clause 4.11.1.2.1 to enable handover of Non GBR bearers to 4G. Correct that the EBI of default QoS flow can be revoked early than EBI of other QoS flow within the same PDU Session.","secretary_remarks":"Revision of S2-1912506. This CR was agreed","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":12980,"status":"agreed","reservation_date":"2019-11-25 15:20:58","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912506","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1894.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_136_Reno\/Docs\/S2-1912548.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912775","title":"Number of EBIs","source":"Huawei, HiSilicon, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In case of mobility procedures involving target EPC nodes not supporting 15 EPS bearers, the QoS flow, which is associated with the not supported EPS Bearer ID value, shall not be transferred to EPC network and released at the 5GC side.","secretary_remarks":"e-mail revision 2 of S2-1912546. This CR was agreed","agenda_item_sort_order":21,"ainumber":"6.9","ainame":"Interworking and Migration","tdoc_agenda_sort_order":13030,"status":"agreed","reservation_date":"2019-11-28 05:47:26","uploaded":"2019-11-28 08:32:54","revisionof":"S2-1912546","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1941.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-191090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912775.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]