[{"name":"S2-180008","title":"LS from RAN WG2: LS on details of network identifiers","source":"RAN WG2","contact":"Malik Wahaj Arshad","contact-id":72857,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 is currently standardizing E-UTRA connectivity to 5G CN, as outlined in the WID 'LTE connectivity to 5GCN', RP-171432. In RRC signalling in LTE, a set of 5G system identifiers will be included that are not specified by RAN WG2. This is in correspondence to RRC signalling when connected to 5GC: 1. 5G-S-TMSI - Used in RRC connection setup procedures and for paging. For E-UTRA connected to EPC, S-TMSI was a 40-bit long identifier. As some messages that includes S-TMSI are bit-constrained in terms of size, RAN WG2 would request CT WG4 to provide the length of 5G-S-TMSI along with its constituent identifiers including AMF Set ID, AMF Pointer and 5G-TMSI. RAN 2 would also request CT WG4 to provide the length of AMF Region ID. 2. In case E-UTRA connected to both EPC and 5GC, there would be UEs having either S-TMSI or 5G-S-TMSI in the same cell\/RAN. Considering a specific cell, if the S-TMSI allocated by EPC to one UE and 5G-S-TMSI allocated by 5GC to another UE have the same value and","secretary_remarks":"Postponed S2-178235 from SA WG2#124. Response drafted in S2-180687. Final response in S2-181262","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12260,"status":"replied to","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178235","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, SA WG2","Cc":"","lsoriginalls":"R2-1712068","lsreply":"S2-181262","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180008.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180020","title":"LS from RAN WG2: Reply LS on unified Access Control for 5G NR","source":"RAN WG2","contact":"Sudeep Palat","contact-id":63872,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks SA WG1 for the LS response on unified Access Control for 5G NR. RAN WG2 further discussed the attached SA WG1 CR and has some additional follow up questions. Q1: In the SA WG1 CR S1-173548, AC11-15 use the same category, i.e. Access category 1. RAN WG2 would like to check with SA WG1 if access barring needs to differentiate each of AC 11-15, similarly to handling of AC11-15 in LTE AC (e.g., one flag is signalled for each of AC11-15 for the network to prioritize AC11-15 over the other access categories). Q2: RAN WG2 would like to clarify whether both SMS and SMS over IP use same category 7. RAN WG2 would also like to check with SA WG1 whether different access barring behaviour needs to be supported for SMS and SMS over IP. Q3: RAN WG2 would like to ask SA WG1 if the UAC mechanism requires for AC11-15 UEs separate sets of barring control parameters associated to access attempts for MO data, MO signalling, MMTEL voice and MMTEL video, respectively (similar to that defined f","secretary_remarks":"Postponed S2-179126 from SA WG2#124. Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12210,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-179126","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"CT WG1, SA WG2, CT WG6","lsoriginalls":"R2-1714013","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180020.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180026","title":"LS from CT WG1: LS on session management congestion control","source":"CT WG1","contact":"Yanchao Kang","contact-id":72631,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has discussed the DNN based congestion control and S-NSSAI based congestion control. CT WG1 would like SA WG2 to answer the following questions: CT WG1 has noticed that the DNN based congestion control is very similar to the APN based congestion control in EPS system. Question 1: Shall the UE run the same timer for DNN based congestion control in 5GS and APN based congestion control in EPS? If yes, shall the UE keep the timer running upon inter-system change? Question 2: Can a network with slicing also apply DNN based congestion control, or will such network apply only S-NSSAI based congestion control? If a network with slicing can also apply DNN based congestion control, how does the SMF determine whether a DNN is congested for a UE when the UE has PDU sessions to that DNN via multiple slices? If a network with slicing can also apply DNN-based congestion control, please consider the following scenario: The UE attempts to establish a PDU session X with S-NSSAI#1 and a DNN#1 comb","secretary_remarks":"Responses drafted in S2-180238 and S2-180538. Final response in S2-181263","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12370,"status":"replied to","reservation_date":"2017-12-19 11:54:35","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-175379","lsreply":"S2-181263","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180026.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180027","title":"LS from CT WG1: LS on Mobility management congestion control","source":"CT WG1","contact":"Lalith Kumar","contact-id":60520,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has discussed the NAS level congestion control as captured in 3GPP TS 23.501, sub clause 5.19.7.2. CT WG1 is not clear for some of the requirements and hence request SA WG2 to answer following questions: Question 1: Is it possible that AMF can give Mobility Management back-off timer over non-3GPP access? Question 2: In case of the same PLMN for both 3GPP access and non-3GPP access, if Mobility Management back-off timer is running, is UE not allowed to initiate NAS signalling on both 3GPP access and non-3GPP access? Or is the Mobility Management back-off timer applicable per access on which UE received the timer? Question 3: If 3GPP access and non-3GPP access are connected to different core networks (different PLMNs) but those are ePLMNs, and if the Mobility Management back-off timer is running, is the UE not allowed to initiate NAS signalling on both 3GPP access and non-3GPP access? Or is the Mobility Management back-off timer applicable per access on which UE received the timer","secretary_remarks":"Responses drafted in S2-180237, S2-180358 and S2-180682. This LS was postponed. Revised at S2#126 in S2-181423.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12420,"status":"revised","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181423","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"C1-175413","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180027.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180032","title":"LS from CT WG4: Reply LS on PLMN and RAT selection policies for roaming","source":"CT WG4","contact":"Peter Schmitt","contact-id":13753,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 thanks CT WG1 for their reply LS on PLMN and RAT selection policies for roaming. CT WG4 has discussed the information provided in the CT WG1 and SA WG3 LS. CT WG4 would like to provide CT WG1 and SA WG3 feedback and provide input on: - The service in the HPLMN that will originate the steering of roaming messages. In CT WG4 understanding the list of preferred PLMN\/access technology combinations is part of the subscription data and therefore belongs to the UDM. From CT WG4 perspective, this is seen as a normal service offered by the UDM to the AMF, and will use the same service operations used for downloading and updating the user profile to the AMF. Whether these data need to be secured is seen as a decision which should be taken by SA WG3.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12500,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG3","Cc":"CT WG3, SA WG2","lsoriginalls":"C4-176362","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180032.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180033","title":"LS from CT WG6: LS on a potential USIM solution for PLMN and RAT selection policies for roaming","source":"CT WG6","contact":"Tim Evans","contact-id":49202,"tdoctype":"LS in","for":"Action","abstract":"In LS S2-175286, SA WG2 have defined the following new requirements for PLMN and RAT selection policies for roaming: - a control plane solution is used from the HPLMN to the UE. - VPLMN is able to relay this information to the UE. - VPLMN shall not be able to alter the information sent by the HPLMN; i.e. UE needs to be able to check the integrity of the information provided to it. - UE shall be able to detect if VPLMN alter or remove those information and act accordingly. CT WG6 would like to indicate that the existing mechanism for USIM OTA (defined in TS 31.115 and TS 31.116) and that provides integrity protection, cyphering and replay protection, is a generic protocol that can be adapted to many transports.The USIM OTA also allows the operator to immediately send a REFRESH command for steering of roaming (see TS 31.111) to trigger the steering of roaming procedure. CT WG6 would be happy to work with the relevant groups to extend the OTA transport to the control plane, if this become","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12510,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, CT WG1, CT WG4","Cc":"SA WG1","lsoriginalls":"C6-170696","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180033.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180035","title":"LS from RAN WG2: Reply LS on supported features by 5GC for E-UTRA connected to 5G CN","source":"RAN WG2","contact":"Manivannan Thyagarajan","contact-id":68484,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 would like to thank SA WG5 for the reply LS on supported features by 5GC for E-UTRA connected to 5G CN. RAN WG2 would like to point out that in the RAN WG2 reply LS R2-1712041 sent to RAN WG3 and copied to SA WG5 after the RAN WG2#99bis meeting it was already communicated that for LTE connected to 5GC, from pure radio interface perspective, MDT could be supported with the same functionality as that of LTE connected to EPC but MDT is not part of the Rel-15 NR WID scope. As for QMC streaming, from RAN WG2 point of view, the E-UTRA radio interface functionality for QMC streaming would be the same for EPC and 5GC and hence can be supported. It is up to other groups to indicate if it can be supported from their perspective.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12520,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"SA WG1, SA WG2, CT WG1, RAN WG3","lsoriginalls":"R2-1714203","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180035.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180044","title":"LS from SA WG1: Reply LS on requirements on unified access control for 5GS","source":"SA WG1","contact":"Betsy Covell","contact-id":68109,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks CT WG1 for their reply LS on unified Access Control for 5G NR. SA WG1 is pleased to provide the following clarifications. Question 1: In EPS, according to TS 22.011, a UE configured for EAB initiating an emergency call shall ignore any EAB information that is broadcast by the network. Is CT WG1's understanding correct that according to TS 22.261 the priority between access category 2 (delay tolerant service) and access category 3 (emergency) has been reverted, i.e. a UE configured for delay tolerant service initiating an emergency call shall use access category 2 (instead of 3)? SA WG1 reply 1: SA WG1 has agreed the attached CR which clarifies that the emergency access category takes precedence over the access category for a delay tolerant service. Question 2: What is the relationship between the terms 'configured for EAB' and 'configured for delay tolerant service'? Are they equivalent terms or are they referring to exactly the same configuration'? SA WG1 reply 2: SA WG1","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12200,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2, CT WG6, RAN WG2","lsoriginalls":"S1-174623","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180044.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180045","title":"LS from SA WG1: Reply LS on unified access control for 5G NR","source":"SA WG1","contact":"Krister S\u00e4llberg","contact-id":11978,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks RAN WG2 for their LS on unified access control for 5G System. SA WG1 provides answers below and informs that SA WG1 has agreed the attached CR. RAN WG2 Question 1: In the SA WG1 CR S1-173548, AC11-15 use the same category, i.e. Access category 1. RAN WG2 would like to check with SA WG1 if access barring needs to differentiate each of AC 11-15, similarly to handling of AC11-15 in LTE AC (e.g., one flag is signalled for each of AC11-15 for the network to prioritize AC11-15 over the other access categories). SA WG1 Response: SA WG1 has agreed to document this differently in the attached CR to make it clearer. In addition, SA WG1 see a need to extend to separately give priority handling for MPS and MCS respectively. RAN WG2 Question 2: RAN WG2 would like to clarify whether both SMS and SMS over IP use same category 7. RAN WG2 would also like to check with SA WG1 whether different access barring behaviour needs to be supported for SMS and SMS over IP. SA WG1 Response: SA WG1 d","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12220,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1, SA WG2, CT WG6","lsoriginalls":"S1-174624","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180045.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180057","title":"23.502: Clean-up of the registration procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. At registration: The SUPI may only be provided by the UE in case of an Emergency Registration 2. \u00a74.2.2.2.1:transform the EN 'Aspects related to dual registration in 3GPP and non-3GPP access is FFS' into a reference to \u00a74.12 3. \u00a74.2.2.2.2 step 14: If the serving NF removal reason indicated by the UDM is Initial Registration, then the old AMF does not invoke the Namf_EventExposure_Notify but invokes the Nsmf_PDUSession_ReleaseSMContext (SUPI, PDU Session ID) service operation towards all the associated SMFs  4. \u00a74.2.2.2.2 Step 18 : clarify that 'when the AMF has changed the new AMF notifies the SMF for each PDU sessions that it has taken over the responsibility of the signalling path towards the UE: the new AMF invokes the Nsmf_PDUSession_UpdateSMContext service operation using SMF information received from the old AMF at step 5. It also indicates whether the 'PDU Session(s) is to be re-activated' 5. \u00a74.2.2.2.2  requires miscellaneous corrections \/ clarifications;","secretary_remarks":"Revised, merging S2-180641 and S2-180660, to S2-181191.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12570,"status":"revised","reservation_date":"2018-01-06 09:27:41","uploaded":"2018-01-16 08:24:30","revisionof":"","revisedto":"S2-181191","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180057.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180101","title":"23.502: Resolution of ENs in Connection, Registration and Mobility Management procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following ENs are resolved: Editor's note: Aspects related to dual registration in 3GPP and non-3GPP access is FFS. Aspects for dual registration have been described in the registration call flow as well e.g. in 4.12.8. It is proposed to remove the EN and add a reference from 4.2.2.2.1 to 4.12.8.  Editor's note: It is FFS if HO attach indication is to be added. So far no need for handover indication been identified e.g. same AMF used for 3GPP and non-3GPP access. It is proposed to remove the EN.  Editor's note: It is FFS how UE Radio capabilities are provided.  Different cases exist, e.g. for Initial Registration and when the AMF does not have any UE Radio Capability stored, then the AMF should obtain the UE Radio Capability information by sending the N2 message (INITIAL CONTEXT SETUP REQUEST without UE Radio Capability information included to the NG-RAN. This triggers the NG-RAN to request the UE Radio Capability from the UE and upload it to the AMF in the N2 in","secretary_remarks":"Revised to S2-181192.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12600,"status":"revised","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 14:52:43","revisionof":"","revisedto":"S2-181192","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180101.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180104","title":"23.501: Idle and connected state terminology cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following terminology is applied:  - Idle mode and Connected mode changed to idle state and connected state, while using idle mode mobility and connected mode mobility. Some additional cleanup e.g. usage of dash and 'CM-'.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12680,"status":"approved","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-181617","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180104.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180105","title":"23.502: Idle and connected state terminology cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following terminology is applied:  - Idle mode and Connected mode changed to idle state and connected state, while using idle mode mobility and connected mode mobility. Some additional cleanup e.g. usage of dash and 'CM-'.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12690,"status":"approved","reservation_date":"2018-01-11 16:54:29","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-181629","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180105.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180115","title":"Requirements on EPC and 5GC Identifiers","source":"Cisco","contact":"Irfan Ali","contact-id":74090,"tdoctype":"discussion","for":"Agreement","abstract":"Discussing the requirements for the identifiers","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12300,"status":"noted","reservation_date":"2018-01-12 02:02:46","uploaded":"2018-01-16 01:34:49","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_125_Gothenburg\/Docs\/S2-180115.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180116","title":"23.501: Requirements on EPC and 5GC Identifiers","source":"Cisco","contact":"Irfan Ali","contact-id":74090,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Captures the requirements on EPC and 5GC Identifiers.","secretary_remarks":"Not Handled","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12310,"status":"not treated","reservation_date":"2018-01-12 02:02:46","uploaded":"2018-01-16 01:34:49","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180116.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180117","title":"[draft] Reply LS on details of network identifiers","source":"Cisco","contact":"Irfan Ali","contact-id":74090,"tdoctype":"LS out","for":"Approval","abstract":"Replies to RAN WG2 question that there is no collision in paging identities when eNB is connected to both EPC and 5GC","secretary_remarks":"Not Handled","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12320,"status":"not treated","reservation_date":"2018-01-12 02:02:46","uploaded":"2018-01-16 01:34:49","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180117.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180121","title":"23.501: AMF initiated DNN based congestion control","source":"Vivo","contact":"Yanchao Kang","contact-id":72631,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Upon receipt of the NAS Transport Error message including a back-off timer and the associated DNN, the UE will not send any NAS SM signalling for the specific DNN","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12490,"status":"noted","reservation_date":"2018-01-12 07:40:53","uploaded":"2018-01-16 08:55:21","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180121.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180237","title":"[Draft] Reply LS on Mobility management congestion control","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 answers to CT WG1 questions on NAS MM congestion control in LS S2-180027.","secretary_remarks":"Response to S2-180027. Merged into S2-181189","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12430,"status":"merged","reservation_date":"2018-01-14 21:18:22","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180237.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180238","title":"[Draft] Reply LS on session management congestion control","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 answers to CT WG1 questions on NAS SM congestion control in LS S2-180026.","secretary_remarks":"Response to S2-180026. Merged into S2-181188","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12380,"status":"merged","reservation_date":"2018-01-14 21:18:22","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180238.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180292","title":"23.502: 502: clarification UDR usage in MM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that UDM\/PCF may invoke UDR services are clarified.","secretary_remarks":"Revised to S2-181252.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12700,"status":"revised","reservation_date":"2018-01-15 10:13:02","uploaded":"2018-01-16 14:55:18","revisionof":"","revisedto":"S2-181252","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180292.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180299","title":"23.502: Clarification related to Subscription data type","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Alignment the descriptions with the Table 5.2.3.3.1-1 - Adding an new type 'Slice Selection Subscription data' into the Table 5.2.3.3.1-1  It can be used for the Registration with AMF re-allocation. Instead of getting whole subscription data, get  only information for slice selection. - Adding an additional field (UE context for a PDU session) for SMF Selection Subscription data into the  Table 5.2.3.3.1-1  It was an agreement during non-3GPP related session at SA#124 that the UE context for a PDU session  stored in UDM can be used for the H-SMF selection in HR roaming, in case of the handover to 3GPP  access from N3GPP access via different PLMN. - Adding an additional field (Static IP address\/prefix) for Session Management Subscription data into the  Table 5.2.3.3.1-1.","secretary_remarks":"Revised, merging S2-180471 and S2-180684, to S2-181190.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12530,"status":"revised","reservation_date":"2018-01-15 10:45:23","uploaded":"2018-01-16 10:46:05","revisionof":"","revisedto":"S2-181190","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180299.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180334","title":"23.501: UE specific DRX parameter negotiation between UE and AMF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revised to S2-181253.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12720,"status":"revised","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"S2-181253","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180334.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180335","title":"23.502: UE specific DRX parameter negotiaction between UE and AMF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revised to S2-181254.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12790,"status":"revised","reservation_date":"2018-01-15 13:20:29","uploaded":"2018-01-16 12:28:57","revisionof":"","revisedto":"S2-181254","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180335.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180358","title":"[DRAFT] Reply LS on Mobility management congestion control","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to CT WG1 LS in C1-175413\/S2-180027 on MM congestion control. This LS pertains to the handling of MM back-off timer across 3GPP systems","secretary_remarks":"Response to S2-180027 Revised, merging S2-180237 and S2-180682, to S2-181189.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12440,"status":"revised","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"S2-181189","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180358.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180416","title":"23.502: Clarifying setup of the security context in RAN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifying that AMF sets up the security context in RAN only when user plane resources are setup.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12820,"status":"noted","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180416.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180440","title":"23.502: Clarification on AMF behavior due to Subscriber Data Change in UDM","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add description and reference to clause 4.2.4.2, align the terminology used in clause 4.2.4.2 with clause 4.5.1. Add the Configured NSSAI into the UE Configuration Update Command message.","secretary_remarks":"Revised to S2-181251.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12660,"status":"revised","reservation_date":"2018-01-15 19:47:32","uploaded":"2018-01-16 03:12:54","revisionof":"","revisedto":"S2-181251","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180440.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180451","title":"23.502: Update to UCU and Registration procedure","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Deletion of indication that current 5G-GUTI is invalid from the AMF in UCU  2. Configured NSSAI may be included by the AMF in the UCU message","secretary_remarks":"Revised to S2-181200.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12640,"status":"revised","reservation_date":"2018-01-15 21:27:14","uploaded":"2018-01-16 14:36:58","revisionof":"","revisedto":"S2-181200","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180451.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180471","title":"23.502: SMF dynamically allocated subscription data","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 'SMF dynamically allocated subscription data' is defined to be accessed using Nudm_SDM service. At AMF registration to UDM, the AMF is required to read newly defined 'SMF dynamically allocated subscription data'.","secretary_remarks":"Merged into S2-181190","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12560,"status":"merged","reservation_date":"2018-01-15 23:43:16","uploaded":"2018-01-16 14:30:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180471.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180523","title":"5G System Temporary Identifier(s)","source":"Nokia, Nokia Shanghai Bell (Rapporteur)","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion paper is about analyzing the size of 5G System Temporary Identifier(s), considering also Option 5\/7 architecture, EPS Interworking.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12330,"status":"noted","reservation_date":"2018-01-16 04:57:56","uploaded":"2018-01-16 14:57:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180523.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180538","title":"DRAFT Reply LS on session management congestion control","source":"Qualcomm Europe Inc.(France)","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-180026 Revised, merging S2-180238, to S2-181188.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12390,"status":"revised","reservation_date":"2018-01-16 05:33:42","uploaded":"2018-01-16 11:31:38","revisionof":"","revisedto":"S2-181188","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180538.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180622","title":"23.502: UE context removal in UDM during deregistration procedure","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: SMF invoke Nudm_SDM_Unsubscribe and Nudm_UECM_Deregistration service operations at Step 5 for the UDM to remove the corresponding subscription and UE context.","secretary_remarks":"Revised in S2-180658","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12830,"status":"revised","reservation_date":"2018-01-16 08:32:33","uploaded":"2018-01-16 08:49:16","revisionof":"","revisedto":"S2-180658","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180622.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180625","title":"23.502: Removal of Nudm_UECM_DeregistrationNotification ACK message","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Nudm_UECM_DeregistrationNotification ACK is removed from the step 3. 2. Step 4 box is extended to the UDM side.","secretary_remarks":"Revised in S2-180660","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12860,"status":"revised","reservation_date":"2018-01-16 08:39:51","uploaded":"2018-01-16 08:49:16","revisionof":"","revisedto":"S2-180660","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180625.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180641","title":"23.501: Removal redundant text in Registration procedure","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove the redundant sentence","secretary_remarks":"Merged into S2-181191.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12620,"status":"merged","reservation_date":"2018-01-16 08:52:26","uploaded":"2018-01-16 10:21:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180641.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180642","title":"23.502: Alignment of Namf_MT_EnableUEReachability service operation","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove reference to clause 4.2.3.4 and clause 4.2.2.3.3. Remove the NEF,PCF,SMF,UDM from known consumers of Namf_MT_EnableUEReachability in table 5.2.2.1-1 and add SMSF.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12880,"status":"endorsed","reservation_date":"2018-01-16 08:52:26","uploaded":"2018-01-16 10:21:01","revisionof":"","revisedto":"S2-181540","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180642.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180644","title":"23.502: Clarification on PCF ID during AMF relocation","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In registration procedure a new trigger to perform Policy Association Establishment to the PCF is added. The PCF ID is added in UE context so it can be reused for handover.","secretary_remarks":"Merged in a 6.5.6 session into S2-180979.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12630,"status":"merged","reservation_date":"2018-01-16 08:52:26","uploaded":"2018-01-16 10:21:01","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180644.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180658","title":"23.502: UE context removal in UDM during deregistration procedure","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: SMF invoke Nudm_SDM_Unsubscribe and Nudm_UECM_Deregistration service operations at Step 5 for the UDM to remove the corresponding subscription and UE context.","secretary_remarks":"Revision of S2-180622 Revised to S2-181255.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12840,"status":"revised","reservation_date":"2018-01-16 09:18:19","uploaded":"2018-01-16 09:49:45","revisionof":"S2-180622","revisedto":"S2-181255","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180658.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180660","title":"23.502: Removal of Nudm_UECM_DeregistrationNotification ACK message","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Nudm_UECM_DeregistrationNotification ACK is removed from the step 3. 2. Step 4 box is extended to the UDM side.","secretary_remarks":"Revision of S2-180625. Merged into S2-181191","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12870,"status":"merged","reservation_date":"2018-01-16 09:22:19","uploaded":"2018-01-16 09:49:45","revisionof":"S2-180625","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180660.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180682","title":"[DRAFT] Reply LS on mobility management congestion control","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-180027. Merged into S2-181189","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12470,"status":"merged","reservation_date":"2018-01-16 09:38:20","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180682.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180683","title":"Network identifier issues for E-UTRA connected to EPC and 5GC","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"discussion","for":"Agreement","abstract":"This paper discusses network identifier issues for E-UTRA connected to EPC and 5GC based on the related LS from RAN WG2 in R2-1712068.","secretary_remarks":"Not Handled","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12360,"status":"not treated","reservation_date":"2018-01-16 09:43:21","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180683.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180687","title":"[DRAFT] Reply LS on details of network identifiers","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2","secretary_remarks":"Response to S2-180008 Revised to S2-181186.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12270,"status":"revised","reservation_date":"2018-01-16 09:47:02","uploaded":"2018-01-16 14:13:31","revisionof":"","revisedto":"S2-181186","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180687.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180693","title":"23.501: Use of identifiers for mobility between GERAN\/UTRAN and 5GS","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies that upon mobility to the 5G System the UE may use a 5G-GUTI in the Registration procedure if it has a valid 5G-GUTI.  NOTE: the use of identifiers for mobility from the 5G System is clarified in TS 23.060.","secretary_remarks":"Revised to S2-181256.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12890,"status":"revised","reservation_date":"2018-01-16 10:12:18","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"S2-181256","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180693.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180701","title":"Use of identifiers for mobility between GERAN\/UTRAN and 5GS","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that upon mobility from the 5G System the UE may use a P-TMSI in the GPRS Attach procedure if it has a valid P-TMSI.  NOTE: the use of identifiers for mobility to the 5G System is clarified in TS 23.501.","secretary_remarks":"Revised to S2-181257.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12910,"status":"revised","reservation_date":"2018-01-16 10:15:42","uploaded":"2018-01-16 14:50:35","revisionof":"","revisedto":"S2-181257","release":"Rel-15","crspec":23.06,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2035.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180701.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180710","title":"23.501: Clarification on NAS level congestion control","source":"LG Electronics","contact":"Sang Min Park","contact-id":62105,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Specified SMF's behaviour on notifying DNN congestion to the AMF.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12480,"status":"noted","reservation_date":"2018-01-16 11:14:06","uploaded":"2018-01-16 11:36:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180710.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180721","title":"23.501: Clarification on UE specific DRX parameter from old AMF to new AMF","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove description 'The UE specific DRX Parameters are sent from the old AMF to the new AMF as part of the MM context information during the AMF change mobility' in clause 5.4.5.","secretary_remarks":"Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12780,"status":"approved","reservation_date":"2018-01-16 12:05:51","uploaded":"2018-01-16 12:25:18","revisionof":"","revisedto":"S2-181496","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180721.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180724","title":"23.501: Management of service area restriction","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Service Area Restrictions that are sent to a UE consist of a single type of information, i.e., either Allowed Area or Non-Allowed Area.","secretary_remarks":"Revised to S2-181258.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12930,"status":"revised","reservation_date":"2018-01-16 12:10:46","uploaded":"2018-01-16 12:26:19","revisionof":"","revisedto":"S2-181258","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180724.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180744","title":"23.502: Update of Reachability procedures","source":"Lenovo, Motorola Mobility","contact":"Zhuoyun Zhang","contact-id":67292,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Adding step 2b in Figure 4.2.5.2-1. 2. Clarify step 4 in Figure 4.2.5.2-1. 3. Adding description of step 2b in clause 4.2.5.3.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12950,"status":"endorsed","reservation_date":"2018-01-16 12:58:15","uploaded":"2018-01-16 13:06:25","revisionof":"","revisedto":"S2-182229","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180744.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180750","title":"23.501: 5G-GUTI, 5G-S-TMSI definition and mapping rules","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Based on considerations in S2-1780523, we propose the following mapping rules: 1) MMEGI = AMF Region ID (no change here) 2) MMEC = AMF SET ID 3) M-TMSI = AMF Pointer + 5G-M-TMSI Furthermore, it has been agreed that S-TMSI is unique across AMF Sets thus the AMF pointer value can be stated as optional and this can help avoid GUTI reallocations by AMF.","secretary_remarks":"Revised to S2-181187.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12340,"status":"revised","reservation_date":"2018-01-16 13:55:54","uploaded":"2018-01-16 14:57:01","revisionof":"","revisedto":"S2-181187","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180750.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180760","title":"Discussion on Access and Congestion Control","source":"KPN N.V.","contact":"Toni Dimitrovski","contact-id":66437,"tdoctype":"discussion","for":"Discussion","abstract":"Access and Congestion Control","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12230,"status":"noted","reservation_date":"2018-01-16 14:33:49","uploaded":"2018-01-16 14:35:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180760.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180766","title":"23.501: Clarification of signalling with higher priority","source":"KPN","contact":"Toni Dimitrovski","contact-id":66437,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify UEs behaviour related to initiating higher priority signalling.","secretary_remarks":"Revised to S2-181185.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12240,"status":"revised","reservation_date":"2018-01-16 14:56:19","uploaded":"2018-01-16 14:59:55","revisionof":"","revisedto":"S2-181185","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180766.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181185","title":"23.501: Clarification of signalling with higher priority","source":"KPN","contact":"Toni Dimitrovski","contact-id":66437,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify UEs behaviour related to initiating higher priority signalling.","secretary_remarks":"Revision of S2-180766. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12250,"status":"approved","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180766","revisedto":"S2-182159","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181185.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181186","title":"[DRAFT] Reply LS on details of network identifiers","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2","secretary_remarks":"Revision of S2-180687. Revised to S2-181262.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12280,"status":"revised","reservation_date":"2018-01-24 10:28:34","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180687","revisedto":"S2-181262","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181186.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181187","title":"23.501: 5G-GUTI, 5G-S-TMSI definition and mapping rules","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Based on considerations in S2-1780523, we propose the following mapping rules: 1) MMEGI = AMF Region ID (no change here) 2) MMEC = AMF SET ID 3) M-TMSI = AMF Pointer + 5G-M-TMSI Furthermore, it has been agreed that S-TMSI is unique across AMF Sets thus the AMF pointer value can be stated as optional and this can help avoid GUTI reallocations by AMF.","secretary_remarks":"Revision of S2-180750. WITHDRAWN","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12350,"status":"withdrawn","reservation_date":"2018-01-24 13:38:23","uploaded":null,"revisionof":"S2-180750","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181188","title":"DRAFT Reply LS on session management congestion control","source":"SA WG2","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-180538, merging S2-180238. Revised to S2-181263.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12400,"status":"revised","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180538","revisedto":"S2-181263","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181188.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181189","title":"[DRAFT] Reply LS on Mobility management congestion control","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to CT WG1 LS in C1-175413\/S2-180027 on MM congestion control. This LS pertains to the handling of MM back-off timer across 3GPP systems","secretary_remarks":"Revision of S2-180358, merging S2-180237 and S2-180682. Revised to S2-181343.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12450,"status":"revised","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180358","revisedto":"S2-181343","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181189.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181190","title":"23.502: Clarification related to Subscription data type","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Alignment the descriptions with the Table 5.2.3.3.1-1 - Adding an new type 'Slice Selection Subscription data' into the Table 5.2.3.3.1-1  It can be used for the Registration with AMF re-allocation. Instead of getting whole subscription data, get  only information for slice selection. - Adding an additional field (UE context for a PDU session) for SMF Selection Subscription data into the  Table 5.2.3.3.1-1  It was an agreement during non-3GPP related session at SA#124 that the UE context for a PDU session  stored in UDM can be used for the H-SMF selection in HR roaming, in case of the handover to 3GPP  access from N3GPP access via different PLMN. - Adding an additional field (Static IP address\/prefix) for Session Management Subscription data into the  Table 5.2.3.3.1-1.","secretary_remarks":"Revision of S2-180299, merging S2-180471 and S2-180684. Revised to S2-181340.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12540,"status":"revised","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180299","revisedto":"S2-181340","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181190.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181191","title":"23.502: Clean-up of the registration procedure","source":"Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. At registration: The SUPI may only be provided by the UE in case of an Emergency Registration 2. \u00a74.2.2.2.1:transform the EN 'Aspects related to dual registration in 3GPP and non-3GPP access is FFS' into a reference to \u00a74.12 3. \u00a74.2.2.2.2 step 14: If the serving NF removal reason indicated by the UDM is Initial Registration, then the old AMF does not invoke the Namf_EventExposure_Notify but invokes the Nsmf_PDUSession_ReleaseSMContext (SUPI, PDU Session ID) service operation towards all the associated SMFs  4. \u00a74.2.2.2.2 Step 18 : clarify that 'when the AMF has changed the new AMF notifies the SMF for each PDU sessions that it has taken over the responsibility of the signalling path towards the UE: the new AMF invokes the Nsmf_PDUSession_UpdateSMContext service operation using SMF information received from the old AMF at step 5. It also indicates whether the 'PDU Session(s) is to be re-activated' 5. \u00a74.2.2.2.2  requires miscellaneous corrections \/ clarifications;","secretary_remarks":"Revision of S2-180057, merging S2-180641 and S2-180660. Revised to S2-181310.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12580,"status":"revised","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180057","revisedto":"S2-181310","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181191.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181192","title":"23.502: Resolution of ENs in Service Request procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following ENs are resolved: Editor's note: Aspects related to dual registration in 3GPP and non-3GPP access is FFS. Aspects for dual registration have been described in the registration call flow as well e.g. in 4.12.8. It is proposed to remove the EN and add a reference from 4.2.2.2.1 to 4.12.8.  Editor's note: It is FFS if HO attach indication is to be added. So far no need for handover indication been identified e.g. same AMF used for 3GPP and non-3GPP access. It is proposed to remove the EN.  Editor's note: It is FFS how UE Radio capabilities are provided.  Different cases exist, e.g. for Initial Registration and when the AMF does not have any UE Radio Capability stored, then the AMF should obtain the UE Radio Capability information by sending the N2 message (INITIAL CONTEXT SETUP REQUEST without UE Radio Capability information included to the NG-RAN. This triggers the NG-RAN to request the UE Radio Capability from the UE and upload it to the AMF in the N2 in","secretary_remarks":"Revision of S2-180101. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12610,"status":"approved","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180101","revisedto":"S2-181622","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181192.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181200","title":"23.502: Update to UCU and Registration procedure","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Deletion of indication that current 5G-GUTI is invalid from the AMF in UCU  2. Configured NSSAI may be included by the AMF in the UCU message","secretary_remarks":"Revision of S2-180451. Withdrawn in parallel session (not provided).","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12650,"status":"withdrawn","reservation_date":"2018-01-25 06:55:52","uploaded":null,"revisionof":"S2-180451","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181251","title":"23.502: Clarification on AMF behavior due to Subscriber Data Change in UDM","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add description and reference to clause 4.2.4.2, align the terminology used in clause 4.2.4.2 with clause 4.5.1. Add the Configured NSSAI into the UE Configuration Update Command message.","secretary_remarks":"Revision of S2-180440. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12670,"status":"approved","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180440","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181251.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181252","title":"23.502: 502: clarification UDR usage in MM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that UDM\/PCF may invoke UDR services are clarified.","secretary_remarks":"Revision of S2-180292. Endorsed in parallel session","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12710,"status":"endorsed","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180292","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181252.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181253","title":"23.501: UE specific DRX parameter negotiation between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revision of S2-180334. Revised to S2-181311.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12730,"status":"revised","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180334","revisedto":"S2-181311","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181253.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181254","title":"23.502: UE specific DRX parameter negotiaction between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revision of S2-180335. Revised to S2-181312.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12800,"status":"revised","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180335","revisedto":"S2-181312","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181254.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181255","title":"23.502: UE context removal in UDM during deregistration procedure","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: SMF invoke Nudm_SDM_Unsubscribe and Nudm_UECM_Deregistration service operations at Step 5 for the UDM to remove the corresponding subscription and UE context.","secretary_remarks":"Revision of S2-180658. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12850,"status":"approved","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180658","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181255.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181256","title":"23.501: Use of identifiers for mobility between GERAN\/UTRAN and 5GS","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifies that upon mobility to the 5G System the UE may use a 5G-GUTI in the Registration procedure if it has a valid 5G-GUTI.  NOTE: the use of identifiers for mobility from the 5G System is clarified in TS 23.060.","secretary_remarks":"Revision of S2-180693. Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12900,"status":"approved","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180693","revisedto":"S2-181506","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181256.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181257","title":"Use of identifiers for mobility between GERAN\/UTRAN and 5GS","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that upon mobility from the 5G System the UE may use a P-TMSI in the GPRS Attach procedure if it has a valid P-TMSI.  NOTE: the use of identifiers for mobility to the 5G System is clarified in TS 23.501.","secretary_remarks":"Revision of S2-180701. This CR was agreed","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12920,"status":"agreed","reservation_date":"2018-01-25 06:55:52","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180701","revisedto":"","release":"Rel-15","crspec":23.06,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2035.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181257.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181258","title":"23.501: Management of service area restriction","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Service Area Restrictions that are sent to a UE consist of a single type of information, i.e., either Allowed Area or Non-Allowed Area.","secretary_remarks":"Revision of S2-180724. Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12940,"status":"approved","reservation_date":"2018-01-25 06:55:53","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180724","revisedto":"S2-182088","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181258.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181262","title":"Reply LS on details of network identifiers","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2","secretary_remarks":"Revision of S2-181186. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12290,"status":"approved","reservation_date":"2018-01-25 06:56:08","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181186","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180008","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181262.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181263","title":"Reply LS on session management congestion control","source":"SA WG2","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-181188. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12410,"status":"approved","reservation_date":"2018-01-25 06:56:08","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181188","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-180026","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181263.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181310","title":"23.502: Clean-up of the registration procedure","source":"Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. At registration: The SUPI may only be provided by the UE in case of an Emergency Registration 2. \u00a74.2.2.2.1:transform the EN 'Aspects related to dual registration in 3GPP and non-3GPP access is FFS' into a reference to \u00a74.12 3. \u00a74.2.2.2.2 step 14: If the serving NF removal reason indicated by the UDM is Initial Registration, then the old AMF does not invoke the Namf_EventExposure_Notify but invokes the Nsmf_PDUSession_ReleaseSMContext (SUPI, PDU Session ID) service operation towards all the associated SMFs  4. \u00a74.2.2.2.2 Step 18 : clarify that 'when the AMF has changed the new AMF notifies the SMF for each PDU sessions that it has taken over the responsibility of the signalling path towards the UE: the new AMF invokes the Nsmf_PDUSession_UpdateSMContext service operation using SMF information received from the old AMF at step 5. It also indicates whether the 'PDU Session(s) is to be re-activated' 5. \u00a74.2.2.2.2  requires miscellaneous corrections \/ clarifications;","secretary_remarks":"Revision of S2-181191. Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12590,"status":"approved","reservation_date":"2018-01-25 14:56:48","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181191","revisedto":"S2-181455","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181310.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181311","title":"23.501: UE specific DRX parameter negotiation between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revision of S2-181253. Revised to S2-181341.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12740,"status":"revised","reservation_date":"2018-01-25 14:56:48","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181253","revisedto":"S2-181341","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181311.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181312","title":"23.502: UE specific DRX parameter negotiaction between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revision of S2-181254. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12810,"status":"approved","reservation_date":"2018-01-25 14:56:48","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181254","revisedto":"S2-181560","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181312.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181340","title":"23.502: Clarification related to Subscription data type","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Alignment the descriptions with the Table 5.2.3.3.1-1 - Adding an new type 'Slice Selection Subscription data' into the Table 5.2.3.3.1-1  It can be used for the Registration with AMF re-allocation. Instead of getting whole subscription data, get  only information for slice selection. - Adding an additional field (UE context for a PDU session) for SMF Selection Subscription data into the  Table 5.2.3.3.1-1  It was an agreement during non-3GPP related session at SA#124 that the UE context for a PDU session  stored in UDM can be used for the H-SMF selection in HR roaming, in case of the handover to 3GPP  access from N3GPP access via different PLMN. - Adding an additional field (Static IP address\/prefix) for Session Management Subscription data into the  Table 5.2.3.3.1-1.","secretary_remarks":"Revision of S2-181190. Agreed in parallel session. Block Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12550,"status":"approved","reservation_date":"2018-01-25 18:15:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181190","revisedto":"S2-181527","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181340.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181341","title":"23.501: UE specific DRX parameter negotiation between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revision of S2-181311. Revised to S2-181363.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12750,"status":"revised","reservation_date":"2018-01-25 18:15:27","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181311","revisedto":"S2-181363","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181341.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181343","title":"[DRAFT] Reply LS on Mobility management congestion control","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to CT WG1 LS in C1-175413\/S2-180027 on MM congestion control. This LS pertains to the handling of MM back-off timer across 3GPP systems","secretary_remarks":"Revision of S2-181189. This was postponed.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12460,"status":"postponed","reservation_date":"2018-01-25 18:15:39","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181189","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181343.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181363","title":"23.501: UE specific DRX parameter negotiation between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"Revision of S2-181341 For e-mail approval. e-mail revision 6 approved. Revised to S2-181395.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12760,"status":"revised","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181341","revisedto":"S2-181395","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181363.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181395","title":"TS 23.501: UE-specific DRX parameter negotiation between UE and AMF","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change 1: It is proposed that the UE specific DRX parameters shall be negotiated between UE and AMF in every registration procedure. If the UE decides to request for UE specific DRX parameters, the UE shall include a UE specific DRX parameters in the registration request message, and AMF determines the UE specific DRX parameters based on the UE request DRX parameters, UE mobility pattern, UE communication pattern, old UE specific DRX parameters, and operator policy. And then AMF sends the UE specific DRX parameters to UE. If the UE does not receive the UE specific DRX parameters information element in the registration accept message because the AMF rejected its request, the UE shall use the DRX cycle broadcasted by the RAN.  Change 2: If the old 'UE specific DRX Parameters' is received from the old AMF as part of the MM context during the AMF change mobility, the target AMF may use the old 'UE specific DRX Parameters' to derive the new 'UE specific DRX Parameters'.","secretary_remarks":"e-mail revision 6 of S2-181363. Approved","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12770,"status":"approved","reservation_date":"2018-02-02 10:04:24","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181363","revisedto":"S2-181559","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181395.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]