[{"name":"S2-1902946","title":"LS from SA WG3: Reply LS on new 5G-GUTI allocation","source":"SA WG3","contact":"Christine Jost","contact-id":49662,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks CT WG1 for liaising. On 5G-GUTI allocation during registration procedures. In the attached agreed CR S3-190415, SA WG3 has updated TS 33.501 such that the message which reallocates the 5G-GUTI during the registration procedure is not specified. On 5G-GUTI allocation in relation to notification procedure over non-3GPP access. In the attached agreed CR S3-190415, SA WG3 has further updated TS 33.501 such that 5G-GUTI reallocation is mandated after Service Request messages sent by the UE in response to a Paging message, but not after other kinds of network triggered Service Request messages sent by the UE. That means that after Service Request messages sent by the UE in response to notification procedure over non-3GPP access, 5G-GUTI reallocation is no longer mandated.","secretary_remarks":"Postponed S2-1901430 from S2#131. 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":11550,"status":"noted","reservation_date":"2019-03-19 06:14:10","uploaded":"2019-03-29 07:20:30","revisionof":"S2-1901430","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"S3-190410","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1902946.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902961","title":"Mapping of the AMF Sets between the AMF Regions","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the definition of Nnrf_NFDiscovery service in clause 5.2.7.3.2 in TS 23.502; in addition to the target TAI, the source AMF must be able to give the source AMF region, source AMF Set, or alternatively the current GUAMI as input parameters for the AMF discovery service, in order to discover the AMF from a suitable target AMF Set.","secretary_remarks":"Revised in parallel session to S2-1904646.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12060,"status":"revised","reservation_date":"2019-03-20 15:10:21","uploaded":"2019-04-02 14:13:35","revisionof":"","revisedto":"S2-1904646","release":"Rel-16","crspec":23.502,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1121.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1902961.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903034","title":"LS from CT WG1: LS on Use of SUCI in NAS signalling","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"While discussing the requirements for the use of SUCI in NAS signalling as specified in TS 33.501, v 15.3.1, CT WG1 noticed that in TS 33.501, subclause 6.12.2, the use of the SUCI is restricted to a few specific situations: The UE shall include a SUCI only in the following 5G NAS messages: - if the UE is sending a Registration Request message of type 'initial registration' to a PLMN for which the UE does not already have a 5G-GUTI, the UE shall include a SUCI to the Registration Request message, or - if the UE includes a 5G-GUTI when sending a Registration Request message of type 'mobility registration updating' or 'periodic registration updating' to a PLMN and, in response, receives an Identity Request message, then the UE shall include a fresh SUCI in the Identity Response message (see clause 6.12.4). whereas in subclause 6.12.4, for the identity request procedure initiated by the AMF, no such restrictions are described: The subscriber identification mechanism may be invoked by the serving network when the UE cannot be identified by means of a temporary identity (5G-GUTI). In particular, it should be used when the serving network cannot retrieve the SUPI based on the 5G-GUTI by which the subscriber identifies itself on the radio path. The mechanism described in figure 6.12.4-1 allows the identification of a UE on the radio path by means of the SUCI. \u2026 The mechanism is initiated by the AMF that requests the UE to send its SUCI. Regarding the identity request procedure for SUCI, CT WG1 followed the stage 2 requirements as specified in the quote from subclause 6.12.4, above. This means that in TS 24.501, use of this procedure is not restricted to the registration procedure, and the UE will always respond to the request. CT WG1 would thus like to ask SA WG3 the following question: Question 1: Does SA WG3 see any security issues with not restricting the identity request procedure for SUCI to the registration procedure? CT WG1 would also like to highlight to SA WG3 that if the UE initiates a de-registration procedure when it does not have a valid 5G-GUTI available, the UE will include its SUCI in the Mobile identity IE (see TS 24.501, subclause 5.5.2.2.1). CT WG1 would like SA WG3 to take this into account and update stage-2 specs if required.","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":11560,"status":"noted","reservation_date":"2019-03-29 08:08:04","uploaded":"2019-03-29 10:31:47","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2","lsoriginalls":"C1-191685","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903034.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903062","title":"LS from RAN WG2: Response LS on inclusion of selected PLMN into the complete message","source":"RAN WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks CT WG1 for their LS (C1-188593) on inclusion of selected PLMN into the complete message. Based on the CR in C1-188534, RAN WG2 noted that the UE in state 5GMM-REGISTERED shall initiate the registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message to the AMF when the UE in 5GMM-CONNECTED mode with RRC inactive indication enters a shared network cell in the current registration area belonging to an equivalent PLMN of the registered PLMN and not belonging to the registered PLMN. Whilst the above CR fixes the identified issue for the UE in RRC_INACTIVE state, similar issue is also applicable for the case of the UE in RRC_CONNECTED state upon reestablishment since the selected PLMN is not included in the RRCReestablishmentComplete message. RAN WG2 respectfully requests CT WG1 to consider whether any changes are also needed to fix the identified issue for the reestablishment case.","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":11570,"status":"noted","reservation_date":"2019-03-29 08:08:04","uploaded":"2019-03-29 10:31:48","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2, RAN WG3","lsoriginalls":"R2-1902726","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903062.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903073","title":"LS from RAN WG3: LS on N2 Mobility Request","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"During the RAN WG3#103 meeting it was pointed out that the N2 Mobility Request\/Response messages as used in TS 23.502 have no equivalent stage-3. RAN WG3 intends to discuss this issue in the following meeting and we welcome further feedback from SA WG2 on this. RAN WG3 respectfully asks SA WG2 to take the above into account and provide further feedback.","secretary_remarks":"Responses drafted in S2-1903262 and S2-1903873. Final response in S2-1904650","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11580,"status":"replied to","reservation_date":"2019-03-29 08:08:04","uploaded":"2019-03-29 10:31:48","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-191138","lsreply":"S2-1904584, S2-1904650","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903073.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903187","title":"Congestion control exception for reporting 5GSM Core Network Capability and Always-on PDU Session Requested indication","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that sending PDU session modifcation in order to report 5GSM UE Capability and always-on PDU session is exempt from MM\/SM congestion control","secretary_remarks":"Revised in parallel session to S2-1904647.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12120,"status":"revised","reservation_date":"2019-03-31 15:28:21","uploaded":"2019-04-02 11:45:46","revisionof":"","revisedto":"S2-1904647","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1061.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903187.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903188","title":"Congestion control exception for reporting 5GSM Core Network Capability and Always-on PDU Session Requested indication","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: It is proposed that sending PDU session modifcation in order to report 5GSM UE Capability and always-on PDU session is exempt from MM\/SM congestion control","secretary_remarks":"Revised in parallel session to S2-1904648.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12150,"status":"revised","reservation_date":"2019-03-31 15:32:08","uploaded":"2019-04-02 11:45:46","revisionof":"","revisedto":"S2-1904648","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1062.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903188.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903255","title":"Correction to N2 AMF Mobility Request","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 4.2.2.2.2: Clarified in step 5 of the Registration procedure that the presence of NGAP UE-TNLA bindings depends on UE's CM state over non-3GPP access. Clarified in step 18 of the Registration procedure that the execution of the AMF Mobility procedure depends on UE's CM state over non-3GPP access.. Clause 5.2.2.2.2: Added 'CM state in non-3GPP access' and 'Global N3IWF ID' to the UE context in AMF (Table 5.2.2.2.2-1).","secretary_remarks":"Revised in parallel session, merging S2-1903730, to S2-1904582.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11590,"status":"revised","reservation_date":"2019-04-01 09:37:08","uploaded":"2019-04-02 13:46:01","revisionof":"","revisedto":"S2-1904582","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1166.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903255.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903256","title":"Correction to N2 AMF Mobility Request","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Clause 4.2.2.2.2: Clarified in step 5 of the Registration procedure that the presence of NGAP UE-TNLA bindings depends on UE's CM state over non-3GPP access. Clarified in step 18 of the Registration procedure that the execution of the AMF Mobility procedure depends on UE's CM state over non-3GPP access.. Clause 5.2.2.2.2: Added 'CM state in non-3GPP access' and 'Global N3IWF ID' to the UE context in AMF (Table 5.2.2.2.2-1).","secretary_remarks":"Revised in parallel session, merging S2-1903731, to S2-1904583.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11610,"status":"revised","reservation_date":"2019-04-01 09:42:42","uploaded":"2019-04-02 13:46:01","revisionof":"","revisedto":"S2-1904583","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1167.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903256.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903262","title":"LS reply on N2 Mobility Request","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"To:RAN WG3. Attachments: TS 23.502 CR1166","secretary_remarks":"Response to S2-1903073. Revised in parallel session to S2-1904584.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11650,"status":"revised","reservation_date":"2019-04-01 10:04:20","uploaded":"2019-04-02 13:46:01","revisionof":"","revisedto":"S2-1904584","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_132_XiAn\/Docs\/S2-1903262.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903269","title":"Back-off timers handling for scheduled communication","source":"NEC","contact":"Iskren Ianev","contact-id":59515,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes that when the network is congested, for UEs with scheduled communication pattern the network should apply a back-off timer value so that the UE does not miss its scheduled communication window. If the UE scheduled communication window is very short, the network may not apply a back-off timer at all.","secretary_remarks":"Revised in parallel session to S2-1904640.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11860,"status":"revised","reservation_date":"2019-04-01 11:29:36","uploaded":"2019-04-01 18:58:26","revisionof":"","revisedto":"S2-1904640","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1094.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903269.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903491","title":"Clarification on NAS level congestion control","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the description in clause 5.19.7.1 to make it general. Clarify clause 5.19.7.2 only describes MM congestion control without changing the title. Clarify the LADN DNN back-off timer usage. Several editorial changes including changing timer to time which was sent to UE in the NAS message. Updating the clause 5.19.7.2 with removing wrongly referred clause numbers.","secretary_remarks":"Revised in parallel session to S2-1904587.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11750,"status":"revised","reservation_date":"2019-04-02 05:12:45","uploaded":"2019-04-02 05:36:34","revisionof":"","revisedto":"S2-1904587","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1158.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903491.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903492","title":"Clarification on NAS level congestion control","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Update the description in clause 5.19.7.1 to make it general. Clarify clause 5.19.7.2 only describes MM congestion control without changing the title. Clarify the LADN DNN back-off timer usage. Several editorial changes including changing timer to time which was sent to UE in the NAS message. Updating the clause 5.19.7.2 with removing wrongly referred clause numbers.","secretary_remarks":"Revised in parallel session to S2-1904588.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11770,"status":"revised","reservation_date":"2019-04-02 05:12:45","uploaded":"2019-04-02 05:36:34","revisionof":"","revisedto":"S2-1904588","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1159.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903492.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903539","title":"Association between the GUAMI and AMF instance","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The 5G AN removes the target AMF corresponding to old GUAMI when the old GUAMI is in use again.","secretary_remarks":"Revised in parallel session to S2-1904641.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11880,"status":"revised","reservation_date":"2019-04-02 07:17:13","uploaded":"2019-04-02 14:49:52","revisionof":"","revisedto":"S2-1904641","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1175.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903539.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903540","title":"Association between the GUAMI and AMF instance","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: The 5G AN removes the target AMF corresponding to old GUAMI when the old GUAMI is in use again.","secretary_remarks":"Revised in parallel session to S2-1904642.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11910,"status":"revised","reservation_date":"2019-04-02 07:17:14","uploaded":"2019-04-02 14:49:52","revisionof":"","revisedto":"S2-1904642","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1176.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903540.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903541","title":"Mobility Restriction","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies in clause 4.15.4.2 that the reachability notification may also be sent in mobility procedures other than registration. And that SMF is expected to subscribe to UE reachability notification. Rev5: Clarifies in HR roaming both V-SMF and H-SMF subscribes to UE reachability event, the V-SMF determines whether to deactivate PDU Session when UE is in non allowed area, the H-SMF determines whether to trigger DL signalling if UE is in non allowed area. The V-SMF transfer the AMF ID to the H-SMF. Clarifies in handover procedures, the AMF notifies to the SMF about the reachability status of the UE. Clarifies in clause 4.15.4.2 SMF is expected to subscribe to UE reachability notification.","secretary_remarks":"Revision of S2-1901858 from S2#131. Revised in parallel session to S2-1904643.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11930,"status":"revised","reservation_date":"2019-04-02 07:17:15","uploaded":"2019-04-02 14:49:52","revisionof":"S2-1901858","revisedto":"S2-1904643","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":934.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903541.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903542","title":"Mobility Restriction","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Clarifies in clause 4.15.4.2 that the reachability notification may also be sent in mobility procedures other than registration. And that SMF is expected to subscribe to UE reachability notification. Rev5: Clarifies in HR roaming both V-SMF and H-SMF subscribes to UE reachability event, the V-SMF determines whether to deactivate PDU Session when UE is in non allowed area, the H-SMF determines whether to trigger DL signalling if UE is in non allowed area. The V-SMF transfer the AMF ID to the H-SMF. Clarifies in handover procedures, the AMF notifies to the SMF about the reachability status of the UE. Clarifies in clause 4.15.4.2 SMF is expected to subscribe to UE reachability notification.","secretary_remarks":"Revised in parallel session to S2-1904644.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11960,"status":"revised","reservation_date":"2019-04-02 07:17:16","uploaded":"2019-04-02 14:49:52","revisionof":"","revisedto":"S2-1904644","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1225.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903542.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903667","title":"Correcting AMF behaviour for Service Request that is not integrity protected","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct 23.502 behavior and refer to appropriate stage 3 TS 24.501 (and not 33.501 in this case)","secretary_remarks":"Agreed in parallel session This was 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":11980,"status":"agreed","reservation_date":"2019-04-02 09:35:10","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1261.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190401","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903667.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903668","title":"Correcting AMF behaviour for Service Request that is not integrity protected","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Correct 23.502 behavior and refer to appropriate stage 3 TS 24.501 (and not 33.501 in this case)","secretary_remarks":"Agreed in parallel session This was 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":11990,"status":"agreed","reservation_date":"2019-04-02 09:35:11","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1262.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-190401","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903668.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903669","title":"Configuration transfer to support N26","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce support for Configuration transfer for 5GS to EPS interworking.","secretary_remarks":"Merged into S2-1903896","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12000,"status":"merged","reservation_date":"2019-04-02 09:35:12","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1224.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903669.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903670","title":"Configuration transfer to support N26","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Introduce support for Configuration transfer for 5GS to EPS interworking.","secretary_remarks":"Merged into S2-1903897","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12010,"status":"merged","reservation_date":"2019-04-02 09:35:13","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1225.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903670.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903671","title":"AMF Failure - Other CP NF Behaviour","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that CP NF can select an AMF from the same AMF region when neither back up AMF nor AMFs in the same AMF set is available.","secretary_remarks":"Agreed in parallel session This was 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":12090,"status":"agreed","reservation_date":"2019-04-02 09:35:14","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1226.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190413","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903671.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903673","title":"AMF behaviour when UE is in a restricted area","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce support for Configuration transfer for 5GS to EPS interworking. that the Network need not page the UE in this case if it knows that the Network is going to reject the Service Request anyway because UE is not allowed service for non-emergency or non-MPS","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":12100,"status":"noted","reservation_date":"2019-04-02 09:35:16","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1227.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903673.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903710","title":"Cleanup of NAS Congestion Control","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Remove SMF check if the ESM message is subject for congestion control in 5.19.7.2. - clarify the UE's behaviour after receiving PDU session release command. - use a unify exempt indication for the both MM and SM congestion control.","secretary_remarks":"Revised in parallel session to S2-1904585.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11710,"status":"revised","reservation_date":"2019-04-02 10:47:39","uploaded":"2019-04-02 12:53:14","revisionof":"","revisedto":"S2-1904585","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1236.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903710.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903711","title":"Cleanup of NAS Congestion Control","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: - Remove SMF check if the ESM message is subject for congestion control in 5.19.7.2. - clarify the UE's behaviour after receiving PDU session release command. - use a unify exempt indication for the both MM and SM congestion control.","secretary_remarks":"Revised in parallel session to S2-1904586.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11730,"status":"revised","reservation_date":"2019-04-02 10:51:04","uploaded":"2019-04-02 12:53:14","revisionof":"","revisedto":"S2-1904586","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1237.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903711.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903730","title":"Correction on the modification of NGAP UE association towards the N3IWF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that RAN UE NGAP ID is sent from the old AMF to the new AMF is the old AMF already establishes N2 connection with a N3IWF for this UE. Replace N2 Mobility Request\/Response messages by INITIAL CONTEXT SETUP procedure. Clarify the RAN UE NGAP ID can also be used in the case of N3IWF.","secretary_remarks":"Merged into S2-1904582.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11680,"status":"merged","reservation_date":"2019-04-02 10:55:39","uploaded":"2019-04-02 14:02:42","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1273.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903730.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903731","title":"Correction on the modification of NGAP UE association towards the N3IWF - R16","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Clarify that RAN UE NGAP ID is sent from the old AMF to the new AMF is the old AMF already establishes N2 connection with a N3IWF for this UE. Replace N2 Mobility Request\/Response messages by INITIAL CONTEXT SETUP procedure. Clarify the RAN UE NGAP ID can also be used in the case of N3IWF.","secretary_remarks":"Merged into S2-1904583.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11690,"status":"merged","reservation_date":"2019-04-02 10:55:40","uploaded":"2019-04-02 14:02:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1274.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903731.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903746","title":"Clarification on the mobility restriction","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed not to limited the deletion of the list of TAs by AMF only in the initial-type registration procedure, but also include the mobility-type and periodic-type registration procedure.","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":12110,"status":"noted","reservation_date":"2019-04-02 11:11:50","uploaded":"2019-04-02 13:55:19","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1244.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903746.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903767","title":"Correction of SM congestion control override","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Congestion control override capability is limited to just bypassing the congestion control in the network, but leaving all other error handling in place.","secretary_remarks":"Revised in parallel session to S2-1904638.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11800,"status":"revised","reservation_date":"2019-04-02 11:22:44","uploaded":"2019-04-02 13:10:38","revisionof":"","revisedto":"S2-1904638","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1248.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903767.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903768","title":"Correction of SM congestion control override","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Congestion control override capability is limited to just bypassing the congestion control in the network, but leaving all other error handling in place.","secretary_remarks":"Revised in parallel session to S2-1904639.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11830,"status":"revised","reservation_date":"2019-04-02 11:24:56","uploaded":"2019-04-02 13:10:38","revisionof":"","revisedto":"S2-1904639","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1249.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903768.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903793","title":"Correction on EPS to 5GS Mobility Registration Procedure","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The V-SMF sends the Nsmf_PDUSession_CreateSMContext_Response right after it receives the Nsmf_PDUSession_CreateSMContext_Request message The V-SMF sends Namf_Communication_N1N2MessageTransfer to AMF after it interact with the H-SMF. Some Editorial changes: Move the description for home-routed roaming case and connected state mobility above","secretary_remarks":"Revised in parallel session to S2-1904645.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12020,"status":"revised","reservation_date":"2019-04-02 11:32:52","uploaded":"2019-04-02 13:19:27","revisionof":"","revisedto":"S2-1904645","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1290.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903793.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903794","title":"Correction on EPS to 5GS Mobility Registration Procedure","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: The V-SMF sends the Nsmf_PDUSession_CreateSMContext_Response right after it receives the Nsmf_PDUSession_CreateSMContext_Request message The V-SMF sends Namf_Communication_N1N2MessageTransfer to AMF after it interact with the H-SMF. Some Editorial changes: Move the description for home-routed roaming case and connected state mobility above","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":12050,"status":"noted","reservation_date":"2019-04-02 11:32:53","uploaded":"2019-04-02 13:19:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1291.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903794.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903873","title":"[DRAFT] Reply LS to LS from RAN WG3: LS on N2 Mobility Request","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Response to S2-1903073","secretary_remarks":"Response to S2-1903073. LATE DOC: Rx: 02\/04, 19:00. Merged into S2-1904584.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11700,"status":"merged","reservation_date":"2019-04-02 16:25:07","uploaded":"2019-04-03 06:11:31","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903873.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904582","title":"Correction to N2 AMF Mobility Request","source":"Intel, Huawei, HiSilicon, Ericsson","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 4.2.2.2.2: Clarified in step 5 of the Registration procedure that the presence of NGAP UE-TNLA bindings depends on UE's CM state via N3IWF. Clarified in step 18 of the Registration procedure that the execution of the AMF Mobility procedure depends on UE's CM state via N3IWF. Clause 5.2.2.2.2: Added 'CM state in non-3GPP access' and 'N2 address information for N3IWF' to the UE context in AMF (Table 5.2.2.2.2-1).","secretary_remarks":"Revision of S2-1903255, merging S2-1903730. Agreed in parallel session This was 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":11600,"status":"agreed","reservation_date":"2019-04-15 10:42:15","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903255","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1166.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190400","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904582.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904583","title":"Correction to N2 AMF Mobility Request","source":"Intel, Huawei, HiSilicon, Ericsson","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 4.2.2.2.2: Clarified in step 5 of the Registration procedure that the presence of NGAP UE-TNLA bindings depends on UE's CM state via N3IWF\/TNGF. Clarified in step 18 of the Registration procedure that the execution of the AMF Mobility procedure depends on UE's CM state via N3IWF\/TNGF. Added 'TNGF' in step 18 of Figure 4.2.2.2.2-1. Clause 5.2.2.2.2: Added 'CM state in non-3GPP access' and 'N2 address information for N3IWF\/TNGF' to the UE context in AMF (Table 5.2.2.2.2-1).","secretary_remarks":"Revision of S2-1903256, merging S2-1903731. Revised in parallel session to S2-1904649.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11620,"status":"revised","reservation_date":"2019-04-15 10:42:16","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903256","revisedto":"S2-1904649","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1167.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904583.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904584","title":"[DRAFT] LS reply on N2 Mobility Request","source":"SA WG2","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. Attachments: TS 23.502 CR1166, CR1167","secretary_remarks":"Revision of S2-1903262, merging S2-1903873. Revised in parallel session to S2-1904650.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11660,"status":"revised","reservation_date":"2019-04-15 10:42:17","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903262","revisedto":"S2-1904650","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_132_XiAn\/Docs\/S2-1904584.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904585","title":"Cleanup of NAS Congestion Control","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - clarify the UE's behaviour after receiving PDU session release command. - use a unify exempt indication for the both MM and SM congestion control.","secretary_remarks":"Revision of S2-1903710. Agreed in parallel session This was 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":11720,"status":"agreed","reservation_date":"2019-04-15 10:42:17","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903710","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1236.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904585.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904586","title":"Cleanup of NAS Congestion Control","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: - clarify the UE's behaviour after receiving PDU session release command. - use a unify exempt indication for the both MM and SM congestion control.","secretary_remarks":"Revision of S2-1903711. Agreed in parallel session This was 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":11740,"status":"agreed","reservation_date":"2019-04-15 10:42:17","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903711","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1237.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904586.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904587","title":"Clarification on NAS level congestion control","source":"Intel, Ericsson","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify clause 5.19.7.2 only describes MM congestion control without changing the title. Clarify the LADN DNN back-off timer applicability. Several editorial changes including changing timer to time which was sent to UE in the NAS message. Updating the clause 5.19.7.2 with removing wrongly referred clause numbers and rephrasing the corresponding sentences. The AMF requirement to enforce NAS back-off timer is removed.","secretary_remarks":"Revision of S2-1903491. Agreed in parallel session This was 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":11760,"status":"agreed","reservation_date":"2019-04-15 10:42:18","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903491","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1158.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904587.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904588","title":"Clarification on NAS level congestion control","source":"Intel, Ericsson","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify clause 5.19.7.2 only describes MM congestion control without changing the title. Clarify the LADN DNN back-off timer applicability. Several editorial changes including changing timer to time which was sent to UE in the NAS message. Updating the clause 5.19.7.2 with removing wrongly referred clause numbers and rephrasing the corresponding sentences. The AMF requirement to enforce NAS back-off timer is removed.","secretary_remarks":"Revision of S2-1903492. Revised in parallel session to S2-1904706.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11780,"status":"revised","reservation_date":"2019-04-15 10:42:19","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903492","revisedto":"S2-1904706","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1159.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904588.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904638","title":"Correction of SM congestion control override","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Congestion control override capability is limited to just bypassing the congestion control in the network, but leaving all other error handling in place.","secretary_remarks":"Revision of S2-1903767. Revised in parallel session to S2-1904708.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11810,"status":"revised","reservation_date":"2019-04-15 10:43:00","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903767","revisedto":"S2-1904708","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1248.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904638.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904639","title":"Correction of SM congestion control override","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Congestion control override capability is limited to just bypassing the congestion control in the network, but leaving all other error handling in place.","secretary_remarks":"Revision of S2-1903768. Revised in parallel session to S2-1904709.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11840,"status":"revised","reservation_date":"2019-04-15 10:43:01","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903768","revisedto":"S2-1904709","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1249.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904639.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904640","title":"Back-off timers handling for scheduled communication","source":"NEC","contact":"Iskren Ianev","contact-id":59515,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes that when the network is congested, for UEs with scheduled communication pattern the network should apply a back-off timer value so that the UE does not miss its scheduled communication window.","secretary_remarks":"Revision of S2-1903269. Agreed in parallel session This was 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":11870,"status":"agreed","reservation_date":"2019-04-15 10:43:02","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903269","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"eNA"}],"crnumber":1094.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-190420","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904640.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904641","title":"Association between the GUAMI and AMF instance","source":"Huawei, HiSilicon, , Nokia, Nokia Shanghai Bell, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The 5G AN removes the target AMF corresponding to old GUAMI when the old GUAMI is in use again.","secretary_remarks":"Revision of S2-1903539. Revised in parallel session to S2-1904710.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11890,"status":"revised","reservation_date":"2019-04-15 10:43:03","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903539","revisedto":"S2-1904710","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1175.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904641.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904642","title":"Association between the GUAMI and AMF instance","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: The 5G AN removes the target AMF corresponding to old GUAMI when the old GUAMI is in use again.","secretary_remarks":"Revision of S2-1903540. Agreed in parallel session This was 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":11920,"status":"agreed","reservation_date":"2019-04-15 10:43:04","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903540","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1176.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904642.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904643","title":"Mobility Restriction","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies in clause 4.15.4.2 that the reachability notification may also be sent in mobility procedures other than registration. And that SMF is expected to subscribe to UE reachability notification. Rev5: Clarifies in HR roaming both V-SMF and H-SMF subscribes to UE reachability event, the V-SMF determines whether to deactivate PDU Session when UE is in non allowed area, the H-SMF determines whether to trigger DL signalling if UE is in non allowed area. The V-SMF transfer the AMF ID to the H-SMF. Clarifies in handover procedures, the AMF notifies to the SMF about the reachability status of the UE. Clarifies in clause 4.15.4.2 SMF is expected to subscribe to UE reachability notification.","secretary_remarks":"Revision of S2-1903541. Revised in parallel session to S2-1904711.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11940,"status":"revised","reservation_date":"2019-04-15 10:43:05","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903541","revisedto":"S2-1904711","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":934.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904643.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904644","title":"Clarification on Mobility Restriction","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Clarifies in clause 4.15.4.2 that the reachability notification may also be sent in mobility procedures other than registration. And that SMF is expected to subscribe to UE reachability notification. Rev5: Clarifies in HR roaming both V-SMF and H-SMF subscribes to UE reachability event, the V-SMF determines whether to deactivate PDU Session when UE is in non allowed area, the H-SMF determines whether to trigger DL signalling if UE is in non allowed area. The V-SMF transfer the AMF ID to the H-SMF. Clarifies in handover procedures, the AMF notifies to the SMF about the reachability status of the UE. Clarifies in clause 4.15.4.2 SMF is expected to subscribe to UE reachability notification.","secretary_remarks":"Revision of S2-1903542. Agreed in parallel session This was 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":11970,"status":"agreed","reservation_date":"2019-04-15 10:43:06","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903542","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1225.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-190400","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904644.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904645","title":"Correction on EPS to 5GS Mobility Registration Procedure","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The V-SMF sends the Nsmf_PDUSession_CreateSMContext_Response right after it receives the Nsmf_PDUSession_CreateSMContext_Request message The V-SMF sends Namf_Communication_N1N2MessageTransfer to AMF after it interact with the H-SMF. Some Editorial changes: Move the description for home-routed roaming case and connected state mobility above","secretary_remarks":"Revision of S2-1903793. Revised in parallel session to S2-1904712.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12030,"status":"revised","reservation_date":"2019-04-15 10:43:07","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903793","revisedto":"S2-1904712","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1290.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904645.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904646","title":"Mapping of the AMF Sets between the AMF Regions","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the definition of Nnrf_NFDiscovery service in clause 5.2.7.3.2 in TS 23.502; in addition to the target TAI, the source AMF must be able to give the source AMF region, source AMF Set, as input parameters for the AMF discovery service, in order to discover the AMF from a suitable target AMF Set.","secretary_remarks":"Revision of S2-1902961. Revised in parallel session to S2-1904713.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12070,"status":"revised","reservation_date":"2019-04-15 10:43:08","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1902961","revisedto":"S2-1904713","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1121.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904646.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904647","title":"Congestion control exception for reporting 5GSM Core Network Capability and Always-on PDU Session Requested indication","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that sending PDU session modifcation in order to report 5GSM UE Capability and always-on PDU session is exempt from MM\/SM congestion control","secretary_remarks":"Revision of S2-1903187. Revised in parallel session to S2-1904714.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12130,"status":"revised","reservation_date":"2019-04-15 10:43:08","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903187","revisedto":"S2-1904714","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1061.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904647.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904648","title":"Congestion control exception for reporting 5GSM Core Network Capability and Always-on PDU Session Requested indication","source":"Qualcomm Incorporated, Ericsson","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: It is proposed that sending PDU session modifcation in order to report 5GSM UE Capability and always-on PDU session will wait until the MM\/SM congestion control timer in the UE expires","secretary_remarks":"Revision of S2-1903188. 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":12160,"status":"agreed","reservation_date":"2019-04-15 10:43:09","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903188","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1062.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904648.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904649","title":"Correction to N2 AMF Mobility Request","source":"Intel, Huawei, HiSilicon, Ericsson","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 4.2.2.2.2: Clarified in step 5 of the Registration procedure that the presence of NGAP UE-TNLA bindings depends on UE's CM state via N3IWF\/TNGF. Clarified in step 18 of the Registration procedure that the execution of the AMF Mobility procedure depends on UE's CM state via N3IWF\/TNGF. Added 'TNGF' in step 18 of Figure 4.2.2.2.2-1 and reverted the arrow directions in steps 18-19 of Figure 4.2.2.2.2-1. Clause 5.2.2.2.2: Added 'CM state for UE connected via N3IWF\/TNGF' and 'N2 address information for N3IWF\/TNGF' to the UE context in AMF (Table 5.2.2.2.2-1).","secretary_remarks":"Revision of S2-1904583. Revised in parallel session to S2-1904707.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11630,"status":"revised","reservation_date":"2019-04-15 10:43:10","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1904583","revisedto":"S2-1904707","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1167.0,"crrevision":2.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904649.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904650","title":"LS reply on N2 Mobility Request","source":"SA WG2","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. Attachments: TS 23.502 CR1166, CR1167","secretary_remarks":"Revision of S2-1904584. Agreed in parallel session This was 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":11670,"status":"approved","reservation_date":"2019-04-15 10:43:11","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1904584","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1903073","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"R3-192723, R3-193145","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904650.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904706","title":"Clarification on NAS level congestion control","source":"Intel, Ericsson","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Clarify clause 5.19.7.2 only describes MM congestion control without changing the title. Clarify the LADN DNN back-off timer applicability. Several editorial changes including changing timer to time which was sent to UE in the NAS message. Updating the clause 5.19.7.2 with removing wrongly referred clause numbers and rephrasing the corresponding sentences. The AMF requirement to enforce NAS back-off timer is removed.","secretary_remarks":"Revision of S2-1904588. Agreed in parallel session This was 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":11790,"status":"agreed","reservation_date":"2019-04-15 10:44:02","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904588","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1159.0,"crrevision":2.0,"crcategory":"A","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904706.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904707","title":"Correction to N2 AMF Mobility Request","source":"Intel, Huawei, HiSilicon, Ericsson","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Clause 4.2.2.2.2: Clarified in step 5 of the Registration procedure that the presence of NGAP UE-TNLA bindings depends on UE's CM state via N3IWF\/TNGF. Clarified in step 18 of the Registration procedure that the execution of the AMF Mobility procedure depends on UE's CM state via N3IWF\/TNGF. Added 'TNGF' in step 18 of Figure 4.2.2.2.2-1 and reverted the arrow directions in steps 18-19 of Figure 4.2.2.2.2-1. Clause 5.2.2.2.2: Added 'CM state for UE connected via N3IWF\/TNGF' and 'N2 address information for N3IWF\/TNGF' to the UE context in AMF (Table 5.2.2.2.2-1).","secretary_remarks":"Revision of S2-1904649. Agreed in parallel session This was 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":11640,"status":"agreed","reservation_date":"2019-04-15 10:44:03","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904649","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1167.0,"crrevision":3.0,"crcategory":"A","tsg_crp":"SP-190400","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904707.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904708","title":"Correction of SM congestion control override","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Congestion control override capability is limited to just bypassing the congestion control in the network, but leaving all other error handling in place.","secretary_remarks":"Revision of S2-1904638. Agreed in parallel session This was 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":11820,"status":"agreed","reservation_date":"2019-04-15 10:44:04","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904638","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1248.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904708.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904709","title":"Correction of SM congestion control override","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Congestion control override capability is limited to just bypassing the congestion control in the network, but leaving all other error handling in place.","secretary_remarks":"Revision of S2-1904639. Agreed in parallel session This was 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":11850,"status":"agreed","reservation_date":"2019-04-15 10:44:04","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904639","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1249.0,"crrevision":2.0,"crcategory":"A","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904709.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904710","title":"Association between the GUAMI and AMF instance","source":"Huawei, HiSilicon, , Nokia, Nokia Shanghai Bell, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The 5G AN removes the target AMF corresponding to old GUAMI when the old GUAMI is in use again.","secretary_remarks":"Revision of S2-1904641. Agreed in parallel session This was 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":11900,"status":"agreed","reservation_date":"2019-04-15 10:44:05","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904641","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1175.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904710.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904711","title":"Clarification on Mobility Restriction","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies in clause 4.15.4.2 that the reachability notification may also be sent in mobility procedures other than registration. And that SMF is expected to subscribe to UE reachability notification. Rev5: Clarifies in HR roaming both V-SMF and H-SMF subscribes to UE reachability event, the V-SMF determines whether to deactivate PDU Session when UE is in non allowed area, the H-SMF determines whether to trigger DL signalling if UE is in non allowed area. The V-SMF transfer the AMF ID to the H-SMF. Clarifies in handover procedures, the AMF notifies to the SMF about the reachability status of the UE. Clarifies in clause 4.15.4.2 SMF is expected to subscribe to UE reachability notification.","secretary_remarks":"Revision of S2-1904643. Agreed in parallel session This was 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":11950,"status":"agreed","reservation_date":"2019-04-15 10:44:06","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904643","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":934.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"SP-190400","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904711.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904712","title":"Correction on EPS to 5GS Mobility Registration Procedure","source":"ZTE, Ericsson","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The V-SMF sends the Nsmf_PDUSession_CreateSMContext_Response right after it receives the Nsmf_PDUSession_CreateSMContext_Request message The V-SMF sends Namf_Communication_N1N2MessageTransfer to AMF after it interact with the H-SMF. Some Editorial changes: Move the description for home-routed roaming case and connected state mobility above","secretary_remarks":"Revision of S2-1904645. Agreed in parallel session This was 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":12040,"status":"agreed","reservation_date":"2019-04-15 10:44:07","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904645","revisedto":"S2-1905247, S2-1905598","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1290.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904712.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904713","title":"Mapping of the AMF Sets between the AMF Regions","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the definition of Nnrf_NFDiscovery service in clause 5.2.7.3.2 in TS 23.502; in addition to the target TAI, the source AMF must be able to give the source AMF region, source AMF Set, as input parameters for the AMF discovery service, in order to discover the AMF from a suitable target AMF Set.","secretary_remarks":"Revision of S2-1904646. Postponed","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":12080,"status":"postponed","reservation_date":"2019-04-15 10:44:08","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904646","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1121.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904713.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904714","title":"Congestion control exception for reporting 5GSM Core Network Capability and Always-on PDU Session Requested indication","source":"Qualcomm Incorporated, Ericsson","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that sending PDU session modifcation in order to report 5GSM UE Capability and always-on PDU session will wait until the MM\/SM congestion control timer in the UE expires","secretary_remarks":"Revision of S2-1904647. 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":12140,"status":"agreed","reservation_date":"2019-04-15 10:44:09","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904647","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1061.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904714.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]