[{"name":"S2-1901405","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-1900008 from S2#130. Response drafted in S2-1901879. Final response in S2-1902892","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":10890,"status":"replied to","reservation_date":"2019-02-05 10:23:56","uploaded":"2019-02-05 10:27:18","revisionof":"S2-1900008","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-187008","lsreply":"S2-1902892","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901405.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901430","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":"This LS was postponed.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11070,"status":"postponed","reservation_date":"2019-02-05 10:23:58","uploaded":"2019-02-05 10:27:18","revisionof":"","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_131_Tenerife\/Docs\/S2-1901430.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901488","title":"PS Data Off status update when congestion control is applied in AMF","source":"Qualcomm Incorporated(?), Intel(?), KPN(?), Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - If the UE has a back-off timer running and want to initiate the SM procedure to update the PS Data Off status, the UE shall indicate that the carried SM message in the UL NAS Transport should not be subject to congestion control. - If the AMF receives 5GMM message UL NAS Transport indicating that the carried NAS SM message should not be subject to congestion control, AMF shall forward the NAS SM signalling to the SMF. Update in Rev4 Adding missing impact in clauses 5.19.7.1 and 5.19.7.2. In clause 5.19.7.3, 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'. Adding description in clauses 5.19.7.3 and 5.19.7.4 that the SMF ensure that the NAS SM message is not subject to congestion control otherwise the SMF shall reject the message, i.e. the SMF shall reject PDU Session Modification received if it's not for Data Off status reporting.","secretary_remarks":"Revision of S2-1901389 from S2#130. Confirm sources! Merged into S2-1902683.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11000,"status":"merged","reservation_date":"2019-02-15 00:58:44","uploaded":"2019-02-19 11:54:18","revisionof":"S2-1901389","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":853.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901488.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901489","title":"PS Data Off status update when UE in non-allowed area or out of LADN area","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description in clauses 5.3.4.1.1 and 5.24 that Data Off status reporting is allowed when UE is non-allowed area. Add description in clauses 5.6.5 and 5.24 that Data Off status reporting is allowed when UE moves out of LADN area.","secretary_remarks":"Revised in parallel session to S2-1902686.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11120,"status":"revised","reservation_date":"2019-02-15 00:58:45","uploaded":"2019-02-19 11:54:18","revisionof":"","revisedto":"S2-1902686","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":913.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901489.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901512","title":"MM Congestion Control and UE Reachability","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Include another UE reachability case in the clause 5.4.1.2 : The UE in CM-IDLE state is not reachable after the UE enters a TA outside its Registration Area when the MM back-off timer is running as described in clause 5.19.7.2. Update the clause 9.7.2 to resolve the self-confliction description and add description that after the MM back-off timer expires, the UE performs Mobility Registration Update before the UE initiates the MO data or MO signalling if it is not within the registration area and if the UE has a pending MO signalling or MO data. Update the clause 5.4.1.3 as the similar function description that UE performs Mobility Registration Update before the UE initiates the MO data or MO signalling if the UE in MICO mode has a pending MO signalling or MO data.","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":11030,"status":"noted","reservation_date":"2019-02-15 07:10:02","uploaded":"2019-02-19 13:26:37","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":917.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901512.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901630","title":"UE Configuration Update Procedure Correction","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Procedure for anchor change of Ethernet PDU Sessions.","secretary_remarks":"Revised in parallel session to S2-1902684.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11040,"status":"revised","reservation_date":"2019-02-18 02:12:27","uploaded":"2019-02-19 13:26:37","revisionof":"","revisedto":"S2-1902684","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1030.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901630.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901704","title":"PS Data Off status update when congestion control is applied in AMF","source":"Qualcomm Incorporated, [Intel, KPN, Ericsson]?","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Provides answer to LS S2-1901406 on new of RRC est. cause in RRC re-establishment","secretary_remarks":"Revision of S2-1901319 from S2#130. Confirm sources!. Revised in parallel session, merging S2-1901488, to S2-1902683.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11010,"status":"revised","reservation_date":"2019-02-18 17:03:12","uploaded":"2019-02-19 13:00:22","revisionof":"S2-1901389","revisedto":"S2-1902683","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":853.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901704.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901777","title":"Adding a new 5G-GUTI allocation condition","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"CR","for":"Approval","abstract":"This contribution discusses the support for emergency session in standalone NPN.","secretary_remarks":"Revised in parallel session to S2-1902685.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11100,"status":"revised","reservation_date":"2019-02-19 01:31:25","uploaded":"2019-02-19 13:05:01","revisionof":"","revisedto":"S2-1902685","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":958.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901777.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901857","title":"Clarificaiton on Core Network type Restriction","source":"Huawei, Hisillicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the MME\/SGSN is relocated before the timer expires, the old MME\/SGSN shall transfer the current value of the timer to the new MME\/SGSN. The new MME\/SGSN shall start the timer according to the transferred value. Remove the 'consecutive' word.","secretary_remarks":"Revised in parallel session to S2-1902687.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11150,"status":"revised","reservation_date":"2019-02-19 03:51:34","uploaded":"2019-02-19 14:35:58","revisionof":"","revisedto":"S2-1902687","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":975.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901857.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901858","title":"Clarification on Mobility restriction-502","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: If the MME\/SGSN is relocated before the timer expires, the old MME\/SGSN shall transfer the current value of the timer to the new MME\/SGSN. The new MME\/SGSN shall start the timer according to the transferred value. Remove the 'consecutive' word.","secretary_remarks":"Revision of S2-1901385 from S2#130. This was postponed. (S2-1901385 from S2#130 remains 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":11170,"status":"postponed","reservation_date":"2019-02-19 03:51:35","uploaded":"2019-02-19 14:35:58","revisionof":"S2-1901385","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":934.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901858.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901859","title":"Clarification on AMF planned removal","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It proposes that the CN type Restriction also restrict whether the UE is allowed to connect to EPC for this PLMN.","secretary_remarks":"Revised in parallel session to S2-1902688.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11180,"status":"revised","reservation_date":"2019-02-19 03:51:36","uploaded":"2019-02-19 14:35:58","revisionof":"","revisedto":"S2-1902688","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":976.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901859.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901878","title":"Clarification on NAS level congestion control","source":"Intel, Qualcomm Incorporated, MediaTek Inc., Ericsson, Sharp, LG Electronics, OPPO, Samsung","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the solution 32 for slice SLA guarantee in TS 23.791. What the meaning of Slice QoE; How to distinguish the RAN resource configuration\/adjustment by OAM and the RAN resource schedule based on the slice SLA fulfilment Info from NSSF. Clarify the relationship between Guaranteed\/Maximum Slice Radio Resource parameters defined by SA WG2 and RRMPolicyRatio2 defined by SA WG2.","secretary_remarks":"Revision of S2-1901399 from S2#130. Revised in parallel session to S2-1902682.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":10970,"status":"revised","reservation_date":"2019-02-19 04:49:47","uploaded":"2019-02-19 06:12:37","revisionof":"S2-1901399","revisedto":"S2-1902682","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":834.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1901878.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1901879","title":"[DRAFT] Reply to LS C1-187008","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"LS out","for":"Approval","abstract":"Reply to LS C1-187008","secretary_remarks":"Response to S2-1901405. Revised in parallel session to S2-1902681.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":10900,"status":"revised","reservation_date":"2019-02-19 04:49:49","uploaded":"2019-02-19 06:12:37","revisionof":"","revisedto":"S2-1902681","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_131_Tenerife\/Docs\/S2-1901879.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902120","title":"Use of maximum number of TAs","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"discussion","for":"Agreement","abstract":"Discussion paper to explain the technical choices in the revision of S2-1901400.","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":11200,"status":"noted","reservation_date":"2019-02-19 12:23:43","uploaded":"2019-02-19 13:54:55","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902120.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902140","title":"Allowed Area and Non-Allowed Area encoding","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"To: GSMA NG RILTE. CC: CT WG1, SA WG5. Attachments: None.","secretary_remarks":"Revision of S2-1901400 from S2#130. Revised in parallel session to S2-1902689.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11230,"status":"revised","reservation_date":"2019-02-19 12:26:54","uploaded":"2019-02-19 13:54:55","revisionof":"S2-1901400","revisedto":"S2-1902689","release":"Rel-16","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":877.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902140.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902681","title":"[DRAFT] Reply LS on SM request reattempt upon PLMN change","source":"SA WG2","contact":"Changhong Shan","contact-id":45586,"tdoctype":"LS out","for":"Approval","abstract":"Reply to LS C1-187008","secretary_remarks":"Revision of S2-1901879. Revised in parallel session to S2-1902805.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":10910,"status":"revised","reservation_date":"2019-02-26 16:16:07","uploaded":"2019-03-08 10:59:02","revisionof":"S2-1901879","revisedto":"S2-1902805","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_131_Tenerife\/Docs\/S2-1902681.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902682","title":"Clarification on NAS level congestion control","source":"Intel, Qualcomm Incorporated, MediaTek Inc., Ericsson, Sharp, LG Electronics, OPPO, Samsung, ZTE, NEC, Orange","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specification of indirect communication of NF\/NF Services via an intermediary function (Service Communication Proxy - SCP) and delegated discovery by this SCP function. Changes in Rev8: Clause 6.2.x on SCP description Added: - Message forwarding and routing to destination NF\/NF service. - More than one SCP may be present in the communication path between NF Services. -The SCP may be deployed in a distributed manner. - removed the EN on consumer authorization and clarified the bullet about 'Communication Security' in NOTE 1: NOTE 1: Communication security, e.g.authorization of the NF Service Consumer to access the NF Service Producer's API are specified in 3GPP TS 33.501 [29]. Clause 6.3.1 changes: 1) Added: The SCP may interact with the NRF to get a discovery result. 2) Updated to: In case of Indirect Communication without Delegated Discovery the requester NF uses the discovery result to select a NF instance and NF Service type while the associated NF service instance selection may be done by the requester NF or an SCP on behalf of the requester NF. 3) changed: stored -> cached 4) The NRF to be used may be provided by the NF consumer as part of the discovery parameters as a result of a NSSF query. Annex X: 1) changed: query -> discovery 2) added: The SCP may interact with an NRF to get a discovery result. 3) updated figure for model C All the changes in rev8 are highlighted in turqoise or yellow color.","secretary_remarks":"Revision of S2-1901878. Revised in parallel session to S2-1902804.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":10980,"status":"revised","reservation_date":"2019-02-26 16:16:07","uploaded":"2019-03-08 10:59:02","revisionof":"S2-1901878","revisedto":"S2-1902804","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":834.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902682.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902683","title":"PS Data Off status update when congestion control is applied in AMF","source":"Qualcomm Incorporated, Intel, Ericsson, KPN","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Reply to LS C1-187008","secretary_remarks":"Revision of S2-1901704, merging S2-1901488. 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":11020,"status":"agreed","reservation_date":"2019-02-26 16:16:08","uploaded":"2019-03-08 10:59:02","revisionof":"S2-1901704","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":853.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"SP-190155","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902683.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902684","title":"UE Configuration Update Procedure Correction","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the description when the DNN or S-NSSAI based congestion control is activated in AMF. Add a new indication of HPLMN congestion, based on this indication UE knows whether a SM back-off timer is for the RPLMN only or for any other PLMN as well, and behaves accordingly as described in the changes. Apply some editorial and wording changes to make the texts more readable. Clarify the scenario when S-NSSAI based back-off timer is not associated with any S-NSSAI and the scenario when S-NSSAI based back-off timer is not associated with any S-NSSAI and DNN. Address the missing description of network initiated PDU Session Release.","secretary_remarks":"Revision of S2-1901630. Revised in parallel session to S2-1902801.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11050,"status":"revised","reservation_date":"2019-02-26 16:16:09","uploaded":"2019-03-08 10:59:02","revisionof":"S2-1901630","revisedto":"S2-1902801","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1030.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902684.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902685","title":"Adding a new 5G-GUTI allocation condition","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"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 or report 5GSM Core Network Capability or report 'always on' PDU sessions , 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-1901777. 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":11110,"status":"agreed","reservation_date":"2019-02-26 16:16:11","uploaded":"2019-03-08 10:59:03","revisionof":"S2-1901777","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":958.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190156","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902685.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902686","title":"PS Data Off status update when UE in non-allowed area or out of LADN area","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the same AMF services the UE over both 3GPP and non-3GPP access, after the AMF reallocates a new 5G-GUTI via non-3GPP access or 3GPP access, the NG-RAN and UE 3GPP access low layer will be configured based on this new 5G-GUTI. If two different AMFs in different PLMNs service the UE over 3GPP and non-3GPP access separately, only after the AMF serving the UE via 3GPP access reallocates a new 5G-GUTI via 3GPP access, the NG-RAN and UE 3GPP access low layer will be configured based on this new 5G-GUTI.","secretary_remarks":"Revision of S2-1901489. Revised in parallel session to S2-1902802.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11130,"status":"revised","reservation_date":"2019-02-26 16:16:12","uploaded":"2019-03-08 10:59:03","revisionof":"S2-1901489","revisedto":"S2-1902802","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":913.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902686.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902687","title":"Clarificaiton on Core Network type Restriction","source":"Huawei, Hisillicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the AMF shall allocate a new 5G-GUTI under some conditions described in TS 33.501.","secretary_remarks":"Revision of S2-1901857. 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":11160,"status":"agreed","reservation_date":"2019-02-26 16:16:13","uploaded":"2019-03-08 10:59:03","revisionof":"S2-1901857","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":975.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190156","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902687.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902688","title":"Clarification on AMF planned removal","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description in clauses 5.3.4.1.1 and 5.24 that Data Off status reporting is allowed when UE is non-allowed area. Add description in clauses 5.6.5 and 5.24 that Data Off status reporting is allowed when UE moves out of LADN area. Changes from rev1: As also generic NAS (MM) level congestion control will block UE from updating Data Off status change, also MM messages for establishing NAS signalling connection can be requested to be exempted.","secretary_remarks":"Revision of S2-1901859. Revised in parallel session to S2-1902807.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11190,"status":"revised","reservation_date":"2019-02-26 16:16:14","uploaded":"2019-03-08 10:59:03","revisionof":"S2-1901859","revisedto":"S2-1902807","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":976.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902688.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902689","title":"Allowed Area and Non-Allowed Area encoding","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It proposes that the CN type Restriction also restrict whether the UE is allowed to connect to EPC for this PLMN.","secretary_remarks":"Revision of S2-1902140. Revised in parallel session to S2-1902803.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11240,"status":"revised","reservation_date":"2019-02-26 16:16:15","uploaded":"2019-03-08 10:59:03","revisionof":"S2-1902140","revisedto":"S2-1902803","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":877.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902689.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902801","title":"UE Configuration Update Procedure Correction","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"To: SA WG3-LI, SA WG3, GSMA 5GJA TF. CC: GSMA Network Group, CT WG1","secretary_remarks":"Revision of S2-1902684. Revised in parallel session to S2-1902806.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11060,"status":"revised","reservation_date":"2019-02-28 11:12:56","uploaded":"2019-03-08 13:43:28","revisionof":"S2-1902684","revisedto":"S2-1902806","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1030.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902801.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902802","title":"PS Data Off status update when UE in non-allowed area or out of LADN area","source":"Ericsson, Intel, LG Electronics","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"To: RAN WG3.","secretary_remarks":"Revision of S2-1902686. 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":11140,"status":"agreed","reservation_date":"2019-02-28 11:13:02","uploaded":"2019-03-08 13:43:28","revisionof":"S2-1902686","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":913.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190155","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902802.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902803","title":"Allowed Area and Non-Allowed Area encoding","source":"Nokia, Nokia Shanghai Bell, Ericsson, Verizon, AT&T","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the same AMF services the UE over both 3GPP and non-3GPP access, after the AMF reallocates a new 5G-GUTI via non-3GPP access or 3GPP access, the NG-RAN and UE 3GPP access low layer will be configured based on this new 5G-GUTI. If two different AMFs in different PLMNs service the UE over 3GPP and non-3GPP access separately, only after the AMF serving the UE via 3GPP access reallocates a new 5G-GUTI via 3GPP access, the NG-RAN and UE 3GPP access low layer will be configured based on this new 5G-GUTI.","secretary_remarks":"Revision of S2-1902689. Revised in parallel session to S2-1902871.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11250,"status":"revised","reservation_date":"2019-02-28 11:13:06","uploaded":"2019-03-08 13:43:29","revisionof":"S2-1902689","revisedto":"S2-1902871","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":877.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902803.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902804","title":"Clarification on NAS level congestion control","source":"Intel, Qualcomm Incorporated, MediaTek Inc., Ericsson, Sharp, LG Electronics, OPPO, Samsung, ZTE, NEC, Orange","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description in clauses 5.3.4.1.1 and 5.24 that Data Off status reporting is allowed when UE is non-allowed area. Add description in clauses 5.6.5 and 5.24 that Data Off status reporting is allowed when UE moves out of LADN area. Changes from rev1: As also generic NAS (MM) level congestion control will block UE from updating Data Off status change, also MM messages for establishing NAS signalling connection can be requested to be exempted.","secretary_remarks":"Revision of S2-1902682. 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":10990,"status":"agreed","reservation_date":"2019-02-28 11:13:11","uploaded":"2019-03-08 13:43:29","revisionof":"S2-1902682","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":834.0,"crrevision":8.0,"crcategory":"F","tsg_crp":"SP-190155","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902804.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902805","title":"Reply LS on SM request reattempt upon PLMN change","source":"SA WG2","contact":"Changhong Shan","contact-id":45586,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachment: S2-1902804","secretary_remarks":"Revision of S2-1902681. Agreed in parallel session. Revised to S2-1902886.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":10920,"status":"revised","reservation_date":"2019-02-28 11:13:14","uploaded":"2019-03-08 13:43:29","revisionof":"S2-1902681","revisedto":"S2-1902886","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_131_Tenerife\/Docs\/S2-1902805.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902806","title":"UE Configuration Update Procedure Correction","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the description when the DNN or S-NSSAI based congestion control is activated in AMF. Add a new indication of HPLMN congestion, based on this indication UE knows whether a SM back-off timer is for the RPLMN only or for any other PLMN as well, and behaves accordingly as described in the changes. Apply some editorial and wording changes to make the texts more readable. Clarify the scenario when S-NSSAI based back-off timer is not associated with any S-NSSAI and the scenario when S-NSSAI based back-off timer is not associated with any S-NSSAI and DNN. Address the missing description of network initiated PDU Session Release.","secretary_remarks":"Revision of S2-1902801. Revised in parallel session to S2-1902870.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11070,"status":"revised","reservation_date":"2019-02-28 12:37:18","uploaded":"2019-03-08 13:43:29","revisionof":"S2-1902801","revisedto":"S2-1902870","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1030.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902806.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902807","title":"Clarification on AMF planned removal","source":"Huawei, HiSilicon, NEC","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"To: CT WG1. Attachment: S2-1902804","secretary_remarks":"Revision of S2-1902688. Revised in parallel session to S2-1902872.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11200,"status":"revised","reservation_date":"2019-02-28 12:37:22","uploaded":"2019-03-08 13:43:29","revisionof":"S2-1902688","revisedto":"S2-1902872","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":976.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902807.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902870","title":"UE Configuration Update Procedure Correction","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The change assumes the proposal in 23.401 CR3498 (S2-1901602) that new PDN type Ethernet is introduced in EPS. Clause 4.11.1.2.1 and 4.11.1.3.2, at 5GS to EPS mobility, Clarify that the AMF provides the MME capabilty of Ethernet and\/or non-IP to the SMF so that the SMF can decide whether to use Ethernet PDN Type or non-IP PDN Type for PDU Session Type Ethernet. Clarify that dedicated bearer may be triggered by PCF also for Ethernet PDN Type. Clause 4.11.1.2.2 and 4.11.1.3.3, at EPS to 5GS mobility, Add NOTE clarifying if the non-IP PDN Type is originally established as Ethernet PDU Session, it means that Ethernet PDN Type is not supported in EPS. Clause 4.11.5 At PDU Session Establishment, UE indicates its capability of Ethernet PDN Type in EPS to the SMF; SMF provides back the network suppport of Ethernet PDN Type in EPS.","secretary_remarks":"Revision of S2-1902806. 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":11080,"status":"agreed","reservation_date":"2019-03-01 16:59:37","uploaded":"2019-03-08 17:09:04","revisionof":"S2-1902806","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1030.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-190159","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902870.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902871","title":"Allowed Area and Non-Allowed Area encoding","source":"Nokia, Nokia Shanghai Bell, Ericsson, Verizon, AT&T","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An extra parameter is added to all the messages that carry the RFSP index. To support a RAN with a mixture of RAN nodes that support and do not support the Group Index, the MME adds the Group Index In Use in the S1 interface PATCH SWITCH ACKNOWLEDGEMENT and HANDOVER REQUEST messages.","secretary_remarks":"Revision of S2-1902803. 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":11260,"status":"agreed","reservation_date":"2019-03-01 16:59:38","uploaded":"2019-03-08 17:09:04","revisionof":"S2-1902803","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":877.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"SP-190155","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902871.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902872","title":"Clarification on AMF planned removal","source":"Huawei, HiSilicon, NEC","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the UE is configured with a new 5G-GUTI in step 2a via non-3GPP access and the UE is registered to the same PLMN via 3GPP and non-3GPP access, then the UE passes the new 5G-GUTI to its 3GPP access' lower layers . If the UE is configured with a new 5G-GUTI in step 2a over the 3GPP access, the UE passes the new 5G-GUTI to its 3GPP access' lower layers. The duplicated paragraphs in the Step 3 is deleted.","secretary_remarks":"Revision of S2-1902807. 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":11210,"status":"agreed","reservation_date":"2019-03-01 16:59:39","uploaded":"2019-03-08 17:09:04","revisionof":"S2-1902807","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":976.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190156","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902872.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902886","title":"[DRAFT] Reply LS on SM request reattempt upon PLMN change","source":"SA WG2","contact":"Changhong Shan","contact-id":45586,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachment: S2-1902804","secretary_remarks":"Revision of S2-1902805. Revised to S2-1902892.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":10930,"status":"revised","reservation_date":"2019-03-01 16:59:46","uploaded":"2019-03-08 17:09:06","revisionof":"S2-1902805","revisedto":"S2-1902892","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_131_Tenerife\/Docs\/S2-1902886.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902892","title":"Reply LS on SM request reattempt upon PLMN change","source":"SA WG2","contact":"Changhong Shan","contact-id":45586,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachment: S2-1902804","secretary_remarks":"Revision of S2-1902886. 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":10940,"status":"approved","reservation_date":"2019-03-01 16:59:49","uploaded":"2019-03-08 17:09:07","revisionof":"S2-1902886","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1901405","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_131_Tenerife\/Docs\/S2-1902892.zip","group":"S2","meeting":"S2-131","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]