[{"name":"S2-181423","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":"Postponed S2-180027 from S2#125. Responses drafted in S2-181462 and S2-182236. Final response in S2-182718","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13050,"status":"replied to","reservation_date":"2018-01-29 17:29:47","uploaded":"2018-02-01 17:35:41","revisionof":"S2-180027","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"C1-175413","lsreply":"S2-182718, S2-182718","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181423.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181438","title":"LS from CT WG1: LS on DNN or S-NSSAI based congestion control performed at AMF","source":"CT WG1","contact":"Lin Shu","contact-id":43310,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 is implementing DNN based congestion control (as specified in TS 23.501 subclause 5.19.7.3) and S-NSSAI based congestion control (as specified in TS 23.501 subclause 5.19.7.4) at stage 3. CT WG1 understand the DNN or S-NSSAI based congestion control are performed at the SMF over 5GSM layer. However, CT WG1 found the DNN or S-NSSAI based congestion control can be also performed at the AMF from below descriptions: 'The AMF may provide a NAS Transport Error message for the NAS Transport message carrying an SM message and in the NAS Transport Error message include a back-off timer and the associated DNN. While the back-off timer for the specific DNN is running, then the UE will not send any NAS messages for the specific DNN.' (TS 23.501 subclause 5.19.7.3) '- If an S-NSSAI is determined as congested, then the AMF may apply S-NSSAI based congestion control towards the UE, by providing an NAS Transport Error message for the NAS Transport message carrying the SM message and in the NAS","secretary_remarks":"Responses drafted in S2-181899, S2-182002, S2-182022 and S2-182097. Final response in S2-182865","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13130,"status":"replied to","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-02 14:51:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"C1-180743","lsreply":"S2-182865, S2-182865","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181438.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181439","title":"LS from CT WG1: Reply LS on PLMN and RAT selection policies for roaming","source":"CT WG1","contact":"Marianne Mohali","contact-id":36875,"tdoctype":"LS in","for":"Information","abstract":"In their LS, SA WG3 provided the following feedback: SA WG3 has already discussed S2-175286 and C1-173751 and concluded that these Liaison Statements have incomplete information for the USIM Steering of roaming mechanism. OTA messages can be sent at any time over SMS or data bearers (see 3GPP TS 31.111, 3GPP TS 31.115). These OTA messages can contain USIM Toolkit commands that are for immediate Action: (see 3GPP TS 31.116). The REFRESH - file update command can be issued which instructs the UE to take account of the new PLMN list immediately (available since Rel.99) or the REFRESH - Steering of Roaming which instructs the UE to perform a PLMN selection immediately taking a specific list of PLMN\/RATs into account (available since rel.8). Therefore, SA WG3 kindly requests CT WG1 to provide a detailed answer to the following question: Question from SA WG3: CT WG1 to inform SA WG3 the deficits of the OTA mechanism, as described above in regard to meeting the requirements. Answer from CT WG","secretary_remarks":"Response drafted in S2-182287. Final response in S2-182723","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13270,"status":"replied to","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-02 14:51:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"CT WG6, SA WG3LI, SA WG2, CT WG3, SA WG1","lsoriginalls":"C1-180761","lsreply":"S2-182723, S2-182723","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181439.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181449","title":"LS from RAN WG2: Reply LS on maximum idle mode DRX value","source":"RAN WG2","contact":"Brian Martin","contact-id":72959,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for their LS in S2-175192 entitled 'Reply LS on Supported features by 5GC for E-UTRA connected to 5G CN'. Based on the discussion, RAN WG2 would like to provide the following answers to the questions raised by SA WG2 in their LS. [SA WG2 Question]: SA WG2 would like to inform RAN WGs that SA WG2 is not working on any specific CN (5GC) enhancements related to support of extended DRX in the context of 5GS_ph1 WID. On a related topic, SA WG2 would like to ask RAN WG2 to answer the following question for system design related to IDLE mode DRX cycle: - What does RAN WG2 expect as a (maximum) DRX value for New Radio in rel-15? [RAN WG2 Response]: In the RAN WG2 NR ad-hoc 1801 RAN WG2 made the following agreements: - Idle mode\/inactive mode DRX cycle configuration in NR takes the default DRX cycle parameter in LTE as baseline. - The maximum idle\/inactive mode DRX value in NR is 2.56s. Action: RAN WG2 would like to request SA WG2 to take the above information","secretary_remarks":"Postponed 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":13300,"status":"postponed","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-02 14:51:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"R2-1801660","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181449.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181455","title":"Clean-up of the registration procedure","source":"Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","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 approved draftCR S2-181310. Revised to S2-182714.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13010,"status":"revised","reservation_date":"2018-01-30 12:05:34","uploaded":"2018-02-17 09:37:46","revisionof":"S2-181310","revisedto":"S2-182714","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181455.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181461","title":"Handling of MM back-off timer","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"discussion","for":"Agreement","abstract":"This paper discusses the questions raised by CT WG1, the scenarios at hand and suggests corresponding responses.","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":13080,"status":"noted","reservation_date":"2018-02-01 09:04:53","uploaded":"2018-02-20 12:15:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181461.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181462","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-1800027 on MM congestion control. This LS pertains to the handling of MM back-off timer across 3GPP systems","secretary_remarks":"Response to S2-181423. Merged into S2-182718.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13100,"status":"merged","reservation_date":"2018-02-01 09:04:53","uploaded":"2018-02-20 12:15:33","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_126_Montreal\/Docs\/S2-181462.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181463","title":"Handling of MM back-off timer for N3GPP Access","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is corrected that the MM back-off timer shall not trigger cell\/RAT\/Access Type\/PLMN change.","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":13090,"status":"agreed","reservation_date":"2018-02-01 09:04:53","uploaded":"2018-02-20 12:15:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":4.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181463.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181482","title":"LS from RAN WG3: LS on Extending TAC for NR and NG-RAN","source":"RAN WG3","contact":"Martin Israelsson","contact-id":2462,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 has agreed to introduce an extended TAC in NR and NG-RAN, to increase deployment flexibility for operators while maintaining backwards compatibility with existing network deployments. NGAP will support a CHOICE between the legacy TAC (2 octets) and the new extended TAC (3 octets) to be signaled within the TAI. A gNB supporting NR cells may use either the legacy TAC or the new extended TAC, while an en-gNB supporting LTE cells may only use the legacy TAC. Action: RAN WG3 asks RAN WG2 and SA WG2 groups to take the above into account and provide feedback.","secretary_remarks":"Postponed 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":13310,"status":"postponed","reservation_date":"2018-02-05 14:17:42","uploaded":"2018-02-05 15:20:40","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2","Cc":"-","lsoriginalls":"R3-180634","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181482.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181485","title":"LS from RAN WG3: LS on introducing explicit per-UE TNLA binding release in NGAP","source":"RAN WG3","contact":"Alexander Vesely","contact-id":10078,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 had discussion on introducing explicit per-UE TNLA binding release. Concerns have been raised by one company that applying the explicit per UE-TNLA binding release for a large number of UEs is likely for certain scenarios e.g. during an AMF planned removal, and this may result in substantial processing overload at the NG-RAN side. RAN WG3 would like to ask SA WG2 to provide feedback to this concern. If the concern is acknowledged by SA WG2, RAN WG3 would like SA WG2 to modify stage-2 to avoid such to happen, if needed. Action: RAN WG3 asks SA WG2 to provide feedback on the above.","secretary_remarks":"Response drafted in S2-181763. Final response in S2-182821","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13320,"status":"replied to","reservation_date":"2018-02-05 14:17:42","uploaded":"2018-02-05 15:20:40","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"R3-180646","lsreply":"S2-182821, S2-182821","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181485.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181496","title":"Clarification on UE specific DRX parameter from old AMF to new AMF","source":"Samsung","contact":"Sunghoon Kim","contact-id":59112,"tdoctype":"CR","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":"Revision of approved DraftCR S2-180721. 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":12860,"status":"agreed","reservation_date":"2018-02-06 06:45:13","uploaded":"2018-02-06 06:49:49","revisionof":"S2-180721","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":14.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181496.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181506","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 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 approved DraftCR S2-181256. 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":12890,"status":"agreed","reservation_date":"2018-02-06 17:32:31","uploaded":"2018-02-20 14:24:03","revisionof":"S2-181256","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":17.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181506.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181527","title":"Clarification related to Subscription data type","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Alignment the descriptions in the corresponding procedures with the Table 5.2.3.3.1-1 - Adding the new type 'Slice Selection Subscription data' into the Table 5.2.3.3.1-1 \u00e8 It can be used for the Registration with AMF re-allocation. Instead of getting whole subscription data, get only information for slice selection. - Adding the new type 'UE context in SMF data' into the Table 5.2.3.3.1-1 \u00e8 It was an agreement during non-3GPP relatd 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 (Stactic IP address\/prefix) for Session Management Subscription data into the Table 5.2.3.3.1-1","secretary_remarks":"Revision of approved DraftCR S2-181340. 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":13030,"status":"agreed","reservation_date":"2018-02-08 05:52:31","uploaded":"2018-02-13 06:11:31","revisionof":"S2-181340","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":32.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180101","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181527.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181540","title":"Alignment of Namf_MT_EnableUEReachability service operation","source":"ZTE,China Mobile","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","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. Further changes: remove the step number","secretary_remarks":"Revision of endorsed DRAFTCR S2-180642. 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":13040,"status":"agreed","reservation_date":"2018-02-11 10:24:35","uploaded":"2018-02-19 08:11:28","revisionof":"S2-180642","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":37.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180102","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181540.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181543","title":"AMF Load Re-Balancing for CONNECTE UE","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Similar to mechanism defined for AMF management, with UDSF deployment, the new AMF obtain the UE context from UDSF. Without UDSF deployment, the old AMF move the UE context to specific targt AMF in the same AMF set. 2) For UE(s) in CONNECTED mode, after the it receives redirection request from AMF, 5G-AN considers this as a request to release the NGAP-UE-TNLA-binding with the corresponding AMF for the respective UE(s) while maintaining N3 (user plane connectivity) and UE context information. For subsequent N2 message, the 5G-AN should select the specific target AMF (provided by the original AMF) or a different AMF from the same AMF set and forward the subsequent N2 message.","secretary_remarks":"Revised to S2-182725.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13370,"status":"revised","reservation_date":"2018-02-11 10:32:01","uploaded":"2018-02-19 08:11:28","revisionof":"","revisedto":"S2-182725","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":25.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181543.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181559","title":"UE-specific DRX parameter negotiation between UE and AMF","source":"Huawei, HiSilicon, Ericsson, MediaTek Inc.","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the following parts: 1. If the UE wants to use UE specific DRX parameters, the UE shall include its preferred values consistently in every Initial Registration and Mobility Registration procedure. 2. The AMF shall determine Accepted DRX parameters based on the received UE specific DRX parameters and the AMF should accept the UE requested values, but subject to operator policy the AMF may change the UE requested values. The AMF shall respond to the UE with the Accepted DRX parameters. 3. The UE shall apply the DRX cycle broadcast in the cell bv the RAN unless it has received Accepted DRX parameters from the AMF in which case the UE shall apply either the DRX cycle broadcast in the cell or the Accepted DRX parameters, as defined in TS 38.304 [50] and TS 36.304 [52]. 4. The Periodic Registration procedure does not change the UE's DRX settings.","secretary_remarks":"Revision of approved DRAFTCR S2-181395. 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":12870,"status":"agreed","reservation_date":"2018-02-12 12:50:43","uploaded":"2018-02-12 14:00:59","revisionof":"S2-181395","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":31.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180091","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181559.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181560","title":"UE-specific DRX parameter negotiation between UE and AMF","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the following parts: 1. In Initial Registration and Mobility Registration Update, UE provides the UE Requested DRX parameters, as defined in clause 5.4.5 of TS 23.501 [2]. 2. In Registration Accept message, the Accepted DRX parameters are defined in clause 5.4.5 of TS 23.501 [2].","secretary_remarks":"Revision of approved DRAFTCR S2-181312. 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":12880,"status":"agreed","reservation_date":"2018-02-12 12:50:44","uploaded":"2018-02-12 14:00:59","revisionof":"S2-181312","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":47.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180091","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181560.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181617","title":"Idle and connected state terminology cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","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":"Revision of approved DRAFTCR S2-180104. 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":12900,"status":"agreed","reservation_date":"2018-02-13 13:58:26","uploaded":"2018-02-20 01:46:36","revisionof":"S2-180104","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":50.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180091","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181617.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181623","title":"Editorial correction to section 4.12.8","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Consolidate steps 4 and 5 in step 3 to match the corresponding figure","secretary_remarks":"Revision of approved DRAFTCR S2-180928. 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":12910,"status":"agreed","reservation_date":"2018-02-13 14:33:23","uploaded":"2018-02-20 14:34:49","revisionof":"S2-180928","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":66.0,"crrevision":"","crcategory":"D","tsg_crp":"SP-180096","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181623.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181629","title":"Idle and connected state terminology cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","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":"Revision of approved DRAFTCR S2-180105. 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":12920,"status":"agreed","reservation_date":"2018-02-13 15:02:05","uploaded":"2018-02-20 01:46:36","revisionof":"S2-180105","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":72.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180091","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181629.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181658","title":"UE mobility event notification","source":"Samsung, Nokia, Nokia Shanghai Bell","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: First change. New clause (5.3.X) for UE mobility event notification (by AMF) under 5.3 Registration Management and Connection Management 5.3.X UE mobility event notification (by AMF) New description for UE mobility event notification. Second change. New clause (5.4.X) for NG-RAN location reporting under 5.4 3GPP Specific 5.4.X NG-RAN location reporting Abstract description for NG-RAN location reporting based on request type 1) one-time precise reporting 2) continue reporting whenever UE changes cells 3) reporting for UE presence in Area or Interest Third change. Change '5.6.1 UE Location reporting notification' \u00e0 '5.6.11 UE mobility event notification usage by SMF' - Removed redundant description for UE mobility event notification from 5.6.11 Fourth change. Change on 5.6.5 Support of local area data network - Removed redundant description for AMF behaviors and SMF subscription - Removed the description for RRC inactive state support to the 5.3.X Fifth change. An ad","secretary_remarks":"Revised to S2-182726.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13410,"status":"revised","reservation_date":"2018-02-14 07:48:12","uploaded":"2018-02-20 08:48:33","revisionof":"","revisedto":"S2-182726","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":64.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181658.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181695","title":"Clarification for S-NSSAI based congestion Control","source":"Intel","contact":"Puneet Jain","contact-id":36283,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies all the scenarios when S-NSSAI congestion control back-off timer should be stopped. Few editorial corrections.","secretary_remarks":"Revised to S2-182719.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13140,"status":"revised","reservation_date":"2018-02-15 06:23:30","uploaded":"2018-02-20 06:31:54","revisionof":"","revisedto":"S2-182719","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":72.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181695.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181719","title":"Non-Allowed Area as criterion for Cell Reselection or trigger for PLMN Selection","source":"Intel, Nokia, Nokia Shanghai Bell","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to clarify that entering a Non-Allowed Area shall not be used by the UE as a criterion for Cell Reslection or trigger for PLMN or Selection.","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":13450,"status":"agreed","reservation_date":"2018-02-16 12:26:36","uploaded":"2018-02-20 14:24:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":76.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180098","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181719.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181762","title":"TNL A Binding Release","source":"Nokia, Nokia Shanghai Bell, AT&T, NTT DOCOMO, Verizon","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"discussion","for":"Approval","abstract":"TNL A Binding Release","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":13330,"status":"noted","reservation_date":"2018-02-18 01:44:38","uploaded":"2018-02-20 14:31:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181762.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181763","title":"Reply LS on introducing explicit per-UE TNLA binding release in NGAP","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on introducing explicit per-UE TNLA binding release in NGAP","secretary_remarks":"Response to S2-181485. Revised to S2-182724.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13340,"status":"revised","reservation_date":"2018-02-18 01:44:38","uploaded":"2018-02-20 14:31:19","revisionof":"","revisedto":"S2-182724","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181763.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181764","title":"GUTI unique across AMFs in an AMF SET","source":"Nokia, Nokia Shanghai Bell, Verizon, AT&T, Telecom Italia, NTT DOCOMO","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Explicitly state that the 5G-GUTI, 5G-S-TMSI can be unique across AMFs within an AMF SET. This is in fact a requirement to support AMF resiliency specified in stage 2. Add the missing deployment option.","secretary_remarks":"Revised to S2-182772.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13500,"status":"revised","reservation_date":"2018-02-18 01:44:38","uploaded":"2018-02-20 14:31:19","revisionof":"","revisedto":"S2-182772","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":89.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181764.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181889","title":"5GS Temporary Identifiers and mapping - Requirements","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Approval","abstract":"Analysing the size and structure of 5G System Temporary Identifier(s) and proposing the requirements.","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":13530,"status":"noted","reservation_date":"2018-02-19 13:34:47","uploaded":"2018-02-20 14: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_126_Montreal\/Docs\/S2-181889.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181890","title":"5GS Temporary Identifiers and mapping - solution proposal","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Approval","abstract":"Based on the requirements the 5GS Temporary Identifiers need to fulfil, proposing a solution.","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":13540,"status":"noted","reservation_date":"2018-02-19 13:34:47","uploaded":"2018-02-20 14: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_126_Montreal\/Docs\/S2-181890.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181891","title":"5GS Temporary Identifiers and mapping","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that multiple AMF Set IDs and\/or AMF Pointers may be used by an AMF. Changing the AMF Region ID and AMF Set ID mapping to MMEGI and MMEC.","secretary_remarks":"This was postponed 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":13550,"status":"postponed","reservation_date":"2018-02-19 13:34:47","uploaded":"2018-02-20 15:30:38","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":114.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181891.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181892","title":"[DRAFT] LS on 5GS Temporary Identifiers and mapping","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"LS out on 5GS Temporary 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":13560,"status":"not treated","reservation_date":"2018-02-19 13:34:48","uploaded":"2018-02-20 14:34:49","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181892.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181895","title":"Correction of used Registration Type","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Re-use the Mobility Registration Update when the UE needs to update its capabilities or protocol parameters.","secretary_remarks":"Revised to S2-182727.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13460,"status":"revised","reservation_date":"2018-02-19 13:34:50","uploaded":"2018-02-20 14:34:49","revisionof":"","revisedto":"S2-182727","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":160.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181895.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181899","title":"[DRAFT] Reply LS on DNN or S-NSSAI based congestion control performed at AMF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Proposed LS reply on DNN or S-NSSAI based congestion control performed at AMF","secretary_remarks":"Response to S2-181438. Revised, merging S2-182002, S2-182022 and S2-182097, to S2-182722.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13210,"status":"revised","reservation_date":"2018-02-19 13:34:52","uploaded":"2018-02-20 14:41:24","revisionof":"","revisedto":"S2-182722","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_126_Montreal\/Docs\/S2-181899.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181977","title":"Correction of UDR usage in MM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The flows that UDM may invoke UDR services are clarified in MM related procedures.","secretary_remarks":"Revised to S2-182774.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13610,"status":"revised","reservation_date":"2018-02-19 17:15:32","uploaded":"2018-02-20 14:54:50","revisionof":"","revisedto":"S2-182774","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":170.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181977.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181992","title":"Clarification on the management of service area restrictions","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification on RAN handling for service area restriction when UE is in CM-CONNECTED state. It is proposed to remove the service area restriction in Handover restriction list sent to the RAN.","secretary_remarks":"Revised to S2-182728.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13480,"status":"revised","reservation_date":"2018-02-19 19:06:58","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"S2-182728","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":125.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181992.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-181996","title":"Clarification on NAS-MM protocol","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 8.2.2.1, delete the EN and add a new use cases for NAS-MM protocol transmission.","secretary_remarks":"Withdrawn 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":13640,"status":"withdrawn","reservation_date":"2018-02-19 19:07:02","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":127.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181996.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182000","title":"Mapping between 4G GUTI and 5G GUTI","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 5G and maps to 4G ","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":13600,"status":"not treated","reservation_date":"2018-02-19 19:07:06","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":128.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182000.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182002","title":"[DRAFT] LS Response on DNN or S-NSSAI based congestion control performed at AMF","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"LS out","for":"Approval","abstract":"This is a proposed LS to CT WG1 responding to their request regarding DNN or S-NSSAI based congestion control performed at AMF","secretary_remarks":"Response to S2-181438. Merged into S2-182722.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13240,"status":"merged","reservation_date":"2018-02-19 19:07:07","uploaded":"2018-02-20 14:52:59","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_126_Montreal\/Docs\/S2-182002.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182003","title":"Correction for congestion control","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: DNN\/S-NSSAI based congestion control is applicable at the AMF when the OAM activates it for particular DNN\/S-NSSAI.","secretary_remarks":"Revised to S2-182720.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13160,"status":"revised","reservation_date":"2018-02-19 19:07:07","uploaded":"2018-02-20 14:52:59","revisionof":"","revisedto":"S2-182720","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":129.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182003.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182022","title":"[DRAFT] Reply LS on DNN or S-NSSAI based congestion control performed at AMF","source":"InterDigital Communications","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-181438. Merged into S2-182722.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13250,"status":"merged","reservation_date":"2018-02-19 20:54:42","uploaded":"2018-02-20 14:08:56","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_126_Montreal\/Docs\/S2-182022.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182038","title":"Service Request - AS Security Setup","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to add AS security setup for Service request. Some considerations on doing it in step 3 versus step 12: 1) Providing the AS security context in step 12 could incur a delay (i.e. steps 4 to 11 have to be executed) if RAN needs to perform RRC release with redirection prior to step 12. 2) In step 3, we have the information necessary to configure AS security context. AMF can also provide HRL (handover restriction list). 3) In step 12, it is sufficient to provide PDU session (UP related) context. Thus it is proposed to provide AS secuirty context in step 3. AMF can also provide HRL at this point. In step 12, only PDU session (UP related) context is included.","secretary_remarks":"Revised to S2-182775.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13650,"status":"revised","reservation_date":"2018-02-20 00:14:03","uploaded":"2018-02-20 14:31:19","revisionof":"","revisedto":"S2-182775","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":190.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182038.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182060","title":"Clarification on AMF behaviour due to Subscriber Data Change in UDM - TS 23.502","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","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.","secretary_remarks":"Revised to S2-182717.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13060,"status":"revised","reservation_date":"2018-02-20 03:08:42","uploaded":"2018-02-20 03:56:02","revisionof":"","revisedto":"S2-182717","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":195.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182060.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182088","title":"Management of service area restriction","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"CR","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 approved DRAFTCR S2-181258. Revised to S2-182713.","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-02-20 04:20:49","uploaded":"2018-02-20 08:42:27","revisionof":"S2-181258","revisedto":"S2-182713","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":144.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182088.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182092","title":"Clarification on TAI list assignment for different 5G RATs","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 5G-RAT is replaced by 3GPP access, and the text is rephrased accordingly: The 5G System shall support allocating a single TAI List over different 3GPP accesses.","secretary_remarks":"Revised to S2-182776.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13690,"status":"revised","reservation_date":"2018-02-20 04:35:46","uploaded":"2018-02-20 08:42:27","revisionof":"","revisedto":"S2-182776","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":145.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182092.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182097","title":"[DRAFT] Reply LS on DNN or S-NSSAI based congestion control performed at AMF","source":"Qualcomm Europe Inc.(Italy)","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-181438. Merged into S2-182722.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13260,"status":"merged","reservation_date":"2018-02-20 05:13:14","uploaded":"2018-02-20 05:34:49","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_126_Montreal\/Docs\/S2-182097.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182102","title":"Clarification of SM congestion control","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Back-off timer for a DNN congestion control is applied to the specific APN when UE moves from 5GS to EPS. - Back-off timer for a S-NSSAI and back-off timer for a combination of S-NSSAI and DNN does not apply to any APN ESM procedure when UE moves from 5GS to EPS.","secretary_remarks":"Revised to S2-182721.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13190,"status":"revised","reservation_date":"2018-02-20 05:22:13","uploaded":"2018-02-20 05:34:49","revisionof":"","revisedto":"S2-182721","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":149.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182102.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182111","title":"UE context removal in UDM during deregistration procedure","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Adding that 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. 2. Adding that AMF invoke Nudm_SDM_Unsubscribe at Step 6 for the UDM to remove the corresponding subscription.","secretary_remarks":"Revision of approved DRAFTCR S2-181255. Revised to S2-182715.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12970,"status":"revised","reservation_date":"2018-02-20 06:35:24","uploaded":"2018-02-20 09:09:31","revisionof":"","revisedto":"S2-182715","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":209.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/s2-182111.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182159","title":"Clarification of signalling with higher priority","source":"KPN","contact":"Toni Dimitrovski","contact-id":66437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the higher priority signaling in congestion control.","secretary_remarks":"Revision of approved DRAFTCR S2-181185. Agreed in parallel session. Revised to S2-183006.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12960,"status":"revised","reservation_date":"2018-02-20 08:56:14","uploaded":"2018-02-20 09:02:33","revisionof":"S2-181185","revisedto":"S2-183006","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":162.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182159.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182170","title":"Local deactivation of MICO mode for emergency services","source":"Vivo","contact":"RAN YUE","contact-id":69629,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Delete the requirement for the UE to request deactivation of MICO mode via Registration procedure while the UE is in CM-CONNECTED state after PDU Establishment procedure for Emergency Services is completed. 2. Mandete the UE and network to deactivate MICO mode upon the establishment of PDU session for emergency services.","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":13400,"status":"noted","reservation_date":"2018-02-20 09:17:14","uploaded":"2018-02-20 09:39:47","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":163.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182170.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182171","title":"Notification response","source":"Vivo","contact":"RAN YUE","contact-id":69629,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. For notification message sent over 3GPP access, correct the UE responses and corresponding AMF behavior when re-activation of PDU session over 3GPP allowed and not allowed by UE policy. 2. For notification message sent over non-3GPP access, correct the UE responses and corresponding AMF behavior when 3GPP access is available and not available.","secretary_remarks":"This was 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":13740,"status":"withdrawn","reservation_date":"2018-02-20 09:17:15","uploaded":"2018-02-20 09:39:47","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":222.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182171.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182178","title":"Usage of Unified access control in priority mechanisms","source":"KPN","contact":"Toni Dimitrovski","contact-id":66437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Fixing the references and usage of Access Classes to Access Identities and Access class barring to Unified access control.","secretary_remarks":"Revised, merging S2-181979, to S2-182777.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13720,"status":"revised","reservation_date":"2018-02-20 09:22:33","uploaded":"2018-02-20 09:26:47","revisionof":"","revisedto":"S2-182777","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":165.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182178.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182229","title":"Update of Reachability procedrues","source":"Lenovo, Motorola Mobility","contact":"Zhuoyun Zhang","contact-id":67292,"tdoctype":"CR","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":"Revision of endorsed DRAFTCR S2-180744. Revised to S2-182716.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12990,"status":"revised","reservation_date":"2018-02-20 10:57:15","uploaded":"2018-02-20 11:12:53","revisionof":"S2-180744","revisedto":"S2-182716","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":230.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182229.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182236","title":"[DRAFT] Reply LS on mobility management congestion control","source":"Qualcomm Japan Inc","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-181423. Revised, merging S2-181462, to S2-182718.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13110,"status":"revised","reservation_date":"2018-02-20 12:08:32","uploaded":"2018-02-20 14:25:00","revisionof":"","revisedto":"S2-182718","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_126_Montreal\/Docs\/S2-182236.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182287","title":"[DRAFT] Reply LS on PLMN and RAT selection policies for roaming","source":"SA WG2","contact":"Maria-Cruz Bartolome","contact-id":44824,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, SA WG3. CC: CT WG6, SA WG3LI, CT WG3, SA WG1","secretary_remarks":"LATE DOC: Response to S2-181439. Revised to S2-182723.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13280,"status":"revised","reservation_date":"2018-02-25 21:45:49","uploaded":"2018-03-05 11:17:54","revisionof":"","revisedto":"S2-182723","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG3","Cc":"CT WG6, SA WG3LI, CT WG3, SA WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182287.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182713","title":"Management of service area restriction","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"CR","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-182088. Revised to S2-182966.","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":"revised","reservation_date":"2018-02-28 02:03:28","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182088","revisedto":"S2-182966","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":144.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182713.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182714","title":"Clean-up of the registration procedure","source":"Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","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-181455. 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":13020,"status":"agreed","reservation_date":"2018-02-28 02:03:28","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181455","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180101","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182714.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182715","title":"UE context removal in UDM during deregistration procedure","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Adding that 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. 2. Adding that AMF invoke Nudm_SDM_Unsubscribe at Step 6 for the UDM to remove the corresponding subscription.","secretary_remarks":"Revision of S2-182111. 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":12980,"status":"agreed","reservation_date":"2018-02-28 02:03:29","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182111","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":209.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180106","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182715.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182716","title":"Update of Reachability procedrues","source":"Lenovo, Motorola Mobility","contact":"Zhuoyun Zhang","contact-id":67292,"tdoctype":"CR","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":"Revision of S2-182229. 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":13000,"status":"agreed","reservation_date":"2018-02-28 02:03:30","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182229","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":230.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180106","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182716.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182717","title":"Clarification on AMF behaviour due to Subscriber Data Change in UDM","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","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.","secretary_remarks":"Revision of S2-182060. 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":13070,"status":"agreed","reservation_date":"2018-02-28 02:03:31","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182060","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":195.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180106","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182717.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182718","title":"Reply LS on mobility management congestion control","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-182236, merging S2-181462. 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":13120,"status":"approved","reservation_date":"2018-02-28 02:03:32","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182236","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-181423","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182718.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182719","title":"Clarification for S-NSSAI based congestion Control","source":"Intel","contact":"Puneet Jain","contact-id":36283,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies all the scenarios when S-NSSAI congestion control back-off timer should be stopped. Few editorial corrections.","secretary_remarks":"Revision of S2-181695. 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":13150,"status":"agreed","reservation_date":"2018-02-28 02:03:32","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181695","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":72.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180098","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182719.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182720","title":"Correction for congestion control","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: DNN\/S-NSSAI based congestion control is applicable at the AMF when the OAM activates it for particular DNN\/S-NSSAI.","secretary_remarks":"Revision of S2-182003. Revised in parallel session to S2-182819.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13170,"status":"revised","reservation_date":"2018-02-28 02:03:34","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182003","revisedto":"S2-182819","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":129.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182720.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182721","title":"Clarification of SM congestion control","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Back-off timer for a DNN congestion control is applied to the specific APN when UE moves from 5GS to EPS. - Back-off timer for a S-NSSAI and back-off timer for a combination of S-NSSAI and DNN does not apply to any APN ESM procedure when UE moves from 5GS to EPS.","secretary_remarks":"Revision of S2-182102. 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":13200,"status":"agreed","reservation_date":"2018-02-28 02:03:35","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182102","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":149.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180100","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182721.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182722","title":"[DRAFT] Reply LS on DNN or S-NSSAI based congestion control performed at AMF","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-181899, merging S2-182002, S2-182022 and S2-182097. Revised to S2-182865.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13220,"status":"revised","reservation_date":"2018-02-28 02:03:36","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181899","revisedto":"S2-182865","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_126_Montreal\/Docs\/S2-182722.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182723","title":"Reply LS on PLMN and RAT selection policies for roaming","source":"SA WG2","contact":"Maria-Cruz Bartolome","contact-id":44824,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG6, SA WG3-LI, SA WG3, CT WG3, SA WG1","secretary_remarks":"Revision of S2-182287. 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":13290,"status":"approved","reservation_date":"2018-02-28 02:03:36","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182287","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-181439","lsto":"CT WG1","Cc":"CT WG6, SA WG3-LI, SA WG3, CT WG3, SA WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182723.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182724","title":"Reply LS on introducing explicit per-UE TNLA binding release in NGAP","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on introducing explicit per-UE TNLA binding release in NGAP","secretary_remarks":"Revision of S2-181763. Revised in parallel session to S2-182821.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13350,"status":"revised","reservation_date":"2018-02-28 02:03:36","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181763","revisedto":"S2-182821","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182724.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182725","title":"AMF Load Re-Balancing for CONNECTE UE","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Similar to mechanism defined for AMF management, with UDSF deployment, the new AMF obtain the UE context from UDSF. Without UDSF deployment, the old AMF move the UE context to specific targt AMF in the same AMF set. 2) For UE(s) in CONNECTED mode, after the it receives redirection request from AMF, 5G-AN considers this as a request to release the NGAP-UE-TNLA-binding with the corresponding AMF for the respective UE(s) while maintaining N3 (user plane connectivity) and UE context information. For subsequent N2 message, the 5G-AN should select the specific target AMF (provided by the original AMF) or a different AMF from the same AMF set and forward the subsequent N2 message.","secretary_remarks":"Revision of S2-181543. Revised to S2-182891.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13380,"status":"revised","reservation_date":"2018-02-28 02:03:36","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181543","revisedto":"S2-182891","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":25.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182725.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182726","title":"UE mobility event notification","source":"Samsung, Nokia, Nokia Shanghai Bell, LG Electronics","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: First change. New clause (5.3.X) for UE mobility event notification (by AMF) under 5.3 Registration Management and Connection Management 5.3.X UE mobility event notification (by AMF) New description for UE mobility event notification. Second change. New clause (5.4.X) for NG-RAN location reporting under 5.4 3GPP Specific 5.4.X NG-RAN location reporting Abstract description for NG-RAN location reporting based on request type 1) one-time precise reporting 2) continue reporting whenever UE changes cells 3) reporting for UE presence in Area or Interest Third change. Change '5.6.1 UE Location reporting notification' \u00e0 '5.6.11 UE mobility event notification usage by SMF' - Removed redundant description for UE mobility event notification from 5.6.11 Fourth change. Change on 5.6.5 Support of local area data network - Removed redundant description for AMF behaviors and SMF subscription - Removed the description for RRC inactive state support to the 5.3.X Fifth change. An ad","secretary_remarks":"Revision of S2-181658. Revised in parallel session, merging S2-181510, to S2-182820.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13420,"status":"revised","reservation_date":"2018-02-28 02:03:37","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181658","revisedto":"S2-182820","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":64.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182726.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182727","title":"Correction of used Registration Type","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Re-use the Mobility Registration Update when the UE needs to update its capabilities or protocol parameters.","secretary_remarks":"Revision of S2-181895. 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":13470,"status":"agreed","reservation_date":"2018-02-28 02:03:38","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181895","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":160.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182727.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182728","title":"Clarification on the management of service area restrictions","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification on RAN handling for service area restriction when UE is in CM-CONNECTED state. It is proposed to remove the service area restriction in Handover restriction list sent to the RAN.","secretary_remarks":"Revision of S2-181992. Withdrawn (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":13490,"status":"withdrawn","reservation_date":"2018-02-28 02:03:39","uploaded":null,"revisionof":"S2-181992","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":125.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182772","title":"GUTI unique across AMFs in an AMF SET","source":"Nokia, Nokia Shanghai Bell, Verizon, AT&T, Telecom Italia, NTT DOCOMO","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Explicitly state that the 5G-GUTI, 5G-S-TMSI can be unique across AMFs within an AMF SET. This is in fact a requirement to support AMF resiliency specified in stage 2. Add the missing deployment option.","secretary_remarks":"Revision of S2-181764. Revised to S2-182963.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13510,"status":"revised","reservation_date":"2018-02-28 21:27:47","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181764","revisedto":"S2-182963","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":89.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182772.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182773","title":"[DRAFT] LS on 5G-S-TMSI code space","source":"SA WG2","contact":"Peter Hedman","contact-id":27550,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3. CC: CT WG1, CT WG4. Attachments: S2-181889","secretary_remarks":"Created in parallel session. Revised to S2-182895.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13570,"status":"revised","reservation_date":"2018-02-28 21:27:48","uploaded":"2018-03-05 11:37:53","revisionof":"","revisedto":"S2-182895","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"CT WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182773.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182774","title":"Correction of UDR usage in MM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The flows that UDM may invoke UDR services are clarified in MM related procedures.","secretary_remarks":"Revision of S2-181977. Revised to S2-182893.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13620,"status":"revised","reservation_date":"2018-02-28 21:27:48","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181977","revisedto":"S2-182893","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":170.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182774.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182775","title":"Service Request - AS Security Setup","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to add AS security setup for Service request. Some considerations on doing it in step 3 versus step 12: 1) Providing the AS security context in step 12 could incur a delay (i.e. steps 4 to 11 have to be executed) if RAN needs to perform RRC release with redirection prior to step 12. 2) In step 3, we have the information necessary to configure AS security context. AMF can also provide HRL (handover restriction list). 3) In step 12, it is sufficient to provide PDU session (UP related) context. Thus it is proposed to provide AS secuirty context in step 3. AMF can also provide HRL at this point. In step 12, only PDU session (UP related) context is included.","secretary_remarks":"Revision of S2-182038. Revised in parallel session to S2-182825.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13660,"status":"revised","reservation_date":"2018-02-28 21:27:49","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182038","revisedto":"S2-182825","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":190.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182775.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182776","title":"Clarification on TAI list assignment for different 5G RATs","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 5G-RAT is replaced by 3GPP access, and the text is rephrased accordingly: The 5G System shall support allocating a single TAI List over different 3GPP accesses.","secretary_remarks":"Revision of S2-182092. Revised to S2-182965.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13700,"status":"revised","reservation_date":"2018-02-28 21:27:51","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182092","revisedto":"S2-182965","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":145.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182776.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182777","title":"Usage of Unified access control in priority mechanisms","source":"KPN, Vencore Labs, OEC, AT&T, MediaTek Inc","contact":"Toni Dimitrovski","contact-id":66437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Fixing the references and usage of Access Classes to Access Identities and Access class barring to Unified access control.","secretary_remarks":"Revision of S2-182178, merging S2-181979. 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":13730,"status":"agreed","reservation_date":"2018-02-28 21:27:52","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182178","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":165.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180100","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182777.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182819","title":"Correction for congestion control","source":"Huawei, HiSilicon","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: DNN\/S-NSSAI based congestion control is applicable at the AMF when the OAM activates it for particular DNN\/S-NSSAI.","secretary_remarks":"Revision of S2-182720. 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":13180,"status":"agreed","reservation_date":"2018-03-01 18:39:32","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182720","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":129.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180099","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182819.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182820","title":"UE mobility event notification","source":"Samsung, Nokia, Nokia Shanghai Bell, LG Electronics","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: First change. New clause (5.3.X) for UE mobility event notification (by AMF) under 5.3 Registration Management and Connection Management 5.3.X UE mobility event notification (by AMF) New description for UE mobility event notification. Second change. New clause (5.4.X) for NG-RAN location reporting under 5.4 3GPP Specific 5.4.X NG-RAN location reporting Abstract description for NG-RAN location reporting based on request type 1) one-time precise reporting 2) continue reporting whenever UE changes cells 3) reporting for UE presence in Area or Interest Third change. Change '5.6.1 UE Location reporting notification' \u00e0 '5.6.11 UE mobility event notification usage by SMF' - Removed redundant description for UE mobility event notification from 5.6.11 Fourth change. Change on 5.6.5 Support of local area data network - Removed redundant description for AMF behaviors and SMF subscription - Removed the description for RRC inactive state support to the 5.3.X Fifth change. An ad","secretary_remarks":"Revision of S2-182726, merging S2-181510. Revised to S2-182892.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13430,"status":"revised","reservation_date":"2018-03-01 18:39:33","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182726","revisedto":"S2-182892","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":64.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182820.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182821","title":"Reply LS on introducing explicit per-UE TNLA binding release in NGAP","source":"SA WG2","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3","secretary_remarks":"Revision of S2-182724. 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":13360,"status":"approved","reservation_date":"2018-03-01 18:39:34","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182724","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-181485","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182821.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182825","title":"Service Request - AS Security Setup","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to add AS security setup for Service request. Some considerations on doing it in step 3 versus step 12: 1) Providing the AS security context in step 12 could incur a delay (i.e. steps 4 to 11 have to be executed) if RAN needs to perform RRC release with redirection prior to step 12. 2) In step 3, we have the information necessary to configure AS security context. AMF can also provide HRL (handover restriction list). 3) In step 12, it is sufficient to provide PDU session (UP related) context. Thus it is proposed to provide AS secuirty context in step 3. AMF can also provide HRL at this point. In step 12, only PDU session (UP related) context is included.","secretary_remarks":"Revision of S2-182775. Revised to S2-182894.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13670,"status":"revised","reservation_date":"2018-03-01 18:39:38","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182775","revisedto":"S2-182894","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":190.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182825.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182865","title":"Reply LS on DNN or S-NSSAI based congestion control performed at AMF","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-182722. 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":13230,"status":"approved","reservation_date":"2018-03-02 14:39:04","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182722","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-181438","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182865.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182891","title":"AMF Load Re-Balancing For CONNECTED mode UE","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Similar to mechanism defined for AMF management, with UDSF deployment, the new AMF obtain the UE context from UDSF. Without UDSF deployment, the old AMF move the UE context to specific targt AMF in the same AMF set. 2) For UE(s) in CONNECTED mode, after the it receives redirection request from AMF, 5G-AN considers this as a request to release the NGAP-UE-TNLA-binding with the corresponding AMF for the respective UE(s) while maintaining N3 (user plane connectivity) and UE context information. For subsequent N2 message, the 5G-AN should select the specific target AMF (provided by the original AMF) or a different AMF from the same AMF set and forward the subsequent N2 message.","secretary_remarks":"Revision of S2-182725. 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":13390,"status":"agreed","reservation_date":"2018-03-02 14:40:35","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182725","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":25.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182891.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182892","title":"UE mobility event notification","source":"Samsung, Nokia, Nokia Shanghai Bell, LG Electronics","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: First change. New clause (5.3.X) for UE mobility event notification (by AMF) under 5.3 Registration Management and Connection Management 5.3.X UE mobility event notification (by AMF) New description for UE mobility event notification. Second change. New clause (5.4.X) for NG-RAN location reporting under 5.4 3GPP Specific 5.4.X NG-RAN location reporting Abstract description for NG-RAN location reporting based on request type 1) one-time precise reporting 2) continue reporting whenever UE changes cells 3) reporting for UE presence in Area or Interest Third change. Change '5.6.1 UE Location reporting notification' \u00e0 '5.6.11 UE mobility event notification usage by SMF' - Removed redundant description for UE mobility event notification from 5.6.11 Fourth change. Change on 5.6.5 Support of local area data network - Removed redundant description for AMF behaviors and SMF subscription - Removed the description for RRC inactive state support to the 5.3.X Fifth change. An ad","secretary_remarks":"Revision of S2-182820. 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":13440,"status":"agreed","reservation_date":"2018-03-02 14:40:37","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182820","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":64.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-180098","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182892.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182893","title":"Correction of UDR usage in MM related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The flows that UDM may invoke UDR services are clarified in MM related procedures.","secretary_remarks":"Revision of S2-182774. 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":13630,"status":"agreed","reservation_date":"2018-03-02 14:40:38","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182774","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":170.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182893.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182894","title":"Service Request - AS Security Setup","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to add AS security setup for Service request. Some considerations on doing it in step 3 versus step 12: 1) Providing the AS security context in step 12 could incur a delay (i.e. steps 4 to 11 have to be executed) if RAN needs to perform RRC release with redirection prior to step 12. 2) In step 3, we have the information necessary to configure AS security context. AMF can also provide HRL (handover restriction list). 3) In step 12, it is sufficient to provide PDU session (UP related) context. Thus it is proposed to provide AS secuirty context in step 3. AMF can also provide HRL at this point. In step 12, only PDU session (UP related) context is included.","secretary_remarks":"Revision of S2-182825. 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":13680,"status":"noted","reservation_date":"2018-03-02 14:40:39","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182825","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":190.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182894.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182895","title":"[DRAFT] LS on 5G-S-TMSI code space","source":"SA WG2","contact":"Peter Hedman","contact-id":27550,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3. CC: CT WG1, CT WG4. Attachments: S2-181889","secretary_remarks":"Revision of S2-182773. Revised to S2-182964.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13580,"status":"revised","reservation_date":"2018-03-02 14:40:40","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182773","revisedto":"S2-182964","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"CT WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182895.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182963","title":"GUTI unique across AMFs in an AMF SET","source":"Nokia, Nokia Shanghai Bell, Verizon, AT&T, Telecom Italia, NTT DOCOMO","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Explicitly state that the 5G-GUTI, 5G-S-TMSI can be unique across AMFs within an AMF SET. This is in fact a requirement to support AMF resiliency specified in stage 2. Add the missing deployment option.","secretary_remarks":"Revision of S2-182772. Revised to S2-182986.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13520,"status":"revised","reservation_date":"2018-03-05 10:36:28","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182772","revisedto":"S2-182986","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":89.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182963.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182964","title":"LS on 5G-S-TMSI code space","source":"SA WG2","contact":"Peter Hedman","contact-id":27550,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3. CC: CT WG1, CT WG4. Attachments: S2-181889","secretary_remarks":"Revision of S2-182895. 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":13590,"status":"approved","reservation_date":"2018-03-05 10:36:30","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182895","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"CT WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182964.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182965","title":"Clarification on TAI list assignment for different 5G RATs","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 5G-RAT is replaced by 3GPP access, and the text is rephrased accordingly: The 5G System shall support allocating a single TAI List over different 3GPP accesses.","secretary_remarks":"Revision of S2-182776. 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":13710,"status":"agreed","reservation_date":"2018-03-05 10:36:30","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182776","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":145.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180099","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182965.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182966","title":"Management of service area restriction information","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"CR","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-182713. 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":12950,"status":"agreed","reservation_date":"2018-03-05 10:36:32","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182713","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":144.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180099","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182966.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-182986","title":"GUTI unique across AMFs in an AMF SET","source":"Nokia, Nokia Shanghai Bell, Verizon, AT&T, Telecom Italia, NTT DOCOMO","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Explicitly state that the 5G-GUTI, 5G-S-TMSI can be unique across AMFs within an AMF SET. This is in fact a requirement to support AMF resiliency specified in stage 2. Add the missing deployment option.","secretary_remarks":"Revision of S2-182963. Revised to S2-183012.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":13521,"status":"revised","reservation_date":"2018-03-05 10:37:21","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182963","revisedto":"S2-183012","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":89.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182986.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-183006","title":"Clarification of signalling with higher priority","source":"KPN","contact":"Toni Dimitrovski","contact-id":66437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the higher priority signaling in congestion control.","secretary_remarks":"Revision of S2-182159. This was left for e-mail approval. Noted","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12961,"status":"noted","reservation_date":"2018-03-05 10:40:17","uploaded":"2018-03-08 13:57:54","revisionof":"S2-182159","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":162.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-183006.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}, {"name":"S2-183012","title":"GUTI unique across AMFs in an AMF SET","source":"Nokia, Nokia Shanghai Bell, Verizon, AT&T, Telecom Italia, NTT DOCOMO","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Explicitly state that the 5G-GUTI, 5G-S-TMSI can be unique across AMFs within an AMF SET. This is in fact a requirement to support AMF resiliency specified in stage 2. Add the missing deployment option.","secretary_remarks":"Revision of S2-182986. 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":13522,"status":"agreed","reservation_date":"2018-03-05 10:40:37","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182986","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":89.0,"crrevision":4.0,"crcategory":"C","tsg_crp":"SP-180095","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-183012.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]