[{"name":"S2-184656","title":"LS from CT WG1: LS on deactivation of MICO mode due to emergency service","source":"CT WG1","contact":"Yanchao Kang","contact-id":72631,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 identified the following in TS 23.501 subclause 5.4.1.3. 'A UE initiating emergency service shall not indicate MICO preference during Registration procedure. When the MICO mode is already activated in the UE, the UE shall request deactivation of MICO mode via Registration procedure while the UE is in CM-CONNECTED state after PDU Establishment procedure for Emergency Services is completed.' For this particular case, CT WG1 has agreed that MICO mode is deactivated without explicit signalling between the UE and the network (see attached PCR). That is if the MICO mode was activated, the UE and the AMF shall locally deactivate MICO mode during the establishment of a PDU session for emergency services. In this way the network resources can be spared. Action: CT WG1 kindly asks SA WG2 to take CT WG1 decision into account and update their specifications if needed.","secretary_remarks":"Postponed S2-183069 from S2#127. 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":17510,"status":"noted","reservation_date":"2018-05-04 06:13:09","uploaded":"2018-05-04 06:17:56","revisionof":"S2-183069","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-181765","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184656.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184661","title":"LS from RAN WG3: LS on data forwarding for intra-system handover","source":"RAN WG3","contact":"Lixiang Xu","contact-id":50973,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 has agreed to support both per-DRB level and per-PDU session level tunnelling for direct data forwarding in order to support lossless intra-system handover. In case direct forwarding is not possible for NG-based handover, the UPF should provide an intermediate tunnel endpoint identifier per DRB to apply indirect data forwarding. Action: RAN WG3 kindly ask SA WG2 whether it is feasible to configure intermediate tunnel endpoint per DRB at UPF for supporting indirect data forwarding via 5GC.","secretary_remarks":"Postponed S2-183079 from S2#127. Postponed","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17520,"status":"postponed","reservation_date":"2018-05-04 06:13:09","uploaded":"2018-05-04 06:17:56","revisionof":"S2-183079","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2","lsoriginalls":"R3-181542","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184661.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184683","title":"LS from CT WG1: LS on SR in 5G","source":"CT WG1","contact":"Lalith Kumar","contact-id":60520,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has considered the following scenario: 1. The UE's 5GMM layer sends a SERVICE REQUEST message. 2. Meanwhile, the 5GMM layer receives from the upper layers an indication that there is a need to send an uplink user data for a PDU session which is related to a delay sensitive application and is not requested to be reactivated in the SERVICE REQUEST message in step 1. 3. The 5GMM layer will delay sending another SERVICE REQUEST message for reactivation of the PDU session described in step 2 until the service request procedure initiated in step 1 is completed because it has been agreed to design that the UE is not allowed to initiate a new service request procedure before an old service request procedure is completed. CT WG1 assumed that the above design might not be able to satisfy the KPI's of delay sensitive applications (e.g. MCPTT) and agreed a solution as attached. Operators in CT WG1 believe using this feature, UEs may start making request for network resources even for operat","secretary_remarks":"Responses drafted in S2-185028 and S2-185258. Final response in S2-186173","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17560,"status":"replied to","reservation_date":"2018-05-04 06:13:10","uploaded":"2018-05-04 06:17:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG6","lsoriginalls":"C1-182809","lsreply":"S2-186173","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184683.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184684","title":"LS from CT WG1: LS on applicability of Reflective QoS for Emergency PDU","source":"CT WG1","contact":"Mahmoud Watfa","contact-id":72074,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 discussed whether Reflective QoS (RQoS) is allowed to be applied for a PDU session for emergency services. Action: CT WG1 kindly requests SA WG2 to inform CT WG1 whether RQoS is allowed to be applied for a PDU session for emergency services.","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":17500,"status":"noted","reservation_date":"2018-05-04 06:13:10","uploaded":"2018-05-04 06:17:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"C1-182817","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184684.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184844","title":"Correction to indirect forwarding at intra 5GS N2 HO","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The CN (SMF\/UPF) allocates the N3 UP address and Tunnel IDs for indirect data forwarding corresponding to the data fowarding tunnel endpoints established by T-RAN.","secretary_remarks":"Revision of (Postponed) S2-183812 from S2#127. 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-05-18 20:13:51","uploaded":"2018-05-22 01:22:52","revisionof":"S2-183812","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":378.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180483","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184844.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184871","title":"Resolving EN related to paging priority","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: No need been identified in TS 23.501, 38.413 and paging cause is not used in EPS i.e. it is proposed to remove EN ' Editor's note: The need to send Paging Cause to (R)AN and UE is FFS '  If the UE (PDU Session) is registered in EPC, then the Network Triggered Service Request is executed as described in TS 23.401 [13], i.e. there is no need to describe the case in Network Triggered Service Request procedure of TS 23.502. Remove the EN.","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":17650,"status":"agreed","reservation_date":"2018-05-18 20:28:17","uploaded":"2018-05-22 12:49:04","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":409.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180488","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184871.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184930","title":"Fixes for HO Procedure - Handling MT Signaling from SMF.","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) It is proposed to clarify SMF behavior for both X2 and N2 HO. 2) It is proposed to update the Service operation with the necessary parameters for HO.","secretary_remarks":"Revised in parallel session to S2-186109.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17660,"status":"revised","reservation_date":"2018-05-21 01:29:23","uploaded":"2018-05-22 14:18:12","revisionof":"","revisedto":"S2-186109","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":417.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184930.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185028","title":"[DRAFT] Reply LS on SR in 5G","source":"Samsung Electronics Romania","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 thanks CT WG1 for the LS on SR in 5G and would like to provide the feedback","secretary_remarks":"Response to S2-184683. Revised in parallel session to S2-186107.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17580,"status":"revised","reservation_date":"2018-05-21 09:33:23","uploaded":"2018-05-21 10:08:42","revisionof":"","revisedto":"S2-186107","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185028.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185030","title":"Discussion on network control of always-on PDU session","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"discussion","for":"Agreement","abstract":"Discussion for incoming LS S2-184683","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":17570,"status":"noted","reservation_date":"2018-05-21 09:40:27","uploaded":"2018-05-21 10:08:42","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_127BIS_Newport_Beach\/Docs\/S2-185030.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185068","title":"Corrections in Service Request procedure","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Clarifies that security context is optional in N2 Request 2. RRC Reconfiguration is only needed if DRBs are established","secretary_remarks":"Merged into S2-186110","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-05-21 11:41:57","uploaded":"2018-05-22 11:34:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":444.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185068.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185087","title":"Mobility restrictions","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified that the Mobility Restrictions may restrict the mobility towards EPS.","secretary_remarks":"Revised in parallel session to S2-186113.","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-05-21 14:36:53","uploaded":"2018-05-22 13:57:31","revisionof":"","revisedto":"S2-186113","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":448.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185087.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185089","title":"PPD clarification with multiple QoS flows","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding text that configuration of several QoS flows due to PPD in UPF is to be used in RRC inactive, and that SMF may create several QoS flows from one PCC rule.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17750,"status":"postponed","reservation_date":"2018-05-21 14:44:08","uploaded":"2018-05-22 01:22:52","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":400.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185089.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185175","title":"TS 23.501 Update QFI binding Function","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Reword the sentence 'The SMF may configures the UPF in such a way that traffic with the same QoS but different paging differentiation requirements is transferred in different QoS Flows. In addition, the SMF may indicate over N2 to the NG-RAN the Paging Policy Indicator (PPI) for a QoS Flow (QFI) so that for a UE in RRC Inactive state the NG-RAN may enforce specific paging policies in the case of NG-RAN paging, based on 5QI, ARP and this PPI associated with the QFI of an incoming DL PDU'.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17760,"status":"postponed","reservation_date":"2018-05-22 01:54:15","uploaded":"2018-05-22 15:01:49","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":412.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185175.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185195","title":"Update of the Handover procedure considering the ongoing inter NG-RAN node handover","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the source-RAN node receives the downlink N2 signalling when the handover is ongong, the old NG-RAN node indicates the failure to the the NF (e.g. AMF or SMF) that generates such N2 downlink signalling.","secretary_remarks":"Revised in parallel session to S2-186122.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17680,"status":"revised","reservation_date":"2018-05-22 03:11:33","uploaded":"2018-05-22 14:28:20","revisionof":"","revisedto":"S2-186122","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":467.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185195.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185197","title":"Update of the Network Triggered Service Request procedure for some clarifications","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. The SMF determines the AMF and invokes the Namf_Communication_N1N2MessageTransfer to the AMF including the PDU Session ID associated with the N4 Session ID received in step 2a. 2. The AMF may include in the reject message an indication that the SMF needs not trigger the Namf_Communication_N1N2MessageTransfer Reques to the AMF, if the SMF has not subscribed to the event of the UE reachability. 3. Upon reception of an Namf_Communication_N1N2MessageTransfer response with an indication that its request has been temporarily rejected, the SMF shall start a locally configured guard timer and wait for any message to come from an AMF. Upon reception of a message from an AMF, the SMF shall re-invoke the Namf_Communication_N1N2MessageTransfer (with N2 SM info) to the AMF from which it received the message. Otherwise the SMF takes the step 3c at expiry of the guard timer. If the SMF decides that the control plane buffering applies, the SMF shall request UPF to start forwardin","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":17710,"status":"agreed","reservation_date":"2018-05-22 03:11:35","uploaded":"2018-05-22 14:28:20","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":468.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185197.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185258","title":"[DRAFT] Response LS on SR in 5G","source":"Qualcomm Korea","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1.  CC: SA WG6","secretary_remarks":"Response to S2-184683. Not Handled","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17640,"status":"not treated","reservation_date":"2018-05-22 06:13:49","uploaded":"2018-05-22 11:24:38","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG6","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185258.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185271","title":"Indirect Data forwarding for N2 HO","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - RRC transparent container indicates which DRB or QoS flows are subject to data forwarding. - Target NG-RAN allocates the data forwarding tunnel for the UE. - SMF requests UPF allocates the data forwarding tunnel according to the tunnel established by target NG-RAN.","secretary_remarks":"Revision of (Postponed) S2-184334 from S2#127. Revised in parallel session to S2-186106.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17540,"status":"revised","reservation_date":"2018-05-22 07:05:50","uploaded":"2018-05-22 11:24:38","revisionof":"S2-184334","revisedto":"S2-186106","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":342.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185271.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185423","title":"Mobility restrictions","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removed the 'under a given RAT' in relation to Forbidden area and Service area restrictions.","secretary_remarks":"Revised in parallel session to S2-186108.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17610,"status":"revised","reservation_date":"2018-05-22 11:55:00","uploaded":"2018-05-22 13:57:31","revisionof":"","revisedto":"S2-186108","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":448.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185423.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185450","title":"Clarifying use-cases of network triggered service request","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Added other NF as trigger for NT service request 2. Added the case that trigger can be an N1 message","secretary_remarks":"Revised in parallel session to S2-186111.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17720,"status":"revised","reservation_date":"2018-05-22 13:18:08","uploaded":"2018-05-22 14:31:01","revisionof":"","revisedto":"S2-186111","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":501.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185450.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185451","title":"Clarifying UE Reachability Notification Procedure","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Clarified the event reporting from reachability procedure. 2. Added URRP-AMF as an abbreviation 3. Event subscription by UDM does not have URRP-AMF as a paramter. So deleted that.","secretary_remarks":"Revised in parallel session to S2-186112.","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-05-22 13:18:08","uploaded":"2018-05-22 15:14:58","revisionof":"","revisedto":"S2-186112","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":502.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185451.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185505","title":"LS from RAN WG3: LS on  5G CM-Connected Mobility Restrictions","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 has been reviewing stage 2 specification of Mobility Restrictions in Section 5.3.4.1 of TS 23.501 and realised that Forbidden Areas can be configured per UE under a given RAT. While such is for sure possible to configure and signal, RAN WG3 is of the opinion that it introduces an unnecessary option, disregarding the fact that 5G TACs can be defined to contain E-UTRA and NR cells and global per RAT restrictions are possible to be indicated within the Mobility Restriction information anyhow. RAN WG3 asks SA WG2 to reconsider the introduction of the per RAT Forbidden Area. Action: RAN WG3 asks SA WG2 to reconsider the specification of Forbidden Areas under a given RAT and provide otherwise justification of this option.","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":17630,"status":"noted","reservation_date":"2018-05-27 13:46:18","uploaded":"2018-05-27 13:57:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, RAN WG2","lsoriginalls":"R3-183512","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185505.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186106","title":"Indirect Data forwarding for N2 HO","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - RRC transparent container indicates which DRB or QoS flows are subject to data forwarding. - Target NG-RAN allocates the data forwarding tunnel for the UE. - SMF requests UPF allocates the data forwarding tunnel according to the tunnel established by target NG-RAN.","secretary_remarks":"Revision of S2-185271. 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-05-31 14:31:08","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185271","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":342.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-180485","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186106.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186107","title":"[DRAFT] Reply LS on SR in 5G","source":"Samsung Electronics Romania","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 thanks CT WG1 for the LS on SR in 5G and would like to provide the feedback","secretary_remarks":"Revision of S2-185028. Revised in parallel session to S2-186173.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17590,"status":"revised","reservation_date":"2018-05-31 14:31:10","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185028","revisedto":"S2-186173","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186107.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186108","title":"Mobility restrictions","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removed the 'under a given RAT' in relation to Forbidden area and Service area restrictions.","secretary_remarks":"Revision of S2-185423. 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":17620,"status":"agreed","reservation_date":"2018-05-31 14:31:11","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185423","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":448.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180486","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186108.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186109","title":"Fixes for HO Procedure - Handling MT Signaling from SMF.","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) It is proposed to clarify SMF behavior for both X2 and N2 HO. 2) It is proposed to update the Service operation with the necessary parameters for HO.","secretary_remarks":"Revision of S2-184930. 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":17670,"status":"agreed","reservation_date":"2018-05-31 14:31:12","uploaded":"2018-06-02 18:27:54","revisionof":"S2-184930","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":417.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180485","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186109.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186111","title":"Clarifying use-cases of network triggered service request","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Added other NF as trigger for NT service request 2. Added the case that trigger can be an N1 message","secretary_remarks":"Revision of S2-185450. Revised in parallel session to S2-186172.","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":17730,"status":"revised","reservation_date":"2018-05-31 14:31:14","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185450","revisedto":"S2-186172","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":501.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186111.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186112","title":"Clarifying UE Reachability Notification Procedure","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Clarified the event reporting from reachability procedure. 2. Added URRP-AMF as an abbreviation 3. Event subscription by UDM does not have URRP-AMF as a paramter. So deleted that.","secretary_remarks":"Revision of S2-185451. 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-05-31 14:31:15","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185451","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":502.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180481","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186112.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186113","title":"Mobility restrictions","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified that the Mobility Restrictions may restrict the mobility towards EPS.","secretary_remarks":"Revision of S2-185087. 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-05-31 14:31:16","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185087","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":448.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180486","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186113.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186122","title":"Update of the Handover procedure considering the ongoing inter NG-RAN node handover","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the source-RAN node receives the downlink N2 signalling when the handover is ongong, the old NG-RAN node indicates the failure to the the NF (e.g. AMF or SMF) that generates such N2 downlink signalling.","secretary_remarks":"Revision of S2-185195. 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":17690,"status":"agreed","reservation_date":"2018-05-31 14:31:44","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185195","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":467.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180490","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186122.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186172","title":"Clarifying use-cases of network triggered service request","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Added other NF as trigger for NT service request 2. Added the case that trigger can be an N1 message","secretary_remarks":"Revision of S2-186111. 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":17740,"status":"agreed","reservation_date":"2018-06-02 16:42:50","uploaded":"2018-06-02 18:27:55","revisionof":"S2-186111","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":501.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180482","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186172.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186173","title":"Reply LS on SR in 5G","source":"SA WG2","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-186107. 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":17600,"status":"approved","reservation_date":"2018-06-02 16:42:51","uploaded":"2018-06-02 18:27:55","revisionof":"S2-186107","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-184683","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186173.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186303","title":"Clarification on single outstanding Service Request","source":"Intel, MediaTek Inc., T-Mobile USA","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Mobility Registration procedure: clarified that the UE can indicate in the PDU Sessions To Be Activated either PDU Sessions with pending uplink data or PDU Sessions that are configured to be used with always-on user plane resources. The PDU Sessions To Be Activated is used if there are pending data for at least one PDU Session.  Service Request procedure: clarified that the UE can indicate in the PDU Sessions To Be Activated either PDU Sessions with pending uplink data or PDU Sessions that are configured to be used with always-on user plane resources.","secretary_remarks":"Revision of S2-184340 from SA2#127. This CR was agreed","agenda_item_sort_order":26,"ainumber":"6.5.7.1","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":16581,"status":"agreed","reservation_date":"2018-06-05 11:33:09","uploaded":"2018-06-05 12:37:57","revisionof":"S2-184340","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":509.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180480","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186303.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]