[{"name":"S2-1900048","title":"LS from RAN WG2: LS on agreements regarding UE behaviour in RRC_INACTIVE while going out-of-service","source":"RAN WG2","contact":"Alexander Sayenko","contact-id":47308,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 would like to thank CT WG1 for the feedback indicating that previous agreements would have caused considerable changes in CT WG1 specifications with limited benefits. Based on that, RAN WG2 has re-discussed UE behaviour and made the following agreements: Agreements 1 If the UE enters 'Any cell selection' the UE remains in RRC_INACTIVE 2 The UE goes to RRC_IDLE after camping on the acceptable cell (change to previous agreements). RAN WG2 understanding is that a UE can remain in RRC_INACTIVE state while searching for the suitable or acceptable cell (i.e. when a UE is in 'any cell selection' state) because cell search and cell re-selection actions are transparent to NAS. However, if a UE fails to find any suitable cell and finally camps on the acceptable cell, AS layer will move to RRC_IDLE and inform NAS about it. The resulting UE behaviour is captured in TS 38.304 and TS 38.331 (CRs attached)","secretary_remarks":"Noted","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13530,"status":"noted","reservation_date":"2018-12-20 06:41:15","uploaded":"2018-12-20 06:41:45","revisionof":"S2-1812484","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"R2-1818802","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900048.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900118","title":"Support of piggybacking of NAS SM message while configuring a DRB","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removes the NG-RAN requirement to wait with forwarding NAS message.","secretary_remarks":"Revised in parallel session to S2-1901089.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13540,"status":"revised","reservation_date":"2019-01-11 22:59:09","uploaded":"2019-01-15 02:50:05","revisionof":"","revisedto":"S2-1901089","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":879.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900118.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900119","title":"[DRAFT] LS on support of piggybacking of NAS message while configuring a DRB","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Informs that SA WG2 has updated 23.502 with regards to usage of piggybacking of NAS message while configuring a DRB","secretary_remarks":"Revised in parallel session to S2-1901090.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13560,"status":"revised","reservation_date":"2019-01-11 22:59:10","uploaded":"2019-01-15 02:50:05","revisionof":"","revisedto":"S2-1901090","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900119.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900398","title":"Correction on current HO procedures","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correspondingly, three changes are proposed: 1. the source-AMF determines the intra 5GS N2 handover or 5GS to EPS handover from the 'Target RAN ID', and the 'intra\/inter system handover indication' is removed. 2. the 'Direct Forwarding Path Availability' is include as a standalone IE of 'handover required message' for the 5GS to EPS handover using N26 interface. 3. the 'Service area restriction' is took away from 'N2 information', but included in the 'UE context information'.","secretary_remarks":"Revised in parallel session to S2-1901091.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13590,"status":"revised","reservation_date":"2019-01-15 01:55:59","uploaded":"2019-01-15 15:00:14","revisionof":"","revisedto":"S2-1901091","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":925.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900398.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900399","title":"Correction on secondary RAT data reporting procedure for HO","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Propose to modify Xn HO to clarify the HO flag is for AMF buffering purpose. 2. Propose to modify N2 HO to reflect that the RAN Usage data report is conducted during HO execution phase. With such modification, several steps in N2 HO are also changed. 3. Clarify that the RAN Usage data report is for a general HO procedure, not only for the specific X2 based HO.","secretary_remarks":"Revised in parallel session to S2-1901092.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13620,"status":"revised","reservation_date":"2019-01-15 01:56:01","uploaded":"2019-01-15 15:00:14","revisionof":"","revisedto":"S2-1901092","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":926.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900399.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900400","title":"Presence of Reference ID in Location Reporting Control","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Make the reference ID in location reporting control message mandatory.","secretary_remarks":"Revised in parallel session to S2-1901093.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13680,"status":"revised","reservation_date":"2019-01-15 01:56:02","uploaded":"2019-01-15 15:00:14","revisionof":"","revisedto":"S2-1901093","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":927.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900400.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900483","title":"Correction to Xn handover for network sharing_501","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifying that only the target PLMN ID pointing to same 5GC can be transferred to the target RAN via Xn interface.","secretary_remarks":"Revised in parallel session to S2-1901094.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13700,"status":"revised","reservation_date":"2019-01-15 07:32:54","uploaded":"2019-01-15 10:29:36","revisionof":"","revisedto":"S2-1901094","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":856.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900483.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900484","title":"Correction to Xn handover for network sharing_502","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Clarifying Xn handover with PLMN change is only applied to the scenario where the target PLMN points to same 5GC as the serving PLMN; 2. Clarifying N2 handover can be triggered if the target PLMN doesn't point to the same 5GC.","secretary_remarks":"Revised in S2-1901316","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13720,"status":"revised","reservation_date":"2019-01-15 07:32:55","uploaded":"2019-01-15 10:29:36","revisionof":"","revisedto":"S2-1901316","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":944.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900484.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900568","title":"Fixes for DC secondary RAT charging report procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce RAN report towards AMF Usage of HO flag is clarified Fix the message and the HO included within Nsmf_PDUSession_UpdateRequest. Update the section to 4.21.","secretary_remarks":"Revised in parallel session to S2-1901104.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13640,"status":"revised","reservation_date":"2019-01-15 10:16:42","uploaded":"2019-01-15 14:29:46","revisionof":"","revisedto":"S2-1901104","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":960.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900568.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900661","title":"UE presence in restricted area indication during inter NG-RAN node N2 based handover","source":"Nokia, Nokia Shanghai Bell","contact":"Yannick Lair","contact-id":76350,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a 'UE presence in restricted area indication' as input for Nsmf_PDUSession_UpdateSMContext. Also, UE location information should be removed since already covered by target ID. For Target ID, simply refer to Target ID as provided by S-RAN. Remove SMF causes from the reason for failure in the List Of PDU Sessions failed to be setup in Handover Request Acknowledge.","secretary_remarks":"Revised in parallel session to S2-1901103.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13740,"status":"revised","reservation_date":"2019-01-15 14:10:59","uploaded":"2019-01-15 14:59:56","revisionof":"","revisedto":"S2-1901103","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":982.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900661.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901089","title":"Support of piggybacking of NAS SM message while configuring a DRB","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removes the NG-RAN requirement to wait with forwarding NAS message.","secretary_remarks":"Revision of S2-1900118. Agreed in parallel session. This was Block approved","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13550,"status":"agreed","reservation_date":"2019-01-22 02:09:26","uploaded":"2019-01-28 09:47:52","revisionof":"S2-1900118","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":879.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190157","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901089.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901090","title":"[DRAFT] LS on support of piggybacking of NAS message while configuring a DRB","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Informs that SA WG2 has updated 23.502 with regards to usage of piggybacking of NAS message while configuring a DRB","secretary_remarks":"Revision of S2-1900119. Revised in parallel session to S2-1901314.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13570,"status":"revised","reservation_date":"2019-01-22 02:09:27","uploaded":"2019-01-28 09:47:52","revisionof":"S2-1900119","revisedto":"S2-1901314","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901090.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901091","title":"Correction on current HO procedures","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correspondingly, three changes are proposed: 1. the source-AMF determines the intra 5GS N2 handover or 5GS to EPS handover from the 'Target RAN ID', and the 'intra\/inter system handover indication' is removed. 2. the 'Direct Forwarding Path Availability' is include as a standalone IE of 'handover required message' for the 5GS to EPS handover using N26 interface. 3. the 'Service area restriction' is took away from 'N2 information', but included in the 'UE context information'.","secretary_remarks":"Revision of S2-1900398. Revised in parallel session to S2-1901219.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13600,"status":"revised","reservation_date":"2019-01-22 02:09:27","uploaded":"2019-01-28 09:47:52","revisionof":"S2-1900398","revisedto":"S2-1901219","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":925.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901091.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901092","title":"Correction on secondary RAT data reporting procedure for HO","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Propose to modify Xn HO to clarify the HO flag is for AMF buffering purpose. 2. Propose to modify N2 HO to reflect that the RAN Usage data report is conducted during HO execution phase. With such modification, several steps in N2 HO are also changed. 3. Clarify that the RAN Usage data report is for a general HO procedure, not only for the specific X2 based HO.","secretary_remarks":"Revision of S2-1900399. WITHDRAWN","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13630,"status":"withdrawn","reservation_date":"2019-01-22 02:09:28","uploaded":null,"revisionof":"S2-1900399","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":926.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901093","title":"Presence of Reference ID in Location Reporting Control","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Make the reference ID in location reporting control message mandatory.","secretary_remarks":"Revision of S2-1900400. Agreed in parallel session. This was Block approved","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13690,"status":"agreed","reservation_date":"2019-01-22 02:09:29","uploaded":"2019-01-28 09:47:52","revisionof":"S2-1900400","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":927.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190158","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901093.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901094","title":"Correction to Xn handover for network sharing_501","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifying that only the target PLMN ID pointing to same 5GC can be transferred to the target RAN via Xn interface.","secretary_remarks":"Revision of S2-1900483. Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13710,"status":"noted","reservation_date":"2019-01-22 02:09:31","uploaded":"2019-01-28 09:47:52","revisionof":"S2-1900483","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":856.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901094.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901103","title":"UE presence in restricted area indication during inter NG-RAN node N2 based handover","source":"Nokia, Nokia Shanghai Bell","contact":"Yannick Lair","contact-id":76350,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a 'UE presence in restricted area indication' as input for Nsmf_PDUSession_UpdateSMContext. Also, UE location information should be removed since already covered by target ID. For Target ID, simply refer to Target ID as provided by S-RAN. Remove SMF causes from the reason for failure in the List Of PDU Sessions failed to be setup in Handover Request Acknowledge.","secretary_remarks":"Revision of S2-1900661. Agreed in parallel session. This was Block approved","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13750,"status":"agreed","reservation_date":"2019-01-22 02:09:39","uploaded":"2019-01-28 09:47:53","revisionof":"S2-1900661","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":982.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190158","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901103.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901104","title":"Fixes for DC secondary RAT charging report procedure","source":"Nokia, Nokia Shanghai Bell, Huawei, HiSilicon","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce RAN report towards AMF Usage of HO flag is clarified Fix the message and the HO included within Nsmf_PDUSession_UpdateRequest. Update the section to 4.21.","secretary_remarks":"Revision of S2-1900568. Revised in parallel session to S2-1901215.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13650,"status":"revised","reservation_date":"2019-01-22 02:09:40","uploaded":"2019-01-28 09:47:53","revisionof":"S2-1900568","revisedto":"S2-1901215","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":960.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901104.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901215","title":"Fixes for DC secondary RAT charging report procedure","source":"Nokia, Nokia Shanghai Bell, Huawei, HiSilicon","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce RAN report towards AMF Usage of HO flag is clarified Fix the message and the HO included within Nsmf_PDUSession_UpdateRequest. Update the section to 4.21.","secretary_remarks":"Revision of S2-1901104. Revised in parallel session to S2-1901315.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13660,"status":"revised","reservation_date":"2019-01-24 13:06:49","uploaded":"2019-01-29 14:08:10","revisionof":"S2-1901104","revisedto":"S2-1901315","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":960.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901215.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901219","title":"Correction on current HO procedures","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correspondingly, three changes are proposed: 1. the source-AMF determines the intra 5GS N2 handover or 5GS to EPS handover from the 'Target RAN ID', and the 'intra\/inter system handover indication' is removed. 2. the 'Direct Forwarding Path Availability' is include as a standalone IE of 'handover required message' for the 5GS to EPS handover using N26 interface. 3. the 'Service area restriction' is took away from 'N2 information', but included in the 'UE context information'.","secretary_remarks":"Revision of S2-1901091. Agreed in parallel session. This was Block approved","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13610,"status":"agreed","reservation_date":"2019-01-24 13:06:53","uploaded":"2019-01-29 14:08:11","revisionof":"S2-1901091","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":925.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190158","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901219.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901314","title":"LS on support of piggybacking of NAS message while configuring a DRB","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, RAN WG2, RAN WG5. CC: RAN WG3. Attachments: S2-1901089","secretary_remarks":"Revision of S2-1901090. Agreed in parallel session This was Block approved","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13580,"status":"approved","reservation_date":"2019-01-24 13:07:43","uploaded":"2019-01-29 14:17:57","revisionof":"S2-1901090","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, RAN WG2, RAN WG5","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901314.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901315","title":"Fixes for DC secondary RAT charging report procedure","source":"Nokia, Nokia Shanghai Bell, Huawei, HiSilicon","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce RAN report towards AMF Usage of HO flag is clarified Fix the message and the HO included within Nsmf_PDUSession_UpdateRequest. Update the section to 4.21.","secretary_remarks":"Revision of S2-1901215. Agreed in parallel session. This was Block approved","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13670,"status":"agreed","reservation_date":"2019-01-24 13:07:43","uploaded":"2019-01-29 14:17:57","revisionof":"S2-1901215","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":960.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190158","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901315.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901316","title":"Correction to Xn handover for network sharing_502","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Clarifying Xn handover with PLMN change is only applied to the scenario where the target PLMN points to same 5GC as the serving PLMN; 2. Clarifying N2 handover can be triggered if the target PLMN doesn't point to the same 5GC.","secretary_remarks":"Revision of S2-1900484. Agreed in parallel session. This was Block approved","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13730,"status":"agreed","reservation_date":"2019-01-24 13:07:44","uploaded":"2019-01-29 14:17:57","revisionof":"S2-1900484","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":944.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190158","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901316.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]