[{"name":"S2-180025","title":"LS from CT WG1: LS on timers for the network-requested PDU session modification procedure and SSC mode 3","source":"CT WG1","contact":"Christian Herrero-Veron","contact-id":45210,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 have analyzed the stage 2 requirements on the network-requested PDU session modification procedure and 'SSC mode 3' in TS 23.502 subclause 4.3.5.2. CT WG1 has identified several issues with the stage 2 text and has several questions regarding the motivation, the objectives and the proposed solution, as follows: 1. What is the purpose of the PDU session release timer provided to the UE? The timer is signalled in the NAS message, but in the CT WG1 view, the NAS layer in the UE has no use for this timer. If the timer is to be used by upper layers, why is it signalled as an IE in a NAS message? NAS layer in the UE layer has no means of controlling the transfer of IP flows between PDU sessions unless, e.g., a release indication from upper layer is received. Therefore, the NAS layer can either initiate PDU session release of the old session or release it locally or perform no action, without the need for a timer from the network. NAS layer will not check what is occurring in the user-","secretary_remarks":"Responses drafted in S2-180167, S2-180289 and S2-180307. Final response in S2-181280","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":12960,"status":"replied to","reservation_date":"2017-12-19 11:54:35","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-175378","lsreply":"S2-181280","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180025.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180054","title":"23.501: Configuration information the UE may exchange with the SMF during the lifetime of a PDU session","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: . - 5.6.10.1: add information the UE may exchange (via PCO) with the SMF during the lifetime of a PDU session","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13620,"status":"not treated","reservation_date":"2018-01-06 09:27:40","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"S2-181456, S2-181458","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180054.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180062","title":"23.502: Updates to PDU session establishment procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. in \u00a7 4.3.1, the V-SMF needs to handle the PDU Type (based on the SA WG2 agreement in Reno); It also needs to handle UE addressing information (allocated IPv4 address, interface identifier) for legal reasons + Wording clarification: 'Information that is not visible to the V-SMF' refers to information that the V-SMF is to relay between N1 and N16 (and that it may store in CDR) but that the V-SMF is not assumed to process otherwise. 2. in \u00a7 4.3.2.3 and 5.2.8.2.3: clarify the HR case for DN authentication \/ authorization of the UE 3.  \u00a7 4.3.2.2.1 Step14, \u00a74.3.3.2 step 7a: In case the (R)AN rejects QFI(s) the SMF is responsible of updating the QoS rules in the UE accordingly; in case of HR roaming it is the H-SMF that is responsible of updating the QoS rules in the UE as the impossibility to set-up some QFI(s) may have impacts on QoS rules of other QFI; when RAN rejects some QFI(s), this rejection has to be propagated to H-SMF (not possible with current Call flow) + co","secretary_remarks":"Revised to S2-181171.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13570,"status":"revised","reservation_date":"2018-01-06 09:27:41","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"S2-181171","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180062.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180063","title":"23.502: Usage of NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco, Verizon?, Deutsche Telecom?","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Specify a flow ( 4.17.X (new) ) for UPF discovery using the NRF. 2. Update NRF services so as to group NFStatusSubscribe and Nnrf_NFDiscoveryRequest in the same service as they handle the same data and clients (NF using NRF to get info on other NF) 3. Update NRF service operations with UPF related information such as UPF Discovery Information.","secretary_remarks":"Revision of Postponed P-CR S2-179325 from S2#124. Confirm Sources! Revised to S2-181271.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13740,"status":"revised","reservation_date":"2018-01-06 09:27:41","uploaded":"2018-01-16 14:42:26","revisionof":"S2-179325","revisedto":"S2-181271","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180063.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180064","title":"23.502\/\u00a7 4.3.6 : case of applications that do not support application mobility","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - at the creation of the contexts related with the PDU session in the UPF: the SMF requests application\/traffic detection in mute mode (the feature exists already) - at UPF mobility : the SMF asks the (old) UPF the status of the different application\/traffic detection contexts - the SMF moves to local switching at the new UPF (DNAI of the new UPF) the application\/traffic detection contexts for which there was no on-going traffic at the old UPF - the SMF takes care that the application\/traffic detection contexts for which there was on-going traffic at the old UPF remain served by the old DNAI until the application stops o when the application stops the SMF instructs the new UPF to direct new flows of this application to the new DNAI (new application instance)","secretary_remarks":"Revised to S2-181166.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13440,"status":"revised","reservation_date":"2018-01-06 09:27:41","uploaded":"2018-01-16 15:00:51","revisionof":"S2-179331","revisedto":"S2-181166","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180064.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180066","title":"23.502: Corrections to SMF selection","source":"Telecom Italia, ZTE, Oracle, NTT DOCOMO","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Updated labels in figures 4.3.2.2.3.2-1, 4.3.2.2.3.3-1 and 4.3.2.2.3.3-2 with the correct service operation names, where the notation 'operation_name|xxx' indicates the intended service operation and its actual semantics. - Updated the text below the figures 4.3.2.2.3.2-1, 4.3.2.2.3.3-1 and 4.3.2.2.3.3-2 with the correct service operation names (same notation as in the figures). - Added missing parameters. - Added text to steps in 3(A) and 3(B) of Option 2 to align with steps 7-8 of Option 1 for SMF selection. - Removed steps in 3(C) of Option 2 for SMF selection. - Minor editorial changes","secretary_remarks":"Revised in parallel session, merging S2-180756, to S2-181120","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13680,"status":"revised","reservation_date":"2018-01-10 07:46:39","uploaded":"2018-01-16 07:56:28","revisionof":"","revisedto":"S2-181120","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180066.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180126","title":"23.502: N4 reporting for PDU Session Inactivity","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Adding a reporting trigger in N4 reporting procedure for PDU Session Inactivity. 2. Editorial change:PDU Session has no data activity->PDU Session has no data transfer","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13670,"status":"not treated","reservation_date":"2018-01-12 09:24:48","uploaded":"2018-01-16 11:38:48","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180126.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180139","title":"23.501: Editorial modification to AF influence on traffic routing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This paper proposes to clean up the notes and correct wordings for consistency and clarificaiton.","secretary_remarks":"Revised to S2-181167.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13460,"status":"revised","reservation_date":"2018-01-12 16:24:15","uploaded":"2018-01-16 02:31:56","revisionof":"","revisedto":"S2-181167","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180139.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180153","title":"23.502: Correction to RAN Initiated QoS Flow Mobility Procedure for Dual Connectivity","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The N11 messages in clause 4.14.1 are replaced with service operations.","secretary_remarks":"Revised to S2-181169.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13520,"status":"revised","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"S2-181169","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180153.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180167","title":"[Draft] Reply LS on timers for the network-requested PDU session modification procedure and 'SSC mode 3'","source":"Qualcomm Europe Inc.(Italy)","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-18abcd","secretary_remarks":"Response to S2-180025 Revised, merging S2-180289 and S2-180307, to S2-181104.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13050,"status":"revised","reservation_date":"2018-01-12 19:01:27","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"S2-181104","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180167.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180169","title":"23.502: SSS mode 3 timeout NAS timer replacement with a PCO lifetime value","source":"Qualcomm Incorporated","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to align the logic of 'timer' and 'lifetime value' of procedures in 4.3.5.2 and 4.3.5.3 to address CT WG1 concerns in their LS in S2-180025, by not providing a PDU session Release timer as a NAS timer in 4.3.5.2, and instead provide a PDU Session Address Lifetime value to the UE upper layers in the PCO.","secretary_remarks":"Merged into S2-181105","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":12980,"status":"merged","reservation_date":"2018-01-12 19:12:10","uploaded":"2018-01-16 05:42:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180169.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180241","title":"23.501: Usage of NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco, Verizon?, Deutsche Telecom?","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Split the UPF selection between a step of Discovery of available UPF(s) and a step of selection of an UPF for a PDU Session and refer to N4 Node Level Procedures where the UPF and the SMF may exchange information such as the support of optional functionalities and capabilities 2. The discovery (OAM or NRF) allows to get the N4 address of the UPF 3. The SMF area allows the operators to partition SMF and UPF into regional clusters that are managed by different teams within the operator","secretary_remarks":"Confirm Sources! Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13790,"status":"not treated","reservation_date":"2018-01-14 21:32:10","uploaded":"2018-01-16 14:42:26","revisionof":"","revisedto":"S2-181457, S2-181459","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180241.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180245","title":"23.501: Corrections on UE Location change notification","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: First change. Name of the notification - proposal is to use 'UE location change notification' instead of 'UE mobility event Notification' Second change. Use 'UE presence in LADN' and its descriptions Third change. Add 'SMF enable downlink data notification or not' on receiving the notification And more minor changes including editorial changes.","secretary_remarks":"Revised to S2-181109.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13140,"status":"revised","reservation_date":"2018-01-15 01:48:49","uploaded":"2018-01-16 07:04:46","revisionof":"","revisedto":"S2-181109","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180245.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180247","title":"23.501: LADN support for RRC Inactive","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: First change It is proposed to use the agreed termilogy (i.e. the UE presence in LADN; IN, OUT or UNKNOWN) instead of using 'the relationship between UE location and a LADN service area. It is proposed to correct the description of the AMF behaviour when it is subscribed for LADN, that is. 'the AMF tracks the UE location with considering CM state and RRC state and determines the UE presence in LADN and notifies the information to the SMF' Second change In case of the deployment that RRC inactive state can be enabled, the AMF triggers N2 Notification procedure to track the UE presence in LADN even when the UE transits to the RRC Inactive state.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13320,"status":"not treated","reservation_date":"2018-01-15 01:59:43","uploaded":"2018-01-16 07:04:46","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180247.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180263","title":"23.502: Correction on PDU Session Establishment procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Change 'Namf_PDUSession_CreateSMContext Request' into 'Nsmf_PDUSession_CreateSMContext Request\/ Nsmf_PDUSession_UpdateSMContext Request' in step 3a of Figure 4.3.2.2.1-1, and Change 'Namf_PDUSession_CreateSMContext Response' into 'Nsmf_PDUSession_CreateSMContext Response\/ Nsmf_PDUSession_UpdateSMContext Response'in step 5 of Figure 4.3.2.2.1-1. 2. Move the step'First Downlink Data' to step 16b bebow in Figure 4.3.2.2.1-1 to align with Figure 4.3.2.2.2-1. 3. Replace 'Access Technology Type' into 'Access Type' in discrption of step1. 4. Add 'or switching between 3GPP access and non-3GPP access' in discrption of step 2. 5. Editorial modify 'For' into 'for 'in 'Subscription For PDU Session Status Notification' in discrption of step 3, and editorial modify 'then' into 'that' in discrption of step 3. 6. Add 'as described in TS 23.501 [2] clause 6.3.7' in discrption of step 7a. 7. Remove the overlap step number mark 9.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13600,"status":"not treated","reservation_date":"2018-01-15 07:31:03","uploaded":"2018-01-16 11:42:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180263.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180264","title":"23.502: Update PDU Session Modification procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add step 1e in 4.3.3.3 PDU Session Modification for home-routed roaming.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13610,"status":"not treated","reservation_date":"2018-01-15 07:31:03","uploaded":"2018-01-16 11:42:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180264.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180265","title":"23.502: Correction on AF influence on traffic routing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Addition of the removal of AF request in Processing AF requests to influence traffic routing  2) Addition of modification (update or delete) the AF request in NEF Transferring an AF request to the relevant PCF","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13480,"status":"endorsed","reservation_date":"2018-01-15 07:31:03","uploaded":"2018-01-16 11:42:53","revisionof":"","revisedto":"S2-181550","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180265.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180288","title":"23.501: Editorial on support for LADN","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Editorial modifications.","secretary_remarks":"Merged into S2-181111.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13250,"status":"merged","reservation_date":"2018-01-15 10:05:31","uploaded":"2018-01-16 13:10:38","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180288.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180289","title":"[DRAFT] LS Response on PDU session release timers in 'SSC mode 3'","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"This contribution proposes to answer the LS from CT WG1 .","secretary_remarks":"Response to S2-180025. Merged into S2-181104.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13030,"status":"merged","reservation_date":"2018-01-15 10:05:31","uploaded":"2018-01-16 13:10:38","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180289.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180290","title":"23.502: Clarification on PDU Session Release timer provided to the UE for 'SSC mode 3'","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Provide the release timer to the UE by transparent means.","secretary_remarks":"Revised, merging S2-180169 and S2-180373, to S2-181105.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13000,"status":"revised","reservation_date":"2018-01-15 10:05:31","uploaded":"2018-01-16 13:10:38","revisionof":"","revisedto":"S2-181105","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180290.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180294","title":"23.502: 502: Correction of UDR usage in SM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that UDM\/PCF may invoke UDR services are clarified.","secretary_remarks":"Revised to S2-181272.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13720,"status":"revised","reservation_date":"2018-01-15 10:19:34","uploaded":"2018-01-16 14:55:18","revisionof":"","revisedto":"S2-181272","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180294.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180307","title":"[DRAFT] LS reply on timers for the network-requested PDU session modification procedure and 'SSC mode 3'","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"Proposed reply to incoming LS in S2-180025","secretary_remarks":"Response to S2-180025. Merged into S2-181104.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13040,"status":"merged","reservation_date":"2018-01-15 12:21:04","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180307.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180333","title":"23.502: Align the UE location presence status of LADN Session into Network Triggered Service Request procedure","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: for the LADN PDU session, if UE presence in LADN is Unknown status and DL data arrives, the SMF may not trigger a notification to the AMF.","secretary_remarks":"Revised to S2-181108.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13120,"status":"revised","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:56","revisionof":"","revisedto":"S2-181108","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180333.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180346","title":"23.502: Cleanup of the service request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Per above reason of changes, the related clarification and changes are updated.","secretary_remarks":"Revised to S2-181164.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13350,"status":"revised","reservation_date":"2018-01-15 13:37:06","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"S2-181164","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180346.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180372","title":"23.501: Remaining IP address\/prefix lifetime with SSC mode 3","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies how the network signals the remaining lifetime for a PDU Session in case of SSC mode 3 with multiple PDU Sessions and with Multi-homed IPv6 PDU Session.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":12970,"status":"approved","reservation_date":"2018-01-15 14:36:26","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"S2-181507","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180372.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180373","title":"23.502: Remaining IP address\/prefix lifetime with SSC mode 3","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Aligns the text in clause 4.3.5.2 with the text in clause 4.3.5.3.","secretary_remarks":"Merged into S2-181105","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":12990,"status":"merged","reservation_date":"2018-01-15 14:38:03","uploaded":"2018-01-16 14:50:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180373.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180377","title":"23.502: LADN Signalling to SMF","source":"Sony","contact":"Svante Aln\u00e5s","contact-id":62551,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) In the signalling from AMF to SMF include sufficient information to SMF regarding LADN so that SMF are able to process the request directly 2) Add GPSI in the corresponding interface to SMF","secretary_remarks":"Revised, merging S2-180751, to S2-181114.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13270,"status":"revised","reservation_date":"2018-01-15 15:08:41","uploaded":"2018-01-16 14:33:43","revisionof":"","revisedto":"S2-181114","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180377.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180415","title":"23.501: Corrections to UPF selection and resolution of related Editor's Note","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Marge into a single list. Generalize the topological aspects that may be taken into account by the SMF. Remove editor's note.","secretary_remarks":"Revised to S2-181273.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13800,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"S2-181273","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180415.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180441","title":"23.501: Clarification in LADN clause 5.6.5 - TS 23.501","source":"Intel, ZTE, ETRI, KDDI","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The AMF and SMF know whether a DNN is a LADN DNN based on the UE subscription information received from the UDM. AMF indicates to UE whether a DNN is a LADN DNN. AMF indicates to UE that the LADN is not available in the UE's current Registration Area. Align the terms with 23.502 to 'UE presence in a LADN'. Add missing SMF behaviour when the UE presence in a LADN is OUT. Remove the redundant description for SMF behaviour when the UE presence in a LADN is IN or UNKNOWN.","secretary_remarks":"Revised, merging S2-180288 and S2-180545, to S2-181111.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13180,"status":"revised","reservation_date":"2018-01-15 19:47:32","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"S2-181111","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180441.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180442","title":"23.502: Clarification on LADN related aspects - TS 23.502","source":"Intel, ZTE, ETRI, KDDI","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify the SMF behaviour on rejecting the request when UE's presence in a LADN is OUT for the procedure of General Registration, UE Triggered Service Request, UE Requested PDU Session Establishment and Modification. Clarify how AMF updates UE about the LADN information change and UE behaviour when the LADN service area information is empty. Correct the wording of 'UE presence in LADN' to 'UE presence in a LADN' in clause 4.15.4. Add the detail on how the LADN DNN is indicated from UDM to AMF and SMF in clause 5.2.3.3.1.","secretary_remarks":"Revised to S2-181112.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13200,"status":"revised","reservation_date":"2018-01-15 19:47:32","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"S2-181112","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180442.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180480","title":"23.501: Update to AF influence on traffic routing","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. This paper proposes to optionally include an application identifier in the PDU Session setup\/modification request to allow AF influence to be applied before application traffic starts. 2. This paper proposes to use AF transaction ID for the AF to correlate AF request and SMF notification.","secretary_remarks":"Revised to S2-181168.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13490,"status":"revised","reservation_date":"2018-01-16 01:03:56","uploaded":"2018-01-16 02:31:56","revisionof":"","revisedto":"S2-181168","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180480.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180490","title":"23.501: CR Relation between the SSC mode the PDU type","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In this release, SSC mode 3 only apply to IP PDU type.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13710,"status":"approved","reservation_date":"2018-01-16 02:16:38","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"S2-181554","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180490.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180501","title":"LADN handling in PDU session establishment procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Approval","abstract":"In this contribution,how to handle LADN session in PDU establishment procedure is discussed.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13340,"status":"not treated","reservation_date":"2018-01-16 02:47:16","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180501.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180502","title":"23.501: Clarification on LADN PDU Session establishment handling","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Add explicit description that DNN include information on whether the DNN is LADN. 2) AMF can reject the PDU Session establishment request.","secretary_remarks":"Revised to S2-181115.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13160,"status":"revised","reservation_date":"2018-01-16 02:47:16","uploaded":"2018-01-16 13:54:33","revisionof":"","revisedto":"S2-181115","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180502.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180508","title":"23.502: Correction on Secondary authorization\/authentication procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This contribution clarifies duiring PDU session establishment, how secondary authorization\/authentication is performed, especially on authorization\/authentication without using UPF. There are also some corrections on Figure 4.3.2.3-1 and some other descriptions.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13630,"status":"not treated","reservation_date":"2018-01-16 02:57:27","uploaded":"2018-01-16 11:42:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180508.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180525","title":"23.501: Clarification on mobility event subscription transfer","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the new AMF notiifes current status only when the new AMF does not know the last reported status.","secretary_remarks":"Revised to S2-181165.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13410,"status":"revised","reservation_date":"2018-01-16 04:59:31","uploaded":"2018-01-16 10:45:51","revisionof":"","revisedto":"S2-181165","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180525.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180539","title":"23.502: PDU session ID in PDU session management procedure","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. PDU session ID is included in N1 SM NAS message in UE requested PDU session establishement\/modification\/release procedure. 2. PDU session ID is removed from Nsmf_PDUSession_CreateSMContext service operation. 3. cleanup the PDU session ID transmission for SSC mode 3 PDU session.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13660,"status":"endorsed","reservation_date":"2018-01-16 05:46:11","uploaded":"2018-01-16 11:31:38","revisionof":"","revisedto":"S2-182093","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180539.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180541","title":"23.502: LADN PDU session deactivation in N2 HO procedure","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. T-AMF does not request the SM context during HO preparation if the target cell is out of the LADN service area. 2. T-AMF includes the LADN PDU session in the non-accepted PDU session list.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13400,"status":"noted","reservation_date":"2018-01-16 05:49:18","uploaded":"2018-01-16 11:31:38","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180541.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180545","title":"23.501: SMF behaviour when UE is out of LADN service area","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the description on SMF notification to the UPF and the SMF rejection of user plane establishment to make TS 23.501 aligned with TS 23.502.","secretary_remarks":"Merged into S2-181111.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13260,"status":"merged","reservation_date":"2018-01-16 06:03:58","uploaded":"2018-01-16 08:13:45","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180545.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180546","title":"23.502: SMF behaviour based on LADN notification","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the SMF shall perform as defined in the TS 23.501 section 5.6.5 when it is notified about UE presence in the LADN service area during the Registration, UE Triggered Service Request, AN Release and Handover procedures. Clarify that Downlink Data Notification is disabled by the SMF when UE is out of LADN service area during the Service Request procedures.","secretary_remarks":"Handover part endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13390,"status":"endorsed","reservation_date":"2018-01-16 06:03:58","uploaded":"2018-01-16 08:13:45","revisionof":"","revisedto":"S2-181493","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180546.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180547","title":"23.502: Clarification on Internal Event Exposure","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarification on system behaviour in case of mobility event notification happens, and which procedure may trigger the mobility event notification.","secretary_remarks":"Revised to S2-181116.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13300,"status":"revised","reservation_date":"2018-01-16 06:03:58","uploaded":"2018-01-16 08:13:45","revisionof":"","revisedto":"S2-181116","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180547.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180602","title":"23.501: Update on Traffic Detection Information","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Replacing PDU session ID with CN tunnel info as one of the traffic detection parameters.","secretary_remarks":"Revised to S2-181170.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13540,"status":"revised","reservation_date":"2018-01-16 07:31:11","uploaded":"2018-01-16 14:20:35","revisionof":"","revisedto":"S2-181170","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180602.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180603","title":"23.501: Proposal of Specifying Packet Detection Rule","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Proposed detailed descriptions of Packet Detection Rule.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13560,"status":"endorsed","reservation_date":"2018-01-16 07:31:11","uploaded":"2018-01-16 14:20:35","revisionof":"","revisedto":"S2-181553","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180603.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180604","title":"Proposal of Sequence Number Marking in the User Plane Function","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Approval","abstract":"It is proposed to marking user plane packet with sequence number in the packet header by user plane function.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13640,"status":"not treated","reservation_date":"2018-01-16 07:31:11","uploaded":"2018-01-16 14:20:36","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180604.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180605","title":"23.501: Proposal of Sequence Number Marking in the User Plane Function","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Propose a solution to achieve sequence number marking on user plane packet.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13650,"status":"not treated","reservation_date":"2018-01-16 07:31:11","uploaded":"2018-01-16 14:20:36","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180605.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180657","title":"23.501: Location information needed for UPF selection","source":"Nokia, Nokia Shanghai Bell,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13840,"status":"not treated","reservation_date":"2018-01-16 09:18:02","uploaded":"2018-01-16 14:42:26","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180657.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180667","title":"23.501: Add UNKNOWN status to UE location change","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding UNKNOWN status to UE Location change notification subclause.","secretary_remarks":"Revised to S2-181106.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13100,"status":"revised","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"S2-181106","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180667.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180668","title":"23.502: Generalize exposure of Mobility Events from AMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Generalize 'Exposure of Mobility Events from AMF' to cover both LADN and other cases.","secretary_remarks":"Revised to S2-181107.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13080,"status":"revised","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"S2-181107","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180668.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180669","title":"23.501: Clarification on editor's note related with LADN","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Delete the editor's note and clarify the UE determines whether a DNN is a LADN DNN based on URSP.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13330,"status":"not treated","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180669.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180670","title":"23.502: Operation type in Nsmf_PDUSession_UpdateSMContext Request","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: (1) Change the 'Cause' in Nsmf_PDUSession_Update SM Context Request during procedures of clause 4.2 to 4.12 to 'Operation type'. (2) Change 'Nsmf_PDUSession_UpdateSMContext Ack' in clause 4.2.6 and 4.12.4.2 to 'Nsmf_PDUSession_UpdateSMContext Response'. (3) Change the 'SM N2 Information' to 'N2 SM Information', 'MM N2 SM Information' to 'N2 MM Information'.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13850,"status":"not treated","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180670.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180671","title":"23.502: Rejection of PDU session establishment when authentication or authorization fails","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: (1) Clarify that the SMF should reject the PDU Session Establishment Request from the UE with an appropriate cause when the PDU Session cannot be established. (2) Correct wrong step number (step 19->step 20) in step 6.  (3) Editorial modificaiton in the service name in step 3a and 5 the Figure 4.3.2.2.1-1.","secretary_remarks":"Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13590,"status":"not treated","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180671.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180751","title":"23.502: LADN service area and SMF","source":"NEC","contact":"Taka Yoshizawa","contact-id":40702,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to update TS 23.502 clause 4.3.2.2: 'UE Requested PDU Session Establishment' step 3 'From AMF to SMF' to include this indication (named as 'LADN_Status) to indicate current relationship between UE location and a LADN service area (i.e. IN, OUT, UNKNOWN). Additionally, based on step 3, it updates step 4 to allow SMF check the validity of the UE request: it checks: (If the DNN corresponds to an LADN), whether the UE is located IN, OUT, UNKNOWN to the LADN service area based on, LADN_Status and the UE location reporting from the AMF.","secretary_remarks":"Merged into S2-181114.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13290,"status":"merged","reservation_date":"2018-01-16 13:57:13","uploaded":"2018-01-16 14:41:08","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180751.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180764","title":"23.501: Additional text in 5.6.7","source":"NEC","contact":"Taka Yoshizawa","contact-id":40702,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adds text in Sec. 5.6.7 to clarify that AF is able to register and receive policies for traffic treatment and gets notified about any updated policies through previous subscription.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13510,"status":"noted","reservation_date":"2018-01-16 14:54:00","uploaded":"2018-01-16 14:58:18","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180764.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181104","title":"[Draft] Reply LS on timers for the network-requested PDU session modification procedure and 'SSC mode 3'","source":"Qualcomm Europe Inc.(Italy)","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-18abcd","secretary_remarks":"Revision of S2-180167, merging S2-180289 and S2-180307. Revised to S2-181280.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13060,"status":"revised","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180167","revisedto":"S2-181280","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181104.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181105","title":"23.502: Clarification on PDU Session Release timer provided to the UE for 'SSC mode 3'","source":"Huawei, HiSilicon, Intel, Qualcomm Incorporated","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Provide the release timer to the UE by transparent means.","secretary_remarks":"Revision of S2-180290, merging S2-180169 and S2-180373. Revised to S2-181278.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13010,"status":"revised","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180290","revisedto":"S2-181278","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181105.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181106","title":"23.501: Add UNKNOWN status to UE location change","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding UNKNOWN status to UE Location change notification subclause.","secretary_remarks":"Revision of S2-180667. Postponed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13110,"status":"postponed","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180667","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181106.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181107","title":"23.502: Generalize exposure of Mobility Events from AMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Generalize 'Exposure of Mobility Events from AMF' to cover both LADN and other cases.","secretary_remarks":"Revision of S2-180668. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13090,"status":"approved","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180668","revisedto":"S2-181548","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181107.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181108","title":"23.502: Align the UE location presence status of LADN Session into Network Triggered Service Request procedure","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: for the LADN PDU session, if UE presence in LADN is Unknown status and DL data arrives, the SMF may not trigger a notification to the AMF.","secretary_remarks":"Revision of S2-180333. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13130,"status":"approved","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180333","revisedto":"S2-181549","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181108.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181109","title":"23.501: Corrections on UE Location change notification","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: First change. Name of the notification - proposal is to use 'UE location change notification' instead of 'UE mobility event Notification' Second change. Use 'UE presence in LADN' and its descriptions Third change. Add 'SMF enable downlink data notification or not' on receiving the notification And more minor changes including editorial changes.","secretary_remarks":"Revision of S2-180245. Postponed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13150,"status":"postponed","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180245","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181109.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181111","title":"23.501: Clarification in LADN clause 5.6.5 - TS 23.501","source":"Intel, ZTE, ETRI, KDDI, Huawei","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The AMF and SMF know whether a DNN is a LADN DNN based on the UE subscription information received from the UDM. AMF indicates to UE whether a DNN is a LADN DNN. AMF indicates to UE that the LADN is not available in the UE's current Registration Area. Align the terms with 23.502 to 'UE presence in a LADN'. Add missing SMF behaviour when the UE presence in a LADN is OUT. Remove the redundant description for SMF behaviour when the UE presence in a LADN is IN or UNKNOWN.","secretary_remarks":"Revision of S2-180441, merging S2-180288 and S2-180545. Noted","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13190,"status":"noted","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180441","revisedto":"S2-181535","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181111.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181112","title":"23.502: Clarification on LADN related aspects - TS 23.502","source":"Intel, ZTE, ETRI, KDDI","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify the SMF behaviour on rejecting the request when UE's presence in a LADN is OUT for the procedure of General Registration, UE Triggered Service Request, UE Requested PDU Session Establishment and Modification. Clarify how AMF updates UE about the LADN information change and UE behaviour when the LADN service area information is empty. Correct the wording of 'UE presence in LADN' to 'UE presence in a LADN' in clause 4.15.4. Add the detail on how the LADN DNN is indicated from UDM to AMF and SMF in clause 5.2.3.3.1.","secretary_remarks":"Revision of S2-180442. This was withdrawn.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13210,"status":"withdrawn","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180442","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181112.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181113","title":"Key Open Issues of LADN Principles","source":"Drafting group","contact":"Maurice Pope","contact-id":648,"tdoctype":"discussion","for":"Discussion","abstract":"Drafted based on the discussion during LADN Drafting Session","secretary_remarks":"Created in parallel session Revised to S2-181274.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13220,"status":"revised","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"","revisedto":"S2-181274","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181113.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181114","title":"23.502: LADN Signalling to SMF","source":"Sony, NEC","contact":"Svante Aln\u00e5s","contact-id":62551,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) In the signalling from AMF to SMF include sufficient information to SMF regarding LADN so that SMF are able to process the request directly 2) Add GPSI in the corresponding interface to SMF","secretary_remarks":"Revision of S2-180377, merging S2-180751. Postponed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13280,"status":"postponed","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180377","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181114.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181115","title":"23.501: Clarification on LADN PDU Session establishment handling","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Add explicit description that DNN include information on whether the DNN is LADN. 2) AMF can reject the PDU Session establishment request.","secretary_remarks":"Revision of S2-180502. This was withdrawn.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13170,"status":"withdrawn","reservation_date":"2018-01-23 13:27:53","uploaded":null,"revisionof":"S2-180502","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181116","title":"23.502: Clarification on Internal Event Exposure","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarification on system behaviour in case of mobility event notification happens, and which procedure may trigger the mobility event notification.","secretary_remarks":"Revision of S2-180547. Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13310,"status":"endorsed","reservation_date":"2018-01-23 13:27:53","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180547","revisedto":"S2-181494","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181116.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181120","title":"23.502: Corrections to SMF selection","source":"Telecom Italia, ZTE, Oracle, NTT DOCOMO, Vodafone?, Orange?, Huawei?, Ericsson?","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Updated labels in figures 4.3.2.2.3.2-1, 4.3.2.2.3.3-1 and 4.3.2.2.3.3-2 with the correct service operation names, where the notation 'operation_name|xxx' indicates the intended service operation and its actual semantics. - Updated the text below the figures 4.3.2.2.3.2-1, 4.3.2.2.3.3-1 and 4.3.2.2.3.3-2 with the correct service operation names (same notation as in the figures). - Added missing parameters. - Added text to steps in 3(A) and 3(B) of Option 2 to align with steps 7-8 of Option 1 for SMF selection. - Removed steps in 3(C) of Option 2 for SMF selection. - Minor editorial changes","secretary_remarks":"Revision of S2-180066, merging S2-180756. Revised to S2-181277.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13690,"status":"revised","reservation_date":"2018-01-23 13:27:54","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180066","revisedto":"S2-181277","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181120.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181164","title":"23.502: Cleanup of the service request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Per above reason of changes, the related clarification and changes are updated.","secretary_remarks":"Revision of S2-180346. Revised to S2-181275.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13360,"status":"revised","reservation_date":"2018-01-24 06:42:56","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180346","revisedto":"S2-181275","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181164.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181165","title":"23.501: Clarification on mobility event subscription transfer","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the new AMF notiifes current status only when the new AMF does not know the last reported status.","secretary_remarks":"Revision of S2-180525. Revised to S2-181276.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13420,"status":"revised","reservation_date":"2018-01-24 06:42:56","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180525","revisedto":"S2-181276","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181165.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181166","title":"23.502\/\u00a7 4.3.6 : case of applications that do not support application mobility","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - at the creation of the contexts related with the PDU session in the UPF: the SMF requests application\/traffic detection in mute mode (the feature exists already) - at UPF mobility : the SMF asks the (old) UPF the status of the different application\/traffic detection contexts - the SMF moves to local switching at the new UPF (DNAI of the new UPF) the application\/traffic detection contexts for which there was no on-going traffic at the old UPF - the SMF takes care that the application\/traffic detection contexts for which there was on-going traffic at the old UPF remain served by the old DNAI until the application stops o when the application stops the SMF instructs the new UPF to direct new flows of this application to the new DNAI (new application instance)","secretary_remarks":"Revision of S2-180064. WITHDRAWN","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13450,"status":"withdrawn","reservation_date":"2018-01-24 06:42:57","uploaded":null,"revisionof":"S2-180064","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181167","title":"23.501: Editorial modification to AF influence on traffic routing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This paper proposes to clean up the notes and correct wordings for consistency and clarificaiton.","secretary_remarks":"Revision of S2-180139. Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13470,"status":"endorsed","reservation_date":"2018-01-24 06:42:57","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180139","revisedto":"S2-181583","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181167.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181168","title":"23.501: Update to AF influence on traffic routing","source":"Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. This paper proposes to optionally include an application identifier in the PDU Session setup\/modification request to allow AF influence to be applied before application traffic starts. 2. This paper proposes to use AF transaction ID for the AF to correlate AF request and SMF notification.","secretary_remarks":"Revision of S2-180480. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13500,"status":"approved","reservation_date":"2018-01-24 06:42:57","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180480","revisedto":"S2-181582","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181168.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181169","title":"23.502: Correction to RAN Initiated QoS Flow Mobility Procedure for Dual Connectivity","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The N11 messages in clause 4.14.1 are replaced with service operations.","secretary_remarks":"Revision of S2-180153. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13530,"status":"approved","reservation_date":"2018-01-24 06:42:57","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180153","revisedto":"S2-181551","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181169.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181170","title":"23.501: Update on Traffic Detection Information","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Replacing PDU session ID with CN tunnel info as one of the traffic detection parameters.","secretary_remarks":"Revision of S2-180602. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13550,"status":"approved","reservation_date":"2018-01-24 06:42:57","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180602","revisedto":"S2-181552","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181170.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181171","title":"23.502: Updates to PDU session establishment procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. in \u00a7 4.3.1, the V-SMF needs to handle the PDU Type (based on the SA WG2 agreement in Reno); It also needs to handle UE addressing information (allocated IPv4 address, interface identifier) for legal reasons + Wording clarification: 'Information that is not visible to the V-SMF' refers to information that the V-SMF is to relay between N1 and N16 (and that it may store in CDR) but that the V-SMF is not assumed to process otherwise. 2. in \u00a7 4.3.2.3 and 5.2.8.2.3: clarify the HR case for DN authentication \/ authorization of the UE 3.  \u00a7 4.3.2.2.1 Step14, \u00a74.3.3.2 step 7a: In case the (R)AN rejects QFI(s) the SMF is responsible of updating the QoS rules in the UE accordingly; in case of HR roaming it is the H-SMF that is responsible of updating the QoS rules in the UE as the impossibility to set-up some QFI(s) may have impacts on QoS rules of other QFI; when RAN rejects some QFI(s), this rejection has to be propagated to H-SMF (not possible with current Call flow) + co","secretary_remarks":"Revision of S2-180062. Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13580,"status":"endorsed","reservation_date":"2018-01-24 06:42:57","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180062","revisedto":"S2-181454","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181171.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181271","title":"23.502: Usage of NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Specify a flow ( 4.17.X (new) ) for UPF discovery using the NRF. 2. Update NRF services so as to group NFStatusSubscribe and Nnrf_NFDiscoveryRequest in the same service as they handle the same data and clients (NF using NRF to get info on other NF) 3. Update NRF service operations with UPF related information such as UPF Discovery Information.","secretary_remarks":"Revision of S2-180063. Revised off-line to S2-181360","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13750,"status":"revised","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180063","revisedto":"S2-181360","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181271.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181272","title":"23.502: 502: Correction of UDR usage in SM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that UDM\/PCF may invoke UDR services are clarified.","secretary_remarks":"Revision of S2-180294. Endorsed in parallel session","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13730,"status":"endorsed","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180294","revisedto":"S2-181989","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181272.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181273","title":"23.501: Corrections to UPF selection and resolution of related Editor's Note","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Marge into a single list. Generalize the topological aspects that may be taken into account by the SMF. Remove editor's note.","secretary_remarks":"Revision of S2-180415. Revised to S2-181365.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13810,"status":"revised","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180415","revisedto":"S2-181365","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181273.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181274","title":"Key Open Issues of LADN Principles","source":"Drafting group","contact":"Changhong Shan","contact-id":45586,"tdoctype":"discussion","for":"Discussion","abstract":"Drafted based on the discussion during LADN Drafting Session","secretary_remarks":"Revision of S2-181113. Revised to S2-181358.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13230,"status":"revised","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181113","revisedto":"S2-181358","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181274.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181275","title":"23.502: Cleanup of the service request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Per above reason of changes, the related clarification and changes are updated.","secretary_remarks":"Revision of S2-181164. Revised to S2-181279.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13370,"status":"revised","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181164","revisedto":"S2-181279","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181275.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181276","title":"23.501: Clarification on mobility event subscription transfer","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that the new AMF notiifes current status only when the new AMF does not know the last reported status.","secretary_remarks":"Revision of S2-181165. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13430,"status":"approved","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181165","revisedto":"S2-181510","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181276.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181277","title":"23.502: Corrections to SMF selection","source":"Telecom Italia, ZTE, Oracle, NTT DOCOMO, Vodafone, Orange, Huawei, Ericsson","contact":"Mario Madella","contact-id":23765,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Updated labels in figures 4.3.2.2.3.2-1, 4.3.2.2.3.3-1 and 4.3.2.2.3.3-2 with the correct service operation names, where the notation 'operation_name|xxx' indicates the intended service operation and its actual semantics. - Updated the text below the figures 4.3.2.2.3.2-1, 4.3.2.2.3.3-1 and 4.3.2.2.3.3-2 with the correct service operation names (same notation as in the figures). - Added missing parameters. - Added text to steps in 3(A) and 3(B) of Option 2 to align with steps 7-8 of Option 1 for SMF selection. - Removed steps in 3(C) of Option 2 for SMF selection. - Minor editorial changes","secretary_remarks":"Revision of S2-181120. This was Endorsed.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13700,"status":"endorsed","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181120","revisedto":"S2-181850","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181277.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181278","title":"23.502: Clarification on PDU Session Release timer provided to the UE for 'SSC mode 3'","source":"Huawei, HiSilicon, Intel, Qualcomm Incorporated","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Provide the release timer to the UE by transparent means.","secretary_remarks":"Revision of S2-181105. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13020,"status":"approved","reservation_date":"2018-01-25 09:02:44","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181105","revisedto":"S2-181547","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181278.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181279","title":"23.502: Cleanup of the service request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Per above reason of changes, the related clarification and changes are updated.","secretary_remarks":"Revision of S2-181275. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13380,"status":"approved","reservation_date":"2018-01-25 09:04:47","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181275","revisedto":"S2-181558","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181279.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181280","title":"Reply LS on timers for the network-requested PDU session modification procedure and 'SSC mode 3'","source":"SA WG2","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-181278","secretary_remarks":"Revision of S2-181104. Agreed in parallel session. Block Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13070,"status":"approved","reservation_date":"2018-01-25 09:04:47","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181104","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180025","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181280.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181358","title":"Key Open Issues of LADN Principles","source":"Drafting group","contact":"Changhong Shan","contact-id":45586,"tdoctype":"discussion","for":"Discussion","abstract":"Drafted based on the discussion during LADN Drafting Session","secretary_remarks":"Revision of S2-181274. Conclusions endorsed in parallel session.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13240,"status":"endorsed","reservation_date":"2018-01-26 10:04:47","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181274","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181358.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181360","title":"23.502: Usage of NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Specify a flow ( 4.17.X (new) ) for UPF discovery using the NRF. 2. Update NRF services so as to group NFStatusSubscribe and Nnrf_NFDiscoveryRequest in the same service as they handle the same data and clients (NF using NRF to get info on other NF) 3. Update NRF service operations with UPF related information such as UPF Discovery Information.","secretary_remarks":"Revision of S2-181271. Revised to S2-181364.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13760,"status":"revised","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181271","revisedto":"S2-181364","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181360.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181364","title":"23.502: Usage of NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Specify a flow ( 4.17.X (new) ) for UPF discovery using the NRF. 2. Update NRF services so as to group NFStatusSubscribe and Nnrf_NFDiscoveryRequest in the same service as they handle the same data and clients (NF using NRF to get info on other NF) 3. Update NRF service operations with UPF related information such as UPF Discovery Information.","secretary_remarks":"Revision of S2-181360. For e-mail approval. e-mail revision 2 approved. Revised to S2-181396.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13770,"status":"revised","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181360","revisedto":"S2-181396","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181364.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181365","title":"23.501: Corrections to UPF selection and resolution of related Editor's Note","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Marge into a single list. Generalize the topological aspects that may be taken into account by the SMF. Remove editor's note.","secretary_remarks":"Revision of S2-181273. For e-mail approval. e-mail revision 1 approved. Revised to S2-181397.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13820,"status":"revised","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181273","revisedto":"S2-181397","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181365.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181396","title":"23.502: Usage of NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Specify a flow ( 4.17.X (new) ) for UPF discovery using the NRF. 2. Update NRF services so as to group NFStatusSubscribe and Nnrf_NFDiscoveryRequest in the same service as they handle the same data and clients (NF using NRF to get info on other NF) 3. Update NRF service operations with UPF related information such as UPF Discovery Information.","secretary_remarks":"e-mail revision 2 of S2-181364. Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13780,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181364","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181396.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181397","title":"23.501: Corrections to UPF selection and resolution of related Editor's Note","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Marge into a single list. Generalize the topological aspects that may be taken into account by the SMF. Remove editor's note.","secretary_remarks":"e-mail revision 1 of S2-181365. Approved","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13830,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181365","revisedto":"S2-181610","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181397.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]