[{"name":"S2-181492","title":"Multiple request of Location Reporting for Area of Interest","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF includes Request Reference ID in the Location Report Control message to identify the request for the area of interest. The AMF may include Request Reference ID in the Cancel Location Reporting message which indicates the requested Location Reporting Control for the area of interest, so that the NG-RAN should terminate location reporting for the reference ID for a given UE.","secretary_remarks":"Revision of approved DraftCR S2-181149. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17470,"status":"agreed","reservation_date":"2018-02-06 06:34:52","uploaded":"2018-02-06 06:49:49","revisionof":"S2-181149","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":12.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-181492.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-181495","title":"Paging Policy Differentiation correction","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: PPI is removed from the paging message.","secretary_remarks":"Revision of approved DraftCR S2-181144. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17480,"status":"agreed","reservation_date":"2018-02-06 06:41:36","uploaded":"2018-02-09 03:11:39","revisionof":"S2-181144","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":13.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-181495.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-181515","title":"Update to N2 Handover procedure","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the N2 based handover to allow: 1. The target gNB can receive QoS flow that are subject to data forwarding from the source to target container. 2. Add a condition for source NG-RAN indicating SMF which QoS flows are subject to data forwarding.","secretary_remarks":"Revised in parallel session to S2-182816.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17620,"status":"revised","reservation_date":"2018-02-07 08:00:29","uploaded":"2018-02-10 12:12:47","revisionof":"","revisedto":"S2-182816","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":27.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-181515.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-181558","title":"Cleanup of the service request procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Per above reason of changes, the related clarification and changes are updated.","secretary_remarks":"Revision of approved DRAFTCR S2-181279. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17490,"status":"agreed","reservation_date":"2018-02-12 12:50:42","uploaded":"2018-02-12 14:00:59","revisionof":"S2-181279","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":46.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-181558.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-181561","title":"Update of handover cancel procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change 1: the SBA service (e.g. Nsmf_PDUSession_UpdateSMContext request\/response in the N11 interface) shall be used 5G system. Change 2: The figure 4.11.1.2.3-1 is updated. Change 3: 'handover cancel indication' is added into the handover cancel procedure.","secretary_remarks":"Revision of approved DRAFTCR S2-181138. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17500,"status":"agreed","reservation_date":"2018-02-12 12:50:45","uploaded":"2018-02-12 14:00:59","revisionof":"S2-181138","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":48.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-181561.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-181563","title":"Control of the Messages triggering Paging at AMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF controls the quantity of messages that require the AMF to page the UE. If additional requests received while waiting for a UE response to the Paging Request message, the AMF may determine whether to reject it. Proposal 1: The AMF controls the messages based on priority and number. Proposal 2: If the AMF has sent two Paging Messages to RAN node, the AMF shall reject the subseqeuent messages. Proposal 3: If the AMF has a Paging Messages to RAN node, the AMF shall reject the subseqeuent messages without a higer priority.","secretary_remarks":"Revision of approved DRAFTCR S2-181141. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17510,"status":"agreed","reservation_date":"2018-02-12 12:50:46","uploaded":"2018-02-12 14:00:59","revisionof":"S2-181141","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":33.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180091","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181563.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-181564","title":"Control of the Messages triggering Paging at AMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF controls the quantity of messages that require the AMF to page the UE. If additional requests received while waiting for a UE response to the Paging  Request message, the AMF may determine whether to reject it. Proposal 1: The AMF controls the messages based on priority and number. Proposal 2: If the AMF has sent two Paging Messages to RAN node, the AMF shall reject the subseqeuent messages. Proposal 3: If the AMF has a Paging Messages to RAN node, the AMF shall reject the subseqeuent messages without a higer priority.","secretary_remarks":"Revision of approved DRAFTCR S2-181402. Revised, merging S2-182815, to S2-182861.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17520,"status":"revised","reservation_date":"2018-02-12 12:50:47","uploaded":"2018-02-12 14:00:59","revisionof":"S2-181402","revisedto":"S2-182861","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":49.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-181564.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-181565","title":"Clarification for Area of validity in NW triggered SR procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: (1) Add a clarification in step 4 of clause 4.2.3.2 that step 4-11 can be skipped for the above case. (2) Editorial modification to change 'Area of validity for the N2 information' to 'Area of validity for the N2 SM information'. This part is highlighted in blue color. (3) Delete redundant text in 4.2.3.2. This part is highlighted in green color.","secretary_remarks":"Revision of approved DRAFTCR S2-181147. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17540,"status":"agreed","reservation_date":"2018-02-12 12:50:48","uploaded":"2018-02-12 14:00:59","revisionof":"S2-181147","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":50.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-181565.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-181578","title":"Update Paging Policy Differentiation","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change 1. Clarify that in case of UPF buffering downlink data packet, the SMF determines PPI based on the DSCP received from the UPF. Change 2. Clarify QoS Flow indication is not needed for SMF determining PPI in case of SMF buffering downlink data packet. Change 3. Clarify how UPF handles the QoS Flows with different paging differentiation requirements and how RAN enforces paging policies in order to make it much clearer.","secretary_remarks":"Revision of approved DRAFTCR S2-180675. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17440,"status":"agreed","reservation_date":"2018-02-12 14:18:25","uploaded":"2018-02-13 16:31:21","revisionof":"S2-180675","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":36.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180091","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181578.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-181579","title":"Update Paging Policy Differentiation in Network triggered Service Request procedure","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change 1. Clarify UPF should send information to identify the QoS Flow for the DL data packet instead of information to identify QFI in the step 2a Change 2. Clarify information to identify the QoS Flow is not needed for SMF determining PPI in case of SMF buffering downlink data packet.","secretary_remarks":"Revision of endorsed DRAFTCR S2-180676. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17450,"status":"agreed","reservation_date":"2018-02-12 14:18:26","uploaded":"2018-02-13 16:31:21","revisionof":"S2-180676","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":57.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180091","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181579.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-181618","title":"NAS congestion control update","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified the usage of 5G-AN and NG-RAN.  Clarified that the AMF can apply the general NAS level congestion control towards UEs using any of the 5G-ANs.   Clarified that change of untrusted non-3GPP access network or change of Access Type change does not stop the back-off timers.","secretary_remarks":"Revision of endorsed DRAFTCR S2-180239. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17550,"status":"agreed","reservation_date":"2018-02-13 14:17:30","uploaded":"2018-02-20 01:46:36","revisionof":"S2-180239","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":51.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180098","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181618.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-181622","title":"Resolution of ENs in Service Request procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change:  Editor's note: The required AN parameters are FFS. It is proposed that further details not needed unless requested by e.g. other WG. It is proposed to remove the EN.  Editor's note: It is FFS whether N2 SM information in this message is optional and when it should be carried. In EPS the following are the listed cases for initiating PDN GW initiated bearer modification without bearer QoS update procedure: ' The bearer modification procedure without bearer QoS update is used to update the TFT for an active default or dedicated bearer, to modify the APN-AMBR, to retrieve User Location from the MME, to inform PCO to UE or to instruct the MME (e.g. to activate\/deactivate the location reporting)'  It is proposed to discuss and support sending an updated PCO to the UE also for 5GS, which does not require any N2 SM information to AN.  Additions done after SA WG2#125 (from SA WG2 approved draftCR in S2-181192):  Adopted the changes in clause 4.2.3.2 of the principles from th","secretary_remarks":"Revision of approved DRAFTCR S2-181192. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17460,"status":"agreed","reservation_date":"2018-02-13 14:30:06","uploaded":"2018-02-20 14:34:49","revisionof":"S2-181192","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":65.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-181622.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-181868","title":"Paging cause to the UE","source":"Qualcomm Incorporated, Intel","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"discussion","for":"Approval","abstract":"Discusses the need for paging cause to the UE and proposes to send LS to RAN WGs to request signalling paging cause in the OTA paging message.","secretary_remarks":"Noted in parallel session.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17840,"status":"noted","reservation_date":"2018-02-19 12:53:29","uploaded":"2018-02-20 13:34:04","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-181868.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-181869","title":"[DRAFT] LS on Paging cause from RAN to UE","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 discuss the possibility of sending a paging cause from AMF to RAN and from RAN to UE. The paging cause is used by the UE in order to differentiate paging for IMS voice vs paging caused by other traffic. SA WG2 would like to request feedback whether a 1-bit or 2-bit paging cause indicator can be sent from RAN to UE in paging message","secretary_remarks":"Not Handled","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17850,"status":"not treated","reservation_date":"2018-02-19 12:53:29","uploaded":"2018-02-20 13:34:04","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1, RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181869.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-181871","title":"Preservation of GBR QoS Flows upon redirection","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Proposes to rename the cause code for AN release from 'inter-system redirection' to 'UE redirection'.","secretary_remarks":"Revision of approved DRAFTCR S2-180387. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17560,"status":"agreed","reservation_date":"2018-02-19 12:53:30","uploaded":"2018-02-20 13:34:04","revisionof":"S2-180387","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":156.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-181871.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-181938","title":"Correction for UE location in Xn based HO procedure","source":"Samsung","contact":"Jayshree Bharatia","contact-id":63826,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Step 2 of section 4.9.1.2.2 in TS 23.502 includes details regarding assigning RAN identifier to UE location attribute of the Nsmf_PDUSession_UpdateSMContext request operation. Currently, it is unclear whether RAN identifier reflects identifier of the RAN or cell. If this identifier is RAN identifier, it will not be correct since AMF receives target cell identifier in N2 Path Switch Request message from the RAN and not the RAN identifier.","secretary_remarks":"Revision of approved DRAFTCR S2-181139. Revised to S2-182778.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17570,"status":"revised","reservation_date":"2018-02-19 16:08:13","uploaded":"2018-02-19 16:15:12","revisionof":"S2-181139","revisedto":"S2-182778","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":167.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-181938.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-181976","title":"Procedures to support paging priority handling","source":"Vencore Labs, OEC, AT&T","contact":"Vijay Varma","contact-id":74475,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Though the AMF and other network functions together need to control the quantity of messages that require the AMF to page the UE, when the UPF should send additional Data Notification to the SMF and when the SMF should send additional N1N2 message to the AMF should be unambigously specified, particularly the priority aspects.  Proposal 1: When the UPF receives the first Downlink Data for a QoS Flow in the same or different PDU session, indicate that the UPF should send another Data Notification Message to the SMF. Proposal 2: The SMF while waiting for the User Plane Connection to be activated, receives any additional Data Notification message, the SMF should check if the QoS flow indicates an ARP priority level associated with Priority Service and if so send another message to the AMF indicating higher priority. Proposal 3: Delete the erroneous statement relating to the SMF action for regulatory prioritized services.","secretary_remarks":"Revised in parallel session to S2-182815.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17690,"status":"revised","reservation_date":"2018-02-19 17:11:08","uploaded":"2018-02-19 21:28:14","revisionof":"","revisedto":"S2-182815","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":169.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-181976.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-181979","title":"Aligning the use of Access Control","source":"Vencore Labs, OEC, AT&T","contact":"Vijay Varma","contact-id":74475,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Replaced, where applicable, the use of Access Class Barring mechanisms with Unified Access Control mechanisms and updated the reference.","secretary_remarks":"Merged into S2-182777.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17430,"status":"merged","reservation_date":"2018-02-19 17:20:05","uploaded":"2018-02-19 21:27:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":121.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-181979.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-181991","title":"Clarification on handover procedure for home-routed roaming scenario","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a note to clarify that the SMF is a V-SMF in the N2 handover procedure for home-routed roaming case","secretary_remarks":"Revised to S2-182779.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17640,"status":"revised","reservation_date":"2018-02-19 19:06:57","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"S2-182779","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":176.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-181991.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-181993","title":"Correction to inter NG-RAN node N2 based handover","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: \u00fc Correct the wrong refered steps in 4.9.1.3.2. \u00fc Delete the unnecessary standalone registeration in step 7","secretary_remarks":"Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17660,"status":"agreed","reservation_date":"2018-02-19 19:06:59","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":177.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-181993.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-181997","title":"Correction on N4 Session Modification Request in Handover procedure","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Move the LADN related description to the last part of this procedure with a minor change.  2. Add a description for mobility related events notification from AMF.","secretary_remarks":"Revised to S2-182781.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17670,"status":"revised","reservation_date":"2018-02-19 19:07:03","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"S2-182781","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":179.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-181997.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-181998","title":"Correction on Service Request procedure when UE establishes a signalling connection only","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For signalling connection only Service Request: 1. Correct the skipped steps defined in step 3. 2. Add the clue for AMF awaring the type of service request is 'signalling connection only'. 3. Clarify when UE is in CM-IDLE state, NG-RAN will not store the SM-related information.","secretary_remarks":"Revised to S2-182782.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17710,"status":"revised","reservation_date":"2018-02-19 19:07:04","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"S2-182782","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":180.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-181998.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-181999","title":"Clarify how to send end marker during HO procedure","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that in case of the Source UPF is a UL CL or BP, the SMF indicates only one of the PSA to send 'end marker' packet. To ensure the 'end marker' is the last user plane packet on the old path, the SMF should modify the path on other PSAs before it indicates the PSA to send 'end marker' packets.","secretary_remarks":"Revised in parallel session to S2-182818.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17790,"status":"revised","reservation_date":"2018-02-19 19:07:05","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"S2-182818","release":"Rel-15","crspec":23.502,"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-181999.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-182008","title":"Aligning 23.502 onto 29.244 about PPD","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: .align 23.502 onto 29.244: the UPF unconditionaly reports DSCP","secretary_remarks":"Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17730,"status":"agreed","reservation_date":"2018-02-19 20:11:14","uploaded":"2018-02-19 20:15:51","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":183.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-182008.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-182011","title":"Service Request procedure corrections","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: As above.","secretary_remarks":"Revision of approved DRAFTCR S2-181308. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17590,"status":"agreed","reservation_date":"2018-02-19 20:32:56","uploaded":"2018-02-19 20:36:19","revisionof":"S2-181308","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":185.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-182011.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-182014","title":"New cause for UP reactivation failure in Service Request procedure","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, In Step 11 a new cause of 'resource unavailability' for UP connection activation failure is added; 2, For the cause of 'resource unavailability', the UE may retry UP connection activation using Service Request.","secretary_remarks":"Revised to S2-182783.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17740,"status":"revised","reservation_date":"2018-02-19 20:54:37","uploaded":"2018-02-20 14:08:56","revisionof":"","revisedto":"S2-182783","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":186.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-182014.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-182020","title":"Rejection of UP activation during the Registration procedure","source":"InterDigital Communications","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, In Step 11 a new cause of 'resource unavailability' for UP connection activation failure is added; 2, For the cause of 'resource unavailability', the UE may retry UP connection activation using Service Request.","secretary_remarks":"Revised in parallel session to S2-182817.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17760,"status":"revised","reservation_date":"2018-02-19 20:54:40","uploaded":"2018-02-20 14:08:56","revisionof":"","revisedto":"S2-182817","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":187.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-182020.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-182100","title":"Service reject when UE is in Non-Allowed area","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that when the UE initiates the service request in a Non-Allowed Area, AMF will rejects the service request to UE.","secretary_remarks":"Noted in parallel session.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17810,"status":"noted","reservation_date":"2018-02-20 05:18:45","uploaded":"2018-02-20 05:34:49","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":148.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-182100.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-182103","title":"Reject Cause in Service Accept message","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A single rejection cause is included in Service Accept if multiple PDU session re-activation are rejected by SMFs.","secretary_remarks":"Noted in parallel session.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17820,"status":"noted","reservation_date":"2018-02-20 05:26:21","uploaded":"2018-02-20 10:32:15","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":208.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-182103.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-182110","title":"Clarification on RRM desciption","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add 'NGAP' in front of DOWNLINK NAS TRANSPORT message.","secretary_remarks":"Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17830,"status":"agreed","reservation_date":"2018-02-20 06:32:06","uploaded":"2018-02-20 06:52:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":152.0,"crrevision":"","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-182110.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-182221","title":"Update of Mobility Restrictions","source":"Lenovo, Motorola Mobility","contact":"Zhuoyun Zhang","contact-id":67292,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Clarification of Service area restrictions in clause 5.3.4.1.1. 2. Changing 'Paging Area Update' to 'RAN Notification Area Update' in clause 5.4.2.","secretary_remarks":"Revision of approved DRAFTCR S2-180737. Revised to S2-182780.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17600,"status":"revised","reservation_date":"2018-02-20 10:37:24","uploaded":"2018-02-20 11:12:53","revisionof":"S2-180737","revisedto":"S2-182780","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":180.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182221.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-182778","title":"Correction for UE location in Xn based HO procedure","source":"Samsung","contact":"Jayshree Bharatia","contact-id":63826,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Step 2 of section 4.9.1.2.2 in TS 23.502 includes details regarding assigning RAN identifier to UE location attribute of the Nsmf_PDUSession_UpdateSMContext request operation. Currently, it is unclear whether RAN identifier reflects identifier of the RAN or cell. If this identifier is RAN identifier, it will not be correct since AMF receives target cell identifier in N2 Path Switch Request message from the RAN and not the RAN identifier.","secretary_remarks":"Revision of S2-181938. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17580,"status":"agreed","reservation_date":"2018-02-28 21:27:52","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181938","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":167.0,"crrevision":1.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-182778.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-182779","title":"Clarification on handover procedure for home-routed roaming scenario","source":"Huawei, HiSillicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a note to clarify that the SMF is a V-SMF in the N2 handover procedure for home-routed roaming case","secretary_remarks":"Revision of S2-181991. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17650,"status":"agreed","reservation_date":"2018-02-28 21:27:53","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181991","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":176.0,"crrevision":1.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-182779.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-182780","title":"Update of Mobility Restrictions","source":"Lenovo, Motorola Mobility","contact":"Zhuoyun Zhang","contact-id":67292,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Clarification of Service area restrictions in clause 5.3.4.1.1. 2. Changing 'Paging Area Update' to 'RAN Notification Area Update' in clause 5.4.2.","secretary_remarks":"Revision of S2-182221. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17610,"status":"agreed","reservation_date":"2018-02-28 21:27:55","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182221","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":180.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-182780.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-182781","title":"Correction on N4 Session Modification Request in Handover procedure","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Move the LADN related description to the last part of this procedure with a minor change.  2. Add a description for mobility related events notification from AMF.","secretary_remarks":"Revision of S2-181997. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17680,"status":"agreed","reservation_date":"2018-02-28 21:27:56","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181997","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":179.0,"crrevision":1.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-182781.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-182782","title":"Correction on Service Request procedure when UE establishes a signalling connection only","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For signalling connection only Service Request: 1. Correct the skipped steps defined in step 3. 2. Add the clue for AMF awaring the type of service request is 'signalling connection only'. 3. Clarify when UE is in CM-IDLE state, NG-RAN will not store the SM-related information.","secretary_remarks":"Revision of S2-181998. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17720,"status":"agreed","reservation_date":"2018-02-28 21:27:57","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181998","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":180.0,"crrevision":1.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-182782.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-182783","title":"New cause for UP reactivation failure in Service Request procedure","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, In Step 11 a new cause of 'resource unavailability' for UP connection activation failure is added; 2, For the cause of 'resource unavailability', the UE may retry UP connection activation using Service Request.","secretary_remarks":"Revision of S2-182014. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17750,"status":"agreed","reservation_date":"2018-02-28 21:27:58","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182014","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":186.0,"crrevision":1.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-182783.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-182815","title":"Procedures to support paging priority handling","source":"Vencore Labs, OEC, AT&T, Huawei","contact":"Vijay Varma","contact-id":74475,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Though the AMF and other network functions together need to control the quantity of messages that require the AMF to page the UE, when the UPF should send additional Data Notification to the SMF and when the SMF should send additional N1N2 message to the AMF should be unambigously specified, particularly the priority aspects.  Proposal 1: When the UPF receives the first Downlink Data for a QoS Flow in the same or different PDU session, indicate that the UPF should send another Data Notification Message to the SMF. Proposal 2: The SMF while waiting for the User Plane Connection to be activated, receives any additional Data Notification message, the SMF should check if the QoS flow indicates an ARP priority level associated with Priority Service and if so send another message to the AMF indicating higher priority. Proposal 3: Delete the erroneous statement relating to the SMF action for regulatory prioritized services.","secretary_remarks":"Revision of S2-181976. Merged into S2-182861.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17700,"status":"merged","reservation_date":"2018-03-01 18:39:28","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181976","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":169.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-182815.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-182816","title":"Update to N2 Handover procedure","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the N2 based handover to allow: 1. The target gNB can receive QoS flow that are subject to data forwarding from the source to target container. 2. Add a condition for source NG-RAN indicating SMF which QoS flows are subject to data forwarding.","secretary_remarks":"Revision of S2-181515. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17630,"status":"agreed","reservation_date":"2018-03-01 18:39:29","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181515","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":27.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-182816.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-182817","title":"Rejection of UP activation during the Registration procedure","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, In Step 11 a new cause of 'resource unavailability' for UP connection activation failure is added; 2, For the cause of 'resource unavailability', the UE may retry UP connection activation using Service Request.","secretary_remarks":"Revision of S2-182020. Revised to S2-182896.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17770,"status":"revised","reservation_date":"2018-03-01 18:39:30","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182020","revisedto":"S2-182896","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":187.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-182817.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-182818","title":"Clarify how to send end marker during HO procedure","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that in case of the Source UPF is a UL CL or BP, the SMF indicates only one of the PSA to send 'end marker' packet. To ensure the 'end marker' is the last user plane packet on the old path, the SMF should modify the path on other PSAs before it indicates the PSA to send 'end marker' packets.","secretary_remarks":"Revision of S2-181999. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17800,"status":"agreed","reservation_date":"2018-03-01 18:39:31","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181999","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":181.0,"crrevision":1.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-182818.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-182861","title":"Control of the Messages triggering Paging at AMF","source":"Huawei, Hisilicon, Vencore Labs, OEC, AT&T","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF controls the quantity of messages that require the AMF to page the UE. If additional requests received while waiting for a UE response to the Paging  Request message, the AMF may determine whether to reject it. Proposal 1: The AMF controls the messages based on priority and number. Proposal 2: If the AMF has sent two Paging Messages to RAN node, the AMF shall reject the subseqeuent messages. Proposal 3: If the AMF has a Paging Messages to RAN node, the AMF shall reject the subseqeuent messages without a higer priority.","secretary_remarks":"Revision of S2-181564, merging S2-182815. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17530,"status":"agreed","reservation_date":"2018-03-02 14:39:00","uploaded":"2018-03-05 11:37:54","revisionof":"S2-181564","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":49.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180091","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182861.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-182896","title":"Rejection of UP activation during the Registration procedure","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, In Step 11 a new cause of 'resource unavailability' for UP connection activation failure is added; 2, For the cause of 'resource unavailability', the UE may retry UP connection activation using Service Request.","secretary_remarks":"Revision of S2-182817. Agreed in parallel session. Block approved.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17780,"status":"agreed","reservation_date":"2018-03-02 14:40:40","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182817","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":187.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-182896.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}]