[{"name":"S2-1811628","title":"LS from RAN WG2: LS on UE identity to calculate PF and PO in NR","source":"RAN WG2","contact":"Martin Van Der Zee","contact-id":58600,"tdoctype":"LS in","for":"Action","abstract":"For security\/privacy reasons RAN WG2 agreed to use the last 10 bits of the 5G-S-TMSI, instead of the IMSI, to calculate the Paging Frame (PF) and Paging Occasion (PO) to monitor paging in NR, as specified in section 7.1 in TS 38.304 (v15.1.0): The following parameters are used for the calculation of PF and i_s above: \u2026 UE_ID: 5G-S-TMSI mod 1024 \u2026 If the UE has no 5G-S-TMSI, for instance when the UE has not yet registered onto the network, the UE shall use as default identity UE_ID = 0 in the PF and i_s formulas above. 5G-S-TMSI is a 48 bit long bit string as defined in [10]. 5G-S-TMSI shall in the formulae above be interpreted as a binary number where the left most bit represents the most significant bit. Action: RAN WG2 kindly asks RAN WG3, SA WG2 and CT WG1 to take the RAN WG2 agreement into account.","secretary_remarks":"Postponed S2-1811228 from S2#129. Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13450,"status":"noted","reservation_date":"2018-11-10 08:27:14","uploaded":"2018-11-21 06:04:48","revisionof":"S2-1811228","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG2, CT WG1","Cc":"","lsoriginalls":"R2-1816046","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811628.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811660","title":"LS from CT WG1: Reply LS on agreements regarding UE behaviour in RRC_INACTIVE while going out-of-service","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks RAN WG2 for their LS on agreements regarding UE behaviour in RRC_INACTIVE while going out-of-service in R2-1816058\/ C1-186584. The RAN WG2 LS indicated the following agreements: Agreements 1 If the UE enters 'Any cell selection' the UE remains in RRC_INACTIVE 2 If the UE camps on an acceptable cell (i.e. 'Camped on any cell' state) the UE remains in RRC_INACTIVE, and then goes to IDLE when RNAU update timer expires or until the UE NAS initiates signalling. CT WG1 notes that aligning with the above agreements would mean considerable CT WG1 specification impacts with a very limited benefits, for the following reasons: The UE can move to any cell selection state only in the following situations: 1) If the current PLMN is part of the forbidden PLMNs list; or 2) If the current TAI is in of one of the 5GS forbidden tracking areas list. Case 1) above can only occur if the UE moves out of the registered PLMN and equivalent PLMN list, and in this case the UE will anyways move out of RRC_INACTIVE state as per current CT WG1 specification in TS 24.501 subclause 5.3.1.4. Thus above RAN WG2 agreement cannot be applied in this case. For case 2) above to occur, the UE will have to move out of the current registered TAI list and enter a TAI in one of the 5GS forbidden tracking areas list while also belonging to the registered PLMN which is a very rare case. Furthermore, in this rare case maintaining the UE in RRC_INACTIVE state is helpful only if the UE moves back to its registered TAI list before the RNAU update timer expires otherwise UE will move to IDLE mode. Additionally, since RRC _INACTIVE is part of 5GMM-CONNECTED mode in CT WG1 specification, and that in any cell state the UE is in limited service state at NAS, the RAN WG2 agreements above would also require the UE to be in 5GMM-CONNECTED mode while simultaneously be in limited service state, which is currently not supported by the 5G NAS state machine. Thus CT WG1 would strongly prefer that when the UE enters 'Any cell selection' and when the UE camps on an acceptable cell, the UE moves to idle mode immediately.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13210,"status":"noted","reservation_date":"2018-11-16 07:43:03","uploaded":"2018-11-21 06:07:13","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2","lsoriginalls":"C1-186851","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811660.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811665","title":"LS from CT WG1: Reply LS on inclusion of selected PLMN into the complete message","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks RAN WG2 for their LS on inclusion of selected PLMN into the complete message in R2-1813424\/C1-186303. CT WG1 has currently identified following issues, if AMF and UE-NAS layer are out of sync for selected PLMN ID: 1. If the AMF initiates authentication procedure, the AMF will use old allocated PLMN ID(say PLMN ID-1) whereas the UE will use the currently camped PLMN ID(say PLMN ID-2) in the calculation of Kamf. Thus authentication procedure will fail. 2. If the AMF initiates de-registration procedure with cause #11 assuming UE is on PLMN ID-1, whereas the UE is camped on PLMN ID-2 then the UE will move the PLMN ID-2 to the forbidden PLMN lists instead of PLMN ID-1. As a consequence of this UE will not try for service on PLMN ID-2. CT WG1 notes the following text from the RAN WG3 LS in C1-186657\/R3-186231: 'RAN WG3 has analysed the related scenarios and concluded that even though there is a possibility of a mismatch, the RAN is in full control of this possibility and can apply the same UE handling policies regardless of selected PLMN while the UE remains in RRC_INACTIVE. Furthermore, RAN can take appropriate actions if needed e.g. when configuring a new RNA in case of PLMN ambiguity. More generally, since the UE's RNA is a subset of the TAI list received from the 5GC, the RAN would not expect to apply differentiated handling within the TAI list, irrespective of PLMNs. RAN WG3 also understands that the mismatch is resolved as soon as the RAN moves the UE into RRC_CONNECTED.' CT WG1 understands from above text that RAN WG3 has resolved the UE and AMF out of sync issue for the selected PLMN ID without NAS layer involvement. Thus, no changes to CT WG1 specifications are required.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13230,"status":"noted","reservation_date":"2018-11-16 07:43:03","uploaded":"2018-11-21 06:07:13","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"SA WG2, SA WG3","lsoriginalls":"C1-186994","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811665.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811674","title":"LS from RAN WG3: Reply LS on inclusion of selected PLMN into the complete message","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks RAN WG2 for the received LS on inclusion of selected PLMN into the complete message. RAN WG3 understands from this LS that, in some cases of periodic or mobility RAN area update procedure, the RAN can send a UE immediately back to RRC_INACTIVE. Then if the RAN Notification Area includes multiple PLMNs, the serving PLMN in the UE context stored in the RAN could be different from the UE's selected equivalent PLMN. RAN WG3 has analysed the related scenarios and concluded that even though there is a possibility of a mismatch, the RAN is in full control of this possibility and can apply the same UE handling policies regardless of selected PLMN while the UE remains in RRC_INACTIVE. Furthermore, RAN can take appropriate actions if needed e.g. when configuring a new RNA in case of PLMN ambiguity. More generally, since the UE's RNA is a subset of the TAI list received from the 5GC, the RAN would not expect to apply differentiated handling within the TAI list, irrespective of PLMNs. RAN WG3 also understands that the mismatch is resolved as soon as the RAN moves the UE into RRC_CONNECTED. RAN WG3 therefore concludes that there are no significant impacts of this mismatch for RAN operation while the UE remains in RRC_INACTIVE.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13240,"status":"noted","reservation_date":"2018-11-16 07:43:04","uploaded":"2018-11-21 06:07:13","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1","Cc":"SA WG2","lsoriginalls":"R3-186231","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811674.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811676","title":"LS from RAN WG3: LS on rejected PDU sessions","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"1\/ RAN WG3 is finalizing the 5G intra-system handover and has decided that if the 5GC cannot accept some PDU sessions during the N2 handover the target NG-RAN node can deduce this if these PDU sessions are simply not included in the Handover Request message. However, RAN WG3 noticed that step 9 of section 4.9.1.3.2 of TS 23.502 mentions explicitly a 'list of non-accepted active PDU sessions' in the Handover Request message. If SA WG2 agrees, this can therefore be removed. 2\/ Besides, RAN WG3 noticed that the source NG-RAN node can also decide to not handover some PDU sessions. RAN WG3 would like to ask SA WG2 which use case(s) are considered for the above. Action: RAN WG3 kindly ask SA WG2 to remove the list of non-accepted PDU sessions from the Handover Request message in TS 23.502 if no show stopper is found and also to provide the use case(s) for source NG-RAN node to filter out some PDU sessions from an N2 handover.","secretary_remarks":"Response drafted in S2-1812304. Final response in S2-1813170","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13260,"status":"replied to","reservation_date":"2018-11-16 07:43:04","uploaded":"2018-11-21 06:07:13","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-186261","lsreply":"S2-1813170","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811676.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811843","title":"Selective deactivation for always-on PDU sessions","source":"NTT DOCOMO, LG Electronics, Ericsson","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Propose that the SMF shall not implement deactivation of UP connection to the Always-on PDU Session due to inactivity.","secretary_remarks":"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":13320,"status":"agreed","reservation_date":"2018-11-19 07:56:20","uploaded":"2018-11-20 13:59:55","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":699.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-181089","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811843.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811844","title":"Selective deactivation for always-on PDU sessions","source":"NTT DOCOMO, LG Electronics, Ericsson","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Propose that the SMF should not implement deactivation of UP connection to the Always-on PDU Session due to inactivity.","secretary_remarks":"Revised in parallel session to S2-1812929.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13330,"status":"revised","reservation_date":"2018-11-19 07:58:41","uploaded":"2018-11-20 13:59:55","revisionof":"","revisedto":"S2-1812929","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":817.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811844.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811868","title":"Requirements on 5G-TMSI randomness","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Requirements on randomness of the 5G-TMSI are added for 3GPP Access","secretary_remarks":"Revised in parallel session to S2-1812932.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13470,"status":"revised","reservation_date":"2018-11-19 10:08:02","uploaded":"2018-11-20 09:05:56","revisionof":"","revisedto":"S2-1812932","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":703.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811868.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811869","title":"5G-TMSI reallocation and RRC Inactive","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Steps 2c and 2d are added.","secretary_remarks":"Revised in parallel session to S2-1812933.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13510,"status":"revised","reservation_date":"2018-11-19 10:13:59","uploaded":"2018-11-20 12:23:52","revisionof":"","revisedto":"S2-1812933","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":818.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811869.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811871","title":"UE radio capability for paging information with NR and eLTE connected to the CN","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The above issues are solved, and the bullets are lettered to avoid errors following from the deletion of e.g. a hypen.","secretary_remarks":"Revision of S2-1810721 from S2-129. Revised in parallel session to S2-1812934.","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":"2018-11-19 10:18:40","uploaded":"2018-11-20 09:45:20","revisionof":"S2-1810721","revisedto":"S2-1812934","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":690.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811871.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812074","title":"Clarification on the mobility from 5GS RRC inactive state to EPS","source":"NTT DOCOMO INC.","contact":"Kenichiro Aoyagi","contact-id":73277,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the mobility from RRC inactivity state in 5GC to Idle mode in EPC and the source 5GC behaviout to release radio resources where the UE was in RRC inactive state","secretary_remarks":"Revised in parallel session to S2-1812935.","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":"2018-11-20 01:27:28","uploaded":"2018-11-20 06:30:19","revisionof":"","revisedto":"S2-1812935","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":833.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812074.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812130","title":"Indirect forwarding timer for N2 HO","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Move the start of timer for releasing indirect data forwarding tunnel from preparation phase to the execution phase","secretary_remarks":"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":13630,"status":"agreed","reservation_date":"2018-11-20 05:14:23","uploaded":"2018-11-20 05:17:51","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":838.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-181089","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812130.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812148","title":"TS 23.501: Always on Setting for the EBI allocated PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that for PDU session that support interworking with EPS with N26, always on indication is sent to UE by SMF during PDU session establishment, and the always on indication can be cancelled if all the EBI are revoked.","secretary_remarks":"Revised in parallel session to S2-1812930.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13390,"status":"revised","reservation_date":"2018-11-20 06:25:26","uploaded":"2018-11-20 14:57:01","revisionof":"","revisedto":"S2-1812930","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":721.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812148.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812149","title":"TS 23.502: Always on Setting for the EBI allocated PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that for PDU session that support interworking with EPS with N26, always on indication is sent to UE by SMF during PDU session establishment, and the always on indication can be cancelled if all the EBI(s) are revoked.","secretary_remarks":"Revised in parallel session to S2-1812931.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13430,"status":"revised","reservation_date":"2018-11-20 06:25:27","uploaded":"2018-11-20 14:57:01","revisionof":"","revisedto":"S2-1812931","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":844.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812149.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812159","title":"Discusson_Always on PDU","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"discussion","for":"Presentation","abstract":"Discussion on Always-on PDU Session","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13350,"status":"noted","reservation_date":"2018-11-20 06:30:59","uploaded":"2018-11-20 07:33:06","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_129BIS_West_Palm_Beach\/Docs\/S2-1812159.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812168","title":"Alignment for always-on PDU sessions-501","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introducing a new clause for always-on PDU sessions. In Rev 4: Clarify that always-on PDU session is only applied in 3GPP access. Clarify that UE does not request to activate always-on PDU session when UE initiates Registration and Service Request over non-3GPP access.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13360,"status":"noted","reservation_date":"2018-11-20 06:36:29","uploaded":"2018-11-20 07:33:06","revisionof":"S2-1811571","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":679.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812168.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812192","title":"Deletion of AN tunnel info from Handover Notify message in the EPS-to-5GS handover procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delete the AN tunnel info from Handover Notify message in the EPS-to-5GS handover procedure using N26 interface.","secretary_remarks":"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":13640,"status":"agreed","reservation_date":"2018-11-20 07:42:49","uploaded":"2018-11-20 14:59:39","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":848.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-181088","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812192.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812201","title":"Removal of PPI from N2 SM information","source":"CATT","contact":"Qiang Deng","contact-id":74509,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove PPI from the N2 SM information.","secretary_remarks":"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":13620,"status":"agreed","reservation_date":"2018-11-20 08:15:55","uploaded":"2018-11-20 08:45:47","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":849.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-181090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812201.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812239","title":"Discussion on Xn handover issue in network sharing case","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"discussion","for":"Discussion","abstract":"This paper would like to discuss the solutions to solve network sharing issue.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13650,"status":"noted","reservation_date":"2018-11-20 08:30:14","uploaded":"2018-11-20 09:22:59","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812239.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812286","title":"Non-accepted PDU session in N2 based HO","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - remove the 'list of non-accepted active PDU sessions' in step 9 in subclause 4.9.1.3.2. - move the 'non-accepted PDU session lists' from step 9 to step 12 in subclause 4.9.1.3.2. - clarify that The PDU Sessions failed to be seup list in step 12 includes the List Of PDU Sessions failed to be setup received from target RAN in step 10 and the Non-accepted PDU session List generated by the T-AMF.","secretary_remarks":"Revised in parallel session to S2-1812927.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13270,"status":"revised","reservation_date":"2018-11-20 09:20:02","uploaded":"2018-11-20 13:16:22","revisionof":"","revisedto":"S2-1812927","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":852.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812286.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812304","title":"[DRAFT] Reply LS on rejected PDU sessions","source":"Qualcomm Wireless GmbH","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. Attachments: CR0852","secretary_remarks":"Response to S2-1811676. Revised in parallel session to S2-1812928.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13290,"status":"revised","reservation_date":"2018-11-20 09:55:14","uploaded":"2018-11-20 13:16:22","revisionof":"","revisedto":"S2-1812928","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812304.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812341","title":"UE criteria to request always-on PDU session","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Always-on indication is added as a new parameter in the URSP, but the URSP update and maintenance framework is not affected. B1 and B2 style is applied on bullet items in clause 6.1.2.2.1 as an editorial correction.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13370,"status":"noted","reservation_date":"2018-11-20 11:00:03","uploaded":"2018-11-20 13:20:31","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":184.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812341.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812344","title":"Alignment for always-on PDU sessions-501","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introducing a new clause for always-on PDU sessions.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13380,"status":"noted","reservation_date":"2018-11-20 11:04:40","uploaded":"2018-11-20 13:20:31","revisionof":"S2-1811425","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":679.0,"crrevision":5.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812344.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812470","title":"LS from RAN WG3: Reply LS on UE identity to calculate PF and PO in NR","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks RAN WG2 for the LS on UE identity to calculate PF and PO in NR. RAN WG3 would like to confirm to RAN WG2 that RAN WG3 has already approved and implemented the changes needed in R3-185383 'Removal of UE Identity Index Value IE from Paging'.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13460,"status":"noted","reservation_date":"2018-11-21 14:45:10","uploaded":"2018-11-21 14:45:42","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2, CT WG1","lsoriginalls":"R3-187226","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812470.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812471","title":"LS from RAN WG3: Reply LS on inclusion of selected PLMN into the complete message","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 understands from the received CT WG1 LS that CT WG1 has identified NAS procedures which result in failures or undesirable outcomes, if initiated while UE is RRC_INACTIVE, and there is a PLMN mismatch between UE and AMF. Regarding the Action: requested of RAN WG3, i.e., CT WG1 kindly requests RAN WG3 to confirm that the UE and AMF out of sync issue for the selected PLMN ID is resolved without any NAS involvement as per the LS in C1-186657\/R3-186231. RAN WG3 would like to clarify that the previous response related only to operation and handling of the UE by the RAN while in RRC_INACTIVE, including periodic updates, and under the assumption that the mismatch would be resolved during the transition to connected. However, in the scenarios now provided by CT WG1, the transition to connected is triggered by reception of a Downlink NAS PDU in the RAN. The RAN initiates the resume procedure and becomes aware of the UE's selected PLMN on reception of msg5, but it is possible that the previously received NAS PDU is delivered to the UE, thereby leading to the scenarios described by CT WG1. RAN may be able to avoid this in some cases (e.g. in case of context relocation to a new NG-RAN node, the NAS PDU is not delivered and instead a NAS Non-Delivery procedure is triggered towards the AMF). However, RAN WG3 has not analysed the possible scenarios exhaustively, and therefore, RAN WG3 thinks it is safer for the mismatch to be pre-empted by UE procedures.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13250,"status":"noted","reservation_date":"2018-11-21 14:45:10","uploaded":"2018-11-21 14:45:42","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, RAN WG2","Cc":"SA WG2, SA WG3","lsoriginalls":"R3-187235","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812471.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812484","title":"LS from RAN WG2: LS on agreements regarding UE behaviour in RRC_INACTIVE while going out-of-service","source":"RAN WG2","contact":"Maurice Pope","contact-id":648,"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 in parallel session","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13220,"status":"noted","reservation_date":"2018-11-26 13:08:25","uploaded":"2018-11-26 13:09:02","revisionof":"","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_129BIS_West_Palm_Beach\/Docs\/S2-1812484.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812927","title":"Non-accepted PDU session in N2 based HO","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - remove the 'list of non-accepted active PDU sessions' in step 9 in subclause 4.9.1.3.2. - move the 'non-accepted PDU session lists' from step 9 to step 12 in subclause 4.9.1.3.2. - clarify that The PDU Sessions failed to be seup list in step 12 includes the List Of PDU Sessions failed to be setup received from target RAN in step 10 and the Non-accepted PDU session List generated by the T-AMF.","secretary_remarks":"Revision of S2-1812286. 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":13280,"status":"agreed","reservation_date":"2018-11-27 15:00:39","uploaded":"2018-12-03 14:18:42","revisionof":"S2-1812286","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":852.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-181089","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812927.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812928","title":"[DRAFT] Reply LS on rejected PDU sessions","source":"SA WG2","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. Attachments: S2-1812927","secretary_remarks":"Revision of S2-1812304. Revised in parallel session to S2-1813170.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13300,"status":"revised","reservation_date":"2018-11-27 15:00:40","uploaded":"2018-12-03 14:18:42","revisionof":"S2-1812304","revisedto":"S2-1813170","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812928.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812929","title":"Selective deactivation for always-on PDU sessions","source":"NTT DOCOMO, LG Electronics, Ericsson","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Propose that the SMF should not implement deactivation of UP connection to the Always-on PDU Session due to inactivity.","secretary_remarks":"Revision of S2-1811844. 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":13340,"status":"agreed","reservation_date":"2018-11-27 15:00:40","uploaded":"2018-12-03 14:18:43","revisionof":"S2-1811844","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":817.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-181090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812929.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812930","title":"TS 23.501: Always on Setting for the EBI allocated PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that for PDU session that support interworking with EPS with N26, always on indication is sent to UE by SMF during PDU session establishment, and the always on indication can be cancelled if all the EBI are revoked.","secretary_remarks":"Revision of S2-1812148. Revised in parallel session to S2-1813171.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13400,"status":"revised","reservation_date":"2018-11-27 15:00:41","uploaded":"2018-12-03 14:18:43","revisionof":"S2-1812148","revisedto":"S2-1813171","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":721.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812930.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812931","title":"TS 23.502: Always on Setting for the EBI allocated PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that for PDU session that support interworking with EPS with N26, always on indication is sent to UE by SMF during PDU session establishment, and the always on indication can be cancelled if all the EBI(s) are revoked.","secretary_remarks":"Revision of S2-1812149. Withdrawn","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13440,"status":"withdrawn","reservation_date":"2018-11-27 15:00:42","uploaded":"2018-12-03 14:18:43","revisionof":"S2-1812149","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":844.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812931.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812932","title":"Requirements on 5G-TMSI randomness","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Requirements on randomness of the 5G-TMSI are added for 3GPP Access","secretary_remarks":"Revision of S2-1811868. Revised in parallel session to S2-1813121.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13480,"status":"revised","reservation_date":"2018-11-27 15:00:43","uploaded":"2018-12-03 14:18:44","revisionof":"S2-1811868","revisedto":"S2-1813121","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":703.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812932.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812933","title":"5G-TMSI reallocation and RRC Inactive","source":"Vodafone, NEC","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Steps 2c and 2d are added.","secretary_remarks":"Revision of S2-1811869. Revised in parallel session to S2-1813123.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13520,"status":"revised","reservation_date":"2018-11-27 15:00:44","uploaded":"2018-12-03 14:18:44","revisionof":"S2-1811869","revisedto":"S2-1813123","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":818.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812933.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812934","title":"UE radio capability for paging information with NR and eLTE connected to the CN","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The above issues are solved, and the bullets are lettered to avoid errors following from the deletion of e.g. a hypen.","secretary_remarks":"Revision of S2-1811871. Revised in parallel session to S2-1813122.","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":"2018-11-27 15:00:45","uploaded":"2018-12-03 14:18:44","revisionof":"S2-1811871","revisedto":"S2-1813122","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":690.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812934.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812935","title":"Clarification on the mobility from 5GS RRC inactive state to EPS","source":"NTT DOCOMO INC.","contact":"Kenichiro Aoyagi","contact-id":73277,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the mobility from RRC inactivity state in 5GC to Idle mode in EPC and the source 5GC behaviout to release radio resources where the UE was in RRC inactive state","secretary_remarks":"Revision of S2-1812074. Revised in parallel session to S2-1813174.","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":"2018-11-27 15:00:46","uploaded":"2018-12-03 14:18:44","revisionof":"S2-1812074","revisedto":"S2-1813174","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":833.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812935.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813040","title":"5G-TMSI reallocation and RRC Inactive","source":"InterDigital","contact":"Maurice Pope","contact-id":648,"tdoctype":"CR","for":"Approval","abstract":"-","secretary_remarks":"Created at meeting. WITHDRAWN","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13550,"status":"withdrawn","reservation_date":"2018-11-28 19:58:38","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":731.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813121","title":"Requirements on 5G-TMSI randomness","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Requirements on randomness of the 5G-TMSI are added for 3GPP Access","secretary_remarks":"Revision of S2-1812932. Revised in parallel session to S2-1813172.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13490,"status":"revised","reservation_date":"2018-11-28 22:17:18","uploaded":"2018-12-03 14:25:09","revisionof":"S2-1812932","revisedto":"S2-1813172","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":703.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813121.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813122","title":"UE radio capability for paging information with NR and eLTE connected to the CN","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The above issues are solved, and the bullets are lettered to avoid errors following from the deletion of e.g. a hypen.","secretary_remarks":"Revision of S2-1812934. 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":"agreed","reservation_date":"2018-11-28 22:17:19","uploaded":"2018-12-03 14:25:10","revisionof":"S2-1812934","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":690.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-181090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813122.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813123","title":"5G-TMSI reallocation and RRC Inactive","source":"Vodafone, NEC","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Steps 2c and 2d are added.","secretary_remarks":"Revision of S2-1812933. Revised in parallel session to S2-1813173.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13530,"status":"revised","reservation_date":"2018-11-28 22:17:20","uploaded":"2018-12-03 14:25:10","revisionof":"S2-1812933","revisedto":"S2-1813173","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":818.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813123.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813170","title":"Reply LS on rejected PDU sessions","source":"SA WG2","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. Attachments: S2-1812927","secretary_remarks":"Revision of S2-1812928. 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":13310,"status":"approved","reservation_date":"2018-11-30 16:48:38","uploaded":"2018-12-03 14:25:35","revisionof":"S2-1812928","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1811676","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813170.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813171","title":"TS 23.501: Always on Setting for the EBI allocated PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that for PDU session that support interworking with EPS with N26, always on indication is sent to UE by SMF during PDU session establishment, and the always on indication can be cancelled if all the EBI are revoked.","secretary_remarks":"Revision of S2-1812930. Revised in parallel session to S2-1813175.","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13410,"status":"revised","reservation_date":"2018-11-30 16:48:38","uploaded":"2018-12-03 14:25:36","revisionof":"S2-1812930","revisedto":"S2-1813175","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":721.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813171.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813172","title":"Requirements on 5G-TMSI randomness","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Requirements on randomness of the 5G-TMSI are added for 3GPP Access","secretary_remarks":"Revision of S2-1813121. 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":13500,"status":"agreed","reservation_date":"2018-11-30 16:48:39","uploaded":"2018-12-03 14:25:36","revisionof":"S2-1813121","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":703.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-181090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813172.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813173","title":"5G-TMSI reallocation and RRC Inactive","source":"Vodafone, NEC","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Steps 2c and 2d are added.","secretary_remarks":"Revision of S2-1813123. 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":13540,"status":"agreed","reservation_date":"2018-11-30 16:48:40","uploaded":"2018-12-03 14:25:37","revisionof":"S2-1813123","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":818.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-181084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813173.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813174","title":"Clarification on the mobility from 5GS RRC inactive state to EPS","source":"NTT DOCOMO INC.","contact":"Kenichiro Aoyagi","contact-id":73277,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the mobility from RRC inactivity state in 5GC to Idle mode in EPC and the source 5GC behaviout to release radio resources where the UE was in RRC inactive state","secretary_remarks":"Revision of S2-1812935. WITHDRAWN","agenda_item_sort_order":24,"ainumber":"6.5.7","ainame":"3GPP access specific functionality and flows","tdoc_agenda_sort_order":13610,"status":"withdrawn","reservation_date":"2018-11-30 16:48:41","uploaded":null,"revisionof":"S2-1812935","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":833.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813175","title":"Always on Setting for the EBI allocated PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that for PDU session that support interworking with EPS with N26, always on indication is sent to UE by SMF during PDU session establishment, and the always on indication can be cancelled if all the EBI are revoked.","secretary_remarks":"Revision of S2-1813171. 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":13420,"status":"agreed","reservation_date":"2018-11-30 17:06:25","uploaded":"2018-12-03 14:28:23","revisionof":"S2-1813171","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":721.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-181084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813175.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]