[{"name":"S2-1901422","title":"LS from CT WG1: LS on entering 5GMM-IDLE mode after notification on non-3GPP access","source":"CT WG1","contact":"Mahmoud Watfa","contact-id":72074,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA WG2 for their LS on how the UE enters 5GMM-IDLE mode after receiving a Notification message (with access type indicating 3GPP access) while in 5GMM-CONNECTED mode over the non-3GPP access and in 5GMM-CONNECTED mode with RRC inactive indication over the 3GPP access. CT WG1 would like to inform SA WG2 that no option was adopted for Rel-15 as the scenario is rare and Rel-15 is frozen. CT WG1 would like to inform SA WG2 that Option 1 has been adopted as the way forward for the identified scenario in Rel-16 i.e. the UE transitions to 5GMM-IDLE mode and initiates the service request procedure over the 3GPP access. Action: CT WG1 kindly requests SA WG2 to take the above into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12450,"status":"noted","reservation_date":"2019-02-05 10:23:57","uploaded":"2019-02-05 10:27:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-190379","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901422.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901517","title":"UE presence in restricted area indication in Nsmf_PDUSession_UpdateSMContext","source":"Nokia, Nokia Shanghai Bell","contact":"Yannick Lair","contact-id":76350,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a 'UE presence in restricted area indication' as input for Nsmf_PDUSession_UpdateSMContext.","secretary_remarks":"This was postponed.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12480,"status":"postponed","reservation_date":"2019-02-15 09:47:33","uploaded":"2019-02-19 14:57:17","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1005.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901517.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901860","title":"Xn based handover with I-UPF insertion","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies in clause 4.15.4.2 that the reachability notification may also be sent in mobility procedures other than registration. And that SMF is expected to subscribe to UE reachability notification. Rev4: Clarifies in HR roaming both V-SMF and H-SMF subscribes to UE reachability event, the V-SMF determines whether to deactivate PDU Session when UE is in non allowed area, the H-SMF determines whether to trigger DL signalling if UE is in non allowed area. The V-SMF transfer the AMF ID to the H-SMF. Clarifies in handover procedures, the AMF notifies to the SMF about the reachability status of the UE. Clarifies in clause 4.15.4.2 SMF is expected to subscribe to UE reachability notification.","secretary_remarks":"Revised in parallel session to S2-1902734.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12490,"status":"revised","reservation_date":"2019-02-19 03:51:37","uploaded":"2019-02-19 14:35:58","revisionof":"","revisedto":"S2-1902734","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1065.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901860.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901961","title":"Clarification on NG-RAN behaviour on Periodic RNAU procedure","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During the UE initial Registration with 5GC, this CR proposes changes to reverse the order of the operation of sending the Registration Accept message (i.e. Step 21) to the UE after the operation of Session Management Policy Association between the UE's serving AMF and the UE's serving PCF (i.e. Step 21b). The Step 21b operation is to alert the UE's serving AMF for the session management policy information update from the UE's serving PCF to the UE, if any. If the UE's serving AMF receives any URSP from the UE's serving PCF, the UE's serving AMF will then include the URSP Indication in the Registration Accept to the UE. Once if UE receives that URSP Indication in the Registration Accept, the UE will then wait for the UE Configuration Update from the UE's serving PCF before initiating any new establishment of SA or MA PDU session.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12510,"status":"noted","reservation_date":"2019-02-19 08:19:07","uploaded":"2019-02-19 14:31:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":993.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901961.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901962","title":"Clarification on NG-RAN behaviour on Periodic RNAU procedure","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add dual connectivity based solution for user plane redundancy. Updated thing compared to the CR agreed in last meeting: Remove the explict indication from CN to request RAN to make the PDU session go via MN or SN in normative text. Add a NOTE to illustrate that the NG-RAN may take the parameters in N2 SM Info (e.g. RSN, S-NSSAI, and DNN) into account to decide the PDU sessin do via MN or SN. All the new changes are in cyan","secretary_remarks":"Revised in parallel session to S2-1902735.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12520,"status":"revised","reservation_date":"2019-02-19 08:19:10","uploaded":"2019-02-19 14:31:56","revisionof":"","revisedto":"S2-1902735","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1087.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901962.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902734","title":"Xn based handover with I-UPF insertion","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"To: RAN WG. CC: CT WG3, CT WG4","secretary_remarks":"Revision of S2-1901860. Agreed in parallel session. This was Block approved","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12500,"status":"agreed","reservation_date":"2019-02-26 17:14:22","uploaded":"2019-03-08 10:59:11","revisionof":"S2-1901860","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1065.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190159","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902734.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902735","title":"Clarification on NG-RAN behaviour on Periodic RNAU procedure","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify after sending the notification that the GFBR can no longer be guaranteed, if the QoS Flow is modified or released by 5GC, the NG-RAN will not continue Notification control for the old GFBR","secretary_remarks":"Revision of S2-1901962. Agreed in parallel session. This was Block approved","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":12530,"status":"agreed","reservation_date":"2019-02-26 17:14:23","uploaded":"2019-03-08 10:59:12","revisionof":"S2-1901962","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1087.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190159","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902735.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]