[{"name":"S2-1811667","title":"LS from CT WG1: LS on SM request reattempt upon PLMN change","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"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":"Response drafted in S2-1812310. 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":11410,"status":"postponed","reservation_date":"2018-11-16 07:43:03","uploaded":"2018-11-21 06:07:13","revisionof":"","revisedto":"","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_129BIS_West_Palm_Beach\/Docs\/S2-1811667.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811811","title":"UE Identifier provided during Registration Procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UE should include 5G-GUTI mapped from EPS GUTI available in the UE during initial registration. Also UE should include appropriate GUAMI in the AS signaling.","secretary_remarks":"Revised in parallel session to S2-1812936.","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":"2018-11-19 07:08:33","uploaded":"2018-11-20 14:37:12","revisionof":"","revisedto":"S2-1812936","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":816.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811811.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811813","title":"Data Volume Reporting for Option 4\/7","source":"Nokia, Nokia Shanghai Bell, AT&T, Qualcomm Incorporated, Telecom Italia","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce support for secondary RAT reporting. Inherit similar solution and principles as done for Option 3","secretary_remarks":"Revision of S2-1811245 from S2-129. Revised in parallel session to S2-1813078.","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":"revised","reservation_date":"2018-11-19 07:08:35","uploaded":"2018-11-20 14:37:12","revisionof":"S2-1811245","revisedto":"S2-1813078","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":661.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811813.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811814","title":"Data Volume Reporting for Option 4\/7 - Procedure updates","source":"Nokia, Nokia Shanghai Bell, AT&T, Qualcomm Incorporated, Telecom Italia","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce support for secondary RAT reporting. Inherit similar solution and principles as done for Option 3. Updates to following procedure Handover\u00a0: N2\/Xn AN release CN initiated Selective PDU Session release For N2\/N11, it is part of N2 SM Information\u00a0; For N16, it is a separate attribute.","secretary_remarks":"Wrong TS number and CR number requested. Revised in parallel session to S2-1813079.","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":"revised","reservation_date":"2018-11-19 07:08:36","uploaded":"2018-11-20 14:37:12","revisionof":"","revisedto":"S2-1813079","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":698.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811814.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811815","title":"Configuration Transfer Procedure","source":"Nokia, Nokia Shanghai Bell, Qualcomm Incorporated","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Complete the specification for configuration transfer for AMF <-> AMF and AMF <-> MME interfaces, also generically define the procedure in order to align with RAN specification.","secretary_remarks":"Revision of S2-1810428 from S2-129. Revised in parallel session to S2-1813080.","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":"2018-11-19 07:08:38","uploaded":"2018-11-20 14:37:12","revisionof":"S2-1810428","revisedto":"S2-1813080","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":662.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811815.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811917","title":"Registration procedure with different Registration types","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align the notation of Registration procedure(s) with usage in 23.502 and 24.501 i.e.: Whenever possible explicitly refer to Initial Registration, Periodic Registration Update and Mobility Registration Update. When there is a need to explicitly limit the reference to Mobility Registration Update that is not due to mobility describe it as 'Mobility Registration Update (not due to mobility)'. When the Registration Type does not matter, then simply refer to Registration procedure.","secretary_remarks":"Revised in parallel session to S2-1812937.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":10960,"status":"revised","reservation_date":"2018-11-19 12:17:26","uploaded":"2018-11-20 13:43:50","revisionof":"","revisedto":"S2-1812937","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":708.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811917.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811918","title":"Registration procedure with different Registration types","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align the notation of Registration procedure(s) i.e.: Whenever possible explicitly refer to Initial Registration, Periodic Registration Update and Mobility Registration Update. When there is a need to explicitly limit the reference to Mobility Registration Update that is not due to mobility describe it as 'Mobility Registration Update (not due to mobility)'. When the Registration Type does not matter, then simply refer to Registration procedure.","secretary_remarks":"Revised in parallel session to S2-1812938.","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":"2018-11-19 12:17:28","uploaded":"2018-11-20 13:43:50","revisionof":"","revisedto":"S2-1812938","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":823.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811918.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811925","title":"AUSF and UDM selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The list of different factors that AUSF and UDM NF consumers can use to select an AUSF and UDM instance is provided by order of relevance when available at the AUSF\/UDM NF consumer. The use and access of the different factors is clarified. The use of AUSF and UDM Group IDs is aligned when it comes to the availability of GID by NF consumers only within HPLMN 'Routing ID' term is replaced by 'Routing Indicator' as defined in 23.003 and a formal definition for Routing Indicator is included in the TS. The handling of the default value of the 'Routing Indicator' is also clarified.","secretary_remarks":"Revised in parallel session to S2-1813076.","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":"revised","reservation_date":"2018-11-19 12:17:32","uploaded":"2018-11-20 13:43:50","revisionof":"","revisedto":"S2-1813076","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":710.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811925.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811926","title":"AUSF and UDM selection in 5GC NFs","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF stores the UE's Routing Indicator or UDM\/AUSF Group ID the SUPI belongs to and includes it together with SUPI in network signalling between AMF and other NFs within the 5GC requiring interaction with the UDM. The AMF only provides either the UE's Routing Indicator or the AUSF\/UDM Group ID based on availability of such information at the AMF (e.g. if the AMF received the Routing Indicator from the UE, the AMF just provides the Routing Indicator to other 5GC NFs). The following service operations are impacted: To other AMFs, Namf_Communication_UEContextTransfer. To SMF over Nsmf_PDUSession_Create\/CreateSMContext service operations. The AUSF\/UDM Group ID is only available to AMF in the non roaming case so it is not included in Nsmf_PDUSession_Create operation. To SMSF over Nsmsf_SMService_Activate. These other 5GC NFs can execute AUSF selection (in AMF) and UDM selection based on the UE's Routing Indicator or AUSF\/UDM Group ID if provided by the AMF.","secretary_remarks":"Revised in parallel session to S2-1813077.","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":"revised","reservation_date":"2018-11-19 12:17:33","uploaded":"2018-11-20 13:43:50","revisionof":"","revisedto":"S2-1813077","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":825.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811926.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811970","title":"Registration procedure updates due to UE Policy Control Service","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: After sending REGISTRATION ACCEPT to the UE, new AMF performs an UE Policy Association Establishment as defined in clause\u00a04.16.11 and if applicable, old AMF as defined in clause\u00a04.16.11. AMF inititaes UE Policy Association Termination at deregistration. Other clean ups regarding UE Policy Handling.","secretary_remarks":"Revised in parallel session to S2-1813081.","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":"revised","reservation_date":"2018-11-19 15:04:25","uploaded":"2018-11-20 05:17:51","revisionof":"","revisedto":"S2-1813081","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":827.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811970.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812075","title":"Clarification on OVERLOAD behaviour for the EUTRA connected to 5GC","source":"NTT DOCOMO INC.","contact":"Kenichiro Aoyagi","contact-id":73277,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the AMF overload control is applied only for the UEs connected to 5GC","secretary_remarks":"Revised in parallel session to S2-1813088.","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":"revised","reservation_date":"2018-11-20 01:30:55","uploaded":"2018-11-20 06:30:19","revisionof":"","revisedto":"S2-1813088","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":716.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812075.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812189","title":"Clarification on ID provision to (R)AN for AMF selection in registration procedure","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provides 5G-S-TMSI or GUAMI to 5G AN instead of 5G GUTI during the registration procedure, and update the description about the AMF seletion in AN.","secretary_remarks":"Revised in parallel session to S2-1813082.","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":"2018-11-20 07:42:44","uploaded":"2018-11-20 14:59:39","revisionof":"","revisedto":"S2-1813082","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":847.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812189.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812190","title":"Update the UCU procedure to align with operator defined access category","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description to properly introduce the operator defined access category and align with 24.501.","secretary_remarks":"Revised in parallel session to S2-1813083.","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":"2018-11-20 07:42:46","uploaded":"2018-11-20 14:59:39","revisionof":"","revisedto":"S2-1813083","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":724.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812190.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812191","title":"Update the UCU procedure to align with operator defined access category","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the 'Operator-defined Access Category' related description to the UE Configuration Update procedure in TS 23.502. Add the 'Operator-defined Access Category' in the procedure of Registration.","secretary_remarks":"Revised in parallel session to S2-1813084.","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":"2018-11-20 07:42:47","uploaded":"2018-11-20 14:59:39","revisionof":"S2-1811234","revisedto":"S2-1813084","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":795.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812191.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812298","title":"[DRAFT] Reply LS on the Unified Access Control over NG interface","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"Reply to RAN WG3 LS on on the Unified Access Control over NG interface (R3-187271)","secretary_remarks":"Response to S2-1812476. Revised in parallel session to S2-1813086.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11370,"status":"revised","reservation_date":"2018-11-20 09:36:40","uploaded":"2018-11-20 09:58:42","revisionof":"","revisedto":"S2-1813086","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812298.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812299","title":"Unified Access Control clarification and triggers","source":"ORANGE?, NEC?, ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Addition of text to properly introduce this feature by its name 2) Addition of the triggering conditions of the Unified Access Control mechanism (similarly to TS 23.401).","secretary_remarks":"Revised in S2-1812457","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11330,"status":"revised","reservation_date":"2018-11-20 09:36:40","uploaded":"2018-11-20 09:58:42","revisionof":"S2-1811566","revisedto":"S2-1812457","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":660.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812299.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812307","title":"SM request reattempt upon PLMN change","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - clarify that UE is not allowed to initiate a ESM message for the S-NSSAI after PLMN change if UE receives a back-off timer in the original PLMN. - The back-off timer receives from a PLMN associated with no S-NSSAI or any combination of S-NSSAI and DNN shall not block UE to send a EMS message without S-NSSAI or without S-NSSAI and DNN in a new PLMN.","secretary_remarks":"This was postponed.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11420,"status":"postponed","reservation_date":"2018-11-20 09:59:34","uploaded":"2018-11-20 13:16:22","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":727.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812307.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812310","title":"[DRAFT] Reply LS on SM request reattempt upon PLMN change","source":"Qualcomm Wireless GmbH","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-1811667. Revised in parallel session to S2-1813087.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11430,"status":"revised","reservation_date":"2018-11-20 10:03:00","uploaded":"2018-11-20 13:16:22","revisionof":"","revisedto":"S2-1813087","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_129BIS_West_Palm_Beach\/Docs\/S2-1812310.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812440","title":"Unified Access Control clarification and triggers","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Addition of text to properly introduce this feature by its name 2) Addition of the triggering conditions of the Unified Access Control mechanism (similarly to TS 23.401).","secretary_remarks":"Revision of S2-1811566 from S2-129. Merged into S2-1813085.","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":"merged","reservation_date":"2018-11-20 14:31:21","uploaded":"2018-11-20 14:54:53","revisionof":"S2-1811566","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":660.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812440.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812453","title":"Avoiding overloading the target of AMF Load Re-Balancing","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Additional text to specify the consideration of the load of the target AMF. 2) Condition removed 3) 'redirect UE(s)' replaced by 'redirect all UEs'.","secretary_remarks":"Revision of S2-1810447 from S2-129. Revised in parallel session to S2-1813089.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11290,"status":"revised","reservation_date":"2018-11-20 14:50:15","uploaded":"2018-11-20 14:52:37","revisionof":"S2-1810447","revisedto":"S2-1813089","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":666.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812453.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812457","title":"Unified Access Control clarification and triggers","source":"ORANGE, NEC, ZTE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Addition of text to properly introduce this feature by its name 2) Addition of the triggering conditions of the Unified Access Control mechanism (similarly to TS 23.401).","secretary_remarks":"Revision of S2-1812299. Revised in parallel session to S2-1813085.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11340,"status":"revised","reservation_date":"2018-11-20 14:56:01","uploaded":"2018-11-20 14:57:22","revisionof":"S2-1812299","revisedto":"S2-1813085","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":660.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812457.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812476","title":"LS from RAN WG3: LS on the Unified Access Control over NG interface","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 discussed Unified Access Control over NG interface. According to TS23.501: The NG-RAN node shall initiate such Unified Access Control when: - all the AMFs connected to this NG-RAN node request to restrict the load for UEs that access the network by sending OVERLOAD START message containing a categorized criteria. There is different understanding in RAN WG3 on what categorized criteria is, and on possible differences with respect to the information contained in the Overload Action: IE in TS 38.413. Action: RAN WG3 kindly asks SA WG2 to clarify what categorized criteria is and on whether it is different with respect to the information contained in the Overload Action: IE in TS 38.413.","secretary_remarks":"Response drafted in S2-1812298. Final response in S2-1813361","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11320,"status":"replied to","reservation_date":"2018-11-21 14:45:10","uploaded":"2018-11-21 14:45:42","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-187271","lsreply":"S2-1813361","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812476.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812936","title":"UE Identifier provided during Registration Procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UE should include 5G-GUTI mapped from EPS GUTI available in the UE during initial registration. Also UE should include appropriate GUAMI in the AS signaling.","secretary_remarks":"Revision of S2-1811811. Revised in parallel session to S2-1813090.","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":"revised","reservation_date":"2018-11-27 15:00:48","uploaded":"2018-12-03 14:18:45","revisionof":"S2-1811811","revisedto":"S2-1813090","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":816.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812936.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812937","title":"Registration procedure with different Registration types","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align the notation of Registration procedure(s) with usage in 23.502 and 24.501 i.e.: Whenever possible explicitly refer to Initial Registration, Periodic Registration Update and Mobility Registration Update. When there is a need to explicitly limit the reference to Mobility Registration Update that is not due to mobility describe it as 'Mobility Registration Update (not due to mobility)'. When the Registration Type does not matter, then simply refer to Registration procedure.","secretary_remarks":"Revision of S2-1811917. 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":10970,"status":"agreed","reservation_date":"2018-11-27 15:00:49","uploaded":"2018-12-03 14:18:45","revisionof":"S2-1811917","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":708.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-181090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812937.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812938","title":"Registration procedure with different Registration types","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align the notation of Registration procedure(s) i.e.: Whenever possible explicitly refer to Initial Registration, Periodic Registration Update and Mobility Registration Update. When there is a need to explicitly limit the reference to Mobility Registration Update that is not due to mobility describe it as 'Mobility Registration Update (not due to mobility)'. When the Registration Type does not matter, then simply refer to Registration procedure.","secretary_remarks":"Revision of S2-1811918. 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":"2018-11-27 15:00:52","uploaded":"2018-12-03 14:18:45","revisionof":"S2-1811918","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":823.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-181090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812938.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813076","title":"AUSF and UDM selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The list of different factors that AUSF and UDM NF consumers can use to select an AUSF and UDM instance is provided by order of relevance when available at the AUSF\/UDM NF consumer. The use and access of the different factors is clarified. The use of AUSF and UDM Group IDs is aligned when it comes to the availability of GID by NF consumers only within HPLMN 'Routing ID' term is replaced by 'Routing Indicator' as defined in 23.003 and a formal definition for Routing Indicator is included in the TS. The handling of the default value of the 'Routing Indicator' is also clarified.","secretary_remarks":"Revision of S2-1811925. Revised off-line to S2-1813369.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11090,"status":"revised","reservation_date":"2018-11-28 19:58:49","uploaded":"2018-12-03 14:24:50","revisionof":"S2-1811925","revisedto":"S2-1813369","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":710.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813076.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813077","title":"AUSF and UDM selection in 5GC NFs","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF stores the UE's Routing Indicator or UDM\/AUSF Group ID the SUPI belongs to and includes it together with SUPI in network signalling between AMF and other NFs within the 5GC requiring interaction with the UDM. The AMF only provides either the UE's Routing Indicator or the AUSF\/UDM Group ID based on availability of such information at the AMF (e.g. if the AMF received the Routing Indicator from the UE, the AMF just provides the Routing Indicator to other 5GC NFs). The following service operations are impacted: To other AMFs, Namf_Communication_UEContextTransfer. To SMF over Nsmf_PDUSession_Create\/CreateSMContext service operations. The AUSF\/UDM Group ID is only available to AMF in the non roaming case so it is not included in Nsmf_PDUSession_Create operation. To SMSF over Nsmsf_SMService_Activate. These other 5GC NFs can execute AUSF selection (in AMF) and UDM selection based on the UE's Routing Indicator or AUSF\/UDM Group ID if provided by the AMF.","secretary_remarks":"Revision of S2-1811926. Revised off-line to S2-1813370.","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":"2018-11-28 19:58:50","uploaded":"2018-12-03 14:24:50","revisionof":"S2-1811926","revisedto":"S2-1813370","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":825.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813077.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813078","title":"Data Volume Reporting for Option 4\/7","source":"Nokia, Nokia Shanghai Bell, AT&T, Qualcomm Incorporated, Telecom Italia","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce support for secondary RAT reporting. Inherit similar solution and principles as done for Option 3","secretary_remarks":"Revision of S2-1811813. 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":11010,"status":"agreed","reservation_date":"2018-11-28 19:58:51","uploaded":"2018-12-03 14:24:50","revisionof":"S2-1811813","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":661.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"SP-181087","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813078.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813079","title":"Data Volume Reporting for Option 4\/7 - Procedure updates","source":"Nokia, Nokia Shanghai Bell, AT&T, Qualcomm Incorporated, Telecom Italia","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce support for secondary RAT reporting. Inherit similar solution and principles as done for Option 3. Updates to following procedure Handover\u00a0: N2\/Xn AN release CN initiated Selective PDU Session release For N2\/N11, it is part of N2 SM Information\u00a0; For N16, it is a separate attribute.","secretary_remarks":"Revision of S2-1811814. 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":11030,"status":"agreed","reservation_date":"2018-11-28 19:58:52","uploaded":"2018-12-03 14:24:51","revisionof":"S2-1811814","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":863.0,"crrevision":"","crcategory":"B","tsg_crp":"SP-181088","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813079.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813080","title":"Configuration Transfer Procedure","source":"Nokia, Nokia Shanghai Bell, Qualcomm Incorporated","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Complete the specification for configuration transfer for AMF <-> AMF and AMF <-> MME interfaces, also generically define the procedure in order to align with RAN specification.","secretary_remarks":"Revision of S2-1811815. Revised in parallel session to S2-1813169.","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":"2018-11-28 19:58:53","uploaded":"2018-12-03 14:24:51","revisionof":"S2-1811815","revisedto":"S2-1813169","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":662.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813080.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813081","title":"Registration procedure updates due to UE Policy Control Service","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: After sending REGISTRATION ACCEPT to the UE, new AMF performs an UE Policy Association Establishment as defined in clause\u00a04.16.11 and if applicable, old AMF as defined in clause\u00a04.16.11. AMF inititaes UE Policy Association Termination at deregistration. Other clean ups regarding UE Policy Handling.","secretary_remarks":"Revision of S2-1811970. Revised in parallel session to S2-1813099.","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":"2018-11-28 19:58:54","uploaded":"2018-12-03 14:24:52","revisionof":"S2-1811970","revisedto":"S2-1813099","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":827.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813081.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813082","title":"Clarification on ID provision to RAN in registration procedure","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provides 5G-S-TMSI or GUAMI to 5G AN instead of 5G GUTI during the registration procedure, and update the description about the AMF seletion in AN.","secretary_remarks":"Revision of S2-1812189. 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":11190,"status":"agreed","reservation_date":"2018-11-28 19:58:55","uploaded":"2018-12-03 14:24:52","revisionof":"S2-1812189","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":847.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-181085","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813082.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813083","title":"Update the UCU procedure to align with operator defined access category","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description to properly introduce the operator defined access category and align with 24.501.","secretary_remarks":"Revision of S2-1812190. Revised in parallel session to S2-1813167.","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":"revised","reservation_date":"2018-11-28 19:58:56","uploaded":"2018-12-03 14:24:53","revisionof":"S2-1812190","revisedto":"S2-1813167","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":724.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813083.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813084","title":"Update the UCU procedure with operator-defined access category definitions","source":"Huawei, Hisilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the 'Operator-defined Access Category' related description to the UE Configuration Update procedure in TS 23.502. Add the 'Operator-defined Access Category' in the procedure of Registration.","secretary_remarks":"Revision of S2-1812191. 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":11240,"status":"agreed","reservation_date":"2018-11-28 19:58:57","uploaded":"2018-12-03 14:24:53","revisionof":"S2-1812191","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":795.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-181091","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813084.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813085","title":"Unified Access Control clarification and triggers","source":"ORANGE, NEC, ZTE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Addition of text to properly introduce this feature by its name 2) Addition of the triggering conditions of the Unified Access Control mechanism (similarly to TS 23.401).","secretary_remarks":"Revision of S2-1812457, merging S2-1812440. Revised in parallel session to S2-1813308.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11350,"status":"revised","reservation_date":"2018-11-28 19:58:58","uploaded":"2018-12-03 14:24:54","revisionof":"S2-1812457","revisedto":"S2-1813308","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":660.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813085.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813086","title":"[DRAFT] Reply LS on the Unified Access Control over NG interface","source":"SA WG2","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"Reply to RAN WG3 LS on on the Unified Access Control over NG interface (R3-187271)","secretary_remarks":"Revision of S2-1812298. Revised in parallel session to S2-1813309.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11380,"status":"revised","reservation_date":"2018-11-28 19:58:59","uploaded":"2018-12-03 14:24:54","revisionof":"S2-1812298","revisedto":"S2-1813309","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813086.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813087","title":"[DRAFT] Reply LS on SM request reattempt upon PLMN change","source":"Qualcomm Wireless GmbH","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-1812310. 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":11440,"status":"withdrawn","reservation_date":"2018-11-28 19:58:59","uploaded":null,"revisionof":"S2-1812310","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813088","title":"Clarification on OVERLOAD behaviour for the EUTRA connected to 5GC","source":"NTT DOCOMO INC., Ericsson","contact":"Kenichiro Aoyagi","contact-id":73277,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the AMF overload control is applied only for the UEs connected to 5GC","secretary_remarks":"Revision of S2-1812075. Revised in parallel session to S2-1813168.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11270,"status":"revised","reservation_date":"2018-11-28 19:58:59","uploaded":"2018-12-03 14:24:54","revisionof":"S2-1812075","revisedto":"S2-1813168","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":716.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813088.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813089","title":"Avoiding overloading the target of AMF Load Re-Balancing","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Additional text to specify the consideration of the load of the target AMF. 2) Condition removed 3) 'redirect UE(s)' replaced by 'redirect all UEs'.","secretary_remarks":"Revision of S2-1812453. Revised in parallel session to S2-1813362.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11300,"status":"revised","reservation_date":"2018-11-28 19:59:00","uploaded":"2018-12-03 14:24:55","revisionof":"S2-1812453","revisedto":"S2-1813362","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":666.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813089.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813090","title":"UE Identifier provided during Registration Procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UE should include 5G-GUTI mapped from EPS GUTI available in the UE during initial registration. Also UE should include appropriate GUAMI in the AS signaling.","secretary_remarks":"Revision of S2-1812936. 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":10950,"status":"agreed","reservation_date":"2018-11-28 19:59:01","uploaded":"2018-12-03 14:24:55","revisionof":"S2-1812936","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":816.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-181090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813090.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813099","title":"Registration procedure updates due to UE Policy Control Service","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: After sending REGISTRATION ACCEPT to the UE, new AMF performs an UE Policy Association Establishment as defined in clause\u00a04.16.11 and if applicable, old AMF as defined in clause\u00a04.16.11. AMF inititaes UE Policy Association Termination at deregistration. Other clean ups regarding UE Policy Handling.","secretary_remarks":"Revision of S2-1813081. Revised in parallel session to S2-1813109.","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":"revised","reservation_date":"2018-11-30 14:06:14","uploaded":"2018-12-03 14:25:26","revisionof":"S2-1813081","revisedto":"S2-1813109","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":827.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813099.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813109","title":"Registration procedure updates due to UE Policy Control Service","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: After sending REGISTRATION ACCEPT to the UE, new AMF performs an UE Policy Association Establishment as defined in clause\u00a04.16.11 and if applicable, old AMF as defined in clause\u00a04.16.11. AMF inititaes UE Policy Association Termination at deregistration. Other clean ups regarding UE Policy Handling.","secretary_remarks":"Revision of S2-1813099. 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":11170,"status":"agreed","reservation_date":"2018-11-30 17:10:07","uploaded":"2018-12-03 14:28:48","revisionof":"S2-1813099","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":827.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-181090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813109.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813167","title":"Update the UCU procedure with operator-defined access category definitions","source":"Huawei, HiSilicon, Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description to properly introduce the operator defined access category and align with 24.501.","secretary_remarks":"Revision of S2-1813083. 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":11220,"status":"agreed","reservation_date":"2018-11-30 16:48:35","uploaded":"2018-12-03 14:25:34","revisionof":"S2-1813083","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":724.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-181091","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813167.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813168","title":"Clarification on OVERLOAD behaviour for the EUTRA connected to 5GC","source":"NTT DOCOMO INC., Ericsson","contact":"Kenichiro Aoyagi","contact-id":73277,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the AMF overload control is applied only for the UEs connected to 5GC","secretary_remarks":"Revision of S2-1813088. 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":11280,"status":"agreed","reservation_date":"2018-11-30 16:48:36","uploaded":"2018-12-03 14:25:34","revisionof":"S2-1813088","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":716.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-181085","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813168.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813169","title":"Configuration Transfer Procedure","source":"Nokia, Nokia Shanghai Bell, Qualcomm Incorporated","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Complete the specification for configuration transfer for AMF <-> AMF and AMF <-> MME interfaces, also generically define the procedure in order to align with RAN specification.","secretary_remarks":"Revision of S2-1813080. Revised in parallel session to S2-1813177.","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":"2018-11-30 16:48:37","uploaded":"2018-12-03 14:25:35","revisionof":"S2-1813080","revisedto":"S2-1813177","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":662.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813169.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813177","title":"Configuration Transfer Procedure","source":"Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Ericsson","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Complete the specification for configuration transfer for AMF <-> AMF and AMF <-> MME interfaces, also generically define the procedure in order to align with RAN specification.","secretary_remarks":"Revision of S2-1813169. 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":11070,"status":"agreed","reservation_date":"2018-11-30 17:06:27","uploaded":"2018-12-03 14:28:23","revisionof":"S2-1813169","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":662.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-181086","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813177.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813308","title":"Unified Access Control clarification and triggers","source":"ORANGE, NEC, ZTE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Addition of text to properly introduce this feature by its name 2) Addition of the triggering conditions of the Unified Access Control mechanism (similarly to TS 23.401).","secretary_remarks":"Revision of S2-1813085. 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":11360,"status":"noted","reservation_date":"2018-11-30 17:06:38","uploaded":"2018-12-03 14:28:43","revisionof":"S2-1813085","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":660.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813308.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813309","title":"[DRAFT] Reply LS on the Unified Access Control over NG interface","source":"SA WG2","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3","secretary_remarks":"Revision of S2-1813086. Revised in parallel session to S2-1813361.","agenda_item_sort_order":19,"ainumber":"6.5.2","ainame":"Common Access Control, RM and CM functions and procedure flows","tdoc_agenda_sort_order":11390,"status":"revised","reservation_date":"2018-11-30 17:06:39","uploaded":"2018-12-03 14:28:43","revisionof":"S2-1813086","revisedto":"S2-1813361","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813309.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813361","title":"Reply LS on the Unified Access Control over NG interface","source":"SA WG2","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3","secretary_remarks":"Revision of S2-1813309. 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":11400,"status":"approved","reservation_date":"2018-11-30 17:11:31","uploaded":"2018-12-03 14:29:02","revisionof":"S2-1813309","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1812476","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813361.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813362","title":"Avoiding overloading the target of AMF Load Re-Balancing","source":"ORANGE","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Additional text to specify the consideration of the load of the target AMF. 2) Condition removed 3) 'redirect UE(s)' replaced by 'redirect all UEs'.","secretary_remarks":"Revision of S2-1813089. 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":11310,"status":"agreed","reservation_date":"2018-11-30 17:11:31","uploaded":"2018-12-03 14:29:02","revisionof":"S2-1813089","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":666.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-181084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813362.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813369","title":"AUSF and UDM selection","source":"Ericsson, Nokia, Nokia Shanghai Bell, Huawei","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The list of different factors that AUSF and UDM NF consumers can use to select an AUSF and UDM instance is provided by order of relevance when available at the AUSF\/UDM NF consumer. The use and access of the different factors is clarified. The use of AUSF and UDM Group IDs is aligned when it comes to the availability of GID by NF consumers only within HPLMN 'Routing ID' term is replaced by 'Routing Indicator' as defined in 23.003 and a formal definition for Routing Indicator is included in the TS. The handling of the default value of the 'Routing Indicator' is also clarified.","secretary_remarks":"Revision of S2-1813076. 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":11100,"status":"agreed","reservation_date":"2018-12-01 15:00:52","uploaded":"2018-12-03 14:29:28","revisionof":"S2-1813076","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":710.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-181084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813369.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813370","title":"AUSF and UDM selection in 5GC NFs","source":"Ericsson, Huawei","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF stores the UE's Routing Indicator or UDM\/AUSF Group ID the SUPI belongs to and includes it together with SUPI in network signalling between AMF and other NFs within the 5GC requiring interaction with the UDM. The AMF only provides either the UE's Routing Indicator or the AUSF\/UDM Group ID based on availability of such information at the AMF (e.g. if the AMF received the Routing Indicator from the UE, the AMF just provides the Routing Indicator to other 5GC NFs). The following service operations are impacted: To other AMFs, Namf_Communication_UEContextTransfer. To SMF over Nsmf_PDUSession_Create\/CreateSMContext service operations. The AUSF\/UDM Group ID is only available to AMF in the non roaming case so it is not included in Nsmf_PDUSession_Create operation. To SMSF over Nsmsf_SMService_Activate. These other 5GC NFs can execute AUSF selection (in AMF) and UDM selection based on the UE's Routing Indicator or AUSF\/UDM Group ID if provided by the AMF.","secretary_remarks":"Revision of S2-1813077. Revised to S2-1813387.","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":"2018-12-01 15:00:53","uploaded":"2018-12-03 14:29:28","revisionof":"S2-1813077","revisedto":"S2-1813387","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":825.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813370.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1813387","title":"AUSF and UDM selection in 5GC NFs","source":"Ericsson, Huawei","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AMF stores the UE's Routing Indicator or UDM\/AUSF Group ID the SUPI belongs to and includes it together with SUPI in network signalling between AMF and other NFs within the 5GC requiring interaction with the UDM. The AMF only provides either the UE's Routing Indicator or the AUSF\/UDM Group ID based on availability of such information at the AMF (e.g. if the AMF received the Routing Indicator from the UE, the AMF just provides the Routing Indicator to other 5GC NFs). The following service operations are impacted: To other AMFs, Namf_Communication_UEContextTransfer. To SMF over Nsmf_PDUSession_Create\/CreateSMContext service operations. The AUSF\/UDM Group ID is only available to AMF in the non roaming case so it is not included in Nsmf_PDUSession_Create operation. To SMSF over Nsmsf_SMService_Activate. These other 5GC NFs can execute AUSF selection (in AMF) and UDM selection based on the UE's Routing Indicator or AUSF\/UDM Group ID if provided by the AMF.","secretary_remarks":"Revision of S2-1813370. 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":11131,"status":"agreed","reservation_date":"2018-12-01 15:01:20","uploaded":"2018-12-03 14:29:34","revisionof":"S2-1813370","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":825.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-181084","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1813387.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]