[{"name":"S2-181447","title":"LS from CT WG4: Reply LS on transparent relay between SMF in the VPLMN and SMF in the HPLMN","source":"CT WG4","contact":"Bruno Landais","contact-id":17613,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks SA WG2 for their LS on transparent relay between SMF in the VPLMN and SMF in the HPLMN. CT WG4 considers that it is feasible to design a stage 3 solution over N16, along principles similar as those listed in SA WG2 Answers 4 and 5, allowing: ? the V-SMF to transfer NAS SM information which it does not need to interpret, in a container over N16 towards the H-SMF; ? the V-SMF to transfer NAS SM information which it does not comprehend (unknown IEs or IEs with an unknown value not set to 'reserved' according to the release to which the V-SMF complies), in a different container over N16 towards the H-SMF; ? the H-SMF to transfer NAS SM information which the V-SMF does not need to interpret, in one container over N16 towards the V-SMF; ? the V-SMF to append unknown NAS SM information received in the N16 container at the end of the NAS SM message it sends to the UE. The principles to transfer NAS SM information over N16 are specified in the attached 29.502 pCR. Action: CT WG4 k","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":14190,"status":"noted","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-02 14:51:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"C4-181383","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181447.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181454","title":"Corrections to PDU session establishment \/ modification procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","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 endorsed draftCR S2-181171. Revised to S2-182693.","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-30 12:05:33","uploaded":"2018-02-17 09:37:46","revisionof":"S2-181171","revisedto":"S2-182693","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181454.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181457","title":"Using NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","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 usinf NRF to get info on other NF) 3. Update NRF service operations with UPF rlated information such as UPF Discovery Information","secretary_remarks":"Revision of approved draftCR S2-181396. Revised to S2-182694.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13780,"status":"revised","reservation_date":"2018-01-30 12:05:36","uploaded":"2018-02-17 11:44:25","revisionof":"S2-180241","revisedto":"S2-182694","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":5.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181457.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181459","title":"Using NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","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":"Revision of unhandled draftCR S2-180241. Revised to S2-182813.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":15020,"status":"revised","reservation_date":"2018-01-30 13:31:25","uploaded":"2018-02-17 11:44:25","revisionof":"S2-180241","revisedto":"S2-182813","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181459.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181460","title":"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":"CR","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":"Revision of unhandled draftCR S2-180054. Revised to S2-182806.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14820,"status":"revised","reservation_date":"2018-01-31 13:03:29","uploaded":"2018-02-17 11:44:25","revisionof":"S2-181456","revisedto":"S2-182806","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181460.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181481","title":"LS from IETF DMM: Reply LS on indicating service continuity usage of the additional IPv6 prefix in Router Advertisement","source":"IETF DMM","contact":"Sri Gundavelli","contact-id":43435,"tdoctype":"LS in","for":"Information","abstract":"Dear SA WG2 Chair: Thank you for your LS query (Reference: https:\/\/datatracker.ietf.org\/liaison\/1554\/). The IETF DMM working group has reviewed the LS statement and below is our response based on the discussions in the WG and feedback. In our view, the work-item described in the LS query has three components: 1.) The approach of coloring IPv4 and IPv6 addresses\/prefixes with mobility properties. This is about standardizing IP address address\/prefix \u00b3types'. Each \u00b3type' has a certain behavior that the network is expected to provide. Section 3.1, of draft-ietf-dmm-ondemand-mobility-13 defines the following four address types, which are applicable to both IPv4 and IPv6 addresses and prefixes. #a. Fixed IP Address #b. Session-lasting IP Address #c. Non-persistent IP Address #d. Graceful Replacement IP Address These modes, #a, #b, #c,and #d can be mapped to the 3GPP SSC modes 1, 2 and 3. We are happy to report that this work-item is on track to become an \u00b3informational standard', and will m","secretary_remarks":"Response to S2-179625. Response drafted in S2-182064. Final response in S2-182967","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14110,"status":"replied to","reservation_date":"2018-02-05 14:17:42","uploaded":"2018-02-05 15:20:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"LS_from_IETF_DMM","lsreply":"S2-182967","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181481.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181493","title":"SMF behaviour based on LADN notification","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"CR","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 Handover procedures.","secretary_remarks":"Revision of part endorsed DraftCR S2-180546. Revised to S2-182695.","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-02-06 06:41:34","uploaded":"2018-02-09 03:11:39","revisionof":"S2-180546","revisedto":"S2-182695","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":13.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181493.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181494","title":"Clarification on Internal Event Exposure","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification on which procedure may trigger the mobility event notification.","secretary_remarks":"Revision of endorsed DraftCR S2-181116. 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":13830,"status":"agreed","reservation_date":"2018-02-06 06:41:35","uploaded":"2018-02-09 03:11:39","revisionof":"S2-181116","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":14.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180101","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181494.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181507","title":"Remaining IP address\/prefix lifetime with SSC mode 3","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","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":"Revision of approved DraftCR S2-180372. Revised to S2-182696.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13840,"status":"revised","reservation_date":"2018-02-06 18:04:56","uploaded":"2018-02-20 14:24:03","revisionof":"S2-180372","revisedto":"S2-182696","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":18.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181507.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181510","title":"Clarification on mobility event subscription transfer","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the new AMF may decide not to notify current status when the new AMF knows the event is reported by the old AMF","secretary_remarks":"Revision of approved DraftCR S2-181276. Merged into S2-182820.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13860,"status":"merged","reservation_date":"2018-02-06 23:30:56","uploaded":"2018-02-13 23:13:07","revisionof":"S2-181276","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":19.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181510.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181522","title":"Simplify the LADN PDU Session handling","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The PDU Session Establishment procedure and UE triggered Service Request procedure are updated to clarify that LADN PDU Session handling is performed after the onging system procedure.","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":14540,"status":"not treated","reservation_date":"2018-02-08 05:11:45","uploaded":"2018-02-09 03:11:39","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":31.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181522.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181533","title":"Wildcard DNN subscription","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Subscription Information may include a wildcard DNN per subscribed S-NSSAI: when a wildcard DNN is associated with a subscribed S-NSSAI, the UE is allowed to request access to any DNN value associated within the scope of this S-NSSAI.","secretary_remarks":"Revised to S2-182710.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14300,"status":"revised","reservation_date":"2018-02-08 15:23:28","uploaded":"2018-02-17 09:37:46","revisionof":"","revisedto":"S2-182710","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":21.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181533.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181535","title":"Clarification in LADN clause 5.6.5 - TS 23.501","source":"Nokia, Nokia Shanghai Bell, Samsung, Ericsson?","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Principles of the changes : - How UE is aware\/configured that a DNN is a LADN DNN is out of scope of rel-15 (as agreed in Gothenburg) - AMF not serving a LADN serving area does not need to be configured with LADN information for that DNN (as agreed in Gothenburg) - AMF serving a LADN service area is configured with LADN information and provides this information to the UE (per existing specification)  - A UE not receiving any LADN information from the AMF for a subscribed LADN DNN configured in the UE (e.g. because that AMF is not configured with LADN information for a DNN) shall assume that it is outside of the LADN service area for such DNN - SMF has a configuration whether a DNN is a LADN DNN or not (this can e.g. be part of the regular DNN configuration in SMF) - When SMF subscribes to 'UE presence in area of interest' for a LADN DNN, and the AMF is not configured with any LADN information for that DNN, the AMF shall reply to the SMF that it has no information abo","secretary_remarks":"Revision of noted DRAFTCR S2-181111. Confirm sources. No CR number. Revised off-line to S2-182814.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14420,"status":"revised","reservation_date":"2018-02-09 18:29:31","uploaded":"2018-02-18 18:18:42","revisionof":"S2-181111","revisedto":"S2-182814","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":22.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181535.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181547","title":"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":"CR","for":"Approval","abstract":"Summary of change: Provide the release timer to the UE by transparent means.","secretary_remarks":"Revision of approved DRAFTCR S2-181278. 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":13870,"status":"agreed","reservation_date":"2018-02-12 12:31:05","uploaded":"2018-02-12 14:00:24","revisionof":"S2-181278","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":40.0,"crrevision":"","crcategory":"C","tsg_crp":"SP-180095","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181547.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181548","title":"Generalize exposure of Mobility Events from AMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Generalize 'Exposure of Mobility Events from AMF' to cover both LADN and other cases.","secretary_remarks":"Revision of approved DRAFTCR S2-181107. Revised to S2-182697.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13880,"status":"revised","reservation_date":"2018-02-12 12:31:11","uploaded":"2018-02-12 14:00:24","revisionof":"S2-181107","revisedto":"S2-182697","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":41.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181548.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181549","title":"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":"CR","for":"Approval","abstract":"Summary of change: Clarify that for 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 approved DRAFTCR S2-181108. Revised to S2-182698.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13900,"status":"revised","reservation_date":"2018-02-12 12:31:12","uploaded":"2018-02-12 14:00:24","revisionof":"S2-181108","revisedto":"S2-182698","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":42.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181549.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181550","title":"Correction on AF influence on traffic routing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","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":"Revision of endorsed DRAFTCR S2-180265. 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":13930,"status":"agreed","reservation_date":"2018-02-12 12:31:13","uploaded":"2018-02-12 14:00:24","revisionof":"S2-180265","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":43.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180102","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181550.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181551","title":"Correction to RAN Initiated QoS Flow Mobility Procedure for Dual Connectivity","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The N11 messages in clause 4.14.1 are replaced with service operations.","secretary_remarks":"Revision of approved DRAFTCR S2-181169. 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":13940,"status":"agreed","reservation_date":"2018-02-12 12:31:14","uploaded":"2018-02-12 14:00:24","revisionof":"S2-181169","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":44.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180102","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181551.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181552","title":"Update on Traffic Detection Information","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","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 approved DRAFTCR S2-181170. 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":13950,"status":"agreed","reservation_date":"2018-02-12 12:31:14","uploaded":"2018-02-12 14:00:24","revisionof":"S2-181170","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":26.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181552.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181553","title":"Proposal of Specifying Packet Detection Rule","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Proposed detailed descriptions of Packet Detection Rule.","secretary_remarks":"Revision of endorsed DRAFTCR S2-180603. 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":13960,"status":"agreed","reservation_date":"2018-02-12 12:31:15","uploaded":"2018-02-12 14:00:24","revisionof":"S2-180603","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":27.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181553.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181554","title":"Relation between the SSC mode the PDU type","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In this release, SSC mode 3 only apply to IP PDU type.","secretary_remarks":"Revision of approved DRAFTCR S2-180490. Revised to S2-182699.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13970,"status":"revised","reservation_date":"2018-02-12 12:31:16","uploaded":"2018-02-12 14:00:24","revisionof":"S2-180490","revisedto":"S2-182699","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":28.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181554.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181582","title":"Correction to AF influence on traffic routing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This paper proposes to use AF transaction ID for the AF to correlate AF request and SMF notification.","secretary_remarks":"Revision of approved DRAFTCR S2-181168. Revised to S2-182700.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13990,"status":"revised","reservation_date":"2018-02-12 15:15:39","uploaded":"2018-02-12 15:35:23","revisionof":"S2-181168","revisedto":"S2-182700","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":37.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181582.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181583","title":"Clarifications to AF influence on traffic routing","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This paper cleans up the notes and corrects wordings for consistency and clarification.","secretary_remarks":"Revision of endorsed DRAFTCR S2-181167. 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":14010,"status":"agreed","reservation_date":"2018-02-12 15:15:40","uploaded":"2018-02-12 15:35:23","revisionof":"S2-181167","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":38.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181583.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181610","title":"Corrections to UPF selection and resolution of related Editor's Note","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","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 approved DRAFTCR S2-181397. 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":14020,"status":"agreed","reservation_date":"2018-02-13 13:18:46","uploaded":"2018-02-20 01:46:36","revisionof":"S2-181397","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":44.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181610.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181638","title":"Application Trigger procedure updates","source":"Ericsson, Convida Wireless LLC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The usage of Nudm_SDM_Get operation is described including new Subscription Data type: 'Identifier translation'. This new Subscription Data type requires GPSI as key, instead of SUPI. Nnef_Trigger service operation names are updated to reflect better the functionality performed.","secretary_remarks":"Revision of approved DRAFTCR S2-181357. Revised to S2-182701.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14030,"status":"revised","reservation_date":"2018-02-13 15:24:47","uploaded":"2018-02-20 01:46:36","revisionof":"S2-181357","revisedto":"S2-182701","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":78.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181638.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181659","title":"Discussion - Roaming support for LADN","source":"Samsung, Qualcomm Incorporated","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discusses the roaming support for LADN.","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":14400,"status":"not treated","reservation_date":"2018-02-14 07:53:39","uploaded":"2018-02-20 08:48: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_126_Montreal\/Docs\/S2-181659.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181667","title":"Operation type in Nsmf_PDUSession_UpdateSMContext Request","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","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":"Revised to S2-182810.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14920,"status":"revised","reservation_date":"2018-02-14 09:27:57","uploaded":"2018-02-20 09:46:50","revisionof":"","revisedto":"S2-182810","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":87.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181667.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181668","title":"Corrections of PDU session establishment procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","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) Change the service name in step 3 and 5 of the Figure 4.3.2.2.1-1. (3) Replace 'Access Technology Type' into 'Access Type' in step1. (4) Add 'or switching between 3GPP access and non-3GPP access' in step 2. (5) Change 'For' into 'for 'in 'Subscription For PDU Session Status Notification' in step 3, and 'then' to 'that' in step 3. (6) Correct wrong step number (step 19->step 20) in step 6.  (7) Add 'as described in TS 23.501 [2] clause 6.3.7' in discrption of step 7a. (8) Remove the overlap step number mark 9. (9) Move the step 'First Downlink Data' after step 16b.","secretary_remarks":"Revised to S2-182808.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14880,"status":"revised","reservation_date":"2018-02-14 09:27:58","uploaded":"2018-02-20 09:46:50","revisionof":"","revisedto":"S2-182808","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":88.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181668.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181669","title":"Correction on Secondary authorization or authentication procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","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":"Revised to S2-182807.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14850,"status":"revised","reservation_date":"2018-02-14 09:27:59","uploaded":"2018-02-20 09:46:50","revisionof":"","revisedto":"S2-182807","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":89.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181669.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181670","title":"N4 reporting for PDU Session Inactivity","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","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":"Revised to S2-182802.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14710,"status":"revised","reservation_date":"2018-02-14 09:28:00","uploaded":"2018-02-20 09:46:50","revisionof":"","revisedto":"S2-182802","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":90.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181670.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181671","title":"Update PDU Session Modification procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add step 1e in 4.3.3.3 PDU Session Modification for home-routed roaming.","secretary_remarks":"Revised to S2-182809.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14900,"status":"revised","reservation_date":"2018-02-14 09:28:01","uploaded":"2018-02-20 09:46:50","revisionof":"","revisedto":"S2-182809","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":91.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181671.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181672","title":"Correction on DNN management","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: (1) The DNN is removed when the PDU Session is released. (2) The DNN is stored in the PDU Session level context of the AMF. (3) The DNN is transmitted from one AMF to another AMF during AMF relocation as part of the PDU Session information.","secretary_remarks":"Revised to S2-182712.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14380,"status":"revised","reservation_date":"2018-02-14 09:28:02","uploaded":"2018-02-20 09:46:50","revisionof":"","revisedto":"S2-182712","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":92.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181672.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181673","title":"Correction to CN-initiated selective deactivation of UP connection of an existing PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the following new case that will trigger SMF to deactive a PDU session: \u00fc A PDU session is failed to setup due to no response from the SMF within maximum wait time during handover procedure in clause 4.9.1. For the new case and all QoS flows of a PDU session are rejected by the NG-RAN, add the description that the SMF should not invokes Namf_Communication_N1N2MessageTransfer service operation to release the NG-RAN resources associated with the PDU session with NG-RAN and UE.","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":14870,"status":"not treated","reservation_date":"2018-02-14 09:28:03","uploaded":"2018-02-20 09:46:50","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":93.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181673.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181680","title":"SSC mode of the additional PSA in an IPv6 multi-homed PDU Session","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to add a reference to the IETF draft draft-feng-dmm-ra-prefixtype-01 that allows for providing IP address property meta-data in the Router Advertisement message according to the meanings in the IETF draft draft-ietf-dmm-ondemand-mobility-13.","secretary_remarks":"Revised to S2-182704.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14120,"status":"revised","reservation_date":"2018-02-14 17:46:45","uploaded":"2018-02-20 14:24:03","revisionof":"","revisedto":"S2-182704","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":69.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181680.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181681","title":"SSC mode of the additional PSA in an IPv6 multi-homed PDU Session","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to add a reference to the IETF draft draft-feng-dmm-ra-prefixtype-01 that allows for providing IP address property meta-data in the Router Advertisement message according to the meanings in the IETF draft draft-ietf-dmm-ondemand-mobility-13.","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":14140,"status":"not treated","reservation_date":"2018-02-14 17:48:34","uploaded":"2018-02-20 14:24:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":95.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181681.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181704","title":"Selection mode transfer over N11 and N16 (wildcard DNN)","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Selection Mode is transferred from AMF to SMF (H-SMF via V-SMF). Typo (operation name ContextRequest) in \u00a7 5.2.8.2.10 + 5.2.8.1","secretary_remarks":"Revised to S2-182711.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14340,"status":"revised","reservation_date":"2018-02-15 16:52:50","uploaded":"2018-02-17 09:37:46","revisionof":"","revisedto":"S2-182711","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":105.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181704.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181706","title":"Correcting the support of charging Characteristics","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UDM\/UDR provides Charging Charactistics to SMF. How it is used is defined in SA WG5 specifications .","secretary_remarks":"Revised to S2-182797.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14600,"status":"revised","reservation_date":"2018-02-15 16:52:53","uploaded":"2018-02-17 09:37:46","revisionof":"","revisedto":"S2-182797","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":107.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181706.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181716","title":"Correcting the support of charging Characteristics","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UDM\/UDR provides Charging Charactistics to SMF. How it is used is specified in SA WG5 specifications","secretary_remarks":"Wrong CR number!. Revised to S2-182798.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14620,"status":"revised","reservation_date":"2018-02-16 09:01:52","uploaded":"2018-02-17 09:37:46","revisionof":"","revisedto":"S2-182798","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":75.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181716.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181823","title":"Roaming support for LADN","source":"Samsung, Qualcomm Incorporated","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to add two sentences in clause 5.6.5 as follows: - In this release, LADN is supported only for non-roaming scenario. - The AMF does not provide the LADN Information to the roaming UE.","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":14470,"status":"not treated","reservation_date":"2018-02-19 06:42:46","uploaded":"2018-02-20 08:48:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":100.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181823.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181825","title":"Clarification on Location reporting procedures","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the AMF may provide mulitple areas of interest to NG-RAN. The NG-RAN only report once location information when it detects the UE has move out of or into multiple areas of interest. The AMF may cancel the area of interest location report in NG-RAN.","secretary_remarks":"Revised to S2-182799.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14640,"status":"revised","reservation_date":"2018-02-19 08:04:59","uploaded":"2018-02-19 08:11:28","revisionof":"","revisedto":"S2-182799","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":138.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181825.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181848","title":"LADN Signaling to SMF","source":"Sony, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Ericsson","contact":"Svante Aln\u00e5s","contact-id":62551,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In the signaling from AMF to SMF, include sufficient information to SMF regarding LADN so that SMF are able to process the request directly","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":14520,"status":"not treated","reservation_date":"2018-02-19 10:05:06","uploaded":"2018-02-20 14:36:15","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":150.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181848.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181850","title":"Corrections to SMF selection","source":"Telecom Italia, ZTE, Oracle, NTT DOCOMO, Vodafone, Orange, Huawei, Ericsson, Deutsche Telekom","contact":"Mario Madella","contact-id":23765,"tdoctype":"CR","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. - 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. - 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 (NRF is no more NSSF consumer). - Minor editorial changes","secretary_remarks":"Revision of endorsed DRAFTCR S2-181277. 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":14050,"status":"agreed","reservation_date":"2018-02-19 10:31:57","uploaded":"2018-02-19 11:31:11","revisionof":"S2-181277","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":152.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181850.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181855","title":"UE support for Multi-homed IPv6 PDU Session","source":"Intel, Qualcomm Inc., MediaTek Inc.","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to to clarify that UE's support for Multi-homed IPv6 PDU Session is indicated to the network as part of its 5G Session Management capability.","secretary_remarks":"Revised to S2-182800.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14670,"status":"revised","reservation_date":"2018-02-19 10:50:10","uploaded":"2018-02-20 14:24:03","revisionof":"","revisedto":"S2-182800","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":105.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181855.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181856","title":"UE support for Multi-homed IPv6 PDU Session","source":"Intel, Qualcomm Inc., MediaTek Inc.","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to to clarify that UE's support for Multi-homed IPv6 PDU Session is indicated to the network as part of its 5G Session Management capability.","secretary_remarks":"Revised to S2-182801.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14690,"status":"revised","reservation_date":"2018-02-19 10:51:44","uploaded":"2018-02-20 14:24:03","revisionof":"","revisedto":"S2-182801","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":153.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181856.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181859","title":"Adding the missing GPSI parameter in SMF","source":"Sony","contact":"Svante Aln\u00e5s","contact-id":62551,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the missing parameter in the SMF's service interface.","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":14940,"status":"agreed","reservation_date":"2018-02-19 12:37:30","uploaded":"2018-02-20 14:36:15","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":154.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181859.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181870","title":"Transparent relay between V-SMF and H-SMF in case of different feature support","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - The V-SMF transfers NAS SM information which it does not comprehend (unknown IEs or IEs with an unknown value not set to 'reserved' according to the release to which the V-SMF complies), in a separate container over N16 towards the H-SMF. - The H-SMF transfers NAS SM information which the V-SMF does not need to interpret, in one container over N16 towards the V-SMF;  - The V-SMF appends unknown NAS SM information received in the N16 container at the end of the NAS SM message it sends to the UE","secretary_remarks":"Revised to S2-182706.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14200,"status":"revised","reservation_date":"2018-02-19 12:53:29","uploaded":"2018-02-20 13:34:04","revisionof":"","revisedto":"S2-182706","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":155.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181870.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181983","title":"Corrections to LADN configuration and signalling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Principles of the changes: - How UE is aware that a DNN is a LADN DNN is out of scope of rel-15 (as agreed in Gothenburg) - AMF not serving a LADN serving area does not need to be configured with LADN information for that DNN (as agreed in Gothenburg) - AMF serving a LADN service area is configured with LADN information and provides this information to the UE (per existing specification)  - A UE not receiving any LADN information from the AMF (e.g. because that AMF is not configured with LADN information for a DNN) shall assume that it is outside of the LADN service area - SMF has a configuration whether a DNN is a LADN DNN or not (this can be part of the regular DNN configuration in SMF) - When SMF subscribes to 'UE presence in area of interest' for a LADN DNN, and the AMF is not configured with any LADN information for that DNN, the AMF shall reply to the SMF that it has no information about the LADN area. The SMF shall then assume that the UE is OUTSIDE the LADN s","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":14480,"status":"not treated","reservation_date":"2018-02-19 17:38:06","uploaded":"2018-02-20 14:21:32","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":123.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181983.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181989","title":"Correction of UDR usage in SM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The flows that UDM may invoke UDR services in session related procedures are clarified.","secretary_remarks":"Revision of revised DRAFTCR S2-181272 (S2-181397 was approved). Revised to S2-182703.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14080,"status":"revised","reservation_date":"2018-02-19 17:42:18","uploaded":"2018-02-20 14:54:51","revisionof":"S2-181272","revisedto":"S2-182703","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":175.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181989.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182029","title":"Discussion on IMS P-CSCF Discovery in 5GC","source":"T-Mobile USA INC","contact":"Christopher Joul","contact-id":31136,"tdoctype":"discussion","for":"Discussion","abstract":"Discusses the IP-CAN based discovery of P-CSCF in relation to 5GC with comparison to the similar method for GPRS\/EPS.","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":14790,"status":"not treated","reservation_date":"2018-02-19 23:33:03","uploaded":"2018-02-20 07:40:19","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182029.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182030","title":"P--CSCF Discovery for IMS in 5GC using IP-CAN method","source":"T-Mobile USA, Nokia, Nokia Shanghai Bell","contact":"Christopher Joul","contact-id":31136,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update text under the diagram for PDU Session Establishment method for 'non roaming and local breakout' (4.3.2.2.1), such that, if the UE requests a PDU Session for IMS, the UE can indicate it is requesting a P-CSCF IP address (or addresses), and that this request is transparently passed to the SMF, and that the SMF includes the address in the response. There is no need to make any changes to 'home routed roaming'(4.3.2.2.2) as this references the changed steps in the non roaming procedure (4.3.2.2.1). Whether the indicator is passed via Extended PCO defined in TS 24.501 or a separated parameter is under stage 3 responsibility.","secretary_remarks":"Revised to S2-182805.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14800,"status":"revised","reservation_date":"2018-02-19 23:36:31","uploaded":"2018-02-20 07:40:19","revisionof":"","revisedto":"S2-182805","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":189.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182030.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182061","title":"Address missing information to enable direct notification from SMF to AF in AF influence procedure","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description in clause 4.3.6.2 to say that PCF needs to tell SMF about the IP address and port of AF Control Plane which the SMF shall use to send direct notification to AF.","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":14550,"status":"noted","reservation_date":"2018-02-20 03:08:43","uploaded":"2018-02-20 03:56:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":196.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182061.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182062","title":"LADN Clarification - 23.501","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the LADN support only applies to non-roaming and LBO roaming scenarios. Remove the text describing configuration of LADN Information in AMF and when\/how AMF sends the LADN Information to UE in order to make LADN support transparent to AMF. Add description on configuring LADN Information in SMF and how SMF responds to UE when the SMF receives the PDU Session Establishment Request and what additional information needs to be included in the NAS SM response message. Address how the UE knows whether a DNN is LADN DNN based on the discussion and endorsed paper S2-181358. Replace 'shall' with 'may'. Align the terms with 23.502 to 'UE presence in LADN service area'. Remove the redudant description for SMF behavior when the UE presence in a LADN is IN or UNKNOWN. Merge changes from Huawei paper S2-180288 on SMF behavior.","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":14500,"status":"not treated","reservation_date":"2018-02-20 03:08:44","uploaded":"2018-02-20 03:56:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":139.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182062.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182063","title":"LADN Clarification - 23.502","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the SMF behavior on rejecting the request when UE's presence in a LADN is OUT for the procedure of General Registration and UE Requested PDU Session Modification procedure. The SMF includes the LADN service area information in the PDU Session Establishment Response and PDU Session Reject message. Editorial change in clause 4.2.3.2.","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":14530,"status":"not treated","reservation_date":"2018-02-20 03:08:45","uploaded":"2018-02-20 03:56:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":197.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182063.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182064","title":"[DRAFT] LS on indicating service continuity usage of the additional IPv6 prefix in Router Advertisement","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"LS out","for":"Approval","abstract":"Response to (email sent on: Fri, 2 Feb 2018 22:24:17) \/ S2-181481","secretary_remarks":"Response to S2-181481. Revised to S2-182705.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14150,"status":"revised","reservation_date":"2018-02-20 03:08:46","uploaded":"2018-02-20 03:56:02","revisionof":"","revisedto":"S2-182705","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IETF Internet Area, DMM, 6MAN","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182064.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182091","title":"Alignment CR for Application Function influence on traffic routing procedure","source":"ETRI","contact":"Soo Hwan Lee","contact-id":69517,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: First change: In the procedure for AF influence on traffic routing, the AF and the PCF interactions in step 2 and 3, and the PCF and SMF interactions in step 5 refer to the step 1b and 2b, and the step 5 and 6 of Session Management Policy Modification, respectively.  Second change: In Session Management Policy Modification, Npcf_PolicyAuthorization_Create\/Update service operation is proposed for the step 1b and 2b in order to align with the procedure of AF influence on traffic routing   Third chage:  In the step 1b of PDU Session Modification, it is clarified that AF influence on traffic routing can be a triggering condition by referring to the PCF and the SMF interaction in the procedure of AF infleunce on traffic routing. In the last step (i.e., step 12), it is added that UP reconfiguration may be occurred by the consecutive step of AF influence on traffic routing procedure (i.e., step 6 in clause 4.3.6.2).","secretary_remarks":"Revised to S2-182795.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14560,"status":"revised","reservation_date":"2018-02-20 04:32:47","uploaded":"2018-02-20 07:43:01","revisionof":"","revisedto":"S2-182795","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":205.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182091.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182093","title":"PDU session ID in PDU session management procedure","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","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.","secretary_remarks":"Revision of endorsed DRAFTCR S2-180539. Revised to S2-182702.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14060,"status":"revised","reservation_date":"2018-02-20 04:40:16","uploaded":"2018-02-20 05:03:01","revisionof":"S2-180539","revisedto":"S2-182702","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":206.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182093.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182104","title":"Updates to AF influence on traffic routing","source":"Samsung","contact":"Jayshree Bharatia","contact-id":63826,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This paper makes the following two changes: 1. Corrects statement in first paragraph for AF belonging to the 3rd party. Existing statement is not readable. 2. Provides editorial updates to statement for better readability","secretary_remarks":"Revised to S2-182796.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14580,"status":"revised","reservation_date":"2018-02-20 05:32:45","uploaded":"2018-02-20 05:45:32","revisionof":"","revisedto":"S2-182796","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":150.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182104.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182106","title":"Updates to description of CN Tunnel Info","source":"Samsung","contact":"Jayshree Bharatia","contact-id":63826,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Existing description of CN Tunnel Info does not include modification of CN Tunnel Info attribute when it is allocated either by SMF or UPF. This paper updates existing text to include these details.","secretary_remarks":"Revised to S2-182812.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14970,"status":"revised","reservation_date":"2018-02-20 05:38:00","uploaded":"2018-02-20 05:45:51","revisionof":"","revisedto":"S2-182812","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":151.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182106.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182172","title":"Re-activation of PDU sessions based on UE policy","source":"Vivo","contact":"RAN YUE","contact-id":69629,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Upon reception of notification message, the UE shall initiate a service request procedure over 3GPP access if allowed by UE policy.","secretary_remarks":"This was withdrawn.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":15050,"status":"withdrawn","reservation_date":"2018-02-20 09:17:16","uploaded":"2018-02-20 09:39:47","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":164.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182172.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182187","title":"N4 user plane path","source":"Huawei","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that N4-u user plane tunnel is used for packet forwarding between UPF and SMF.","secretary_remarks":"Revised to S2-182804.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14760,"status":"revised","reservation_date":"2018-02-20 09:30:13","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"S2-182804","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":171.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182187.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182188","title":"Proposal of Sequence Number Marking in the User Plane Packet","source":"Huawei, HiSilicon, SK Telecom","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"discussion","for":"Discussion","abstract":"It is proposed to mark 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":15000,"status":"not treated","reservation_date":"2018-02-20 09:30:14","uploaded":"2018-02-20 14:52:59","revisionof":"","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_126_Montreal\/Docs\/S2-182188.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182189","title":"Proposal of Sequence Number Marking in the User Plane Function","source":"Huawei, HiSilicon, SK Telecom","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Propose to achieve sequence number marking on user plane packet.","secretary_remarks":"Withdrawn in parallel session.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":15010,"status":"withdrawn","reservation_date":"2018-02-20 09:30:14","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":172.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182189.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182190","title":"SSC Mode Selection","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Instead of modifying the Reqeusted SSC mode, the SMF rejects the PDU Session establishement request with information on the SSC modes suggested. The UE can use one of these SSC modes or select another URSP rule, if present.","secretary_remarks":"Revised to S2-182811.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14950,"status":"revised","reservation_date":"2018-02-20 09:30:15","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"S2-182811","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":173.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182190.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182191","title":"Proposal of QER, URR and FAR","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The same parameters as described in the CUPS specification TS 23.214 are proposed for the QER, URR and FAR of the UPF. Terminology is aligned and parameters that are not needed in 5GS are proposed to be removed.","secretary_remarks":"Revised to S2-182803.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14730,"status":"revised","reservation_date":"2018-02-20 09:30:16","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"S2-182803","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":174.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182191.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182225","title":"Addition of PDU Session Type IPv4v6","source":"NTT DOCOMO","contact":"Atsushi Minokuchi","contact-id":26474,"tdoctype":"discussion","for":"Agreement","abstract":"This document highlights a case where lack of support of the dual-stack PDU type IPv4v6 causes an issue. It is proposed that SA WG2 consider and solve this issue either in Rel-15 or Rel-16, preferably in Rel-15.","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":14230,"status":"not treated","reservation_date":"2018-02-20 10:45:48","uploaded":"2018-02-20 11:22:26","revisionof":"","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_126_Montreal\/Docs\/S2-182225.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182226","title":"Addition of PDU Session type IPv4v6","source":"NTT DOCOMO, KDDI, Deutsche Telekom, Nokia, Vodafone, Telecom Italia, AT&T, ZTE, NEC, Cisco, LG Electronics, Telstra","contact":"Atsushi Minokuchi","contact-id":26474,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add PDU Session type IPv4v6. Add clarification on setting a different PDU type for the second PDU session to the same DNN Add a text on V-SMF's behavior for the home routed case.","secretary_remarks":"Revised to S2-182707.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14240,"status":"revised","reservation_date":"2018-02-20 10:48:33","uploaded":"2018-02-20 11:22:26","revisionof":"","revisedto":"S2-182707","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":181.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182226.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182227","title":"Addition of PDU Session type IPv4v6","source":"NTT DOCOMO, KDDI, Deutsche Telekom, Nokia, Vodafone, Telecom Italia, AT&T, ZTE, NEC, Cisco, LG Electronics, Telstra","contact":"Atsushi Minokuchi","contact-id":26474,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add PDU Session type IPv4v6","secretary_remarks":"Revised to S2-182708.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14260,"status":"revised","reservation_date":"2018-02-20 10:50:41","uploaded":"2018-02-20 11:22:26","revisionof":"","revisedto":"S2-182708","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":229.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182227.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182228","title":"Addition of PDU Session type IPv4v6","source":"NTT DOCOMO, KDDI, Deutsche Telekom, Nokia, Vodafone, Telecom Italia, AT&T, ZTE, NEC, Cisco, LG Electronics, Telstra","contact":"Atsushi Minokuchi","contact-id":26474,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add PDU Session type IPv4v6","secretary_remarks":"Revised to S2-182709.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14280,"status":"revised","reservation_date":"2018-02-20 10:53:24","uploaded":"2018-02-20 11:22:26","revisionof":"","revisedto":"S2-182709","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":36.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182228.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182275","title":"Discussion on aspects for LADN","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"discussion","for":"Discussion","abstract":"This conttribution describes several aspects related to LADN, starting from the requirements that led to the development of the LADN feature.","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":14410,"status":"not treated","reservation_date":"2018-02-20 14:44:01","uploaded":"2018-02-20 14:52:59","revisionof":"","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_126_Montreal\/Docs\/S2-182275.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182276","title":"Correction on aspects for LADN","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. The information whether a DNN is an LADN DNN is configured in the SMF. 2. Remove the subscription information from the UDM. 3. Add a mechanism how the AMF notifies the UE LADN service area.  4. Add an NOTE that any optimization is not needed for the scenario the UE is out of LADN service area. 5. Editorial modifications.","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":14510,"status":"not treated","reservation_date":"2018-02-20 14:44:01","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":190.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182276.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182286","title":"Discussion on LADN options","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"discussion","for":"Approval","abstract":"The contribution discusses options for LADN.","secretary_remarks":"LATE DOC: Rx 23\/02, 17:50. Not Handled","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14490,"status":"not treated","reservation_date":"2018-02-23 17:44:34","uploaded":"2018-02-23 17:45:08","revisionof":"","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_126_Montreal\/Docs\/S2-182286.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182693","title":"Corrections to PDU session establishment \/ modification procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","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-181454. Revised to S2-182841.","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-02-27 14:37:46","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181454","revisedto":"S2-182841","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182693.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182694","title":"Using NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","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 usinf NRF to get info on other NF) 3. Update NRF service operations with UPF rlated information such as UPF Discovery Information","secretary_remarks":"Revision of S2-181457. Revised to S2-182969.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13790,"status":"revised","reservation_date":"2018-02-27 14:37:47","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181457","revisedto":"S2-182969","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":5.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182694.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182695","title":"SMF behaviour based on LADN notification","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"CR","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 Handover procedures.","secretary_remarks":"Revision of S2-181493. 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":13820,"status":"agreed","reservation_date":"2018-02-27 14:37:49","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181493","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":13.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180101","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182695.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182696","title":"Remaining IP address\/prefix lifetime with SSC mode 3","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","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":"Revision of S2-181507. 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":13850,"status":"agreed","reservation_date":"2018-02-27 14:37:50","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181507","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":18.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182696.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182697","title":"Generalize exposure of Mobility Events from AMF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","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-181548. 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":13890,"status":"agreed","reservation_date":"2018-02-27 14:37:51","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181548","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":41.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180102","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182697.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182698","title":"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":"CR","for":"Approval","abstract":"Summary of change: Clarify that for 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-181549. Revised to S2-182851.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13910,"status":"revised","reservation_date":"2018-02-27 14:37:52","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181549","revisedto":"S2-182851","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":42.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182698.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182699","title":"Relation between the SSC mode 3 and the PDU type","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In this release, SSC mode 3 only apply to IP PDU type.","secretary_remarks":"Revision of S2-181554. 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":13980,"status":"agreed","reservation_date":"2018-02-27 14:37:53","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181554","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":28.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182699.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182700","title":"Correction to AF influence on traffic routing","source":"Huawei, HiSillicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This paper proposes to use AF transaction ID for the AF to correlate AF request and SMF notification.","secretary_remarks":"Revision of S2-181582. 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":14000,"status":"agreed","reservation_date":"2018-02-27 14:37:55","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181582","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":37.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182700.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182701","title":"Application Trigger procedure updates","source":"Ericsson, Convida Wireless LLC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The usage of Nudm_SDM_Get operation is described including new Subscription Data type: 'Identifier translation'. This new Subscription Data type requires GPSI as key, instead of SUPI. Nnef_Trigger service operation names are updated to reflect better the functionality performed.","secretary_remarks":"Revision of S2-181638. 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":14040,"status":"agreed","reservation_date":"2018-02-27 14:37:56","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181638","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":78.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180103","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182701.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182702","title":"PDU session ID in PDU session management procedure","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","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.","secretary_remarks":"Revision of S2-182093. 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":14070,"status":"agreed","reservation_date":"2018-02-27 14:37:57","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182093","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":206.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180106","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182702.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182703","title":"Correction of UDR usage in SM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The flows that UDM may invoke UDR services in session related procedures are clarified.","secretary_remarks":"Revision of S2-181989. Revised to S2-182842.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14090,"status":"revised","reservation_date":"2018-02-27 14:37:58","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181989","revisedto":"S2-182842","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":175.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182703.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182704","title":"SSC mode of the additional PSA in an IPv6 multi-homed PDU Session","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to add a reference to the IETF draft draft-feng-dmm-ra-prefixtype-01 that allows for providing IP address property meta-data in the Router Advertisement message according to the meanings in the IETF draft draft-ietf-dmm-ondemand-mobility-13.","secretary_remarks":"Revision of S2-181680. Withdrawn in parallel session.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14130,"status":"withdrawn","reservation_date":"2018-02-27 14:37:59","uploaded":null,"revisionof":"S2-181680","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":69.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182705","title":"[DRAFT] LS on indicating service continuity usage of the additional IPv6 prefix in Router Advertisement","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"LS out","for":"Approval","abstract":"Response to (email sent on: Fri, 2 Feb 2018 22:24:17) \/ S2-181481","secretary_remarks":"Revision of S2-182064. Revised to S2-182844.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14160,"status":"revised","reservation_date":"2018-02-27 14:38:00","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182064","revisedto":"S2-182844","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IETF Internet Area, DMM, 6MAN","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182705.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182706","title":"Transparent relay between V-SMF and H-SMF in case of different feature support","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - The V-SMF transfers NAS SM information which it does not comprehend (unknown IEs or IEs with an unknown value not set to 'reserved' according to the release to which the V-SMF complies), in a separate container over N16 towards the H-SMF. - The H-SMF transfers NAS SM information which the V-SMF does not need to interpret, in one container over N16 towards the V-SMF;  - The V-SMF appends unknown NAS SM information received in the N16 container at the end of the NAS SM message it sends to the UE","secretary_remarks":"Revision of S2-181870. Revised to S2-182843.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14210,"status":"revised","reservation_date":"2018-02-27 14:38:00","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181870","revisedto":"S2-182843","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":155.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182706.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182707","title":"Addition of PDU Session type IPv4v6","source":"NTT DOCOMO, KDDI, Deutsche Telekom, Nokia, Vodafone, Telecom Italia, AT&T, ZTE, NEC, Cisco, LG Electronics, Telstra, Verizon, ORANGE","contact":"Atsushi Minokuchi","contact-id":26474,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add PDU Session type IPv4v6. Add clarification on setting a different PDU type for the second PDU session to the same DNN Add a text on V-SMF's behavior for the home routed case.","secretary_remarks":"Revision of S2-182226. 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":14250,"status":"agreed","reservation_date":"2018-02-27 14:38:01","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182226","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":181.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-180125","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182707.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182708","title":"Addition of PDU Session type IPv4v6","source":"NTT DOCOMO, KDDI, Deutsche Telekom, Nokia, Vodafone, Telecom Italia, AT&T, ZTE, NEC, Cisco, LG Electronics, Telstra, Verizon, ORANGE","contact":"Atsushi Minokuchi","contact-id":26474,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add PDU Session type IPv4v6","secretary_remarks":"Revision of S2-182227. 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":14270,"status":"agreed","reservation_date":"2018-02-27 14:38:02","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182227","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":229.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-180125","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182708.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182709","title":"Addition of PDU Session type IPv4v6","source":"NTT DOCOMO, KDDI, Deutsche Telekom, Nokia, Vodafone, Telecom Italia, AT&T, ZTE, NEC, Cisco, LG Electronics, Telstra, Verizon, ORANGE","contact":"Atsushi Minokuchi","contact-id":26474,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add PDU Session type IPv4v6","secretary_remarks":"Revision of S2-182228. 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":14290,"status":"agreed","reservation_date":"2018-02-27 14:38:03","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182228","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":36.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-180125","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182709.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182710","title":"Wildcard DNN subscription","source":"Nokia, Nokia Shanghai Bell, Telecom Italia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Subscription Information may include a wildcard DNN per subscribed S-NSSAI: when a wildcard DNN is associated with a subscribed S-NSSAI, the UE is allowed to request access to any DNN value associated within the scope of this S-NSSAI.","secretary_remarks":"Revision of S2-181533. Revised to S2-182845.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14310,"status":"revised","reservation_date":"2018-02-28 02:03:25","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181533","revisedto":"S2-182845","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":21.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182710.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182711","title":"Selection mode transfer over N11 and N16 (wildcard DNN)","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Selection Mode is transferred from AMF to SMF (H-SMF via V-SMF). Typo (operation name ContextRequest) in \u00a7 5.2.8.2.10 + 5.2.8.1","secretary_remarks":"Revision of S2-181704. Revised to S2-182846.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14350,"status":"revised","reservation_date":"2018-02-28 02:03:26","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181704","revisedto":"S2-182846","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":105.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182711.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182712","title":"Correction on DNN management","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: (1) The DNN is removed when the PDU Session is released. (2) The DNN is stored in the PDU Session level context of the AMF. (3) The DNN is transmitted from one AMF to another AMF during AMF relocation as part of the PDU Session information.","secretary_remarks":"Revision of S2-181672. 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":14390,"status":"agreed","reservation_date":"2018-02-28 02:03:27","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181672","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":92.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180103","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182712.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182795","title":"Alignment CR for Application Function influence on traffic routing procedure","source":"ETRI","contact":"Soo Hwan Lee","contact-id":69517,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: First change: In the procedure for AF influence on traffic routing, the AF and the PCF interactions in step 2 and 3, and the PCF and SMF interactions in step 5 refer to the step 1b and 2b, and the step 5 and 6 of Session Management Policy Modification, respectively.  Second change: In Session Management Policy Modification, Npcf_PolicyAuthorization_Create\/Update service operation is proposed for the step 1b and 2b in order to align with the procedure of AF influence on traffic routing   Third chage:  In the step 1b of PDU Session Modification, it is clarified that AF influence on traffic routing can be a triggering condition by referring to the PCF and the SMF interaction in the procedure of AF infleunce on traffic routing. In the last step (i.e., step 12), it is added that UP reconfiguration may be occurred by the consecutive step of AF influence on traffic routing procedure (i.e., step 6 in clause 4.3.6.2).","secretary_remarks":"Revision of S2-182091. 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":14570,"status":"agreed","reservation_date":"2018-02-28 21:28:08","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182091","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":205.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180106","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182795.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182796","title":"Updates to AF influence on traffic routing","source":"Samsung","contact":"Jayshree Bharatia","contact-id":63826,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This paper makes the following two changes: 1. Corrects statement in first paragraph for AF belonging to the 3rd party. Existing statement is not readable. 2. Provides editorial updates to statement for better readability","secretary_remarks":"Revision of S2-182104. 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":14590,"status":"agreed","reservation_date":"2018-02-28 21:28:09","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182104","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":150.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180100","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182796.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182797","title":"Correcting the support of charging Characteristics","source":"Nokia, Nokia Shanghai Bell, Deutsch Telecom","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UDM\/UDR provides Charging Charactistics to SMF. How it is used is defined in SA WG5 specifications .","secretary_remarks":"Revision of S2-181706. 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":14610,"status":"agreed","reservation_date":"2018-02-28 21:28:10","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181706","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":107.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182797.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182798","title":"Correcting the support of charging Characteristics","source":"Nokia, Nokia Shanghai Bell, Deutsch Telekom","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UDM\/UDR provides Charging Charactistics to SMF. How it is used is specified in SA WG5 specifications","secretary_remarks":"Revision of S2-181716. 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":14630,"status":"agreed","reservation_date":"2018-02-28 21:28:11","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181716","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":75.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182798.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182799","title":"Clarification on Location reporting procedures","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the AMF may provide mulitple areas of interest to NG-RAN. The NG-RAN only report once location information when it detects the UE has move out of or into multiple areas of interest. The AMF may cancel the area of interest location report in NG-RAN.","secretary_remarks":"Revision of S2-181825. Revised to S2-182848.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14650,"status":"revised","reservation_date":"2018-03-01 18:39:13","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181825","revisedto":"S2-182848","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":138.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182799.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182800","title":"UE support for Multi-homed IPv6 PDU Session","source":"Intel, Qualcomm Inc., MediaTek Inc.","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to to clarify that UE's support for Multi-homed IPv6 PDU Session is indicated to the network as part of its 5G Session Management capability.","secretary_remarks":"Revision of S2-181855. 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":14680,"status":"agreed","reservation_date":"2018-03-01 18:39:14","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181855","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":105.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182800.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182801","title":"UE support for Multi-homed IPv6 PDU Session","source":"Intel, Qualcomm Inc., MediaTek Inc.","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to to clarify that UE's support for Multi-homed IPv6 PDU Session is indicated to the network as part of its 5G Session Management capability.","secretary_remarks":"Revision of S2-181856. 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":14700,"status":"agreed","reservation_date":"2018-03-01 18:39:15","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181856","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":153.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182801.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182802","title":"N4 reporting for PDU Session Inactivity","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","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":"Revision of S2-181670. 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":14720,"status":"agreed","reservation_date":"2018-03-01 18:39:16","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181670","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":90.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180103","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182802.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182803","title":"Proposal of QER, URR and FAR","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The same parameters as described in the CUPS specification TS 23.214 are proposed for the QER, URR and FAR of the UPF. Terminology is aligned and parameters that are not needed in 5GS are proposed to be removed.","secretary_remarks":"Revision of S2-182191. Revised to S2-182968.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14740,"status":"revised","reservation_date":"2018-03-01 18:39:17","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182191","revisedto":"S2-182968","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":174.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182803.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182804","title":"N4 user plane path","source":"Huawei","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that N4-u user plane tunnel is used for packet forwarding between UPF and SMF.","secretary_remarks":"Revision of S2-182187. Revised to S2-182849.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14770,"status":"revised","reservation_date":"2018-03-01 18:39:18","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182187","revisedto":"S2-182849","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":171.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182804.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182805","title":"P-CSCF Discovery for IMS in 5GC using IP-CAN method","source":"T-Mobile USA, Nokia, Nokia Shanghai Bell","contact":"Christopher Joul","contact-id":31136,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update text under the diagram for PDU Session Establishment method for 'non roaming and local breakout' (4.3.2.2.1), such that, if the UE requests a PDU Session for IMS, the UE can indicate it is requesting a P-CSCF IP address (or addresses), and that this request is transparently passed to the SMF, and that the SMF includes the address in the response. There is no need to make any changes to 'home routed roaming'(4.3.2.2.2) as this references the changed steps in the non roaming procedure (4.3.2.2.1). Whether the indicator is passed via Extended PCO defined in TS 24.501 or a separated parameter is under stage 3 responsibility.","secretary_remarks":"Revision of S2-182030. 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":14810,"status":"agreed","reservation_date":"2018-03-01 18:39:19","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182030","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":189.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180106","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182805.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182806","title":"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":"CR","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":"Revision of S2-181460. Revised to S2-182850.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14830,"status":"revised","reservation_date":"2018-03-01 18:39:20","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181460","revisedto":"S2-182850","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182806.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182807","title":"Correction on Secondary authorization\/authentication procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","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":"Revision of S2-181669. 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":14860,"status":"agreed","reservation_date":"2018-03-01 18:39:21","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181669","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":89.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180103","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182807.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182808","title":"Corrections of PDU session establishment procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","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) Change the service name in step 3 and 5 of the Figure 4.3.2.2.1-1. (3) Replace 'Access Technology Type' into 'Access Type' in step1. (4) Add 'or switching between 3GPP access and non-3GPP access' in step 2. (5) Change 'For' into 'for 'in 'Subscription For PDU Session Status Notification' in step 3, and 'then' to 'that' in step 3. (6) Correct wrong step number (step 19->step 20) in step 6.  (7) Add 'as described in TS 23.501 [2] clause 6.3.7' in discrption of step 7a. (8) Remove the overlap step number mark 9. (9) Move the step 'First Downlink Data' after step 16b.","secretary_remarks":"Revision of S2-181668. 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":14890,"status":"agreed","reservation_date":"2018-03-01 18:39:21","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181668","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":88.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180103","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182808.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182809","title":"Update PDU Session Modification procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add step 1e in 4.3.3.3 PDU Session Modification for home-routed roaming.","secretary_remarks":"Revision of S2-181671. 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":14910,"status":"agreed","reservation_date":"2018-03-01 18:39:22","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181671","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":91.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180103","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182809.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182810","title":"Operation type in Nsmf_PDUSession_UpdateSMContext Request","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","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":"Revision of S2-181667. 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":14930,"status":"agreed","reservation_date":"2018-03-01 18:39:23","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181667","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":87.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180103","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182810.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182811","title":"SSC Mode Selection","source":"Huawei, Hisilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Instead of modifying the Reqeusted SSC mode, the SMF rejects the PDU Session establishement request with information on the SSC modes suggested. The UE can use one of these SSC modes or select another URSP rule, if present.","secretary_remarks":"Revision of S2-182190. 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":14960,"status":"agreed","reservation_date":"2018-03-01 18:39:24","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182190","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":173.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180100","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182811.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182812","title":"Updates to description of CN Tunnel Info","source":"Samsung","contact":"Jayshree Bharatia","contact-id":63826,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Existing description of CN Tunnel Info does not include modification of CN Tunnel Info attribute when it is allocated either by SMF or UPF. This paper updates existing text to include these details.","secretary_remarks":"Revision of S2-182106. Revised to S2-182852.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14980,"status":"revised","reservation_date":"2018-03-01 18:39:25","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182106","revisedto":"S2-182852","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":151.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182812.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182813","title":"Using NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","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":"Revision of S2-181459. Revised to S2-182973.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":15030,"status":"revised","reservation_date":"2018-03-01 18:39:26","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181459","revisedto":"S2-182973","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182813.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182814","title":"Clarification in LADN clause 5.6.5 - TS 23.501","source":"Nokia, Nokia Shanghai Bell,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Principles of the changes : - How UE is aware\/configured that a DNN is a LADN DNN is out of scope of rel-15 (as agreed in Gothenburg) - AMF not serving a LADN serving area does not need to be configured with LADN information for that DNN (as agreed in Gothenburg) - AMF serving a LADN service area is configured with LADN information and provides this information to the UE (per existing specification)  - A UE not receiving any LADN information from the AMF for a subscribed LADN DNN configured in the UE (e.g. because that AMF is not configured with LADN information for a DNN) shall assume that it is outside of the LADN service area for such DNN - SMF has a configuration whether a DNN is a LADN DNN or not (this can e.g. be part of the regular DNN configuration in SMF) - When SMF subscribes to 'UE presence in area of interest' for a LADN DNN, and the AMF is not configured with any LADN information for that DNN, the AMF shall reply to the SMF that it has no information abo","secretary_remarks":"Revision of S2-181535. Revised to S2-182847.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14430,"status":"revised","reservation_date":"2018-03-01 18:39:27","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181535","revisedto":"S2-182847","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":22.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182814.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182841","title":"Corrections to PDU session establishment \/ modification procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","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-182693. 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":13770,"status":"agreed","reservation_date":"2018-03-01 18:39:52","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182693","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180101","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182841.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182842","title":"Correction of UDR usage in SM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The flows that UDM may invoke UDR services in session related procedures are clarified.","secretary_remarks":"Revision of S2-182703. 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":14100,"status":"agreed","reservation_date":"2018-03-01 18:39:53","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182703","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":175.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182842.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182843","title":"Transparent relay between V-SMF and H-SMF in case of different feature support","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - The V-SMF transfers NAS SM information which it does not comprehend (unknown IEs or IEs with an unknown value not set to 'reserved' according to the release to which the V-SMF complies), in a separate container over N16 towards the H-SMF. - The H-SMF transfers NAS SM information which the V-SMF does not need to interpret, in one container over N16 towards the V-SMF;  - The V-SMF appends unknown NAS SM information received in the N16 container at the end of the NAS SM message it sends to the UE","secretary_remarks":"Revision of S2-182706. 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":14220,"status":"agreed","reservation_date":"2018-03-01 18:39:54","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182706","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":155.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182843.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182844","title":"[DRAFT] LS on indicating service continuity usage of the additional IPv6 prefix in Router Advertisement","source":"SA WG2","contact":"Changhong Shan","contact-id":45586,"tdoctype":"LS out","for":"Approval","abstract":"To: IETF Internet Area, IETF DMM. CC: IETF 6MAN, CT WG1, TSG CT","secretary_remarks":"Revision of S2-182705. Revised to S2-182967.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14170,"status":"revised","reservation_date":"2018-03-01 18:39:55","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182705","revisedto":"S2-182967","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IETF Internet Area, IETF DMM","Cc":"IETF 6MAN, CT WG1, TSG CT","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182844.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182845","title":"Wildcard DNN subscription","source":"Nokia, Nokia Shanghai Bell, Telecom Italia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Subscription Information may include a wildcard DNN per subscribed S-NSSAI: when a wildcard DNN is associated with a subscribed S-NSSAI, the UE is allowed to request access to any DNN value associated within the scope of this S-NSSAI.","secretary_remarks":"Revision of S2-182710. Revised to S2-182853.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14320,"status":"revised","reservation_date":"2018-03-01 18:39:55","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182710","revisedto":"S2-182853","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":21.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182845.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182846","title":"Selection mode transfer over N11 and N16 (wildcard DNN)","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Selection Mode is transferred from AMF to SMF (H-SMF via V-SMF). Typo (operation name ContextRequest) in \u00a7 5.2.8.2.10 + 5.2.8.1","secretary_remarks":"Revision of S2-182711. Revised to S2-182970.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14360,"status":"revised","reservation_date":"2018-03-01 18:39:56","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182711","revisedto":"S2-182970","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":105.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182846.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182847","title":"Clarification in LADN clause 5.6.5 - TS 23.501","source":"Ericsson Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Principles of the changes : - How UE is aware\/configured that a DNN is a LADN DNN is out of scope of rel-15 (as agreed in Gothenburg) - AMF not serving a LADN serving area does not need to be configured with LADN information for that DNN (as agreed in Gothenburg) - AMF serving a LADN service area is configured with LADN information and provides this information to the UE (per existing specification)  - A UE not receiving any LADN information from the AMF for a subscribed LADN DNN configured in the UE (e.g. because that AMF is not configured with LADN information for a DNN) shall assume that it is outside of the LADN service area for such DNN - SMF has a configuration whether a DNN is a LADN DNN or not (this can e.g. be part of the regular DNN configuration in SMF) - When SMF subscribes to 'UE presence in area of interest' for a LADN DNN, and the AMF is not configured with any LADN information for that DNN, the AMF shall reply to the SMF that it has no information abo","secretary_remarks":"Revision of S2-182814. Wrong document uploaded. Revised in S2-182971.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14440,"status":"revised","reservation_date":"2018-03-01 18:43:42","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182814","revisedto":"S2-182971","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":22.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182847.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182848","title":"Clarification on Location reporting procedures","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the AMF may provide mulitple areas of interest to NG-RAN. The NG-RAN only report once location information when it detects the UE has move out of or into multiple areas of interest. The AMF may cancel the area of interest location report in NG-RAN.","secretary_remarks":"Revision of S2-182799. 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":14660,"status":"agreed","reservation_date":"2018-03-01 18:43:43","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182799","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":138.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180104","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182848.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182849","title":"N4 User Plane Path","source":"Huawei","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that N4-u user plane tunnel is used for packet forwarding between UPF and SMF.","secretary_remarks":"Revision of S2-182804. 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":14780,"status":"agreed","reservation_date":"2018-03-01 18:43:44","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182804","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":171.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180100","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182849.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182850","title":"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":"CR","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":"Revision of S2-182806. 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":14840,"status":"agreed","reservation_date":"2018-03-01 18:43:50","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182806","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182850.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182851","title":"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":"CR","for":"Approval","abstract":"Summary of change: Clarify that for 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-182698. 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":13920,"status":"agreed","reservation_date":"2018-03-01 18:43:51","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182698","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":42.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180102","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182851.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182852","title":"Updates to description of CN Tunnel Info","source":"Samsung","contact":"Jayshree Bharatia","contact-id":63826,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Existing description of CN Tunnel Info does not include modification of CN Tunnel Info attribute when it is allocated either by SMF or UPF. This paper updates existing text to include these details.","secretary_remarks":"Revision of S2-182812. 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":14990,"status":"agreed","reservation_date":"2018-03-01 18:43:52","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182812","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":151.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180100","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182852.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182853","title":"Wildcard DNN subcription","source":"Nokia, Nokia Shanghai Bell, Telecom Italia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Subscription Information may include a wildcard DNN per subscribed S-NSSAI: when a wildcard DNN is associated with a subscribed S-NSSAI, the UE is allowed to request access to any DNN value associated within the scope of this S-NSSAI.","secretary_remarks":"Revision of S2-182845. 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":14330,"status":"agreed","reservation_date":"2018-03-01 18:43:53","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182845","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":21.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-180090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182853.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182967","title":"LS on indicating service continuity usage of the additional IPv6 prefix in Router Advertisement","source":"SA WG2","contact":"Changhong Shan","contact-id":45586,"tdoctype":"LS out","for":"Approval","abstract":"To: IETF Internet Area, IETF DMM. CC: IETF 6MAN, CT WG1, TSG CT","secretary_remarks":"Revision of S2-182844. 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":14180,"status":"approved","reservation_date":"2018-03-05 10:36:33","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182844","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-181481","lsto":"IETF Internet Area, IETF DMM","Cc":"IETF 6MAN, CT WG1, TSG CT","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182967.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182968","title":"Proposal of QER, URR and FAR","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The same parameters as described in the CUPS specification TS 23.214 are proposed for the QER, URR and FAR of the UPF. Terminology is aligned and parameters that are not needed in 5GS are proposed to be removed.","secretary_remarks":"Revision of S2-182803. 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":14750,"status":"agreed","reservation_date":"2018-03-05 10:36:33","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182803","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":174.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180100","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182968.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182969","title":"Using NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","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 usinf NRF to get info on other NF) 3. Update NRF service operations with UPF rlated information such as UPF Discovery Information","secretary_remarks":"Revision of S2-182694. Revised to S2-182987.","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-03-05 10:36:34","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182694","revisedto":"S2-182987","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":5.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182969.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182970","title":"Selection mode transfer over N11 and N16 (wildcard DNN)","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Selection Mode is transferred from AMF to SMF (H-SMF via V-SMF). Typo (operation name ContextRequest) in \u00a7 5.2.8.2.10 + 5.2.8.1","secretary_remarks":"Revision of S2-182846. Revised to S2-182989.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14370,"status":"revised","reservation_date":"2018-03-05 10:36:35","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182846","revisedto":"S2-182989","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":105.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182970.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182971","title":"Clarification in LADN clause 5.6.5 - TS 23.501","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Principles of the changes : - How UE is aware\/configured that a DNN is a LADN DNN is out of scope of rel-15 (as agreed in Gothenburg) - AMF not serving a LADN serving area does not need to be configured with LADN information for that DNN (as agreed in Gothenburg) - AMF serving a LADN service area is configured with LADN information and provides this information to the UE (per existing specification)  - A UE not receiving any LADN information from the AMF for a subscribed LADN DNN configured in the UE (e.g. because that AMF is not configured with LADN information for a DNN) shall assume that it is outside of the LADN service area for such DNN - SMF has a configuration whether a DNN is a LADN DNN or not (this can e.g. be part of the regular DNN configuration in SMF) - When SMF subscribes to 'UE presence in area of interest' for a LADN DNN, and the AMF is not configured with any LADN information for that DNN, the AMF shall reply to the SMF that it has no information abo","secretary_remarks":"Revision of S2-182847. Revised to S2-182972.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14450,"status":"revised","reservation_date":"2018-03-05 10:36:36","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182847","revisedto":"S2-182972","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":22.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182971.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182972","title":"Clarification in LADN clause 5.6.5 - TS 23.501","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Principles of the changes : - How UE is aware\/configured that a DNN is a LADN DNN is out of scope of rel-15 (as agreed in Gothenburg) - AMF not serving a LADN serving area does not need to be configured with LADN information for that DNN (as agreed in Gothenburg) - AMF serving a LADN service area is configured with LADN information and provides this information to the UE (per existing specification)  - A UE not receiving any LADN information from the AMF for a subscribed LADN DNN configured in the UE (e.g. because that AMF is not configured with LADN information for a DNN) shall assume that it is outside of the LADN service area for such DNN - SMF has a configuration whether a DNN is a LADN DNN or not (this can e.g. be part of the regular DNN configuration in SMF) - When SMF subscribes to 'UE presence in area of interest' for a LADN DNN, and the AMF is not configured with any LADN information for that DNN, the AMF shall reply to the SMF that it has no information abo","secretary_remarks":"Revision of S2-182971. This CR was agreed.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14460,"status":"agreed","reservation_date":"2018-03-05 10:37:13","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182971","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":22.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182972.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182973","title":"Using NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","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":"Revision of S2-182813. 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":15040,"status":"agreed","reservation_date":"2018-03-05 10:37:14","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182813","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182973.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182987","title":"Using NRF for UPF discovery","source":"Nokia, Nokia Shanghai Bell, Cisco,","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","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 usinf NRF to get info on other NF) 3. Update NRF service operations with UPF rlated information such as UPF Discovery Information","secretary_remarks":"Revision of S2-182969. This CR was agreed.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":13801,"status":"agreed","reservation_date":"2018-03-05 10:37:22","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182969","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":5.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-180090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182987.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182989","title":"Selection mode transfer over N11 and N16 (wildcard DNN)","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Selection Mode is transferred from AMF to SMF (H-SMF via V-SMF). Typo (operation name ContextRequest) in \u00a7 5.2.8.2.10 + 5.2.8.1","secretary_remarks":"Revision of S2-182970. This CR was agreed.","agenda_item_sort_order":20,"ainumber":"6.5.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":14371,"status":"agreed","reservation_date":"2018-03-05 10:37:24","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182970","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":105.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-180090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182989.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]