[{"name":"S2-1906883","title":"SMF Delegated Discovery and Selection for HR scenario","source":"NTT DOCOMO, Oracle Corporation, ZTE, Deutsche Telekom AG, Verizon","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provide a solution for delegated SMF and PCF discovery in HR roaming and ETSUN. V-SMF discovery (6.3.2): 1. AMF sends Nsmf_PDUSession_CreateSMContext Request to SCP. The request indicates target PLMN ID for the H-SMF (HPLMN ID). The request indicates 'UE location', 'DNN' and 'V-SMF supports delegated discovery' as discovery and selection parameters to SCP. 2. SCP selects the V-SMF from the serving PLMN. 3. V-SMF determines the need for HR roaming (based on the target HPLMN ID for the H-SMF). 4. V-SMF sends Nsmf_PDUSession_Create Request to SCP. 5. SCP discovers the H-SMF from the vNRF and hNRF based on the HPLMN ID. If the SCP cannot find an V-SMF supporting the delegated discovery, it returns an error to AMF, and AMF performs the discovery of H-SMF and V-SMF. AMF then sends Nsmf_PDUSession_CreateSMContext Request to SCP, and includes the H-SMF address to the request. I-SMF discovery (5.34.3): Similar procedure is used for selecting the I-SMF as above for V-SMF selection with following differences: 2. As a first priority the SCP attempts to discover the SMF supporting the UE location and DNN. If the SCP discovery cannot find an SMF that supports the UE location and DNN, then as a second priority, the SCP attempts to discover the SMF using only the UE location as input (i.e. I-SMF). 3. If the selected SMF determines it cannot serve the DNN, the SMF acts as an I-SMF. I-SMF sends Nsmf_PDUSession_Create Request to SCP. The request does not contain the UE location as a selection parameter. 4. Based on the lack of UE location as a selection parameter, the SCP discovers the SMF supporting the DNN. SMF Service Area: The AMF needs to be aware of the Service Area of the discovered SMF. The proposed solution is that the AMF obtains this information from the SMF after the response for PDU session creation. V-PCF discovery (6.3.7.1): Similar procedure is used for selecting the V-PCF as above for V-SMF selection: 1. AMF sends AM policy association establishment request to SCP. 2. SCP selects the V-PCF. 3. V-PCF includes the V-PCF ID in a response to AMF. 4. AMF sends UE policy association establishment request to SCP, indicating the V-PCF ID as a target. The request indicates target PLMN ID for the H-PCF (HPLMN ID). 5. SCP selects the V-PCF as indicated by the V-PCF ID. 6. V-PCF sends UE policy association establishment request to SCP, indicating the PLMN ID of the H-PCF as a discovery and selection parameter SCP. 7. SCP discovers the H-PCF based on the HPLMN ID. The related open Editor's Notes are removed.","secretary_remarks":"Revision of S2-1904988 from S2#133. Revised in parallel session to S2-1908041.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22830,"status":"revised","reservation_date":"2019-06-11 14:01:49","uploaded":"2019-06-18 10:53:54","revisionof":"S2-1904988","revisedto":"S2-1908041","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1129.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906883.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906971","title":"CTSF challenges","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution lists some challenges related to using CTSF as a new NF mediating the context transfer between two NFs. It is argued that given the unclear need and value of the CTSF, and the expected complexity of addressing the challenges mentioned above the CTSF should not be introduced in R16","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23020,"status":"noted","reservation_date":"2019-06-13 16:12:36","uploaded":"2019-06-18 03:20:11","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eSBA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906971.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906973","title":"Procedures and call flows for SMF Delegated Discovery and Selection in HR and specific SMF Service Areas scenarios","source":"Oracle Corporation, NTT Docomo, ZTE, Deutsche Telekom AG, Verizon UK Ltd","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A new clause Annex X is added to capture the concepts and generic functionality required for addressing the scenario of SMF Discovery and Selection in a delegated mode for Home Routed and specific SMF Service Areas scenarios as well as V-PCF\/H-PCF discovery in a delegated mode.","secretary_remarks":"Revision of S2-1905337 from S2#133. Revised in parallel session to S2-1908042.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22860,"status":"revised","reservation_date":"2019-06-13 19:05:08","uploaded":"2019-06-17 21:47:15","revisionof":"S2-1905337","revisedto":"S2-1908042","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1382.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906973.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906998","title":"Add a 'support of delegated discovery' attribute to producer profile in the NRF","source":"Oracle, NTT Docomo, ZTE, Deutsche Telekom AG","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding an optional 'support of delegated discovery' attribute in producer profile in the NRF to enable the SCP (or a consumer NF) to figure out whether an SMF or PCF supports delegated discovery. NOTE: As of now Support of delegated discovery is relevant only for SMF and PCF. However this paper proposes to make it a generic attribute to make it future proof. For example, it may needed for SCP delegated Discvery in SMSF related procedures (TS 23.502 4.13.3).","secretary_remarks":"Revised in parallel session to S2-1908044.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22890,"status":"revised","reservation_date":"2019-06-13 23:10:19","uploaded":"2019-06-16 22:20:31","revisionof":"","revisedto":"S2-1908044","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1480.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906998.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907020","title":"ESBA PCF discovery and selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Roaming behavior for delegated discovery Editorials for improved readability. E.g. moving text, fixing bullet list etc","secretary_remarks":"Revision of S2-1905056 from S2#133 Merged into S2-1908043","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22930,"status":"merged","reservation_date":"2019-06-14 14:52:23","uploaded":"2019-06-18 03:20:11","revisionof":"S2-1905056","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1310.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907020.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907021","title":"Discussion regarding SMF selection for eSBA","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discusses SMF selection for eSBA","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22910,"status":"noted","reservation_date":"2019-06-14 14:54:00","uploaded":"2019-06-18 13:27:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eSBA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907021.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907127","title":"Support of Service Context Transfer via Context Transfer Storage Function","source":"KDDI, Deutsche Telekom, Telecom Italia, Sprint, AT&T, Verizon, Telstra, Tencent","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To introduce the CTSF and to add the description for the support of Service Context Transfer via CTSF","secretary_remarks":"Revision of S2-1906745 from S2#133. For e-mail approval. Noted","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23410,"status":"noted","reservation_date":"2019-06-15 06:55:11","uploaded":"2019-06-18 14:59:26","revisionof":"S2-1906745","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1391.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907127.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907128","title":"Service Context Transfer Support via CTSF","source":"KDDI, Deutsche Telekom, Telecom Italia, Sprint, AT&T, Verizon, Telstra, Tencent","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This document introduces indirect service context transfer via a context transfer storage function.","secretary_remarks":"Revision of S2-1906746 from S2#133. Revised in parallel session to S2-1908047.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23040,"status":"revised","reservation_date":"2019-06-15 06:59:20","uploaded":"2019-06-18 14:59:39","revisionof":"S2-1906746","revisedto":"S2-1908047","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1393.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907128.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907129","title":"Discussion on SM Context Transfer","source":"Deutsche Telekom","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses and proposes a way forward to finalize context transfer for SM context transfer.","secretary_remarks":"Not Handled","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23120,"status":"not treated","reservation_date":"2019-06-15 07:08:48","uploaded":"2019-06-18 15:00:58","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eSBA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907129.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907215","title":"eSBA SMF and PCF selection","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF does not delegate the SMF discovery to SCP if Network is configured to support ETSUN or the PDU Session is for HR roaming.","secretary_remarks":"Revision of S2-1906569 from S2#133. For e-mail approval. Noted","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23320,"status":"noted","reservation_date":"2019-06-17 00:45:28","uploaded":"2019-06-18 14:13:13","revisionof":"S2-1906569","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1403.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907215.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907216","title":"SMF Context Transfer Procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the below behaviour: how the new SMF interaction with PCF; how the old registration and subscription in UDM is handled; how it is handled if concurrent request from peer NFs comes to the old SMF while the session is transferring to the new SMF; how the N4 session is handled;","secretary_remarks":"Merged into S2-1908098","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23130,"status":"merged","reservation_date":"2019-06-17 00:45:29","uploaded":"2019-06-18 14:13:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1521.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907216.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907220","title":"Consideration for SMF and PCF selection","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discuss the SMF\/PCF selection for the HR roaming and ETSUN case.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22920,"status":"noted","reservation_date":"2019-06-17 00:53:57","uploaded":"2019-06-18 14:13:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907220.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907315","title":"Update SM context transfer procedure","source":"Deutsche Telekom AG","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updated SMF Service Context Transfer procedures in which the SM Context Transfer is performed indirectly via CTSF Removed SM Context ID from step 4 Clarification for Nsmf_PDUSession_SMContextStatusNotify","secretary_remarks":"Revised in parallel session to S2-1908030.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23140,"status":"revised","reservation_date":"2019-06-17 09:23:44","uploaded":"2019-06-18 15:00:05","revisionof":"","revisedto":"S2-1908030","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1539.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907315.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907522","title":"Update of context transfer procedures","source":"Tencent","contact":"Zhuoyun Zhang","contact-id":78278,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the push or pull model is used by the NF based on specific procedures or implementation. Clarify that the context transfer procedure happens before the old NF informs the NRF that it is about to be decommissioned. Other Editorial changes are made.","secretary_remarks":"Remove '-Exception' from WI Code. Revised in parallel session to S2-1908099.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23190,"status":"revised","reservation_date":"2019-06-18 01:47:33","uploaded":"2019-06-18 13:10:00","revisionof":"","revisedto":"S2-1908099","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1597.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907522.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907523","title":"SMF Service Context Transfer procedure update","source":"Tencent","contact":"Zhuoyun Zhang","contact-id":78278,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change Nsmf_PDUSession_StatusNotify to Nsmf_PDUSession_SMContextStatusNotify in clause 4.26.5.2. In clause 4.26.5.3, (1) In step 2, change Nsmf_PDUSession_StatusNotify to Nsmf_PDUSession_SMContextStatusNotify. (2) For the second editor's note, it is proposed to delete it and change N4 session establish to N4 session modification and change SM policy association creation to update. (3) In the original figure, step 6 and 13 are removed due to the revision in the above bullet. 3. Update the service description for Nsmf_PDUSession_SMContextStatusNotify 4. Udpate the service description for Nsmf_PDUSession_ContextPush","secretary_remarks":"Remove ' -Exception' from WI Code Merged into S2-1908098","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23220,"status":"merged","reservation_date":"2019-06-18 02:05:44","uploaded":"2019-06-18 13:10:00","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1598.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907523.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907542","title":"Bulk context transfer using CTSF","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Proposes a solution to achieve this: Source NF \/ OA&M system determines when it needs to offload context and how many contexts it wants to transfer to NFs across sets. At this point, source NF stores context in the CTSF. Source NF can also notify OA&M at this point. OA&M triggers the target NF(s) (could be one or more) to retrieve contexts from the CTSF. (we assume that only one target NF can get access to a certain UE context, target NF retrieves data by simply asking for number of contexts).","secretary_remarks":"Revised in parallel session to S2-1908097.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23250,"status":"revised","reservation_date":"2019-06-18 02:46:17","uploaded":"2019-06-18 12:37:42","revisionof":"","revisedto":"S2-1908097","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1624.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907542.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907543","title":"Bulk context transfer procedure using CTSF","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Proposes a solution to achieve this: Source NF \/ OA&M system determines when it needs to offload context and how many contexts it wants to transfer to NFs across sets. At this point, source NF stores context in the CTSF. Source NF can also notify OA&M at this point. OA&M triggers the target NF(s) (could be one or more) to retrieve contexts from the CTSF. (we assume that only one target NF can get access to a certain UE context, target NF retrieves data by simply asking for number of contexts).","secretary_remarks":"Not Handled","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23290,"status":"not treated","reservation_date":"2019-06-18 02:46:18","uploaded":"2019-06-18 12:37:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1602.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907543.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907630","title":"SMF Service Area","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enhance the Nsmf_EventExposure service to be able to report the change of the SMF Service Area. The AMF that uses delegated SMF discovery uses this service to obtain the SMF Service Area of the selected I\/V-SMF and anchor SMF.","secretary_remarks":"Revised in parallel session to S2-1908046.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23300,"status":"revised","reservation_date":"2019-06-18 08:04:03","uploaded":"2019-06-18 10:53:54","revisionof":"","revisedto":"S2-1908046","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1623.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907630.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907663","title":"Updating the SMF context procedure","source":"Samsung","contact":"Sangsoo Jeong","contact-id":81802,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updated 4.26.5.3 to clarify the target SMF can be selected dynamically in consideration of the actual network status with the use of the target SMF set ID. Updated 4.26.5.1 to clarify that the SMF context transfer procedure can be used between two SMFs within the same SMF set.","secretary_remarks":"Merged into S2-1908098","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23240,"status":"merged","reservation_date":"2019-06-18 09:22:21","uploaded":"2019-06-18 09:25:03","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1632.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907663.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907678","title":"Adding SMF Service Context Transfer procedure-push model","source":"Tencent","contact":"Zhuoyun Zhang","contact-id":78278,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding SMF context transfer push procedure. Clarify that the SMF decides the context transfer model based on local configuration. Other editor changes.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23230,"status":"noted","reservation_date":"2019-06-18 10:03:07","uploaded":"2019-06-18 13:10:00","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1636.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907678.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907707","title":"SMF and PCF selection - option 2","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF first provide selection parameters for H-SMF or H-PCF selection to SCP, and indicate that the request message shall not be sent to the H-SMF\/H-PCF. After H-SMF\/H-PCF discovery, the SCP rejects the request and returns the discovered H-SMF\/H-PCF to NF serivce consumer. The NF service consumer then add H-SMF\/H-PCF into request message, and send it together with parameters for V-SMF\/V-PCF discovery. The SCP discovers and selects V-SMF\/V-PCF, and forward the request message to the selected V-SMF\/V-PCF. During the selection procedure, the AMF also indicate whether the selected SMF profile is required.","secretary_remarks":"Revised in parallel session, merging S2-1907020, to S2-1908043.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22950,"status":"revised","reservation_date":"2019-06-18 11:18:20","uploaded":"2019-06-18 14:13:13","revisionof":"","revisedto":"S2-1908043","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1664.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907707.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908030","title":"Update SM context transfer procedure","source":"Ericsson?, Huawei?, Samsung?, Tencent?, DT","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to modify the procedure description according to the changes below and remove the current editors notes Rev 1 Merge with S2-1906972 Removed first EN 'It is FFS if step 2-3 can be replaced with a subscribe notify of the UE status from SMF to AMF.' Updated the sequence diagram accordingly. The SMF becomes in control of the context transfer instead of the AMF. This could be beneficial in some cases, e.g., when deadlines for context transfer are to be met and the timing information should be managed solely by the Old SMF. Removed second EN: 'It is FFS if step 6 and 9 can be optimised or changed to a modification of the N4 session'. Introduced ''N4 session release' with flag notifying the UPF about the expected re-establishment of the N4 session for the same PDU session. Based on this, the UPF may temporarily keep some information related to the N4 session to optimize packet handling until the N4 session is re-established by the new SMF. Rev 1 Merge with S2-1907128, S2-1907216, S2-1907315, S2-1907523, S2-1907663 Updated 4.26.5.3 to clarify the target SMF can be selected dynamically in consideration of the actual network status with the use of the target SMF set ID. Updated 4.26.5.1 to clarify that the SMF context transfer procedure can be used between two SMFs within the same SMF set. Change Nsmf_PDUSession_StatusNotify to Nsmf_PDUSession_SMContextStatusNotify in clause 4.26.5.2. In clause 4.26.5.3, In step 2, change Nsmf_PDUSession_StatusNotify to Nsmf_PDUSession_SMContextStatusNotify. For the second editor's note, it is proposed to delete it and change N4 session establish to N4 session modification and change SM policy association creation to update. In the original figure, step 6 and 13 are removed due to the revision in the above bullet. Update the service description for Nsmf_PDUSession_SMContextStatusNotify Added Old SMF ID, PDU Session ID, SUPI, SM Context ID tp CreateSMContext request so as to be consistent with the information sent in step 1. Clarified the UE state as CM-IDLE and CM-CONNECTED with RRC inactive state Added notification from New SMF to Old SMF to notify the finishing of the context transfer. Clarified that not 'everything' is removed from the UPF but rather only unused information Clarification in Nsmf_PDUSession_ContextRequest service operation to mention SM Context Transfer How it is handled if concurrent request from peer NFs comes to the old SMF while the session is transferring to the new SMF; How the new SMF interaction with PCF; How the old registration and subscription in UDM is handled; How the N4 session is handled; Updated CreateSMContext service operation","secretary_remarks":"Revision of S2-1907315. Revised in parallel session to S2-1908048.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23150,"status":"revised","reservation_date":"2019-07-04 09:11:28","uploaded":"2019-07-04 09:17:57","revisionof":"S2-1907315","revisedto":"S2-1908048","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1539.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908030.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908041","title":"SMF Delegated Discovery and Selection for HR scenario","source":"NTT DOCOMO, Oracle Corporation, ZTE, Deutsche Telekom AG, Verizon","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provide a solution for delegated SMF and PCF discovery in HR roaming and ETSUN. V-SMF discovery (6.3.2): 1. AMF sends Nsmf_PDUSession_CreateSMContext Request to SCP. The request indicates target PLMN ID for the H-SMF (HPLMN ID). The request indicates 'UE location' and DNN' as discovery and selection parameters to SCP. 2. SCP selects the V-SMF from the serving PLMN. 3. V-SMF determines the need for HR roaming (based on the target HPLMN ID for the H-SMF). 4. V-SMF sends Nsmf_PDUSession_Create Request to SCP. 5. SCP discovers the H-SMF from the vNRF and hNRF based on the HPLMN ID. I-SMF discovery (5.34.3): Similar procedure is used for selecting the I-SMF as above for V-SMF selection with following differences: 1. As a first priority the AMF attempts to get the SMF discovered that supports the UE location and DNN. If the SCP discovery cannot find an SMF that supports the UE location and DNN, the SCP returns an error to AMF and AMF attempts to get the SMF discovered using only the UE location as input (i.e. I-SMF). 2. If the selected SMF determines it cannot serve the DNN, the SMF acts as an I-SMF. I-SMF sends Nsmf_PDUSession_Create Request to SCP. The request does not contain the UE location as a selection parameter. 3. Based on the lack of UE location as a selection parameter, the SCP discovers the SMF supporting the DNN. SMF Service Area: The AMF needs to be aware of the Service Area of the discovered SMF. The proposed solution is that the AMF obtains this information from the NRF after the response for PDU session creation. V-PCF discovery (6.3.7.1): Similar procedure is used for selecting the V-PCF as above for V-SMF selection: 1. AMF sends AM policy association establishment request to SCP. 2. SCP selects the V-PCF. 3. V-PCF includes the V-PCF ID in a response to AMF. 4. AMF sends UE policy association establishment request to SCP, indicating the V-PCF ID as a target. The request indicates target PLMN ID for the H-PCF (HPLMN ID). 5. SCP selects the V-PCF as indicated by the V-PCF ID. 6. V-PCF sends UE policy association establishment request to SCP, indicating the PLMN ID of the H-PCF as a discovery and selection parameter SCP. 7. SCP discovers the H-PCF based on the HPLMN ID. The related open Editor's Notes are removed.","secretary_remarks":"Revision of S2-1906883. Revised in parallel session to S2-1908149.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22840,"status":"revised","reservation_date":"2019-07-04 09:11:42","uploaded":"2019-07-04 09:17:57","revisionof":"S2-1906883","revisedto":"S2-1908149","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1129.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908041.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908042","title":"Procedures and call flows for SMF Delegated Discovery and Selection in HR and specific SMF Service Areas scenarios","source":"Oracle Corporation, NTT Docomo, ZTE, Deutsche Telekom AG, Verizon UK Ltd","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A new clause Annex X is added to capture the concepts and generic functionality required for addressing the scenario of SMF Discovery and Selection in a delegated mode for Home Routed and specific SMF Service Areas scenarios as well as V-PCF\/H-PCF discovery in a delegated mode.","secretary_remarks":"Revision of S2-1906973. Revised in parallel session to S2-1908150.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22870,"status":"revised","reservation_date":"2019-07-04 09:11:43","uploaded":null,"revisionof":"S2-1906973","revisedto":"S2-1908150","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1382.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908043","title":"SMF and PCF selection - option 2","source":"Huawei, HiSilicon, Ericsson?","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF first provide selection parameters for H-SMF or H-PCF selection to SCP, and indicate that the request message shall not be sent to the H-SMF\/H-PCF. After H-SMF\/H-PCF discovery, the SCP rejects the request and returns the discovered H-SMF\/H-PCF to NF serivce consumer. The NF service consumer then add H-SMF\/H-PCF into request message, and send it together with parameters for V-SMF\/V-PCF discovery. The SCP discovers and selects V-SMF\/V-PCF, and forward the request message to the selected V-SMF\/V-PCF. During the selection procedure, the AMF also indicate whether the selected SMF profile is required.","secretary_remarks":"Revision of S2-1907707, merging S2-1907020. Revised in parallel session to S2-1908120.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22960,"status":"revised","reservation_date":"2019-07-04 09:11:44","uploaded":"2019-07-04 09:17:57","revisionof":"S2-1907707","revisedto":"S2-1908120","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1664.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908043.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908044","title":"Add a 'support of delegated discovery' attribute to producer profile in the NRF","source":"Oracle, NTT Docomo, ZTE, Deutsche Telekom AG","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Adding an optional 'support of delegated discovery' attribute in producer profile in the NRF to enable the SCP (or a consumer NF) to figure out whether an SMF or PCF supports delegated discovery. NOTE: As of now Support of delegated discovery is relevant only for SMF and PCF. However this paper proposes to make it a generic attribute to make it future proof. For example, it may needed for SCP delegated Discvery in SMSF related procedures (TS 23.502 4.13.3).","secretary_remarks":"Revision of S2-1906998. Withdrawn","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22900,"status":"withdrawn","reservation_date":"2019-07-04 09:11:45","uploaded":null,"revisionof":"S2-1906998","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1480.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908045","title":"Candidate way forward options for delegated discovery","source":"Huawei","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"Decision","abstract":"-","secretary_remarks":"Created at meeting. Revised in parallel session to S2-1908095.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23000,"status":"revised","reservation_date":"2019-07-04 09:11:46","uploaded":"2019-07-04 09:17:57","revisionof":"","revisedto":"S2-1908095","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908045.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908046","title":"SMF Service Area","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Enhance the Nsmf_EventExposure service to be able to report the change of the SMF Service Area. The AMF that uses delegated SMF discovery uses this service to obtain the SMF Service Area of the selected I\/V-SMF and anchor SMF.","secretary_remarks":"Revision of S2-1907630. Withdrawn","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23310,"status":"withdrawn","reservation_date":"2019-07-04 09:11:46","uploaded":null,"revisionof":"S2-1907630","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1623.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908047","title":"Service Context Transfer Support via CTSF","source":"KDDI, Deutsche Telekom, Telecom Italia, Sprint, AT&T, Verizon, Telstra, Tencent","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This document introduces indirect service context transfer via a context handle.","secretary_remarks":"Revision of S2-1907128. Revised in parallel session to S2-1908096.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23050,"status":"revised","reservation_date":"2019-07-04 09:11:47","uploaded":"2019-07-04 09:17:57","revisionof":"S2-1907128","revisedto":"S2-1908096","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1393.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908047.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908048","title":"Update SM context transfer procedure","source":"DT, Samsung","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to modify the procedure description according to the changes below and remove the current editors notes Rev 1 Merge with S2-1906972 Removed first EN 'It is FFS if step 2-3 can be replaced with a subscribe notify of the UE status from SMF to AMF.' Updated the sequence diagram accordingly. The SMF becomes in control of the context transfer instead of the AMF. This could be beneficial in some cases, e.g., when deadlines for context transfer are to be met and the timing information should be managed solely by the Old SMF. Removed second EN: 'It is FFS if step 6 and 9 can be optimised or changed to a modification of the N4 session'. Introduced ''N4 session release' with flag notifying the UPF about the expected re-establishment of the N4 session for the same PDU session. Based on this, the UPF may temporarily keep some information related to the N4 session to optimize packet handling until the N4 session is re-established by the new SMF. Rev 1 Merge with S2-1907128, S2-1907216, S2-1907315, S2-1907523, S2-1907663 Updated 4.26.5.3 to clarify the target SMF can be selected dynamically in consideration of the actual network status with the use of the target SMF set ID. Updated 4.26.5.1 to clarify that the SMF context transfer procedure can be used between two SMFs within the same SMF set. Change Nsmf_PDUSession_StatusNotify to Nsmf_PDUSession_SMContextStatusNotify in clause 4.26.5.2. In clause 4.26.5.3, In step 2, change Nsmf_PDUSession_StatusNotify to Nsmf_PDUSession_SMContextStatusNotify. For the second editor's note, it is proposed to delete it and change N4 session establish to N4 session modification and change SM policy association creation to update. In the original figure, step 6 and 13 are removed due to the revision in the above bullet. Update the service description for Nsmf_PDUSession_SMContextStatusNotify Added Old SMF ID, PDU Session ID, SUPI, SM Context ID tp CreateSMContext request so as to be consistent with the information sent in step 1. Clarified the UE state as CM-IDLE and CM-CONNECTED with RRC inactive state Added notification from New SMF to Old SMF to notify the finishing of the context transfer. Clarified that not 'everything' is removed from the UPF but rather only unused information Clarification in Nsmf_PDUSession_ContextRequest service operation to mention SM Context Transfer How it is handled if concurrent request from peer NFs comes to the old SMF while the session is transferring to the new SMF; How the new SMF interaction with PCF; How the old registration and subscription in UDM is handled; How the N4 session is handled; Updated CreateSMContext service operation Rev 2 Replaced SMContextStatusNotify with notification from UDM, which was missing and can also serve the same purpose. Adjusted text in 4.XX.4, procedure text and figure to reflect this change Text in 10.1 and 10.2 was not matching the figure. Aligned text with the depicted procedure Moved 'The parameters from step 8 and, if applies, step 9 are used.' (step 10.2) to step 10.1","secretary_remarks":"Revision of S2-1908030. Revised in parallel session, merging S2-1907523, S2-1907216 and S2-1907663, to S2-1908098.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23160,"status":"revised","reservation_date":"2019-07-04 09:11:49","uploaded":"2019-07-04 09:17:57","revisionof":"S2-1908030","revisedto":"S2-1908098","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1539.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908048.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908095","title":"Candidate way forward options for delegated discovery","source":"Huawei","contact":"Maurice Pope","contact-id":648,"tdoctype":"other","for":"Decision","abstract":"-","secretary_remarks":"Revision of S2-1908045. Noted in parallel session","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23010,"status":"noted","reservation_date":"2019-07-04 09:12:45","uploaded":"2019-07-04 09:17:57","revisionof":"S2-1908045","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908095.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908096","title":"Service Context Transfer Support via CTSF","source":"KDDI, Deutsche Telekom, Telecom Italia, Sprint, AT&T, Verizon, Telstra, Tencent","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This document introduces indirect service context transfer via a context handle.","secretary_remarks":"Revision of S2-1908047. Revised in parallel session to S2-1908151.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23060,"status":"revised","reservation_date":"2019-07-04 09:12:45","uploaded":"2019-07-04 09:17:57","revisionof":"S2-1908047","revisedto":"S2-1908151","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1393.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908096.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908097","title":"Bulk context transfer using CTSF","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Proposes a solution to achieve this: Source NF \/ OA&M system determines when it needs to offload context and how many contexts it wants to transfer to NFs across sets. At this point, source NF stores context in the CTSF. Source NF can also notify OA&M at this point. OA&M triggers the target NF(s) (could be one or more) to retrieve contexts from the CTSF. (we assume that only one target NF can get access to a certain UE context, target NF retrieves data by simply asking for number of contexts). Rev-1 During SA WG2#134 eSBA session (Wednesday), it was decided not to support bulk context transfer. Thus this revision updates the paper to generically specify conditions for the transfer and the trigger for the transfer.","secretary_remarks":"Revision of S2-1907542. Revised in parallel session to S2-1908153.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23260,"status":"revised","reservation_date":"2019-07-04 09:12:46","uploaded":"2019-07-04 09:17:57","revisionof":"S2-1907542","revisedto":"S2-1908153","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1624.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908097.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908098","title":"Update SM context transfer procedure","source":"DT, Samsung","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to modify the procedure description according to the changes below and remove the current editors notes Rev 1 Merge with S2-1906972 Removed first EN 'It is FFS if step 2-3 can be replaced with a subscribe notify of the UE status from SMF to AMF.' Updated the sequence diagram accordingly. The SMF becomes in control of the context transfer instead of the AMF. This could be beneficial in some cases, e.g., when deadlines for context transfer are to be met and the timing information should be managed solely by the Old SMF. Removed second EN: 'It is FFS if step 6 and 9 can be optimised or changed to a modification of the N4 session'. Introduced ''N4 session release' with flag notifying the UPF about the expected re-establishment of the N4 session for the same PDU session. Based on this, the UPF may temporarily keep some information related to the N4 session to optimize packet handling until the N4 session is re-established by the new SMF. Rev 1 Merge with S2-1907128, S2-1907216, S2-1907315, S2-1907523, S2-1907663 Updated 4.26.5.3 to clarify the target SMF can be selected dynamically in consideration of the actual network status with the use of the target SMF set ID. Updated 4.26.5.1 to clarify that the SMF context transfer procedure can be used between two SMFs within the same SMF set. Change Nsmf_PDUSession_StatusNotify to Nsmf_PDUSession_SMContextStatusNotify in clause 4.26.5.2. In clause 4.26.5.3, In step 2, change Nsmf_PDUSession_StatusNotify to Nsmf_PDUSession_SMContextStatusNotify. For the second editor's note, it is proposed to delete it and change N4 session establish to N4 session modification and change SM policy association creation to update. In the original figure, step 6 and 13 are removed due to the revision in the above bullet. Update the service description for Nsmf_PDUSession_SMContextStatusNotify Added Old SMF ID, PDU Session ID, SUPI, SM Context ID tp CreateSMContext request so as to be consistent with the information sent in step 1. Clarified the UE state as CM-IDLE and CM-CONNECTED with RRC inactive state Added notification from New SMF to Old SMF to notify the finishing of the context transfer. Clarified that not 'everything' is removed from the UPF but rather only unused information Clarification in Nsmf_PDUSession_ContextRequest service operation to mention SM Context Transfer How it is handled if concurrent request from peer NFs comes to the old SMF while the session is transferring to the new SMF; How the new SMF interaction with PCF; How the old registration and subscription in UDM is handled; How the N4 session is handled; Updated CreateSMContext service operation Rev 2 Replaced SMContextStatusNotify with notification from UDM, which was missing and can also serve the same purpose. Adjusted text in 4.XX.4, procedure text and figure to reflect this change Text in 10.1 and 10.2 was not matching the figure. Aligned text with the depicted procedure Moved 'The parameters from step 8 and, if applies, step 9 are used.' (step 10.2) to step 10.1 Rev 3 Removed section 4.xx.4 (Context Operations During Context Transfer) Removed unused 'CTSF' diagram element in main flow diagram Removed step 18 in procedure (Old SMF redirects requests to New SMF) UDM sending deregistration also for SMF in 5.2.3.2.1","secretary_remarks":"Revision of S2-1908048, merging S2-1907523, S2-1907216 and S2-1907663. Revised in parallel session to S2-1908169.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23170,"status":"revised","reservation_date":"2019-07-04 09:12:47","uploaded":"2019-07-04 09:17:57","revisionof":"S2-1908048","revisedto":"S2-1908169","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1539.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908098.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908099","title":"Update of context transfer procedures","source":"Tencent","contact":"Zhuoyun Zhang","contact-id":78278,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the push or pull model is used by the NF based on specific procedures or implementation. Other Editorial changes are made.","secretary_remarks":"Revision of S2-1907522. Revised in parallel session to S2-1908152.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23200,"status":"revised","reservation_date":"2019-07-04 09:12:48","uploaded":"2019-07-04 09:17:57","revisionof":"S2-1907522","revisedto":"S2-1908152","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1597.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908099.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908120","title":"SMF and PCF selection - option 2","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF sends all the selection parameter to the SCP. If the SMF matched all selection parameter can be found, that SMF is returned. If the SMF matched all parameter can not be found, the AMF interact with NRF to get the H-SMF. After that the SMF send the service request with the selected H-SMF and seletion parameter, the SCP do the V\/I-SMF selection. When the V\/I-SMF receive the request, they forward the request to the indicated H-SMF. For the PCF selection, the AMF select the H-PCF and use the same logic to establish the UE policy association. Also the interaction with NRF, the candidate result may be restricted.","secretary_remarks":"Revision of S2-1908043. Revised in parallel session to S2-1908148.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22970,"status":"revised","reservation_date":"2019-07-04 09:13:14","uploaded":"2019-07-04 09:17:57","revisionof":"S2-1908043","revisedto":"S2-1908148","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1664.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908120.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908148","title":"SMF and PCF selection - option 2","source":"Huawei, HiSilicon, Telecom Italia","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF sends all the selection parameter to the SCP. If the SMF which match all selection parameter can be found, that SMF is used. If the SMF matched all parameter can not be found, the errror returned from SCP. Based on that error response, the AMF interact with NRF to get the H-SMF. The maximum number of NF instances may be requested by AMF and used by the NRF to control the number of the candidate SMF returned from NRF. After that the AMF send the service request with the selected H-SMF and seletion parameter for V-SMF, the SCP do the V\/I-SMF selection. When the V\/I-SMF receives the service request, they send the service request to the indicated H-SMF. For the PCF selection, the AMF select the H-PCF and use the same logic to establish the UE policy association.","secretary_remarks":"Revision of S2-1908120. Revised in parallel session, merging S2-1908149, to S2-1908167.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22980,"status":"revised","reservation_date":"2019-07-04 09:13:50","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1908120","revisedto":"S2-1908167","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1664.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908148.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908149","title":"SMF Delegated Discovery and Selection for HR scenario","source":"NTT DOCOMO, Oracle Corporation, ZTE, Deutsche Telekom AG, Verizon","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provide a solution for delegated SMF and PCF discovery in HR roaming and ETSUN. V-SMF discovery (6.3.2): 1. AMF sends Nsmf_PDUSession_CreateSMContext Request to SCP. The request indicates target PLMN ID for the H-SMF (HPLMN ID). The request indicates 'UE location' and DNN' as discovery and selection parameters to SCP. 2. SCP selects the V-SMF from the serving PLMN. 3. V-SMF determines the need for HR roaming (based on the target HPLMN ID for the H-SMF). 4. V-SMF sends Nsmf_PDUSession_Create Request to SCP. 5. SCP discovers the H-SMF from the vNRF and hNRF based on the HPLMN ID. I-SMF discovery (5.34.3): Similar procedure is used for selecting the I-SMF as above for V-SMF selection with following differences: 1. As a first priority the AMF attempts to get the SMF discovered that supports the UE location and DNN. If the SCP discovery cannot find an SMF that supports the UE location and DNN, the SCP returns an error to AMF and AMF attempts to get the SMF discovered using only the UE location as input (i.e. I-SMF). 2. If the selected SMF determines it cannot serve the DNN, the SMF acts as an I-SMF. I-SMF sends Nsmf_PDUSession_Create Request to SCP. The request does not contain the UE location as a selection parameter. 3. Based on the lack of UE location as a selection parameter, the SCP discovers the SMF supporting the DNN. SMF Service Area: The AMF needs to be aware of the Service Area of the discovered SMF. The proposed solution is that the AMF obtains this information from the NRF after the response for PDU session creation. V-PCF discovery (6.3.7.1): Similar procedure is used for selecting the V-PCF as above for V-SMF selection: 1. AMF sends AM policy association establishment request to SCP. 2. SCP selects the V-PCF. 3. V-PCF includes the V-PCF ID in a response to AMF. 4. AMF sends UE policy association establishment request to SCP, indicating the V-PCF ID as a target. The request indicates target PLMN ID for the H-PCF (HPLMN ID). 5. SCP selects the V-PCF as indicated by the V-PCF ID. 6. V-PCF sends UE policy association establishment request to SCP, indicating the PLMN ID of the H-PCF as a discovery and selection parameter SCP. 7. SCP discovers the H-PCF based on the HPLMN ID. The related open Editor's Notes are removed.","secretary_remarks":"Revision of S2-1908041. Merged into S2-1908167","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":22850,"status":"merged","reservation_date":"2019-07-04 09:13:51","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1908041","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1129.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908149.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908150","title":"Procedures and call flows for SMF Delegated Discovery and Selection in HR and specific SMF Service Areas scenarios and PCF Delegated Discovery and Selection","source":"Oracle Corporation, NTT Docomo, ZTE, Deutsche Telekom AG, Huawei, HiSilicon, Telecom Italia","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A new clause Annex X is added to capture the concepts and generic functionality required for addressing the scenario of SMF Discovery and Selection in a delegated mode for Home Routed and specific SMF Service Areas scenarios as well as V-PCF\/H-PCF discovery in a delegated mode.","secretary_remarks":"Revision of S2-1908042. For e-mail approval. e-mail revision 6 approved. Revised to S2-1908615.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23250,"status":"revised","reservation_date":"2019-07-04 09:13:53","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1908042","revisedto":"S2-1908615","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1382.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908150.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908151","title":"Service Context Transfer Support via CTSF","source":"KDDI, Deutsche Telekom, Telecom Italia, Sprint, AT&T, Verizon, Telstra, Tencent","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This document introduces indirect service context transfer via a context handle.","secretary_remarks":"Revision of S2-1908096. Revised in parallel session to S2-1908157.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23070,"status":"revised","reservation_date":"2019-07-04 09:13:54","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1908096","revisedto":"S2-1908157","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1393.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908151.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908152","title":"Update of context transfer procedures","source":"Tencent","contact":"Zhuoyun Zhang","contact-id":78278,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the push or pull model is used by the NF based on specific procedures or implementation in clause 4.26.1. Other changes are made in clause 4.26.2 and 4.26.3. Changes in Rev 2 compared to Rev 1: The changes in clause 4.26.1 are removed. The changes in clauses 4.26.2 and 4.26.3 are kept.","secretary_remarks":"Revision of S2-1908099. Agreed in parallel session. This was Block approved","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23590,"status":"agreed","reservation_date":"2019-07-04 09:13:56","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1908099","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1597.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190607","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908152.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908153","title":"Bulk context transfer using CTSF","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Revision 1. During SA WG2#134 eSBA session (Wednesday), it was decided not to support bulk context transfer. Thus this revision updates the paper to generically specify conditions for the transfer and the trigger for the transfer. Revision 2: It is up to the source NF to determine when to transfer the UE context to target NF.","secretary_remarks":"Revision of S2-1908097. Revised in parallel session to S2-1908170.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23270,"status":"revised","reservation_date":"2019-07-04 09:13:58","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1908097","revisedto":"S2-1908170","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1624.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908153.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908157","title":"Service Context Transfer Support via CTSF","source":"KDDI, Deutsche Telekom, Telecom Italia, Sprint, AT&T, Verizon, Telstra, Tencent","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This document introduces indirect service context transfer via a context handle.","secretary_remarks":"Revision of S2-1908151. Revised in parallel session to S2-1908168.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23080,"status":"revised","reservation_date":"2019-07-04 09:14:04","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1908151","revisedto":"S2-1908168","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1393.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908157.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908167","title":"eSBA SMF and PCF selection-option 2","source":"Huawei, HiSilicon, Telecom Italia, Ericsson, Oracle Corporation, NTT Docomo","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF sends all the selection parameter to the SCP. If the SMF which match all selection parameter can be found, that SMF is used. If the SMF matched all parameter can not be found, the errror returned from SCP. Based on that error response, the AMF interact with NRF to get the H-SMF. The maximum number of NF instances may be requested by AMF and used by the NRF to control the number of the candidate SMF returned from NRF. After that the AMF send the service request with the selected H-SMF and seletion parameter for V-SMF, the SCP do the V\/I-SMF selection. When the V\/I-SMF receives the service request, they send the service request to the indicated H-SMF. For the PCF selection, the AMF select the H-PCF and use the same logic to establish the UE policy association.","secretary_remarks":"Revision of S2-1908148, merging S2-1908149. Agreed in parallel session. This was Block approved","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23370,"status":"agreed","reservation_date":"2019-07-04 09:14:17","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1908148","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1664.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-190607","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908167.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908168","title":"Service Context Transfer Support via CTSF","source":"KDDI, Deutsche Telekom, Telecom Italia, Sprint, AT&T, Verizon, Telstra, Tencent","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This document introduces indirect service context transfer via a context transfer storage function.","secretary_remarks":"Revision of S2-1908157. Revised in parallel session to S2-1908173.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23090,"status":"revised","reservation_date":"2019-07-04 09:14:18","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1908157","revisedto":"S2-1908173","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1393.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908168.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908169","title":"Update SM context transfer procedure","source":"DT, Samsung","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to modify the procedure description according to the changes below and remove the current editors notes Rev 1 Merge with S2-1906972, Merge with S2-1907128, S2-1907216, S2-1907315, S2-1907523, S2-1907663 Removed first EN 'It is FFS if step 2-3 can be replaced with a subscribe notify of the UE status from SMF to AMF.' Updated the sequence diagram accordingly. The SMF becomes in control of the context transfer instead of the AMF. This could be beneficial in some cases, e.g., when deadlines for context transfer are to be met and the timing information should be managed solely by the Old SMF. Removed second EN: 'It is FFS if step 6 and 9 can be optimised or changed to a modification of the N4 session'. Introduced ''N4 session release' with flag notifying the UPF about the expected re-establishment of the N4 session for the same PDU session. Based on this, the UPF may temporarily keep some information related to the N4 session to optimize packet handling until the N4 session is re-established by the new SMF. Updated 4.26.5.3 to clarify the target SMF can be selected dynamically in consideration of the actual network status with the use of the target SMF set ID. Updated 4.26.5.1 to clarify that the SMF context transfer procedure can be used between two SMFs within the same SMF set. Change Nsmf_PDUSession_StatusNotify to Nsmf_PDUSession_SMContextStatusNotify in clause 4.26.5.2. In clause 4.26.5.3, In step 2, change Nsmf_PDUSession_StatusNotify to Nsmf_PDUSession_SMContextStatusNotify. For the second editor's note, it is proposed to delete it and change N4 session establish to N4 session modification and change SM policy association creation to update. In the original figure, step 6 and 13 are removed due to the revision in the above bullet. Update the service description for Nsmf_PDUSession_SMContextStatusNotify Added Old SMF ID, PDU Session ID, SUPI, SM Context ID tp CreateSMContext request so as to be consistent with the information sent in step 1. Clarified the UE state as CM-IDLE and CM-CONNECTED with RRC inactive state Added notification from New SMF to Old SMF to notify the finishing of the context transfer. Clarified that not 'everything' is removed from the UPF but rather only unused information Clarification in Nsmf_PDUSession_ContextRequest service operation to mention SM Context Transfer How it is handled if concurrent request from peer NFs comes to the old SMF while the session is transferring to the new SMF; How the new SMF interaction with PCF; How the old registration and subscription in UDM is handled; How the N4 session is handled; Updated CreateSMContext service operation Rev 2 Replaced SMContextStatusNotify with notification from UDM, which was missing and can also serve the same purpose. Adjusted text in 4.XX.4, procedure text and figure to reflect this change Text in 10.1 and 10.2 was not matching the figure. Aligned text with the depicted procedure Moved 'The parameters from step 8 and, if applies, step 9 are used.' (step 10.2) to step 10.1 Rev 3 Removed section 4.xx.4 (Context Operations During Context Transfer) Removed unused 'CTSF' diagram element in main flow diagram Removed step 18 in procedure (Old SMF redirects requests to New SMF) UDM sending deregistration also for SMF in 5.2.3.2.1 Rev 4 Step 10.2: Change 'UPF' to 'SMF', clarified 'session' to 'N4 session', removed example in parenthesis Step 10: Changed reference to message, not step number Step 7: For delayed N4 session deletion, changed 'may' to 'if supported, the UPF should' Editorials","secretary_remarks":"Revision of S2-1908098. This CR was agreed","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23560,"status":"agreed","reservation_date":"2019-07-04 09:14:19","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1908098","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1539.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-190607","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908169.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908170","title":"Network Function\/NF Service Context","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Revision 1. During SA WG2#134 eSBA session (Wednesday), it was decided not to support bulk context transfer. Thus this revision updates the paper to generically specify conditions for the transfer and the trigger for the transfer. Revision 2: It is up to the source NF to determine when to transfer the UE context to target NF.","secretary_remarks":"Revision of S2-1908153. Agreed in parallel session. This was Block approved","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23660,"status":"agreed","reservation_date":"2019-07-04 09:14:20","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1908153","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1624.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190607","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908170.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908173","title":"Service Context Transfer Support via CTSF","source":"KDDI, Deutsche Telekom, Telecom Italia, Sprint, AT&T, Verizon, Telstra, Tencent","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This document introduces indirect service context transfer via a context handle.","secretary_remarks":"Revision of S2-1908168. Revised in parallel session to S2-1908174.","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23100,"status":"revised","reservation_date":"2019-07-04 09:14:23","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1908168","revisedto":"S2-1908174","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1393.0,"crrevision":9.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908173.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908174","title":"Service Context Transfer Support via indirect Transfer","source":"KDDI, Deutsche Telekom, Telecom Italia, Sprint, AT&T, Verizon, Telstra, Tencent","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This document introduces indirect service context transfer via a context handle.","secretary_remarks":"Revision of S2-1908173. Agreed in parallel session. This was Block approved","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23490,"status":"agreed","reservation_date":"2019-07-04 09:14:25","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1908173","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1393.0,"crrevision":10.0,"crcategory":"B","tsg_crp":"SP-190607","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908174.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908615","title":"Procedures and call flows for SMF Delegated Discovery and Selection in HR and specific SMF Service Areas scenarios and PCF Delegated Discovery and Selection","source":"Oracle Corporation, NTT Docomo, ZTE, Deutsche Telekom AG, Huawei, HiSilicon, Telecom Italia","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A new clause Annex X is added to capture the concepts and generic functionality required for addressing the scenario of SMF Discovery and Selection in a delegated mode for Home Routed and specific SMF Service Areas scenarios as well as V-PCF\/H-PCF discovery in a delegated mode.","secretary_remarks":"e-mail revision 6 of S2-1908150. This CR was agreed","agenda_item_sort_order":46,"ainumber":"6.19.1","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA) - Exception","tdoc_agenda_sort_order":23260,"status":"agreed","reservation_date":"2019-07-10 09:00:33","uploaded":"2019-07-10 09:17:55","revisionof":"S2-1908150","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1382.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"SP-190607","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908615.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]