[{"name":"S2-1904930","title":"Resolving the EN in Bindings between the consumer and producer","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Describe the supported binding addresses, aligned with the NF Set and NF Service Set concepts. Add a new clause for update of the bindings between the consumer and producer. Rev 4: Only the bindings to NF instance, NF service instance, and NF Set are possible when the binding is created as part of service request.","secretary_remarks":"Revision of S2-1904726 from S2#132. Revised in parallel session to S2-1906513.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24140,"status":"revised","reservation_date":"2019-04-29 13:16:22","uploaded":"2019-05-07 14:35:42","revisionof":"S2-1904726","revisedto":"S2-1906513","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1120.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904930.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904987","title":"Delegated SMF discovery","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"discussion","for":"Discussion","abstract":"This paper proposes principles for delegated SMF discovery","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24210,"status":"noted","reservation_date":"2019-05-03 11:37:12","uploaded":"2019-05-07 14:35:42","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_133_Reno\/Docs\/S2-1904987.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904988","title":"SMF Delegated Discovery and Selection for HR scenario","source":"NTT DOCOMO, Oracle Corporation, ZTE, Deutsche Telekom AG","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) The EN in 23.501 clause 6.3.2 is resolved by proposing that the SCP discovers and selects the V-SMF upon receipt of the PDU session establishment request from the AMF, and then discovers and selects the H-SMF upon receipt of the PDU session establishment request from the V-SMF. 2) Clause 5.34.3 'I-SMF selection' is updated to cover the delegated I-SMF discovery, using a similar procedure as V-SMF discovery in 6.3.2 for HR roaming. 3) Remove the EN related to latency; the possible impacts to latency should be taken into account in Stage 3.","secretary_remarks":"Revision of S2-1904771 from S2#132. For e-mail approval.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24220,"status":"available","reservation_date":"2019-05-03 11:53:57","uploaded":"2019-05-07 14:35:42","revisionof":"S2-1904771","revisedto":"S2-1906883","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1129.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904988.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905055","title":"Principle for H-PCF and H-SMF selection in delegated discovery","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution proposes to align the principles for H-PCF and H-SMF selection so that the AMF behaviour in communication model D is independent of the communication model chosen in the V-PCF and V-SMF.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24240,"status":"noted","reservation_date":"2019-05-03 22:45:08","uploaded":"2019-05-07 13:27:50","revisionof":"","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_133_Reno\/Docs\/S2-1905055.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905056","title":"ESBA PCF discovery and selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: eSBA additions and editorials. eSBA: - according to DP S2-\u2026. - Factors to send to SCP for UE and AM policies in delegated discovery. - Letting the NFs (AMF and SMF) to decide if same PCF shall be used and not configurations in SCP. i.e. retaining these decissions in the NFs also for eSBA. - If AMF wants to re-use the AM and UE policy associations it already has the resource URI, and thus no special handling needed in case of SCP. This CR also takes in changes from CR 1042 (S2-1904798) and makes editorial movements of text. The changes proposed in CR 1042 is marked in green and the moved text in yellow. This CR invalidates CF 1042, since it includes both the changes from from the CR 1042 and in addition adds eSBA functionality.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24380,"status":"noted","reservation_date":"2019-05-03 22:45:08","uploaded":"2019-05-07 13:27:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1310.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905056.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905057","title":"ESBA SMF discovery and selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Handling SMF discovery and selection at roaming according to DP S2-1905055. Adding how AMF acts when using SCP for CioT. Adding EN regarding ETSUN. Removing EN about perfomance issues since this is CT decission domain.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24390,"status":"noted","reservation_date":"2019-05-03 22:45:09","uploaded":"2019-05-07 13:27:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1311.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905057.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905058","title":"Extending the significance of the locality parameter","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Extending the significance of the locality parameter.","secretary_remarks":"Revised in parallel session to S2-1906648.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24820,"status":"revised","reservation_date":"2019-05-03 22:45:10","uploaded":"2019-05-07 13:27:50","revisionof":"","revisedto":"S2-1906648","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1312.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905058.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905059","title":"Analysis of bulk context transfer","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution lists some challenges related to a bulk context transfer and, given the expected solution complexity in addressing those challenges, it proposes to base the NF service context transfer on per individual context transfer operations in the Rel-16 specifications","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24460,"status":"noted","reservation_date":"2019-05-03 22:45:10","uploaded":"2019-05-07 13:27:50","revisionof":"","revisedto":"","release":"","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_133_Reno\/Docs\/S2-1905059.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905060","title":"SMF context transfer","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A SMF Service Context Transfer procedures is proposed","secretary_remarks":"Revised in parallel session to S2-1906574.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24510,"status":"revised","reservation_date":"2019-05-03 22:45:10","uploaded":"2019-05-07 13:27:50","revisionof":"","revisedto":"S2-1906574","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1325.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905060.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905061","title":"Handling of hidden producer services","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discusses 'hidden' NF service instances and proposes to add a note to 23.501 CR 1222.","secretary_remarks":"Not Handled","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24260,"status":"not treated","reservation_date":"2019-05-03 22:45:11","uploaded":"2019-05-07 13:27:50","revisionof":"","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_133_Reno\/Docs\/S2-1905061.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905062","title":"Service-mesh-based and other SCP deployment options","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Informative Annex with describing a SCP deployment option based on a service mesh Rev 1: Initial mention that this section is a deployment example Clarified and simplified Figure X.1-1 Made Service Agent capitalization consistent Clarified and simplified Figure X.1-2 and its related description (numbering made it less clear) Clarified and simplified Figure X.2- and its related description (numbering made it less clear) Added clarification to Figure X.3-1 so that it is immediately clear to the reader that the division left is implementation-specific Rev 2: Cover: changed category to D Cover: consequences if not approved Added first paragraph stating that this annex is not meant to be an exhaustive list of deployment options. Renamed first title to 'Introduction' and made the title more descriptive Removed normative language from the CR: shall, should, may, must. It is a deployment example and not normative text Rev 3: Removed the last section Rev 4: Content was not marked as 'change' Rev 5: Added clarification that in this example the Service Agent(s) and the 5GC functionality are separate implementations. i.e., that 'co-located' does not mean 'the same code' Added clarification that no assumption is made regarding the internal composition of each '5GC functionality' Added clarification on 'deployment unit' Clarified that this example does not preclude using the service mesh for other protocols Rev 5 email approval -> Rev 6: Further clarification on the separation of the 5GC functionality and the Service Agent Further disclaimer that this example depicts only SBI interactions but that the service mesh could be used for other things also Additional figure showing an NF and NF Services Rev 7: Adding an other example of SCP implementation and deployment","secretary_remarks":"Revision of S2-1904844 from S2#132. Revised in parallel session to S2-1906643.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24690,"status":"revised","reservation_date":"2019-05-03 22:45:11","uploaded":"2019-05-07 13:27:50","revisionof":"S2-1904844","revisedto":"S2-1906643","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1271.0,"crrevision":7.0,"crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905062.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905063","title":"NF Set ID, NF Service Set ID in 23.502","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Inclusion of NF Set ID, NF Service Set ID in 23.502","secretary_remarks":"Revised in parallel session to S2-1906570.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24320,"status":"revised","reservation_date":"2019-05-03 22:45:12","uploaded":"2019-05-07 13:27:50","revisionof":"","revisedto":"S2-1906570","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1326.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905063.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905148","title":"Introducing NF Set and NF Service Set in Service Framework","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Define the NF Set and NF Service Set as the basic part the NF Service Framework. Delete the clause 5.21.3.2 which define the NF Set and NF Service Set. Update the clause 5.21.3.1 to reference the new clause which defines the NF Set and NF Service Set and delete the EN.","secretary_remarks":"Merged into S2-1906512","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24130,"status":"merged","reservation_date":"2019-05-06 02:23:37","uploaded":"2019-05-07 09:59:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1325.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905148.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905149","title":"NF Validity Period for NF Registration and Discovery","source":"Tencent, China Mobile","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The NF may provide validity period to the NRF during the NF regisgtration to the NRF, and the NF profile maintained in an NRF will include the NF validity period and the NF validity period will be provided by the NRF to the NF consumer during the NF discovery procedure.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24440,"status":"noted","reservation_date":"2019-05-06 02:23:38","uploaded":"2019-05-07 09:59:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1326.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905149.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905153","title":"NRF Registration and Discovery Service Update","source":"Tencent, China Mobile","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Nnrf_NFManagement_NFRegister and Nnrf_NFDiscovery_Request service operation are updated with optional parameter: NF validity period. When the NF validity period expires, the NF does not need to send deregistration message to the NRF and NRF automatically marks the NF unavailable. Adding validity period for the discovery result in Nnrf_NFDiscovery_Request service operation in order to align with CR 1091 and stage 3.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24450,"status":"noted","reservation_date":"2019-05-06 02:31:54","uploaded":"2019-05-07 09:59:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1352.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905153.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905168","title":"Support of Service Context Transfer in TS23.501","source":"KDDI","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To add the specification and reference for Service Context Transfer procedures in TS23.502.","secretary_remarks":"Revised in parallel session to S2-1906641.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24610,"status":"revised","reservation_date":"2019-05-06 06:02:31","uploaded":"2019-05-07 12:08:14","revisionof":"","revisedto":"S2-1906641","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1331.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905168.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905200","title":"Resolving the EN in Bindings between the consumer and producer","source":"NTT DOCOMO?, Tencent","contact":"Zhuoyun Zhang","contact-id":78278,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Describe the supported binding addresses, aligned with the NF Set and NF Service Set concepts. Add a new clause for update of the bindings between the consumer and producer. Compared with rev 3, the following changes are made: 1) In step 3 of Figure 4.17.11.3-1, instance B sends the subsequent request to instance A using the binding indication regarding the concerned resource. The current description needs to be aligned with it. 2) In clause 4.17.11.4, the NF service consumer could also update the binding indication according to case C and D, so the general description of the first paragraph needs be aligned. 3) In clause 4.17.11.4, update case C and D with subscribe\/notify interaction.","secretary_remarks":"Revision of S2-1904726 from S2#132. Confirm sources! Merged into S2-1906513.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24180,"status":"merged","reservation_date":"2019-05-06 10:36:54","uploaded":"2019-05-07 11:43:24","revisionof":"S2-1904726","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1120.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905200.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905201","title":"NF Set and NF Service Set - Open items resolution","source":"Nokia?, Nokia Shanghai Bell?, NTT DoCoMo?, Ericsson?, Huawei?, HiSilicon?, ZTE?, Oracle?, Tencent","contact":"Zhuoyun Zhang","contact-id":78278,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Item 1: Following principles are assumed and proposed: 1. Subsequent procedure can trigger reselection within an NF Set. 2. NFs within the NF Set are equivalent, the corresponding service instances of the same service type are equivalent as well Items 2\/3\/4: Simply remove Editor's notes Revision: Principles for binding, selection and reselection. Compared with rev 5, the following changes are made: Editor's note: it is FFS how binding indication applies in case of subscribe\/notify. The subscribe\/notify procedure can also include binding indication according to CR 1120, so this editor's note is not needed. The related description is added in the clause above. Editor's note: whether to specify the condition to include binding indication is FFS. It is also FFS what content will be included within the binding indication. This editor's note is not needed according to the discussion paper S2-1905454.","secretary_remarks":"Revision of S2-1904734 from S2#132. Confirm sources! Merged into S2-1906512","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24270,"status":"merged","reservation_date":"2019-05-06 10:45:56","uploaded":"2019-05-07 11:43:24","revisionof":"S2-1904734","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1222.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905201.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905286","title":"Content of Binding Indication","source":"Oracle Corporation","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Resolving the second part of the EN in S2-1904734: Editor's note: ... It is also FFS what content will be included within the binding indication. This paper adds a column to Table 6.3.1.0-1: Binding Indication Information. The respective rows for that column are filled in with proper values. Text above the table 6.3.1.0-1: 'The binding indication may include NF Service Set ID or NF Set ID.' Is no loner accurate and no longer needed, as it is replaced by the new column - Binding Indication Information. Consequently, it is removed.","secretary_remarks":"Merged into S2-1906512","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24200,"status":"merged","reservation_date":"2019-05-06 14:51:52","uploaded":"2019-05-06 15:35:57","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1361.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905286.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905337","title":"Procedures and call flows for SMF Delegated Discovery and Selection in HR and specific SMF Service Areas scenarios","source":"Oracle Corporation, NTT Docomo","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.","secretary_remarks":"6 companies indicated their objection to this CR and it was then noted.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24230,"status":"noted","reservation_date":"2019-05-06 17:58:13","uploaded":"2019-05-06 23:14:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1382.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905337.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905398","title":"Service Context Transfer Support in UDSF","source":"KDDI, Deutsche Telekom, Telecom Italia","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To rename the abbreviation of UDSF, and to add the description for the support of Service Context Transfer in UDSF","secretary_remarks":"Revised in parallel session to S2-1906639.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24550,"status":"revised","reservation_date":"2019-05-07 04:49:06","uploaded":"2019-05-07 13:37:25","revisionof":"","revisedto":"S2-1906639","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1391.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905398.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905399","title":"Service Context Transfer Support in UDSF","source":"KDDI, Deutsche Telekom, Telecom Italia","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To add the new service in UDSF service","secretary_remarks":"Revised in parallel session to S2-1906640.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24580,"status":"revised","reservation_date":"2019-05-07 04:51:37","uploaded":"2019-05-07 15:02:54","revisionof":"","revisedto":"S2-1906640","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1393.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905399.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905454","title":"Discussion on cleanup of editor's note for binding","source":"Tencent","contact":"Zhuoyun Zhang","contact-id":78278,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution proposes to clean up two Editor's Notes for binding in CR 1222 for TS 23.501.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24110,"status":"noted","reservation_date":"2019-05-07 08:04:41","uploaded":"2019-05-07 11:43:24","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_133_Reno\/Docs\/S2-1905454.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905491","title":"Service-mesh-based SCP deployment option","source":"InterDigital Inc.","contact":"Ulises Olvera","contact-id":72056,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a Service Router deployment option to Annex X","secretary_remarks":"Revision of S2-1904844 from S2#132. Revised in parallel session to S2-1906644.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24720,"status":"revised","reservation_date":"2019-05-07 08:58:45","uploaded":"2019-05-07 14:48:00","revisionof":"S2-1904844","revisedto":"S2-1906644","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1271.0,"crrevision":8.0,"crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905491.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905502","title":"NF Set and NF Service Set - Open items resolution","source":"Nokia?, Nokia Shanghai Bell?, NTT DoCoMo?, Ericsson?, Huawei, HiSilicon, ZTE?, Oracle?","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Item 1: Following principles are assumed and proposed: 1. Subsequent procedure can trigger reselection within an NF Set. 2. NFs within the NF Set are equivalent, the corresponding service instances of the same service type are equivalent as well Items 2\/3\/4: Simply remove Editor's notes Revision: Principles for binding, selection and reselection.","secretary_remarks":"Revision of S2-1904734 from S2#132. Confirm Sources! Merged into S2-1906512.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24280,"status":"merged","reservation_date":"2019-05-07 09:01:16","uploaded":"2019-05-07 14:48:41","revisionof":"S2-1904734","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":1222.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905502.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905503","title":"Resolving the EN in Bindings between the consumer and producer","source":"NTT DOCOMO","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Describe the supported binding addresses, aligned with the NF Set and NF Service Set concepts. Add a new clause for update of the bindings between the consumer and producer.","secretary_remarks":"Revision of S2-1904726 from S2#132. Merged into S2-1906513.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24190,"status":"merged","reservation_date":"2019-05-07 09:01:17","uploaded":"2019-05-07 14:48:41","revisionof":"S2-1904726","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1120.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905503.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905504","title":"ESBA discussion on SMF and PCF selection","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Agreement","abstract":"This controbituon discusses how to select SMF and PCF in HR roaming case","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24370,"status":"noted","reservation_date":"2019-05-07 09:01:18","uploaded":"2019-05-07 14:48:41","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_133_Reno\/Docs\/S2-1905504.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905505","title":"SMF and PCF selection","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Option 1: 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. Option 2: 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 to S2-1906569.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24400,"status":"revised","reservation_date":"2019-05-07 09:01:18","uploaded":"2019-05-07 14:48:41","revisionof":"","revisedto":"S2-1906569","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1403.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905505.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905506","title":"PCF discovery by AF via BSF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In addition to PCF instance info already stored in BSF, it is proposed that binding indication is also stored in BSF. The BSF monitors the availability of PCF\/PCF serivces. Upon request for PCF discovery, the BSF selects PCF based on table Table 6.3.1.0-1 in TS 23.501. The AF includes the same App Session ID in the request if SBI interface is used. For Rx based AF, if the AF detects the failure of the PCF, the AF request for PCF from BSF and establish a new Rx session, in the establishment request, the AF includes the old Rx session ID in the request.","secretary_remarks":"Revised in parallel session to S2-1906572.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24420,"status":"revised","reservation_date":"2019-05-07 09:01:19","uploaded":"2019-05-07 14:48:41","revisionof":"","revisedto":"S2-1906572","release":"Rel-16","crspec":23.503,"crspecversion":"16.0.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":270.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905506.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905507","title":"NF Service Context Transfer Procedures","source":"Deutsche Telekom AG ?, Tencent ?, Verizon ?, KDDI? , Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR introduces NF\/NF Service Context Transfer procedures.","secretary_remarks":"Revision of S2-1904843 from S2#132. Confirm Sources! Merged into S2-1906642","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24650,"status":"merged","reservation_date":"2019-05-07 09:01:21","uploaded":"2019-05-07 14:48:41","revisionof":"S2-1904843","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1305.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905507.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905593","title":"NF Set and NF Service Set - Open items resolution","source":"Nokia, Nokia Shanghai Bell, NTT DoCoMo, Ericsson, Huawei, HiSilicon, ZTE, Oracle","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Item 1: Following principles are assumed and proposed: 1. Subsequent procedure can trigger reselection within an NF Set. 2. NFs within the NF Set are equivalent, the corresponding service instances of the same service type are equivalent as well Items 2\/3\/4: Simply remove Editor's notes Revision: Principles for binding, selection and reselection. Rev 6: Clarification on Reselection of NF Service Instance within equivalent NF Service Sets. Clarify that the Binding Indication can include identifiers of NF service set, NF set, NF instance, NF service instance.","secretary_remarks":"Revision of S2-1904734 from S2#132. Revised in parallel session, merging S2-1905771, S2-1905148, S2-1905201, S2-1905286 and S2-1905502, to S2-1906512.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24290,"status":"revised","reservation_date":"2019-05-07 10:00:40","uploaded":"2019-05-07 12:03:13","revisionof":"S2-1904734","revisedto":"S2-1906512","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1222.0,"crrevision":9.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905593.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905594","title":"NF Set concept for SMF","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that sets of NFs\/NF services\/Services (i.e. SMF) managing UPFs need to be connected to the same UPF. This also implies that the N4 association between SMF and UPF needs to be unique per SMF set. This is essential as any SMF in the SMF set should be able to issue request to modify\/update or delete\/release the PFCP association.","secretary_remarks":"Revised in parallel session to S2-1906571.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24340,"status":"revised","reservation_date":"2019-05-07 10:00:41","uploaded":"2019-05-07 12:03:13","revisionof":"","revisedto":"S2-1906571","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1413.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905594.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905710","title":"SCP Function Update","source":"Huawei, HiSilicon, Tencent??, Nokia??","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the SCP functionality description with delete the repeat descripiton on UDM\/UDR\/AUSF\/UDR\/PCF delegated discovery. Change Option -> Model (Option is a term that is used only when it is being evaluated however when specified, the term option is misleading) Revision 2: SCP is configured with the mapping between NF Group ID(s) and SUPI(s), in the case delegated discovery in Model D is adopted. PCF Group ID is introduced in a similar way as UDM\/UDR\/AUSF Group ID. It is clarified that the UDM\/UDR\/AUSF\/PCF Group ID is not applicable to the corresponding NF consumer in the case of delegated discovery and selection via SCP.","secretary_remarks":"Revision of S2-1904635 from S2#132. Confirm Sources!. Revised in parallel session to S2-1906645.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24750,"status":"revised","reservation_date":"2019-05-07 11:06:02","uploaded":"2019-05-07 14:57:24","revisionof":"S2-1904635","revisedto":"S2-1906645","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1171.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905710.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905720","title":"Update of NRF function and services","source":"Tencent, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding status notification as one NRF funcationaility in clause 6.2.6; Adding SCP in the NRF services in clause 7.2.6. Rev 1->2 Changes: Correction of the Nnrf_NFManagement Service wrt SCP","secretary_remarks":"Revision of S2-1904674 from S2#132. Revised in parallel session to S2-1906646.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24780,"status":"revised","reservation_date":"2019-05-07 11:18:53","uploaded":"2019-05-07 13:30:29","revisionof":"S2-1904674","revisedto":"S2-1906646","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1092.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905720.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905722","title":"SCP and NRF interaction","source":"ZTE, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add NF Set ID and NF Service Set ID as optional input parameters of Nnrf_NFDiscovery","secretary_remarks":"Revision of S2-1904732 from S2#132. Revised in parallel session to S2-1906647.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24800,"status":"revised","reservation_date":"2019-05-07 11:25:52","uploaded":"2019-05-07 13:30:29","revisionof":"S2-1904732","revisedto":"S2-1906647","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1292.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905722.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905758","title":"NF Service Bulk Context Transfer Procedures","source":"Deutsche Telekom AG","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR includes the following changes: - Introduction of Nsmf_ContextTransfer service - Moved ContextPush procedure to Nsmf_ContextTransfer service - Addition of bulk transfer procedures - Corrected typo in Table 5.2.8.1-1: The operation is called ContextRequest, not Context and other minor typos","secretary_remarks":"Revised to S2-1905768","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24470,"status":"revised","reservation_date":"2019-05-07 12:02:05","uploaded":"2019-05-07 12:10:40","revisionof":"","revisedto":"S2-1905768","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1446.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905758.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905768","title":"NF Service Bulk Context Transfer Procedures","source":"Deutsche Telekom AG, KDDI","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR includes the following changes: - Introduction of Nsmf_ContextTransfer service - Addition of bulk transfer procedures - Corrected typo in Table 5.2.8.1-1: The operation is called ContextRequest, not Context and other minor typos","secretary_remarks":"Revision of S2-1905758. Revised off-line in S2-1906515.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24480,"status":"revised","reservation_date":"2019-05-07 12:43:59","uploaded":"2019-05-07 12:50:46","revisionof":"S2-1905758","revisedto":"S2-1906515","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1446.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905768.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905771","title":"NF Set and NF Service Set - Open items resolution","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Item 1: Following principles are assumed and proposed: 1. Subsequent procedure can trigger reselection within an NF Set. 2. NFs within the NF Set are equivalent, the corresponding service instances of the same service type are equivalent as well Items 2\/3\/4: Simply remove Editor's notes Revision: Principles for binding, selection and reselection. Rev 6: Clarification on Reselection of NF Service Instance within equivalent NF Service Sets. Clarify that the Binding Indication can include identifiers of NF service set, NF set, NF instance, NF service instance. Rev 10: Resolves the EN: 'it is FFS how binding indication applies in case of subscribe\/notify.' by including a description how the bindings are used with subscriptions and notifications. Resolves the EN: 'whether to specify the condition to include binding indication is FFS'. The conditions are not specified; it is up to the NF service producer (NF service consumer in case of subscription) to decide if and when to use bindings. The EN can be removed.","secretary_remarks":"Revision of S2-1904734 from S2#132. Merged into S2-1906512","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24120,"status":"merged","reservation_date":"2019-05-07 12:56:08","uploaded":"2019-05-07 14:35:42","revisionof":"S2-1904734","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1222.0,"crrevision":10.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905771.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905774","title":"NF Service Context Transfer Procedures","source":"Deutsche Telekom AG, Tencent, Verizon, KDDI","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR introduces NF\/NF Service Context Transfer procedures.","secretary_remarks":"Revision of S2-1904843 from S2#132. Revised in parallel session, merging S2-1905507, to S2-1906642.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24660,"status":"revised","reservation_date":"2019-05-07 13:10:03","uploaded":"2019-05-07 14:59:39","revisionof":"S2-1904843","revisedto":"S2-1906642","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1305.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905774.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905792","title":"Tracking the ENs of eSBA for R16","source":"China Mobile","contact":"Sun Tao","contact-id":70932,"tdoctype":"other","for":"Discussion","abstract":"List all EN and tracking interested companies to address them.","secretary_remarks":"WITHDRAWN","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24860,"status":"withdrawn","reservation_date":"2019-05-07 14:10:01","uploaded":"2019-05-09 05:13:56","revisionof":"","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_133_Reno\/Docs\/S2-1905792.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905793","title":"Exception sheet for Rel-16 eSBA","source":"China Mobile (eSBA rapporteur)","contact":"Aihua Li","contact-id":58162,"tdoctype":"other","for":"Discussion","abstract":"Exception sheet for Rel-16 eSBA","secretary_remarks":"Revised in parallel session to S2-1906649.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24840,"status":"revised","reservation_date":"2019-05-07 14:13:03","uploaded":"2019-05-07 14:22:40","revisionof":"","revisedto":"S2-1906649","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_133_Reno\/Docs\/S2-1905793.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905796","title":"Tracking the ENs of eSBA for R16","source":"China Mobile (Rapporteur)","contact":"Aihua Li","contact-id":58162,"tdoctype":"other","for":"Discussion","abstract":"List all EN and tracking interested companies to address them.","secretary_remarks":"Not Handled","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24100,"status":"not treated","reservation_date":"2019-05-07 14:24:41","uploaded":"2019-05-07 14:26:23","revisionof":"","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_133_Reno\/Docs\/S2-1905796.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906512","title":"NF Set and NF Service Set - Open items resolution","source":"Nokia, Nokia Shanghai Bell, NTT DoCoMo, Ericsson, Huawei, HiSilicon, ZTE, Oracle","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Item 1: Following principles are assumed and proposed: 1. Subsequent procedure can trigger reselection within an NF Set. 2. NFs within the NF Set are equivalent, the corresponding service instances of the same service type are equivalent as well Items 2\/3\/4: Simply remove Editor's notes Revision: Principles for binding, selection and reselection. Rev 6: Clarification on Reselection of NF Service Instance within equivalent NF Service Sets. Clarify that the Binding Indication can include identifiers of NF service set, NF set, NF instance, NF service instance.","secretary_remarks":"Revision of S2-1905593, merging S2-1905771, S2-1905148, S2-1905201, S2-1905286 and S2-1905502.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25140,"status":"revised","reservation_date":"2019-05-15 17:18:40","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905593","revisedto":"S2-1906742","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1222.0,"crrevision":11.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906512.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906513","title":"Resolving the EN in Bindings between the consumer and producer","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Describe the supported binding addresses, aligned with the NF Set and NF Service Set concepts. Add a new clause for update of the bindings between the consumer and producer. Rev 4: Only the bindings to NF instance, NF service instance, and NF Set are possible when the binding is created as part of service request.","secretary_remarks":"Revision of S2-1904930, merging S2-1905200 and S2-1905503.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25010,"status":"revised","reservation_date":"2019-05-15 17:18:41","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1904930","revisedto":"S2-1906740","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1120.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906513.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906514","title":"Principles for delegated SMF discovery","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"other","for":"Endorsement","abstract":"-","secretary_remarks":"Created in parallel session. Option C was selected to try to agree CRs based on this way forward. Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25090,"status":"available","reservation_date":"2019-05-15 17:18:42","uploaded":"2019-05-19 20:07:54","revisionof":"","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_133_Reno\/Docs\/S2-1906514.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906515","title":"NF Service Bulk Context Transfer Procedures","source":"Deutsche Telekom AG, KDDI","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR includes the following changes: - Introduction of Nsmf_ContextTransfer service - Addition of bulk transfer procedures - Corrected typo in Table 5.2.8.1-1: The operation is called ContextRequest, not Context and other minor typos","secretary_remarks":"Revision of S2-1905768. Revised in parallel session to S2-1906573.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25310,"status":"revised","reservation_date":"2019-05-15 17:18:42","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905768","revisedto":"S2-1906573","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1446.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906515.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906569","title":"eSBA SMF and PCF selection","source":"Huawei, HiSilicon, Telecom Italia, Ericsson, Nokia, Nokia Shanghai Bell, Cisco, KDDI","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-1905505. Agreed with objection; Working Agreement to be created","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24800,"status":"agreed","reservation_date":"2019-05-15 17:19:36","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905505","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1403.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-190396","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906569.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906570","title":"NF Set ID, NF Service Set ID in 23.502","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Inclusion of NF Set ID, NF Service Set ID in 23.502 Rev1>Consistent capitalisations","secretary_remarks":"Revision of S2-1905063. Agreed in parallel session. This was Block approved","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24720,"status":"agreed","reservation_date":"2019-05-15 17:19:37","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905063","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1326.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906570.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906571","title":"NF Set concept for SMF","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that sets of NFs\/NF services\/Services (i.e. SMF) managing UPFs need to be connected to the same UPF. This also implies that the N4 association between SMF and UPF needs to be unique per SMF set. This is essential as any SMF in the SMF set should be able to issue request to modify\/update or delete\/release the PFCP association.","secretary_remarks":"Revision of S2-1905594.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25180,"status":"revised","reservation_date":"2019-05-15 17:19:38","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905594","revisedto":"S2-1906743","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1413.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906571.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906572","title":"PCF discovery by AF via BSF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In addition to PCF instance info already stored in BSF, it is proposed that binding indication is also stored in BSF. The BSF monitors the availability of PCF\/PCF serivces. Upon request for PCF discovery, the BSF selects PCF based on table Table 6.3.1.0-1 in TS 23.501. The AF includes the same App Session ID in the request if SBI interface is used. For Rx based AF, if the AF detects the failure of the PCF, the AF request for PCF from BSF and establish a new Rx session, in the establishment request, the AF includes the old Rx session ID in the request.","secretary_remarks":"Revision of S2-1905506.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25250,"status":"available","reservation_date":"2019-05-15 17:19:39","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905506","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.0.0","workitem":[{"winame":"5G_eSBA"}],"crnumber":270.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906572.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906573","title":"NF Service Bulk Context Transfer Procedures","source":"Deutsche Telekom AG, KDDI","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR includes the following changes: - Introduction of Nsmf_ContextTransfer service - Addition of bulk transfer procedures - Corrected typo in Table 5.2.8.1-1: The operation is called ContextRequest, not Context and other minor typos","secretary_remarks":"Revision of S2-1906515.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25320,"status":"available","reservation_date":"2019-05-15 17:19:40","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1906515","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1446.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906573.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906574","title":"SMF context transfer","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A SMF Service Context Transfer procedures is proposed","secretary_remarks":"Revision of S2-1905060.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25340,"status":"revised","reservation_date":"2019-05-15 17:19:41","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905060","revisedto":"S2-1906729","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1325.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906574.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906639","title":"Service Context Transfer Support in UDSF","source":"KDDI, Deutsche Telekom, Telecom Italia","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To rename the abbreviation of UDSF, and to add the description for the support of Service Context Transfer in UDSF","secretary_remarks":"Revision of S2-1905398.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25520,"status":"revised","reservation_date":"2019-05-16 18:41:29","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905398","revisedto":"S2-1906745","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1391.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906639.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906640","title":"Service Context Transfer Support in UDSF","source":"KDDI, Deutsche Telekom, Telecom Italia","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To add the new service in UDSF service","secretary_remarks":"Revision of S2-1905399.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25540,"status":"revised","reservation_date":"2019-05-16 18:41:30","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905399","revisedto":"S2-1906746","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1393.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906640.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906641","title":"Support of Service Context Transfer in TS23.501","source":"KDDI","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To add the specification and reference for Service Context Transfer procedures in TS23.502.","secretary_remarks":"Revision of S2-1905168.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25560,"status":"revised","reservation_date":"2019-05-16 18:41:31","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905168","revisedto":"S2-1906747","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1331.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906641.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906642","title":"NF Service Context Transfer Procedures","source":"Deutsche Telekom AG, Tencent, Verizon, KDDI","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR introduces NF\/NF Service Context Transfer procedures.","secretary_remarks":"Revision of S2-1905774, merging S2-1905507.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25590,"status":"revised","reservation_date":"2019-05-16 18:41:32","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905774","revisedto":"S2-1906751","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1305.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906642.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906643","title":"Service-mesh-based and other SCP deployment options","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Informative Annex with describing a SCP deployment option based on a service mesh Rev 1: Initial mention that this section is a deployment example Clarified and simplified Figure X.1-1 Made Service Agent capitalization consistent Clarified and simplified Figure X.1-2 and its related description (numbering made it less clear) Clarified and simplified Figure X.2- and its related description (numbering made it less clear) Added clarification to Figure X.3-1 so that it is immediately clear to the reader that the division left is implementation-specific Rev 2: Cover: changed category to D Cover: consequences if not approved Added first paragraph stating that this annex is not meant to be an exhaustive list of deployment options. Renamed first title to 'Introduction' and made the title more descriptive Removed normative language from the CR: shall, should, may, must. It is a deployment example and not normative text Rev 3: Removed the last section Rev 4: Content was not marked as 'change' Rev 5: Added clarification that in this example the Service Agent(s) and the 5GC functionality are separate implementations. i.e., that 'co-located' does not mean 'the same code' Added clarification that no assumption is made regarding the internal composition of each '5GC functionality' Added clarification on 'deployment unit' Clarified that this example does not preclude using the service mesh for other protocols Rev 5 email approval -> Rev 6: Further clarification on the separation of the 5GC functionality and the Service Agent Further disclaimer that this example depicts only SBI interactions but that the service mesh could be used for other things also Additional figure showing an NF and NF Services Rev 7: Adding an other example of SCP implementation and deployment","secretary_remarks":"Revision of S2-1905062.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25610,"status":"revised","reservation_date":"2019-05-16 18:41:33","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905062","revisedto":"S2-1906749","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1271.0,"crrevision":9.0,"crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906643.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906644","title":"Service-mesh-based SCP deployment option","source":"InterDigital Inc.","contact":"Ulises Olvera","contact-id":72056,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a Service Router deployment option to Annex X","secretary_remarks":"Revision of S2-1905491.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25630,"status":"revised","reservation_date":"2019-05-16 18:41:34","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905491","revisedto":"S2-1906748","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1271.0,"crrevision":10.0,"crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906644.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906645","title":"SCP Function Update","source":"Huawei, HiSilicon, Tencent??, Nokia??","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the SCP functionality description with delete the repeat descripiton on UDM\/UDR\/AUSF\/UDR\/PCF delegated discovery. Change Option -> Model (Option is a term that is used only when it is being evaluated however when specified, the term option is misleading) Revision 2: SCP is configured with the mapping between NF Group ID(s) and SUPI(s), in the case delegated discovery in Model D is adopted. PCF Group ID is introduced in a similar way as UDM\/UDR\/AUSF Group ID. It is clarified that the UDM\/UDR\/AUSF\/PCF Group ID is not applicable to the corresponding NF consumer in the case of delegated discovery and selection via SCP.","secretary_remarks":"Revision of S2-1905710.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25650,"status":"revised","reservation_date":"2019-05-16 18:41:35","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905710","revisedto":"S2-1906750","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1171.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906645.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906646","title":"Update of NRF function and services","source":"Tencent, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding status notification as one NRF funcationaility in clause 6.2.6; Adding SCP in the NRF services in clause 7.2.6. Rev 1->2 Changes: Correction of the Nnrf_NFManagement Service wrt SCP Rev 2->3: degregistered -> deregistred, highlights removed","secretary_remarks":"Revision of S2-1905720. Agreed in parallel session. This was Block approved","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25190,"status":"agreed","reservation_date":"2019-05-16 18:41:36","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905720","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1092.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"SP-190410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906646.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906647","title":"SCP and NRF interaction","source":"ZTE, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add NF Set ID and NF Service Set ID as optional input parameters of Nnrf_NFDiscovery","secretary_remarks":"Revision of S2-1905722.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25690,"status":"revised","reservation_date":"2019-05-16 18:41:37","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905722","revisedto":"S2-1906808","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1292.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906647.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906648","title":"Extending the significance of the locality parameter","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Extending the significance of the locality parameter.","secretary_remarks":"Revision of S2-1905058. Agreed in parallel session. This was Block approved","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25240,"status":"agreed","reservation_date":"2019-05-16 18:41:38","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905058","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1312.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-190410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906648.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906649","title":"Exception sheet for Rel-16 eSBA","source":"China Mobile (eSBA rapporteur)","contact":"Aihua Li","contact-id":58162,"tdoctype":"other","for":"Discussion","abstract":"Exception sheet for Rel-16 eSBA","secretary_remarks":"Revision of S2-1905793.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25730,"status":"available","reservation_date":"2019-05-16 18:41:39","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905793","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_133_Reno\/Docs\/S2-1906649.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906729","title":"SMF context transfer","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A SMF Service Context Transfer procedures is proposed","secretary_remarks":"Revision of S2-1906574. Revised in parallel session to S2-1906744.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":26320,"status":"available","reservation_date":"2019-05-19 19:38:19","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906574","revisedto":"S2-1906744","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1325.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906729.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906740","title":"Resolving the EN in Bindings between the consumer and producer","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Describe the supported binding addresses, aligned with the NF Set and NF Service Set concepts. Add a new clause for update of the bindings between the consumer and producer. Rev 4: Only the bindings to NF instance, NF service instance, and NF Set are possible when the binding is created as part of service request.","secretary_remarks":"Revision of S2-1906513. Revised in parallel session to S2-1906741.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25950,"status":"available","reservation_date":"2019-05-19 19:38:33","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906513","revisedto":"S2-1906741","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1120.0,"crrevision":8.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906740.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906741","title":"Resolving the EN in Bindings between the consumer and producer","source":"NTT DOCOMO, Huawei, Tencent","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Describe the supported binding addresses, aligned with the NF Set and NF Service Set concepts. Add a new clause for update of the bindings between the consumer and producer. Rev 4: Only the bindings to NF instance, NF service instance, and NF Set are possible when the binding is created as part of service request. Rev 7: Added resource information. Clarified in 4.17.11.3, step 3 has difference with step 3-4 in figure 4.17.11.2-1. Clarified the procedures regarding subscription\/notification.","secretary_remarks":"Revision of S2-1906740. This CR was agreed","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24560,"status":"agreed","reservation_date":"2019-05-19 19:38:34","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906740","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1120.0,"crrevision":9.0,"crcategory":"F","tsg_crp":"SP-190410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906741.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906742","title":"NF Set and NF Service Set - Open items resolution","source":"Nokia, Nokia Shanghai Bell, NTT DoCoMo, Ericsson, Huawei, HiSilicon, ZTE, Oracle, Tencent","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Item 1: Following principles are assumed and proposed: 1. Subsequent procedure can trigger reselection within an NF Set. 2. NFs within the NF Set are equivalent, the corresponding service instances of the same service type are equivalent as well Items 2\/3\/4: Simply remove Editor's notes Revision: Principles for binding, selection and reselection. Rev 6: Clarification on Reselection of NF Service Instance within equivalent NF Service Sets. Clarify that the Binding Indication can include identifiers of NF service set, NF set, NF instance, NF service instance.","secretary_remarks":"Revision of S2-1906512. Agreed in parallel session. This was Block approved","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24700,"status":"agreed","reservation_date":"2019-05-19 19:38:35","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906512","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1222.0,"crrevision":12.0,"crcategory":"B","tsg_crp":"SP-190410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906742.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906743","title":"NF Set concept for SMF","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that sets of NFs\/NF services\/Services (i.e. SMF) managing UPFs need to be connected to the same UPF. This also implies that the N4 association between SMF and UPF needs to be unique per SMF set. This is essential as any SMF in the SMF set should be able to issue request to modify\/update or delete\/release the PFCP association. Revision 1: Reliability support and introduction of set is not just for failure case, rather to enable resiliency (as pointed out in Tencent paper S2-1905148, set concept and reliability is not just for failure case rather for proactive load balancing, load rebalancing, resiliency framework in general).","secretary_remarks":"Revision of S2-1906571. This CR was agreed","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24750,"status":"agreed","reservation_date":"2019-05-19 19:38:36","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906571","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1413.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"SP-190410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906743.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906744","title":"SMF context transfer","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A SMF Service Context Transfer procedures is proposed Rev1: Editorial Corrections Moved decommissioning description about NRF to separate section Added 2 editors notes with potential alternatives\/enhancements Rev2: Separated decommissioning sections Included responses in figure Clarified that transfer is used between between SMFs in different SMF Sets Further details in the flow Editors notes on aspects to resolve added in flow Rev3: Remover timer fron step 2 and 3","secretary_remarks":"Revision of S2-1906729. This CR was agreed","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24930,"status":"agreed","reservation_date":"2019-05-19 19:38:38","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906729","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1325.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"SP-190410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906744.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906745","title":"Service Context Transfer Support in UDSF","source":"KDDI, Deutsche Telekom, Telecom Italia","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To rename the abbreviation of UDSF, and to add the description for the support of Service Context Transfer in UDSF","secretary_remarks":"Revision of S2-1906639.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":26360,"status":"available","reservation_date":"2019-05-19 19:38:39","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906639","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1391.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906745.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906746","title":"Service Context Transfer Support in UDSF","source":"KDDI, Deutsche Telekom, Telecom Italia","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To add the new service in UDSF service","secretary_remarks":"Revision of S2-1906640.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":26390,"status":"available","reservation_date":"2019-05-19 19:38:40","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906640","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1393.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906746.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906747","title":"Support of Service Context Transfer in TS23.501","source":"KDDI","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To add the specification and reference for Service Context Transfer procedures in TS23.502.","secretary_remarks":"Revision of S2-1906641. Revised to S2-1906775.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":26420,"status":"available","reservation_date":"2019-05-19 19:38:41","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906641","revisedto":"S2-1906775","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1331.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906747.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906748","title":"Service-mesh-based SCP deployment option","source":"InterDigital Inc.","contact":"Ulises Olvera","contact-id":72056,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a Service Router deployment option to Annex X","secretary_remarks":"Revision of S2-1906644. Agreed in parallel session. This was Block approved. Merged by MCC into S2-1906790","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":0,"status":"merged","reservation_date":"2019-05-19 19:38:42","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906644","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1271.0,"crrevision":11.0,"crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906748.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906749","title":"Service-mesh-based and other SCP deployment options","source":"Deutsche Telekom AG, DoCoMo, InterDigital, China Mobile, Cisco, Nokia, KDDI, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Informative Annex with describing a SCP deployment option based on a service mesh Rev 1: Initial mention that this section is a deployment example Clarified and simplified Figure X.1-1 Made Service Agent capitalization consistent Clarified and simplified Figure X.1-2 and its related description (numbering made it less clear) Clarified and simplified Figure X.2- and its related description (numbering made it less clear) Added clarification to Figure X.3-1 so that it is immediately clear to the reader that the division left is implementation-specific Rev 2: Cover: changed category to D Cover: consequences if not approved Added first paragraph stating that this annex is not meant to be an exhaustive list of deployment options. Renamed first title to 'Introduction' and made the title more descriptive Removed normative language from the CR: shall, should, may, must. It is a deployment example and not normative text Rev 3: Removed the last section Rev 4: Content was not marked as 'change' Rev 5: Added clarification that in this example the Service Agent(s) and the 5GC functionality are separate implementations. i.e., that 'co-located' does not mean 'the same code' Added clarification that no assumption is made regarding the internal composition of each '5GC functionality' Added clarification on 'deployment unit' Clarified that this example does not preclude using the service mesh for other protocols Rev 5 email approval -> Rev 6: Further clarification on the separation of the 5GC functionality and the Service Agent Further disclaimer that this example depicts only SBI interactions but that the service mesh could be used for other things also Additional figure showing an NF and NF Services Rev 7: Adding an other example of SCP implementation and deployment Rev 8: Correcting figure and mention direct communication in text Rev 9: Adding original source companies","secretary_remarks":"Revision of S2-1906643. Agreed in parallel session. This was Block approved. Revised by MCC, merging S2-1906748, to S2-1906790.","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":24710,"status":"revised","reservation_date":"2019-05-19 19:38:43","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906643","revisedto":"S2-1906790","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1271.0,"crrevision":12.0,"crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906749.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906750","title":"SCP Function Update","source":"Tencent, Nokia, Huawei, HiSilicon,","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the SCP functionality description with delete the repeat descripiton on UDM\/UDR\/AUSF\/UDR\/PCF delegated discovery. Change Option -> Model (Option is a term that is used only when it is being evaluated however when specified, the term option is misleading) Revision 2: SCP is configured with the mapping between NF Group ID(s) and SUPI(s), in the case delegated discovery in Model D is adopted. PCF Group ID is introduced in a similar way as UDM\/UDR\/AUSF Group ID. It is clarified that the UDM\/UDR\/AUSF\/PCF Group ID is not applicable to the corresponding NF consumer in the case of delegated discovery and selection via SCP. Revision 3: Removes changes to clause 3.1, 6.2.6. Removes the texts 'based on configured mapping information\u2026' in 6.2.19 regarding user identity to NF Group ID mapping and add reference to clause 6.3.1. Revision 4: Rephrase the wording related to resolution of NF Group ID. Remove the NOTEs newly added to 6.3.4, 6.3.7, 6.3.8, 6.3.9.","secretary_remarks":"Revision of S2-1906645. This CR was agreed","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25170,"status":"agreed","reservation_date":"2019-05-19 19:38:44","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906645","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1171.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-190410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906750.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906751","title":"NF Service Context Transfer Procedures","source":"Deutsche Telekom AG, Tencent, Verizon, KDDI, Huawei","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR introduces NF\/NF Service Context Transfer procedures.","secretary_remarks":"Revision of S2-1906642. This CR was agreed","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25070,"status":"agreed","reservation_date":"2019-05-19 19:38:45","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906642","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1305.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"SP-190410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906751.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906775","title":"Support of Service Context Transfer in TS23.501","source":"KDDI, Deutsche Telekom, Verizon, Telstra, Tencent","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To add the specification and reference for Service Context Transfer procedures in TS23.502.","secretary_remarks":"Revision of S2-1906747. This CR was agreed","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25030,"status":"agreed","reservation_date":"2019-05-19 19:39:03","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906747","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_eSBA"}],"crnumber":1331.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"SP-190410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906775.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906790","title":"SCP: Service-mesh-based deployment options","source":"Deutsche Telekom AG, DoCoMo, InterDigital, China Mobile, Cisco, Nokia, KDDI, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Informative Annex with describing a SCP deployment option based on a service mesh. Adding a Service Router deployment option.","secretary_remarks":"MCC revision of S2-1906749, merging S2-1906748. This CR was agreed","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25110,"status":"agreed","reservation_date":"2019-05-21 15:25:55","uploaded":"2019-05-21 16:08:58","revisionof":"S2-1906749","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1271.0,"crrevision":13.0,"crcategory":"D","tsg_crp":"SP-190410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906790.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906808","title":"SCP and NRF interaction","source":"ZTE, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add NF Set ID and NF Service Set ID as optional input parameters of Nnrf_NFDiscovery","secretary_remarks":"e-mail revision 2 of S2-1906647. Approved","agenda_item_sort_order":43,"ainumber":"6.19","ainame":"Enhancements to the Service-Based 5G System Architecture (5G_eSBA)","tdoc_agenda_sort_order":25220,"status":"agreed","reservation_date":"2019-05-24 14:08:23","uploaded":"2019-05-24 14:10:05","revisionof":"S2-1906647","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_eSBA"}],"crnumber":1292.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-190410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906808.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]