[{"name":"S2-2210166","title":"LS from CT WG1: LS on NSSRG restriction on pending NSSAI","source":"CT WG1","contact":"Sung Hwan Won","contact-id":70307,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has been discussing applicability of NSSRG restriction on pending NSSAI case. CT WG1 is asking following question: Question: Should the UE take the S-NSSAIs in the Pending NSSAI into account when applying NSSRG restrictions in the Requested NSSAI?. Action: CT WG1 kindly request SA WG2 to provide an answer to the above questions.","secretary_remarks":"Revision of Postponed S2-2208103 from SA2#153E","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":10570,"status":"available","reservation_date":"2022-10-21 13:22:35","uploaded":"2022-10-25 12:17:21","revisionof":"S2-2208103","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-224073","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154_Toulouse_2022-11\/Docs\/S2-2210166.zip","group":"S2","meeting":"S2-154","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2210639","title":"Pending NSSAI in AMF Relocation and NRRG Information interaction","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that when an AMF has pending NSSAI for a UE and receives a registration request message containing Requested NSSAI from the UE, then the AMF may send pending NSSAI and the requested NSSAI to the NSSF to get the target AMF which will handle the Pending NSSAI and the requested NSSAI. if NSSRG info applies, the S-NSSAI of Pending NSSAI and the added to the Requested NSSAI shall be sharing at least one NSSRG value. if no NSSRG value is shared the AMF shall send the Requested NSSAI from the UE only.","secretary_remarks":"Not Handled","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11000,"status":"not treated","reservation_date":"2022-04-11 11:05:44","uploaded":"2022-11-04 14:17:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3797.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154_Toulouse_2022-11\/Docs\/S2-2210639.zip","group":"S2","meeting":"S2-154","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2210640","title":"On Interaction between NSSAA and NSSRG","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies the impact on Pending NSSAI when the network detects incompatibility when the Information it holds indicates that Pending NSSAI is not compatible with the allowed NSSAI or requested NSSAI, perhaps due to a recent update received from UDM.","secretary_remarks":"Not Handled","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11010,"status":"not treated","reservation_date":"2022-04-11 11:11:54","uploaded":"2022-11-04 14:17:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3798.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154_Toulouse_2022-11\/Docs\/S2-2210640.zip","group":"S2","meeting":"S2-154","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2210655","title":"On Interaction between NSSAA and NSSRG","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates UE configuration update information to allow modification of the pending NSSAI.","secretary_remarks":"Not Handled","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11020,"status":"not treated","reservation_date":"2022-04-11 11:48:47","uploaded":"2022-11-04 14:17:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3634.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154_Toulouse_2022-11\/Docs\/S2-2210655.zip","group":"S2","meeting":"S2-154","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2210679","title":"Further considerations of the feature interaction between NSSAA and subscription-based restrictions to simultaneous registration of network slices.","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":82456,"tdoctype":"discussion","for":"Agreement","abstract":"This paper provides some further considerations on the incoming LS from CT WG1 in S2-2210166 LS from CT WG1: LS on NSSRG restriction on pending NSSAI (C1-224073 )","secretary_remarks":"","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":10610,"status":"available","reservation_date":"2022-04-11 12:05:25","uploaded":"2022-11-04 14:17:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eNS_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154_Toulouse_2022-11\/Docs\/S2-2210679.zip","group":"S2","meeting":"S2-154","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2210681","title":"[DRAFT] Reply LS on NSSRG restriction on pending NSSAI","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":82456,"tdoctype":"LS out","for":"Approval","abstract":"This LS continues with the analysis of impact of NSSAA and NSSRG interaction as triggered by the CT WG1 LS in S2-2210166","secretary_remarks":"","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":10620,"status":"available","reservation_date":"2022-04-11 12:11:40","uploaded":"2022-11-04 14:17:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154_Toulouse_2022-11\/Docs\/S2-2210681.zip","group":"S2","meeting":"S2-154","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2210769","title":"Correction to the Target NSSAI feature in RRC redirection","source":"NEC","contact":"Iskren Ianev","contact-id":59515,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify that If the NG-RAN initiates RRC redirection procedure towards a target cell, the NG-RAN provides the UE with the Target NSSAI so that the UE can request a registration for the S-NSSAI(s) from the Target NSSAI if the target cell is in a TA outside of the current RA.","secretary_remarks":"Revision of (Unhandled) S2-2208969 Not Handled","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11050,"status":"not treated","reservation_date":"2022-04-11 14:13:08","uploaded":"2022-11-04 14:33:04","revisionof":"S2-2208969","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3741.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154_Toulouse_2022-11\/Docs\/S2-2210769.zip","group":"S2","meeting":"S2-154","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300023","title":"LS from CT WG1: LS on NSSRG restriction across different access types over different PLMNs","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 is discussing the applicability of the NSSRG restriction over different access types as specified in below text quoted from TS 23.501. CT WG1 has reached the consensus that the requested NSSAI across different access types over the same PLMN shall share common NSSRG value(s) and this restriction applies to both the UE and the network sides. However, no consensus was reached on whether this restriction is also applicable to the requested NSSAI across different access types over different PLMNs. 'At any time, a UE supporting subscription-based restrictions to simultaneous registration of network slices feature and that has received NSSRG information together with the Configured NSSAI shall only request S-NSSAIs, across all Access Type(s), that share one or more common NSSRG. NOTE: In Requested NSSAI across all Access Type(s), the UE needs to include S-NSSAIs that share at least one common NSSRG.' Hence, CT WG1 would like to ask following questions: Question #1: Shall the Requested NSSAI across different access types over different PLMNs share common NSSRG value(s)? Question #2: If the answer of Question #1 is yes, how does the network (i.e. different AMFs in different PLMNs) enforce the common NSSRG value(s) restriction on the Requested NSSAI?. Action: CT WG1 kindly requests SA WG2 to answer to above questions.","secretary_remarks":"Responses drafted in S2-2300288, S2-2300563, S2-2300856, S2-2300858. Final response in S2-2300563","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11750,"status":"replied to","reservation_date":"2022-12-19 08:34:55","uploaded":"2022-12-19 12:42:51","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-227101","lsreply":"S2-2300563, S2-2301468","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300023.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300287","title":"Discussion on NSSRG restriction across different access types over different PLMNs.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Discussion","abstract":"Discussion on NSSRG restriction across different access types over different PLMNs.","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11770,"status":"noted","reservation_date":"2023-06-01 12:49:28","uploaded":"2023-01-09 13:30:06","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eNS_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300287.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300288","title":"[DRAFT] Reply LS on NSSRG restriction across different access types over different PLMNs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on NSSRG restriction across different access types over different PLMNs from CT WG1","secretary_remarks":"Response to S2-2300023. Covered by S2-2300563. Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11780,"status":"noted","reservation_date":"2023-06-01 12:49:28","uploaded":"2023-01-09 13:30:06","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eNS_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300288.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300289","title":"NSSRG restriction enforcement across different access types over different PLMNs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: NSSRG restriction enforcement across different access types over different PLMNs","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11830,"status":"noted","reservation_date":"2023-06-01 12:49:28","uploaded":"2023-01-09 13:30:06","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3865.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300289.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.15.12.1, 5.15.12.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300290","title":"NSSRG restriction enforcement across different access types over different PLMNs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: NSSRG restriction enforcement across different access types over different PLMNs","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11840,"status":"noted","reservation_date":"2023-06-01 12:49:34","uploaded":"2023-01-09 13:30:06","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.0.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3866.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300290.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.15.12.1, 5.15.12.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300291","title":"NSSRG restriction enforcement across different access types over different PLMNs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: NSSRG restriction enforcement across different access types over different PLMNs","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11850,"status":"noted","reservation_date":"2023-06-01 12:49:39","uploaded":"2023-01-09 13:30:06","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3696.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300291.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.3.2.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300292","title":"NSSRG restriction enforcement across different access types over different PLMNs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: NSSRG restriction enforcement across different access types over different PLMNs","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11860,"status":"noted","reservation_date":"2023-06-01 12:49:41","uploaded":"2023-01-09 13:30:06","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.0.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3697.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300292.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.3.2.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300563","title":"[DRAFT] Reply LS on NSSRG restriction across different access types over different PLMNs","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: TS 23.501 CR#3934","secretary_remarks":"Response to S2-2300023. Approved. CC#4: Revised to remove draft in S2-2301468.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11790,"status":"revised","reservation_date":"2023-09-01 07:36:16","uploaded":"2023-01-09 13:20:47","revisionof":"","revisedto":"C1-230038, S2-2301468","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300563.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300564","title":"Clarification on NSSRG enforcement when a UE registered to different PLMNs over 3GPP access and non-3GPP access","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that no mechansim is specified to enforce NSSRG for a UE registered to different PLMNs over 3GPP access and non-3GPP access.","secretary_remarks":"r03 agreed. Revised to S2-2302073, merging S2-2300867","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11870,"status":"revised","reservation_date":"2023-09-01 07:36:16","uploaded":"2023-01-09 13:20:47","revisionof":"","revisedto":"S2-2302073","release":"Rel-17","crspec":"23.501","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3934.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300564.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.15.12.1, 5.15.12.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300565","title":"Clarification on NSSRG enforcement when a UE registered to different PLMNs over 3GPP access and non-3GPP access","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: Clarify that no mechansim is specified to enforce NSSRG for a UE registered to different PLMNs over 3GPP access and non-3GPP access.","secretary_remarks":"Revised to S2-2302074.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11890,"status":"revised","reservation_date":"2023-09-01 07:36:18","uploaded":"2023-01-09 13:20:47","revisionof":"","revisedto":"S2-2302074","release":"Rel-18","crspec":"23.501","crspecversion":"18.0.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3935.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300565.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.15.12.1, 5.15.12.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300654","title":"S-NSSAI correction for the roaming case","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the missed mapped S-NSSAI in HPLMN in related service operation.","secretary_remarks":"r03 agreed. Revised to S2-2302080.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":12050,"status":"revised","reservation_date":"2023-09-01 08:33:52","uploaded":"2023-01-09 15:34:22","revisionof":"","revisedto":"S2-2302080","release":"Rel-17","crspec":"23.502","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3766.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300654.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.21.2.2, 5.21.2.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300655","title":"S-NSSAI correction for the roaming case","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: Add the missed mapped S-NSSAI in HPLMN in related service operation.","secretary_remarks":"Revised to S2-2302081.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":12070,"status":"revised","reservation_date":"2023-09-01 08:34:04","uploaded":"2023-01-09 15:34:22","revisionof":"","revisedto":"S2-2302081","release":"Rel-18","crspec":"23.502","crspecversion":"18.0.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3767.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300655.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.21.2.2, 5.21.2.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300852","title":"Pending NSSAI and AMF Relocation in Connected mode 23.501.","source":"NEC, Ericsson, Huawei","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that when a AMF has pending NSSAI for a UE and receives a registration request message containing Requested NSSAI from the UE, then the AMF may send pending NSSAI and the requested NSSAI to the NSSF to get the target AMF which will handle the Pending NSSAI and the requested NSSAI.","secretary_remarks":"Revision of S2-2209022. r05 agreed. Revised to S2-2302078.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":12010,"status":"revised","reservation_date":"2023-09-01 10:56:35","uploaded":"2023-01-09 19:12:19","revisionof":"S2-2209022","revisedto":"S2-2302078","release":"Rel-17","crspec":"23.501","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3694.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300852.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.15.5.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300853","title":"Discussion on NSSRG restriction across different access types over different PLMNs.","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"discussion","for":"Discussion","abstract":"Discussion on NSSRG restriction across different access types over different PLMNs.","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11760,"status":"noted","reservation_date":"2023-09-01 10:58:05","uploaded":"2023-01-09 11:41:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"","workitem":[{"winame":"eNS_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300853.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300854","title":"Pending NSSAI and AMF Relocation in Connected mode 23.501.","source":"NEC, Ericsson, Huawei","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"CR","for":"Agreement","abstract":"Rel-18 mirror CR: Summary of change: Specify that when a AMF has pending NSSAI for a UE and receives a registration request message containing Requested NSSAI from the UE, then the AMF may send pending NSSAI and the requested NSSAI to the NSSF to get the target AMF which will handle the Pending NSSAI and the requested NSSAI.","secretary_remarks":"Revised to S2-2302079.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":12030,"status":"revised","reservation_date":"2023-09-01 11:01:02","uploaded":"2023-01-09 19:12:19","revisionof":"","revisedto":"S2-2302079","release":"Rel-18","crspec":"23.501","crspecversion":"18.0.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3998.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300854.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.15.5.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300856","title":"[DRAFT] Reply LS on NSSRG restriction across different access types over different PLMNs","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"LS out","for":"Approval","abstract":"This is LS Reply to CT WG1 regarding NSSRG feature over different PLMNs","secretary_remarks":"Response to S2-2300023. Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11810,"status":"noted","reservation_date":"2023-09-01 11:05:40","uploaded":"2023-01-09 11:42:20","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eNS_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300856.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300858","title":"[DRAFT] Reply LS on NSSRG restriction across different access types over different PLMNs","source":"NEC Corporation","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: TS 23.501 CR#xxxx","secretary_remarks":"Response to S2-2300023. Covered by S2-2300563. Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11820,"status":"noted","reservation_date":"2023-09-01 11:09:39","uploaded":"2023-01-09 19:40:54","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300858.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300864","title":"Clarification on Number of PDU session slice availability check","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed t clarify that NSACF only removes the AT entry while keeping the PDU Session ID when it receives MAPDU release over single AT.","secretary_remarks":"CC#1: Rel-18 mirror CR allocated in S2-2301323. r04 agreed. Revised to S2-2302076.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11970,"status":"revised","reservation_date":"2023-09-01 11:12:09","uploaded":"2023-01-09 11:42:44","revisionof":"","revisedto":"S2-2302076","release":"Rel-17","crspec":"23.502","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3803.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300864.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300867","title":"NSSRG enforcement when a UE is registered to different PLMNs-Rel17","source":"NEC","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies explicitly that when a UE is registering to two different PLMNs over 3GPP access and non-3GPP access, the UE requested NSSAIs over the two accesses shall follow the NSSRG policy i.e. the Requested NSSAI over 3GPP access and non-3GPP access shall follow the NSSRG policy.","secretary_remarks":"Merged into S2-2302073","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11910,"status":"merged","reservation_date":"2023-09-01 11:15:15","uploaded":"2023-01-09 19:41:46","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":4001.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300867.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.15.12.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300870","title":"NSSRG enforcement when a UE is registered to different PLMNs-Rel18","source":"NEC Corporation","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Clarifies explicitly that when a UE is registering to two different PLMNs over 3GPP access and non-3GPP access, the UE requested NSSAIs over the two accesses shall follow the NSSRG policy i.e. the Requested NSSAI over 3GPP access and non-3GPP access shall follow the NSSRG policy. 2.While the UE is registering to a first PLMN, the first PLMN stores the allowed NSSAI in the UDM. When the UE is registering to the second PLMN the AMF of the second PLMN feteches the allowed NSSAI of the first PLMN from the UDM and applies the NSSRG policies to the requested NSSAI received by the second PLMN and the allowed NSSAI of the first PLMN.","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11920,"status":"noted","reservation_date":"2023-09-01 11:19:39","uploaded":"2023-01-09 18:59:18","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.0.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":4003.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300870.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300873","title":"NSSRG enforcement when a UE is registered to different PLMNs-Rel18","source":"NEC","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1.Clarifies explicitly that when a UE is registering to two different PLMNs over 3GPP access and non-3GPP access, the UE requested NSSAIs over the two accesses shall follow the NSSRG policy i.e. the Requested NSSAI over 3GPP access and non-3GPP access shall follow the NSSRG policy. 2.While the UE is registering to a first PLMN, the first PLMN stores the allowed NSSAI in the UDM. When the UE is registering to the second PLMN the AMF of the second PLMN feteches the allowed NSSAI of the first PLMN from the UDM and applies the NSSRG policies to the requested NSSAI received by the second PLMN and the allowed NSSAI of the first PLMN.","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11930,"status":"noted","reservation_date":"2023-09-01 11:23:49","uploaded":"2023-01-09 19:42:47","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.0.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3804.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300873.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2301116","title":"UE-Slice-MBR clarifications including for priority services","source":"Peraton Labs, CISA ECD, T-Mobile USA, AT&T, Verizon","contact":"Robert Streijl","contact-id":92467,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR changes that UE-Slice-MBR applies to an NG-RAN, not RAN. Since the UE-Slice-MBR is an optional attribute, when a UE has a priority subscription, the operator may choose not to provision the UE-Slice-MBR for this UE. However, some operators may still choose to provision this attribute even if the UE has a priority subscription. The choice should be with the operator. No normative clarification is needed in the UE-Slice-MBR clauses. For the case that a UE obtains a priority subscription after 5GS registration, and where the UE has a UE-Slice-MBR in the UDM and the NG-RAN has already provisioned the UE-Slice-MBR for the UE, this user will be subject to ARP and UE-Slice-MBR. A note is added to indicate that the NG-RAN can look at both the UE-Slice-MBR and the ARP of the sessions (including priority sessions), and where the NG-RAN is allowed to pre-empt sessions with lower ARP and potentially still stay within the UE-Slice-MBR of such a UE. Without this clarification, the reader could understand that the ARP plays no role and the NG-RAN will not admit a new QoS Flow as it appears to solely look at the UE-Slice-MBR.","secretary_remarks":"r03 agreed. Revised to S2-2302075.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11950,"status":"revised","reservation_date":"2023-09-01 15:33:11","uploaded":"2023-01-09 20:58:14","revisionof":"","revisedto":"S2-2302075","release":"Rel-17","crspec":"23.501","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":4068.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2301116.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2301185","title":"Clarification on NSSRG enforcement when a UE registered to different PLMNs over 3GPP access and non-3GPP access","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that no mechansim is specified to enforce NSSRG for a UE registered to different PLMNs over 3GPP access and non-3GPP access.","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11940,"status":"noted","reservation_date":"2023-09-01 16:32:47","uploaded":"2023-01-09 17:02:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":4084.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2301185.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.15.12.1, 5.15.12.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2301323","title":"Clarification on Number of PDU session slice availability check","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: It is proposed to clarify that NSACF only removes the received Access Type entry while keeping the PDU Session ID if it locates the entry with both Access Types when it receives update request from the SMF to 'decrease' the count for a PDU Session over single AT.","secretary_remarks":"Rel-18 mirror of S2-2300864. Created at CC#1. Revised to S2-2302077.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11990,"status":"revised","reservation_date":"2023-01-16 17:31:57","uploaded":"2023-01-24 08:01:05","revisionof":"","revisedto":"S2-2302077","release":"Rel-18","crspec":"23.502","crspecversion":"18.0.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3870.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2301323.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2301468","title":"Reply LS on NSSRG restriction across different access types over different PLMNs","source":"SA WG2","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: TS 23.501 CR#3934","secretary_remarks":"Revision of S2-2300563. Aapproved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11800,"status":"approved","reservation_date":"2023-01-24 07:44:19","uploaded":"2023-01-24 08:01:06","revisionof":"S2-2300563","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eNS_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2300023","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2301468.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2302073","title":"Clarification on NSSRG enforcement when a UE registered to different PLMNs over 3GPP access and non-3GPP access","source":"LG Electronics, Ericsson, Nokia, Nokia Shanghai Bell, Apple, NEC, Huawei","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that no mechansim is specified to enforce NSSRG for a UE registered to different PLMNs over 3GPP access and non-3GPP access.","secretary_remarks":"Revision of S2-2300564r03, merging S2-2300867. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11880,"status":"agreed","reservation_date":"2023-01-24 07:49:30","uploaded":"2023-01-24 08:01:09","revisionof":"S2-2300564","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3934.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-230040","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2302073.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.15.12.1, 5.15.12.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2302074","title":"Clarification on NSSRG enforcement when a UE registered to different PLMNs over 3GPP access and non-3GPP access","source":"LG Electronics, Ericsson, Nokia, Nokia Shanghai Bell, Apple, NEC, Huawei","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: Clarify that no mechansim is specified to enforce NSSRG for a UE registered to different PLMNs over 3GPP access and non-3GPP access.","secretary_remarks":"Revision of S2-2300565. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11900,"status":"agreed","reservation_date":"2023-01-24 07:49:31","uploaded":"2023-01-24 08:01:09","revisionof":"S2-2300565","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.0.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3935.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-230040","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2302074.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.15.12.1, 5.15.12.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2302075","title":"UE-Slice-MBR clarifications including for priority services","source":"Peraton Labs, CISA ECD, T-Mobile USA, AT&T, Verizon, ZTE","contact":"Robert Streijl","contact-id":92467,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR changes that UE-Slice-MBR applies to an NG-RAN, not RAN. Since the UE-Slice-MBR is an optional attribute, when a UE has a priority subscription, the operator may choose not to provision the UE-Slice-MBR for this UE. However, some operators may still choose to provision this attribute even if the UE has a priority subscription. The choice should be with the operator. No normative clarification is needed in the UE-Slice-MBR clauses. For the case that a UE obtains a priority subscription after 5GS registration, and where the UE has a UE-Slice-MBR in the UDM and the NG-RAN has already provisioned the UE-Slice-MBR for the UE, this user will be subject to ARP and UE-Slice-MBR. A note is added to indicate that the NG-RAN can look at both the UE-Slice-MBR and the ARP of the sessions (including priority sessions), and where the NG-RAN is allowed to pre-empt sessions with lower ARP and potentially still stay within the UE-Slice-MBR of such a UE. Without this clarification, the reader could understand that the ARP plays no role and the NG-RAN will not admit a new QoS Flow as it appears to solely look at the UE-Slice-MBR.","secretary_remarks":"Revision of S2-2301116r03. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11960,"status":"agreed","reservation_date":"2023-01-24 07:49:32","uploaded":"2023-01-24 08:01:09","revisionof":"S2-2301116","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":4068.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-230040","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2302075.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":false,"clauses_affected":"5.7.1.10, 5.7.2.6, and 5.15.13.","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2302076","title":"Clarification on Number of PDU session slice availability check","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify that NSACF only removes the received Access Type entry while keeping the PDU Session ID if it locates the entry with both Access Types when it receives update request from the SMF to 'decrease' the count for a PDU Session over single AT.","secretary_remarks":"Revision of S2-2300864r04. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11980,"status":"agreed","reservation_date":"2023-01-24 07:49:33","uploaded":"2023-01-24 08:01:09","revisionof":"S2-2300864","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3803.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-230040","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2302076.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2302077","title":"Clarification on Number of PDU session slice availability check","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: It is proposed to clarify that NSACF only removes the received Access Type entry while keeping the PDU Session ID if it locates the entry with both Access Types when it receives update request from the SMF to 'decrease' the count for a PDU Session over single AT.","secretary_remarks":"Revision of S2-2301323. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":12000,"status":"agreed","reservation_date":"2023-01-24 07:49:34","uploaded":"2023-01-24 08:01:09","revisionof":"S2-2301323","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.0.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3870.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-230040","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2302077.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2302078","title":"Pending NSSAI and AMF Relocation in Connected mode 23.501.","source":"NEC, Ericsson, Huawei, Nokia, Nokia Shanghai Bell","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that when a AMF has pending NSSAI for a UE and receives a registration request message containing Requested NSSAI from the UE, then the AMF may send pending NSSAI and the requested NSSAI to the NSSF to get the target AMF which will handle the Pending NSSAI and the requested NSSAI, if these are compatible with the requested NSSAI from the UE. Also the AMF checks whether the Pending NSSAI and requested NSSAIs are compatible or not.","secretary_remarks":"Revision of S2-2300852r05. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":12020,"status":"agreed","reservation_date":"2023-01-24 07:49:35","uploaded":"2023-01-24 08:01:09","revisionof":"S2-2300852","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3694.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-230040","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2302078.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.15.5.2.1, 5.15.12.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2302079","title":"Pending NSSAI and AMF Relocation in Connected mode 23.501.","source":"NEC, Ericsson, Huawei, Nokia, Nokia Shanghai Bell","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"CR","for":"Agreement","abstract":"Rel-18 mirror CR: Summary of change: Specify that when a AMF has pending NSSAI for a UE and receives a registration request message containing Requested NSSAI from the UE, then the AMF may send pending NSSAI and the requested NSSAI to the NSSF to get the target AMF which will handle the Pending NSSAI and the requested NSSAI.","secretary_remarks":"Revision of S2-2300854. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":12040,"status":"agreed","reservation_date":"2023-01-24 07:49:35","uploaded":"2023-01-24 08:01:09","revisionof":"S2-2300854","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.0.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3998.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-230040","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2302079.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2302080","title":"S-NSSAI correction for the roaming case","source":"Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, ZTE","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the missed mapped S-NSSAI in HPLMN in related service operation.","secretary_remarks":"Revision of S2-2300654r03. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":12060,"status":"agreed","reservation_date":"2023-01-24 07:49:36","uploaded":"2023-01-24 08:01:09","revisionof":"S2-2300654","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.7.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3766.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-230040","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2302080.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2302081","title":"S-NSSAI correction for the roaming case","source":"Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, ZTE","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: Add the missed mapped S-NSSAI in HPLMN in related service operation.","secretary_remarks":"Revision of S2-2300655. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":12080,"status":"agreed","reservation_date":"2023-01-24 07:49:37","uploaded":"2023-01-24 08:01:09","revisionof":"S2-2300655","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.0.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3767.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-230040","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2302081.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.21.2.2, 5.2.21.2.4","crsinpack":null,"crsinpacknumber":0}]