[{"name":"S2-1900008","title":"LS from CT WG1: LS on SM request reattempt upon PLMN change","source":"CT WG1","contact":"Tsuyoshi Takakura","contact-id":72622,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 could not agree with UE behaviour of SM request reattempt upon PLMN change with e.g., following scenario. PLMN#A's default S-NSSAI is S-NSSAI#A. PLMN#B's default S-NSSAI is S-NSSAI #B. 1. The UE registers to PLMN#A and requests SM request without S-NSSAI. 2. The PLMN#A rejects the SM request with a back-off timer due to the S-NSSAI only based congestion control. This means the SM request to S-NSSAI#A in PLMN#A is under the congestion control. 3. The UE changes the PLMN to PLMN#B where the default S-NSSAI is S-NSSAI#B and S-NSSAI#B is NOT under the S-NSSAI only based congestion control. CT WG1 would like to ask: Question 1: Upon PLMN change, if a back-off timer is running due to S-NSSAI only based congestion control and associated with no S-NSSAI, is the UE allowed to send a PDU SESSION ESTABLISHMENT REQUEST message without S-NSSAI in new PLMN? Question 2: Upon PLMN change, if a back-off timer is running for [S-NSSAI, DNN] based congestion control and associated with no [S-NSSAI, DNN], is the UE allowed to send a PDU SESSION ESTABLISHMENT REQUEST message without [S-NSSAI, DNN] in new PLMN? Action: CT WG1 kindly asks SA WG2 to answer the questions above.","secretary_remarks":"Postponed S2-1811667 from S2#129BIS. Response drafted in S2-1900421. 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":11540,"status":"postponed","reservation_date":"2018-12-19 08:47:10","uploaded":"2018-12-19 10:07:34","revisionof":"S2-1811667","revisedto":"S2-1901405","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-187008","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900008.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900028","title":"LS from CT WG1: Reply LS on inclusion of selected PLMN into the complete message","source":"CT WG1","contact":"Lalith Kumar","contact-id":80792,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks RAN WG3 (R3-187235\/C1-188492) for their LS on inclusion of selected PLMN into the complete message. CT WG1 has discussed and solved this issue of mismatch between UE and AMF on selected PLMN ID, by introducing a trigger for registration procedure when UE enters a shared network cell belonging to EPLMN in INACTIVE state. The attached CR C1-188534 is agreed.","secretary_remarks":"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":11580,"status":"noted","reservation_date":"2018-12-19 11:46:38","uploaded":"2018-12-19 11:47:59","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, RAN WG2","Cc":"SA WG2","lsoriginalls":"C1-188593","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900028.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900033","title":"LS from CT WG1: LS on 3GPP PS data off and congestion control applied by AMF","source":"CT WG1","contact":"Ivo Sedlacek","contact-id":41880,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 discussed stage-3 solution for ensuring that the SMF is informed about changed 3GPP PS data off UE status when DNN based congestion control, S-NSSAI only based congestion control or S-NSSAI+DNN based congestion control are applied. In such case, the UE sends an UL NAS TRANSPORT message carrying a PDU SESSION MODIFICATION REQUEST message containing the 3GPP PS data off UE status PCO parameter indicating the changed 3GPP PS data off UE status. CT WG1 identified that, when the AMF applies DNN based congestion control, S-NSSAI only based congestion control or S-NSSAI+DNN based congestion control, such PDU SESSION MODIFICATION REQUEST message would not be delivered from the AMF to the SMF since: - the AMF does not inspect the 5GSM message received from the UE; and - the request type provided by the UE to the AMF so far does not distinguish such type of PDU SESSION MODIFICATION REQUEST message from other types of PDU SESSION MODIFICATION REQUEST messages. Question: CT WG1 would like to ask SA WG2 whether a PDU SESSION MODIFICATION REQUEST message containing the 3GPP PS data off UE status PCO parameter indicating the changed 3GPP PS data off UE status needs to be delivered from the AMF to the SMF, even when the AMF applies DNN based congestion control, S-NSSAI only based congestion control or S-NSSAI+DNN based congestion control. Action: CT WG1 would like to ask SA WG2 to answer the question above and update SA WG2 technical specifications, if deemed necessary.","secretary_remarks":"Responses drafted in S2-1900152 and S2-1900478. Final response in S2-1901335","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":"replied to","reservation_date":"2018-12-19 11:46:38","uploaded":"2018-12-19 11:47:59","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-188927","lsreply":"S2-1901335","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900033.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900034","title":"LS from CT WG1: Reply LS on Routing ID","source":"CT WG1","contact":"Jennifer Liu","contact-id":43418,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA WG3, TSG CT and SA WG2 for their LS on Routing ID. CT WG1 has agreed stage 3 solution in CR C1-188946. Action: CT WG1 kindly asks SA WG3 and SA WG2 to take the CT WG1 agreements into account.","secretary_remarks":"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":11570,"status":"postponed","reservation_date":"2018-12-19 11:46:38","uploaded":"2018-12-19 11:47:59","revisionof":"","revisedto":"S2-1901412","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, SA WG2","Cc":"TSG CT, CT WG4, CT WG6","lsoriginalls":"C1-188979","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900034.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900073","title":"Registration Procedure Update with Inter PLMN AMF Reallocation","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If old AMF has UE context for another access type, step 14e is skipped, otherwise, the Old AMF unsubscribes with the UDM for subscription data using Nudm_SDM_unsubscribe . If the new serving AMF and the SMF are in different PLMN, the new serving AMF does not send message to the SMF and step 17 is skipped. Step 18 is updated with that if the new AMF and the old AMF are in the same PLMN, the new AMF creates an NGAP UE association towards the N3IWF to which the UE is connected . New steps 20a to 20c are added to register the new AMF to the UDM for non-3GPP access after step 18,19 are successfully performed, and the UDM will deregister the old AMF and the old AMF unsubscribe the SDM change notification.","secretary_remarks":"Revised in parallel session to S2-1901100.","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-01-11 07:54:53","uploaded":"2019-01-15 12:43:38","revisionof":"","revisedto":"S2-1901100","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":871.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900073.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900151","title":"AMF transfer of PDU Session Modification Request for Data Off reporting during congestion control","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the AMF shall not reject any PDU Session Modification Request message carrying Data Off status when congestion control applies. Remove the incorrect statement 'While the back-off timer for the specific DNN is running, then the UE will not send any NAS messages for the specific DNN'.","secretary_remarks":"Merged into S2-1901098.","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":"merged","reservation_date":"2019-01-13 14:34:01","uploaded":"2019-01-15 02:50:05","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":765.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900151.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900152","title":"[DRAFT] Reply LS on 3GPP PS data off and congestion control applied by AMF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This LS provides a response to CT WG1 for the handling of PDU Session Modification Requests related to Dataoff Status during congestion","secretary_remarks":"Response to S2-1900033. Revised in parallel session, merging S2-1900478, to S2-1901099.","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":"revised","reservation_date":"2019-01-13 14:34:02","uploaded":"2019-01-15 02:50:05","revisionof":"","revisedto":"S2-1901099","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_130_Kochi\/Docs\/S2-1900152.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900176","title":"Correction to UE parameters update procedure","source":"Qualcomm Incorporated","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that in 4.20.2 that the UE performs an initial registration procedure.","secretary_remarks":"Revised in parallel session to S2-1901213.","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":"revised","reservation_date":"2019-01-13 23:54:49","uploaded":"2019-01-15 04:19:11","revisionof":"","revisedto":"S2-1901213","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":889.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900176.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900283","title":"Corrections to AMF overload control procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align text to the RAN WG2 CR and remove the randomisation of indication. Make the support of RRC-Inactive normative, as well as the content of note 1. It is clarified the behaviour in the RAN is applied to the UEs the AMF serves.","secretary_remarks":"Revised in parallel session to S2-1901096.","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-01-14 13:50:26","uploaded":"2019-01-15 12:15:06","revisionof":"","revisedto":"S2-1901096","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":806.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900283.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900420","title":"Clarification on NAS level congestion control","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that AMF stores the back-off timer received from SMF and applies S-NSSAI and DNN based congestion control in order to align with stage 3 description. Correct the wrong description about AMF behaviour for the S-NSSAI and DNN based congestion control. Clarify the case that a back-off timer is not associated to any S-NSSAI and optionally any DNN.","secretary_remarks":"Revised in parallel session, merging S2-1900458, to S2-1901097.","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-01-15 04:09:24","uploaded":"2019-01-15 04:44:16","revisionof":"","revisedto":"S2-1901097","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":834.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900420.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900421","title":"[DRAFT] Reply LS on SM request reattempt upon PLMN change","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-1901xxx","secretary_remarks":"Response to S2-1900008. Revised in parallel session to S2-1901095.","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":"revised","reservation_date":"2019-01-15 04:09:25","uploaded":"2019-01-15 04:44:16","revisionof":"","revisedto":"S2-1901095","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_130_Kochi\/Docs\/S2-1900421.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900437","title":"Provision to send Operator-defined access category definitions integrity protected","source":"NEC","contact":"Kundan Tiwari","contact-id":75778,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that the Operator-defined access category definitions shall be sent integrity protected. When the UE receives ODACD without integrity protected then the UE will ignore it.","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":11880,"status":"noted","reservation_date":"2019-01-15 06:34:45","uploaded":"2019-01-15 11:24:59","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":840.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900437.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900444","title":"Clarification on Mobility restriction-501","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description on whether SMF need be aware the allowed area information in non roaming, LBO roaming , HR roaming case.","secretary_remarks":"Revised in parallel session to S2-1901101.","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-01-15 06:51:14","uploaded":"2019-01-15 14:36:26","revisionof":"","revisedto":"S2-1901101","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":845.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900444.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900445","title":"Clarification on Mobility restriction-502","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies in HR roaming PDU establishment procedure that V-SMF does not subscribe to UE reachability event. Clarifies in HR roaming PDU Session release procedure that AMF triggers PDU Session release if UE moves into non allowed area and the PDU Session is not for regulatory prioritized services. Clarifies in handover procedures, the AMF notifies to the SMF about the reachability status of the UE. Clarifies in clause 4.15.4.2 that the reachability notification may be sent in mobility procedures other than registration. And that SMF is expected to subscribe to UE reachability notification.","secretary_remarks":"Revised in parallel session to S2-1901102.","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":"revised","reservation_date":"2019-01-15 06:51:16","uploaded":"2019-01-15 14:36:26","revisionof":"","revisedto":"S2-1901102","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":934.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900445.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900458","title":"SM back off timer handling alignment","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - clarify that UE is allowed to send the ESM message for the same S-NSSAI or the combination of S-NSSAI and DNN in the new PLMN even if the back-off timer is received in the old PLMN.","secretary_remarks":"Merged into S2-1901097","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-01-15 07:03:45","uploaded":"2019-01-15 11:31:14","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":851.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900458.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900474","title":"PS Data Off status update when congestion control is applied in AMF","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - If UE with activate ESM back-off timer want to initiate the ESM signalling to update the PS data off status, the indication that the message should not be subject to congestion control is sent along with the ESM signalling in the NAS transport message. - If AMF receives a ESM signalling with indication that the message should not be subject to congestion control in the NAS transport message, AMF will forward the ESM signalling to the SMF.","secretary_remarks":"Revised in parallel session, merging S2-1900151, to S2-1901098.","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":"revised","reservation_date":"2019-01-15 07:18:37","uploaded":"2019-01-15 11:31:14","revisionof":"","revisedto":"S2-1901098","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":853.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900474.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900478","title":"[DRAFT] Reply LS on 3GPP PS data off and congestion control applied by AMF","source":"Qualcomm India Pvt Ltd","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-1900033. Merged into S2-1901099.","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":"merged","reservation_date":"2019-01-15 07:28:02","uploaded":"2019-01-15 11:31:14","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_130_Kochi\/Docs\/S2-1900478.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900481","title":"Clarification on AMF selection using 5G-S-TMSI","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing the description that the 5G-S-TMSI may not be sufficient for AMF selection. Clarifying that 5G-S-TMSI may not be usable for AMF selection.","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":12010,"status":"noted","reservation_date":"2019-01-15 07:32:52","uploaded":"2019-01-15 10:29:36","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":855.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900481.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900482","title":"Correction to UE initiated Service Request procedure","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. removing 5G-S-TMSI from N2 parameters. 2. clarifying N3IWF selects AMF based on GUAMI.","secretary_remarks":"Revised in parallel session to S2-1901212.","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-01-15 07:32:53","uploaded":"2019-01-15 10:29:36","revisionof":"","revisedto":"S2-1901212","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":943.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900482.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900498","title":"Correction to Mobility Restrictions for non-3GPP Access","source":"MediaTek Inc., Ericsson","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is corrected that: A Forbidden Area can be informed to the UE for non-3GPP Access (in which case the whole non-3GPP Access is forbidden in the PLMN) The CN type restriction is corrected according to 24.501 that allows it to apply to both 3GPP\/non-3GPP accesses or only to non-3GPP access.","secretary_remarks":"Revised in parallel session to S2-1901211.","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":"revised","reservation_date":"2019-01-15 08:29:52","uploaded":"2019-01-15 10:00:26","revisionof":"","revisedto":"S2-1901211","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":857.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900498.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900525","title":"Clarification on the UE bahaviors under NAS level congestion control","source":"Vivo","contact":"Wen Wang","contact-id":75748,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When DNN based congestion control or S-NSSAI based congestion control is activated, the UE shall stop the SM back-off timer and respond to the 5GC when UE receives a network initiated Deregistration Request message indicates 're-registration required'.","secretary_remarks":"Revised off-line to S2-1901170.","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":"revised","reservation_date":"2019-01-15 08:55:18","uploaded":"2019-01-15 12:50:32","revisionof":"","revisedto":"S2-1901170","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":860.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900525.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1900571","title":"Allowed Area and Non-Allowed Area encoding","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Both Allowed Area and Non-Allowed Area can be encoded as maximum number of Tracking Areas. Editorial update for consistent spelling of Allowed Area and Non-Allowed Area.","secretary_remarks":"Revised in parallel session to S2-1901210.","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-01-15 10:29:47","uploaded":"2019-01-15 10:42:06","revisionof":"","revisedto":"S2-1901210","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":877.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1900571.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901095","title":"[DRAFT] Reply LS on SM request reattempt upon PLMN change","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-1901xxx","secretary_remarks":"Revision of S2-1900421. 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":11560,"status":"withdrawn","reservation_date":"2019-01-22 02:09:33","uploaded":null,"revisionof":"S2-1900421","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901096","title":"Corrections to AMF overload control procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align text to the RAN WG2 CR and remove the randomisation of indication. Make the support of RRC-Inactive normative, as well as the content of note 1. It is clarified the behaviour in the RAN is applied to the UEs the AMF serves.","secretary_remarks":"Revision of S2-1900283. Revised in parallel session to S2-1901313.","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":"revised","reservation_date":"2019-01-22 02:09:33","uploaded":"2019-01-28 09:47:52","revisionof":"S2-1900283","revisedto":"S2-1901313","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":806.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901096.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901097","title":"Clarification on NAS level congestion control","source":"Intel, Qualcomm Incorporated, MediaTek Inc.","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that AMF stores the back-off timer received from SMF and applies S-NSSAI and DNN based congestion control in order to align with stage 3 description. Correct the wrong description about AMF behaviour for the S-NSSAI and DNN based congestion control. Clarify the case that a back-off timer is not associated to any S-NSSAI and optionally any DNN.","secretary_remarks":"Revision of S2-1900420, merging S2-1900458. Revised in parallel session to S2-1901218.","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":"revised","reservation_date":"2019-01-22 02:09:34","uploaded":"2019-01-28 09:47:52","revisionof":"S2-1900420","revisedto":"S2-1901218","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":834.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901097.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901098","title":"PS Data Off status update when congestion control is applied in AMF","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - If UE with activate ESM back-off timer want to initiate the ESM signalling to update the PS data off status, the indication that the message should not be subject to congestion control is sent along with the ESM signalling in the NAS transport message. - If AMF receives a ESM signalling with indication that the message should not be subject to congestion control in the NAS transport message, AMF will forward the ESM signalling to the SMF.","secretary_remarks":"Revision of S2-1900474, merging S2-1900151. Revised off-line to S2-1901259.","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-01-22 02:09:35","uploaded":"2019-01-28 09:47:52","revisionof":"S2-1900474","revisedto":"S2-1901259","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":853.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901098.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901099","title":"[DRAFT] Reply LS on 3GPP PS data off and congestion control applied by AMF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This LS provides a response to CT WG1 for the handling of PDU Session Modification Requests related to Dataoff Status during congestion","secretary_remarks":"Revision of S2-1900152, merging S2-1900478. Revised in parallel session to S2-1901335.","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-01-22 02:09:36","uploaded":"2019-01-28 09:47:53","revisionof":"S2-1900152","revisedto":"S2-1901335","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_130_Kochi\/Docs\/S2-1901099.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901100","title":"Registration Procedure Update with Inter PLMN AMF Reallocation","source":"Tencent, Huawei, HiSilicon","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If old AMF has UE context for another access type, step 14e is skipped, otherwise, the Old AMF unsubscribes with the UDM for subscription data using Nudm_SDM_unsubscribe . If the new serving AMF and the SMF are in different PLMN, the new serving AMF does not send message to the SMF and step 17 is skipped. Step 18 is updated with that if the new AMF and the old AMF are in the same PLMN, the new AMF creates an NGAP UE association towards the N3IWF to which the UE is connected . New steps 20a to 20c are added to register the new AMF to the UDM for non-3GPP access after step 18,19 are successfully performed, and the UDM will deregister the old AMF and the old AMF unsubscribe the SDM change notification.","secretary_remarks":"Revision of S2-1900073. Revised in parallel session to S2-1901217.","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-01-22 02:09:36","uploaded":"2019-01-28 09:47:53","revisionof":"S2-1900073","revisedto":"S2-1901217","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":871.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901100.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901101","title":"Clarification on Mobility restriction-501","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description on whether SMF need be aware the allowed area information in non roaming, LBO roaming , HR roaming case.","secretary_remarks":"Revision of S2-1900444. Revised in parallel session to S2-1901214.","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":"revised","reservation_date":"2019-01-22 02:09:37","uploaded":"2019-01-28 09:47:53","revisionof":"S2-1900444","revisedto":"S2-1901214","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":845.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901101.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901102","title":"Clarification on Mobility restriction-502","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies in HR roaming PDU establishment procedure that V-SMF does not subscribe to UE reachability event. Clarifies in HR roaming PDU Session release procedure that AMF triggers PDU Session release if UE moves into non allowed area and the PDU Session is not for regulatory prioritized services. Clarifies in handover procedures, the AMF notifies to the SMF about the reachability status of the UE. Clarifies in clause 4.15.4.2 that the reachability notification may be sent in mobility procedures other than registration. And that SMF is expected to subscribe to UE reachability notification.","secretary_remarks":"Revision of S2-1900445. Revised to S2-1901270","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-01-22 02:09:38","uploaded":"2019-01-28 09:47:53","revisionof":"S2-1900445","revisedto":"S2-1901270","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":934.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901102.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901170","title":"Clarification on the UE bahaviors under NAS level congestion control","source":"Vivo","contact":"Wen Wang","contact-id":75748,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When DNN based congestion control or S-NSSAI based congestion control is activated, the UE shall stop the SM back-off timer and respond to the 5GC when UE receives a network initiated Deregistration Request message indicates 're-registration required'.","secretary_remarks":"Revision of S2-1900525. Revised in parallel session to S2-1901216.","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":"revised","reservation_date":"2019-01-23 02:06:01","uploaded":"2019-01-29 14:04:13","revisionof":"S2-1900525","revisedto":"S2-1901216","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":860.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901170.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901210","title":"Allowed Area and Non-Allowed Area encoding","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Both Allowed Area and Non-Allowed Area can be encoded as maximum number of Tracking Areas. Editorial update for consistent spelling of Allowed Area and Non-Allowed Area.","secretary_remarks":"Revision of S2-1900571. Revised in parallel session to S2-1901271.","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":"revised","reservation_date":"2019-01-24 13:06:44","uploaded":"2019-01-29 14:08:08","revisionof":"S2-1900571","revisedto":"S2-1901271","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":877.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901210.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901211","title":"Correction to Mobility Restrictions for non-3GPP Access","source":"MediaTek Inc., Ericsson","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is corrected that: A Forbidden Area can be informed to the UE for non-3GPP Access (in which case the whole non-3GPP Access is forbidden in the PLMN) The CN type restriction is corrected according to 24.501 that allows it to apply to both 3GPP\/non-3GPP accesses or only to non-3GPP access.","secretary_remarks":"Revision of S2-1900498. 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":12000,"status":"agreed","reservation_date":"2019-01-24 13:06:45","uploaded":"2019-01-29 14:08:08","revisionof":"S2-1900498","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":857.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190155","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901211.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901212","title":"Correction to UE initiated Service Request procedure","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. removing 5G-S-TMSI from N2 parameters. 2. clarifying N3IWF selects AMF based on GUAMI.","secretary_remarks":"Revision of S2-1900482. 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":12030,"status":"agreed","reservation_date":"2019-01-24 13:06:46","uploaded":"2019-01-29 14:08:08","revisionof":"S2-1900482","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":943.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190158","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901212.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901213","title":"Correction to UE parameters update procedure","source":"Qualcomm Incorporated","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that in 4.20.2 that the UE performs an initial registration procedure.","secretary_remarks":"Revision of S2-1900176. Revised in parallel session to S2-1901272.","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":"revised","reservation_date":"2019-01-24 13:06:47","uploaded":"2019-01-29 14:08:09","revisionof":"S2-1900176","revisedto":"S2-1901272","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":889.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901213.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901214","title":"Clarification on Mobility restriction-501","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description on whether SMF need be aware the allowed area information in non roaming, LBO roaming , HR roaming case.","secretary_remarks":"Revision of S2-1901101. 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":11910,"status":"postponed","reservation_date":"2019-01-24 13:06:48","uploaded":"2019-01-29 14:08:09","revisionof":"S2-1901101","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":845.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901214.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901216","title":"Clarification on the UE bahaviors under NAS level congestion control","source":"Vivo","contact":"Wen Wang","contact-id":75748,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When DNN based congestion control or S-NSSAI based congestion control is activated, the UE shall stop the SM back-off timer and respond to the 5GC when UE receives a network initiated Deregistration Request message indicates 're-registration required'.","secretary_remarks":"Revision of S2-1901170. Revised in parallel session to S2-1901334.","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-01-24 13:06:50","uploaded":"2019-01-29 14:08:10","revisionof":"S2-1901170","revisedto":"S2-1901334","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":860.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901216.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901217","title":"Registration Procedure Update with Inter PLMN AMF Reallocation","source":"Tencent, Huawei, HiSilicon","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If old AMF has UE context for another access type, step 14e is skipped, otherwise, the Old AMF unsubscribes with the UDM for subscription data using Nudm_SDM_unsubscribe . If the new serving AMF and the SMF are in different PLMN, the new serving AMF does not send message to the SMF and step 17 is skipped. Step 18 is updated with that if the new AMF and the old AMF are in the same PLMN, the new AMF creates an NGAP UE association towards the N3IWF to which the UE is connected . New steps 20a to 20c are added to register the new AMF to the UDM for non-3GPP access after step 18,19 are successfully performed, and the UDM will deregister the old AMF and the old AMF unsubscribe the SDM change notification.","secretary_remarks":"Revision of S2-1901100. Revised in parallel session to S2-1901269.","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":"revised","reservation_date":"2019-01-24 13:06:51","uploaded":"2019-01-29 14:08:10","revisionof":"S2-1901100","revisedto":"S2-1901269","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":871.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901217.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901218","title":"Clarification on NAS level congestion control","source":"Intel, Qualcomm Incorporated, MediaTek Inc.","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that AMF stores the back-off timer received from SMF and applies S-NSSAI and DNN based congestion control in order to align with stage 3 description. Correct the wrong description about AMF behaviour for the S-NSSAI and DNN based congestion control. Clarify the case that a back-off timer is not associated to any S-NSSAI and optionally any DNN.","secretary_remarks":"Revision of S2-1901097. Revised off-line to S2-1901268.","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-01-24 13:06:52","uploaded":"2019-01-29 14:08:11","revisionof":"S2-1901097","revisedto":"S2-1901268","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":834.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901218.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901259","title":"PS Data Off status update when congestion control is applied in AMF","source":"Qualcomm Incorporated, Intel, KPN, Ericsson","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - If UE with activate ESM back-off timer want to initiate the ESM signalling to update the PS data off status, the indication that the message should not be subject to congestion control is sent along with the ESM signalling in the NAS transport message. - If AMF receives a ESM signalling with indication that the message should not be subject to congestion control in the NAS transport message, AMF will forward the ESM signalling to the SMF.","secretary_remarks":"Revision of S2-1901098. Agreed in parallel session. Revised to S2-1901389.","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":"revised","reservation_date":"2019-01-24 13:07:28","uploaded":"2019-01-29 14:13:35","revisionof":"S2-1901098","revisedto":"S2-1901389","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":853.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901259.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901268","title":"Clarification on NAS level congestion control","source":"Intel, Qualcomm Incorporated, MediaTek Inc.","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that AMF stores the back-off timer received from SMF and applies S-NSSAI and DNN based congestion control in order to align with stage 3 description. Correct the wrong description about AMF behaviour for the S-NSSAI and DNN based congestion control. Clarify the case that a back-off timer is not associated to any S-NSSAI and optionally any DNN.","secretary_remarks":"Revision of S2-1901218. Revised in parallel session to S2-1901333.","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-01-24 13:07:37","uploaded":"2019-01-29 14:13:35","revisionof":"S2-1901218","revisedto":"S2-1901333","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":834.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901268.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901269","title":"Registration Procedure Update with Inter PLMN AMF Reallocation","source":"Tencent, Huawei, HiSilicon","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If old AMF has UE context for another access type, step 14e is skipped, otherwise, the Old AMF unsubscribes with the UDM for subscription data using Nudm_SDM_unsubscribe . If the new serving AMF and the SMF are in different PLMN, the new serving AMF does not send message to the SMF and step 17 is skipped. Step 18 is updated with that if the new AMF and the old AMF are in the same PLMN, the new AMF creates an NGAP UE association towards the N3IWF to which the UE is connected . New steps 20a to 20c are added to register the new AMF to the UDM for non-3GPP access after step 18,19 are successfully performed, and the UDM will deregister the old AMF and the old AMF unsubscribe the SDM change notification.","secretary_remarks":"Revision of S2-1901217. Revised in parallel session to S2-1901336.","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-01-24 13:07:38","uploaded":"2019-01-29 14:13:35","revisionof":"S2-1901217","revisedto":"S2-1901336","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":871.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901269.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901270","title":"Clarification on Mobility restriction-502","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies in HR roaming PDU establishment procedure that V-SMF does not subscribe to UE reachability event. Clarifies in HR roaming PDU Session release procedure that AMF triggers PDU Session release if UE moves into non allowed area and the PDU Session is not for regulatory prioritized services. Clarifies in handover procedures, the AMF notifies to the SMF about the reachability status of the UE. Clarifies in clause 4.15.4.2 that the reachability notification may be sent in mobility procedures other than registration. And that SMF is expected to subscribe to UE reachability notification.","secretary_remarks":"Revision of S2-1901102. Revised to S2-1901385.","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-01-24 13:07:39","uploaded":"2019-01-29 14:13:35","revisionof":"S2-1901102","revisedto":"S2-1901385","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":934.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901270.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901271","title":"Allowed Area and Non-Allowed Area encoding","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Both Allowed Area and Non-Allowed Area can be encoded as maximum number of Tracking Areas. Editorial update for consistent spelling of Allowed Area and Non-Allowed Area.","secretary_remarks":"Revision of S2-1901210. For e-mail approval. e-mail revision 1 approved. Revised to S2-1901400.","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":"revised","reservation_date":"2019-01-24 13:07:40","uploaded":"2019-01-29 14:13:35","revisionof":"S2-1901210","revisedto":"S2-1901400","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":877.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901271.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901272","title":"Correction to UE parameters update procedure","source":"Qualcomm Incorporated","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that in 4.20.2 that the UE performs an initial registration procedure.","secretary_remarks":"Revision of S2-1901213. 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":12060,"status":"agreed","reservation_date":"2019-01-24 13:07:41","uploaded":"2019-01-29 14:13:35","revisionof":"S2-1901213","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":889.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190157","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901272.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901313","title":"Corrections to AMF overload control procedure","source":"Nokia, Nokia Shanghai Bell, NEC","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align text to the RAN WG2 CR and remove the randomisation of indication. Make the support of RRC-Inactive normative, as well as the content of note 1. It is clarified the behaviour in the RAN is applied to the UEs the AMF serves.","secretary_remarks":"Revision of S2-1901096. Revised in parallel session to S2-1901332.","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-01-24 13:07:42","uploaded":"2019-01-29 14:17:56","revisionof":"S2-1901096","revisedto":"S2-1901332","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":806.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901313.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901332","title":"Corrections to AMF overload control procedure","source":"Nokia, Nokia Shanghai Bell, NEC","contact":"Alessio Casati","contact-id":68028,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align text to the RAN WG2 CR and remove the randomisation of indication. Make the support of RRC-Inactive normative, as well as the content of note 1. It is clarified the behaviour in the RAN is applied to the UEs the AMF serves.","secretary_remarks":"Revision of S2-1901313. 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":11620,"status":"agreed","reservation_date":"2019-01-25 12:25:40","uploaded":"2019-01-29 14:18:03","revisionof":"S2-1901313","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":806.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190155","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901332.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901333","title":"Clarification on NAS level congestion control","source":"Intel, Qualcomm Incorporated, MediaTek Inc., Ericsson, Sharp, ZTE, LG Electronics, OPPO, Samsung","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that AMF stores the back-off timer received from SMF and applies S-NSSAI and DNN based congestion control in order to align with stage 3 description. Correct the wrong description about AMF behaviour for the S-NSSAI and DNN based congestion control. Clarify the case that a back-off timer is not associated to any S-NSSAI and optionally any DNN.","secretary_remarks":"Revision of S2-1901268. For e-mail approval. e-mail revision 6 approved. Revised to S2-1901399.","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":"revised","reservation_date":"2019-01-25 12:25:41","uploaded":"2019-01-29 14:18:03","revisionof":"S2-1901268","revisedto":"S2-1901399","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":834.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901333.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901334","title":"Clarification on the UE bahaviors under NAS level congestion control","source":"Vivo","contact":"Wen Wang","contact-id":75748,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When DNN based congestion control or S-NSSAI based congestion control is activated, the UE shall stop the SM back-off timer and respond to the 5GC when UE receives a network initiated Deregistration Request message indicates 're-registration required'.","secretary_remarks":"Revision of S2-1901216. 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":11720,"status":"agreed","reservation_date":"2019-01-25 12:25:42","uploaded":"2019-01-29 14:18:03","revisionof":"S2-1901216","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":860.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190155","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901334.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901335","title":"Reply LS on 3GPP PS data off and congestion control applied by AMF","source":"SA WG2","contact":"George Foti","contact-id":41317,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachment: TS 23.501 CR0853 (S2-1901389)","secretary_remarks":"Revision of S2-1901099. Agreed in parallel session. This was removed from block approval. 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":11810,"status":"approved","reservation_date":"2019-01-25 12:25:43","uploaded":"2019-01-29 14:18:04","revisionof":"S2-1901099","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1900033","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901335.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901336","title":"Registration Procedure Update with Inter PLMN AMF Reallocation","source":"Tencent, Huawei, HiSilicon","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If old AMF has UE context for another access type, step 14e is skipped, otherwise, the Old AMF unsubscribes with the UDM for subscription data using Nudm_SDM_unsubscribe . If the new serving AMF and the SMF are in different PLMN, the new serving AMF does not send message to the SMF and step 17 is skipped. Step 18 is updated with that if the new AMF and the old AMF are in the same PLMN, the new AMF creates an NGAP UE association towards the N3IWF to which the UE is connected . New steps 20a to 20c are added to register the new AMF to the UDM for non-3GPP access after step 18,19 are successfully performed, and the UDM will deregister the old AMF and the old AMF unsubscribe the SDM change notification.","secretary_remarks":"Revision of S2-1901269. 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-01-25 12:25:43","uploaded":"2019-01-29 14:18:04","revisionof":"S2-1901269","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":871.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-190157","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901336.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901385","title":"Clarification on Mobility restriction-502","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies in HR roaming PDU establishment procedure that V-SMF does not subscribe to UE reachability event. Clarifies in HR roaming PDU Session release procedure that AMF triggers PDU Session release if UE moves into non allowed area and the PDU Session is not for regulatory prioritized services. Clarifies in handover procedures, the AMF notifies to the SMF about the reachability status of the UE. Clarifies in clause 4.15.4.2 that the reachability notification may be sent in mobility procedures other than registration. And that SMF is expected to subscribe to UE reachability notification.","secretary_remarks":"Revision of S2-1901270. 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":11950,"status":"agreed","reservation_date":"2019-01-25 12:26:14","uploaded":"2019-01-29 14:18:10","revisionof":"S2-1901270","revisedto":"S2-1901858","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":934.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190158","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901385.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901389","title":"PS Data Off status update when congestion control is applied in AMF","source":"Qualcomm Incorporated, Intel, KPN, Ericsson","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - If UE with activate ESM back-off timer want to initiate the ESM signalling to update the PS data off status, the indication that the message should not be subject to congestion control is sent along with the ESM signalling in the NAS transport message. - If AMF receives a ESM signalling with indication that the message should not be subject to congestion control in the NAS transport message, AMF will forward the ESM signalling to the SMF.","secretary_remarks":"Revision of S2-1901259. This CR was agreed. Revised at S2#131 in S2-1901704","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-01-25 12:26:17","uploaded":"2019-01-29 14:18:11","revisionof":"S2-1901259","revisedto":"S2-1901488, S2-1901704","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":853.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901389.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901399","title":"Clarification on NAS level congestion control","source":"Intel, Qualcomm Incorporated, MediaTek Inc., Ericsson, Sharp, ZTE, LG Electronics, OPPO, Samsung","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that AMF stores the back-off timer received from SMF and applies S-NSSAI and DNN based congestion control in order to align with stage 3 description. Correct the wrong description about AMF behaviour for the S-NSSAI and DNN based congestion control. Clarify the case that a back-off timer is not associated to any S-NSSAI and optionally any DNN.","secretary_remarks":"e-mail revision 6 of S2-1901333. This CR was agreed. Revised at S2#131 in S2-1901878","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11671,"status":"revised","reservation_date":"2019-02-01 16:50:54","uploaded":"2019-02-01 16:52:35","revisionof":"S2-1901333","revisedto":"S2-1901878","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":834.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901399.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901400","title":"Allowed Area and Non-Allowed Area encoding","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Both Allowed Area and Non-Allowed Area can be encoded as maximum number of Tracking Areas. Editorial update for consistent spelling of Allowed Area and Non-Allowed Area.","secretary_remarks":"e-mail revision 1 of S2-1901271. This CR was agreed. Revised at S2#131 in S2-1902140","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11981,"status":"revised","reservation_date":"2019-02-01 16:50:55","uploaded":"2019-02-01 16:52:35","revisionof":"S2-1901271","revisedto":"S2-1902140","release":"Rel-16","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":877.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_130_Kochi\/Docs\/S2-1901400.zip","group":"S2","meeting":"S2-130","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]