[{"name":"S2-2208103","title":"LS from CT WG1: LS on NSSRG restriction on pending NSSAI","source":"CT WG1","contact":"Kundan Tiwari","contact-id":81849,"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-2205406 from S2#152-e. This LS was postponed","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11440,"status":"postponed","reservation_date":"2022-09-21 05:20:39","uploaded":"2022-09-21 08:06:27","revisionof":"S2-2205406","revisedto":"S2-2210166","release":"Rel-17","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_153E_Electronic_2022-10\/Docs\/S2-2208103.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208107","title":"LS from SA WG3: LS on EAC Mode for NSAC","source":"SA WG3","contact":"Zander (Zhongding) Lei","contact-id":66556,"tdoctype":"LS in","for":"Action","abstract":"In TR33.874, SA WG3 has studied a potential Denial-of-Service issue to network slices caused by a burst of registration requests in an EAC inactive mode. It has been concluded that this potential issue can be mitigated through setting a proper threshold for the EAC mode activation\/de-activation, taking the burst registration into account. Since this mitigation can be an implementation issue and no normative text is generated in SA WG3, it is recommended to include the following informative NOTE in SA WG2 s specification (e.g. TS 23.502): NOTE: The operator can set the thresholds for the EAC mode activation\/de-activation accordingly in order to mitigate potential risk due to a potential burst of registration requests requesting the same slice. Action: SA WG3 kindly requests SA WG2 to take the above information into account in updating respecitve specifications.","secretary_remarks":"Revision of Postponed S2-2205437 from S2#152-e. Response drafted in S2-2208415. Final response in S2-2209260","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11380,"status":"replied to","reservation_date":"2022-09-21 05:20:40","uploaded":"2022-09-21 08:06:27","revisionof":"S2-2205437","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S3-221164","lsreply":"S2-2209260, S2-2209260","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208107.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208116","title":"Reply LS on Support for managing slice for trusted third-party owned application","source":"SA WG1","contact":"Kurt Bischinger","contact-id":26063,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks SA WG6 for their LS on Support for managing slice for trusted third-party owned application. SA WG1 was not sure about how to interpret the question raised by SA WG6: Q:3: Does SA WG1 have specific requirement on managing UEs with different qualities\/priority level within a slice? Some companies understood this to be about dynamic policy control, which is applied for UEs within a network slice, or QoS settings, per flow, within a network slice. However, the used example in the description, about reaching the maximum UEs slice quota, and the potential functionality to not reject certain customers when the maximum quota is reached, seems to imply that the attributes of the network slice itself (as defined in a NEST) could be adapted dependent on which UE is assigned to the network slice. So, SA WG1 would like to ask the following question for clarification to SA WG6: Q1: Is the question from SA WG6 related to requirements concerning the handling of UEs and flows within a network slice or concerning the adaptation of network slice attributes per UE, or concerning something else?","secretary_remarks":"Revision of Postponed S2-2208097 from S2#152-e. Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11350,"status":"noted","reservation_date":"2022-09-21 05:20:40","uploaded":"2022-09-21 08:06:27","revisionof":"S2-2208097","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2","lsoriginalls":"S1-222262","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208116.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208151","title":"LS from SA WG1: Reply LS on Support for managing slice for trusted third-party owned application","source":"SA WG1","contact":"Kurt Bischinger","contact-id":26063,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks SA WG6 for the clarification of the scenario and question initially highlighted in S1-222074\/S6-221484 LS on Support for managing slice for trusted third-party owned application. SA WG1 would like to provide the following answer to this question: Considering the explanation in the use case, does SA WG1 have requirements such that high priority users, identified by 3rd party, are able to achieve access to the provided services even when the slice capacity (or a capacity threshold) has been reached? Answer from SA WG1: No, there are no related requirements.","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11360,"status":"noted","reservation_date":"2022-09-21 05:20:42","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2","lsoriginalls":"S1-222267","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208151.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208161","title":"LS from SA WG6: Reply LS on Reply LS on Support for managing slice for trusted third-party owned application","source":"SA WG6","contact":"Sapan Shah","contact-id":76271,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks SA WG1 for their Reply LS on Reply LS on Support for managing slice for trusted third-party owned application. Q1: Is the question from SA WG6 related to requirements concerning the handling of UEs and flows within a network slice or concerning the adaptation of network slice attributes per UE, or concerning something else? Answer: The question from SA WG6 is related to the requirements concerning the handling of UEs and flows within a networks slice. Further, SA WG6 does not propose or suggest that network slice constraints change to accommodate policy differentiation between subscribers receiving service on a network slice. Please consider following use case: As captured also in clause 5.7.1 of 3GPP TR 22.835, for gaming or online video applications, the end users may have different priority or membership e.g. VIP maintained by 3rd party Service Provider (SP). And depending on the priority or membership information from 3rd party SP perspective, based on the agreement between SP and MNO, the UE have different priority within the available single network slice. Assuming User A is a high priority user for the service provider which means when this user starts to use the application, the user can use the corresponding network slice to guarantee to get the service compared with other users with lower priority and the MNO network resource can accommodate high priority users. In this use case, when a slice has reached its capacity, a new high priority UE will be rejected which may impact high priority user s service experience. SA WG6 seeks solutions in which without altering the policies of the network slice itself the management of the user sessions can accommodate the higher priority user. Considering the explanation in the use case, does SA WG1 have requirements such that high priority users, identified by 3rd party, are able to achieve access to the provided services even when the slice capacity (or a capacity threshold) has been reached?","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11370,"status":"noted","reservation_date":"2022-09-21 08:54:33","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG2","lsoriginalls":"S6-222340","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208161.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208415","title":"[DRAFT] Reply LS on EAC Mode for NSAC","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on EAC Mode for NSAC","secretary_remarks":"Response to S2-2208107. r00 agreed. Revised to S2-2209260.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11390,"status":"revised","reservation_date":"2022-09-29 15:44:49","uploaded":"2022-09-30 12:10:44","revisionof":"","revisedto":"S2-2209260","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eNS2_SEC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208415.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208416","title":"Clarification on EAC Mode for NSAC","source":"Huawei, HiSilicon, ZTE","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In SA WG2#153, it was proposed to add a NOTE on EAC mode configuration: NOTE: The operator can set the thresholds for the EAC mode activation\/de-activation accordingly in order to mitigate potential risk due to a potential burst of registration requests requesting the same slice. But people commented that the note shall contain recommendations to the operator, so it is proposed to change the wording into When the operator set the EAC inactive threshold, the risk due to a potential burst of registration requests needs to be taken into account .","secretary_remarks":"r02 agreed. Revised to S2-2209273.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11410,"status":"revised","reservation_date":"2022-09-29 15:44:49","uploaded":"2022-09-30 12:10:44","revisionof":"","revisedto":"S2-2209273","release":"Rel-17","crspec":"23.502","crspecversion":"17.6.0","workitem":[{"winame":"FS_eNS2_SEC"}],"crnumber":3563.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208416.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208470","title":"AMF provides Target NSSAIs for all TAI in the Registration Area","source":"NEC","contact":"Toshiyuki Tamura","contact-id":97685,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that the AMF provides target NSSAIs to the NG-RAN for each TAI in the TAI list for the UE. Then, the NG-RAN uses a target NSSAI that corresponds to the UE s current TA for the RRC redirection procedure or handover.","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":11560,"status":"not treated","reservation_date":"2022-09-29 23:23:32","uploaded":"2022-09-30 04:37:56","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3717.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208470.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208471","title":"AMF provides Target NSSAIs for all TAI in the Registration Area","source":"NEC","contact":"Toshiyuki Tamura","contact-id":97685,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that the AMF provides target NSSAIs to the NG-RAN for each TAI in the TAI list. Then, the NG-RAN uses a target NSSAI that corresponds to the UE s current TA. Proposed updates are listed below: Add clarifying text indicating that the AMF provides target NSSAIs to the NG-RAN for each TAI in the TAI list. In Nnssf_NSSelection_Get service, the TAI list is added as an input data so that the NSSF can provide Target NSSAI per TAI. In Npcf_AMPolicyControl_Create service, Target NSSAI per TAI is added as an input data so that the PCF can provide RFSP for each Target NSSAI per TAI.","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":11570,"status":"not treated","reservation_date":"2022-09-29 23:25:46","uploaded":"2022-09-30 04:37:56","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3568.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208471.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208521","title":"AMF provides Target NSSAIs for all TAI in the Registration Area","source":"NEC","contact":"Toshiyuki Tamura","contact-id":97685,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that the AMF provides target NSSAIs to the NG-RAN for each TAI in the TAI list. Then, the NG-RAN uses a target NSSAI that corresponds to the UE s current TA. Proposed updates is listed below: RFSP Index for Target NSSAI in the Access and mobility related policy information is updated to be a list of RFSP Index for Target NSSAI per TAI in the TAI list.","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":11580,"status":"not treated","reservation_date":"2022-09-30 04:05:11","uploaded":"2022-09-30 04:37:56","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":748.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208521.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208545","title":"UE-Slice-MBR exemption for priority services","source":"Samsung","contact":"Dongeun Suh","contact-id":84836,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The Subscribed UE-Slice-MBR value of the UE that has priority subscriptions (i.e., MPS or MCX) shall be set to ensure that QoS Flows of priority users are not restricted or rejected.a value that indicates unlimited data rate.","secretary_remarks":"Revision of (Postponed) S2-2206034 from S2#152E. CC#3: Postponed","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11550,"status":"postponed","reservation_date":"2022-09-30 07:16:24","uploaded":"2022-09-30 07:26:42","revisionof":"S2-2206034","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3682.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208545.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208969","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":"Not Handled. Revised at S2#154 in S2-2210769 (not pursued)","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11590,"status":"revised","reservation_date":"2022-09-30 12:58:31","uploaded":"2022-09-30 13:25:48","revisionof":"","revisedto":"S2-2210769","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3741.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208969.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209003","title":"Update in EAC mode procedure","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following changes are proposed: NSACF will add the optional Access Type while sending EAC notification AMF will set the EAC mode for the received Access Type from NSACF","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11430,"status":"noted","reservation_date":"2022-09-30 13:45:02","uploaded":"2022-09-30 13:51:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3592.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209003.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209004","title":"Pending NSSAI and NSSRG","source":"NEC, Ericsson, Huawei, HiSilicon, ZTE","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that the UE and the AMF shall apply NSSRG procedure for a pending S-NSSAI same as for the requested NSSAI.","secretary_remarks":"Revision of (Postponed) S2-2206644 from S2#152E. CC#3: r02 agreed. Revised to S2-2209943.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11520,"status":"revised","reservation_date":"2022-09-30 13:46:29","uploaded":"2022-09-30 17:04:19","revisionof":"S2-2206644","revisedto":"S2-2209943","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3693.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209004.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209022","title":"Pending NSSAI and AMF Relocation in Connected mode 23.501.","source":"NEC, Ericsson","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 (Postponed) S2-2206652 from S2#152E. Approved. CC#3: This was postponed.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11540,"status":"postponed","reservation_date":"2022-09-30 14:00:25","uploaded":"2022-09-30 17:04:19","revisionof":"S2-2206652","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3694.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209022.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209037","title":"[DRAFT] LS on NSSRG restriction on pending NSSAI","source":"NEC","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-xxxxxx, S2-xxxxxx","secretary_remarks":"CC#3: r03 agreed. Revised to S2-2209944.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11450,"status":"revised","reservation_date":"2022-09-30 14:31:20","uploaded":"2022-09-30 17:04:18","revisionof":"","revisedto":"S2-2209944","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_153E_Electronic_2022-10\/Docs\/S2-2209037.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209038","title":"[DRAFT] LS on NSSRG Restrictions on Pending NSSAI","source":"vivo","contact":"Xiaowen Sun","contact-id":96492,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Merged into (Covered by) S2-2209037","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11470,"status":"merged","reservation_date":"2022-09-30 14:32:13","uploaded":"2022-09-30 14:45:34","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_153E_Electronic_2022-10\/Docs\/S2-2209038.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209039","title":"NSSRG restriction on Pending NSSAI","source":"Vivo","contact":"Xiaowen Sun","contact-id":96492,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that an indication is required to allow UE and network to consider the NSSRG value of Requested NSSAI by ignoring Pending NSSAI in a request message.","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11480,"status":"noted","reservation_date":"2022-09-30 14:32:13","uploaded":"2022-09-30 14:45:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3744.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209039.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209040","title":"NSSRG restriction on Pending NSSAI","source":"Vivo","contact":"Xiaowen Sun","contact-id":96492,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that an indication is required to allow UE and network to consider the NSSRG value of Requested NSSAI by ignoring Pending NSSAI in a request message.","secretary_remarks":"Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11490,"status":"noted","reservation_date":"2022-09-30 14:32:14","uploaded":"2022-09-30 14:45:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3594.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209040.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209201","title":"Clarification 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: when the NSSAA completes for the S-NSSAI subject to NSSAA (let's call it S-NSSAI X), there can be different outcomes: if the S-NSSAI that was requested (Let's call it S-NSSAI Y) was allowed and incompatible with S-NSSAI X, then the AMF should just remove the S-NSSAI X from pending NSSAI with a UE configuration update. If the S-NSSAI X was the only S-NSSAI which is pending, the UCU includes an 'empty' Pending S-NSSAI. Then, when the S-NSSAI X is removed from the Pending NSSAI, the UE can decide whether to re-register to request S-NSSAI X instead of S-NSSAY Y.","secretary_remarks":"Revision of (Postponed) S2-2206152 from S2#152E. LATE DOC: Rx 03\/10, 10:50. Postponed","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11500,"status":"postponed","reservation_date":"2022-10-03 10:31:58","uploaded":"2022-10-03 10:49:29","revisionof":"S2-2206152","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3684.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209201.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209202","title":"Clarification 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: when the NSSAA completes for the S-NSSAI subject to NSSAA (let's call it S-NSSAI X), there can be different outcomes: if the S-NSSAI that was requested (Let's call it S-NSSAI Y) was allowed and incompatible with S-NSSAI X, then the AMF should just remove the S-NSSAI X from pending NSSAI with a UE configuration update. If the S-NSSAI X was the only S-NSSAI which is pending, the UCU includes an 'empty' Pending S-NSSAI. Then, when the S-NSSAI X is removed from the Pending NSSAI, the UE can decide whether to re-register to request S-NSSAI X instead of S-NSSAY Y.","secretary_remarks":"Revision of (Noted) S2-2206159 from S2#152E. LATE DOC: Rx 03\/10, 10:50. Noted","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11510,"status":"noted","reservation_date":"2022-10-03 10:34:55","uploaded":"2022-10-03 10:49:29","revisionof":"S2-2206159","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3529.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209202.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209260","title":"LS Reply on EAC Mode for NSAC","source":"SA WG2","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. Attachments: TS 23.502 CR 3563","secretary_remarks":"Revision of S2-2208415r00. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11400,"status":"approved","reservation_date":"2022-10-18 14:16:33","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208415","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eNS2_SEC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2208107","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209260.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209273","title":"Clarification on EAC Mode for NSAC","source":"Huawei, HiSilicon, ZTE","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In SA WG2#153, it was proposed to add a NOTE on EAC mode configuration: NOTE: The operator can set the thresholds for the EAC mode activation\/de-activation accordingly in order to mitigate potential risk due to a potential burst of registration requests requesting the same slice. But people commented that the note shall contain recommendations to the operator, so it is proposed to change the wording into When the operator set the EAC inactive threshold, the risk due to a potential burst of registration requests needs to be taken into account .","secretary_remarks":"Revision of S2-2208416r02. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11420,"status":"agreed","reservation_date":"2022-10-18 14:16:45","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208416","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.6.0","workitem":[{"winame":"eNS2_SEC"}],"crnumber":3563.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-221073","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209273.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209943","title":"Pending NSSAI and NSSRG","source":"NEC, Ericsson, Huawei, HiSilicon, ZTE","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that the UE and the AMF shall apply NSSRG procedure for a pending S-NSSAI same as for the requested NSSAI.","secretary_remarks":"Revision of S2-2209004r02. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11530,"status":"agreed","reservation_date":"2022-10-18 14:23:34","uploaded":"2022-10-18 14:31:36","revisionof":"S2-2209004","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3693.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-221072","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209943.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209944","title":"LS out on NSSRG restriction on pending NSSAI","source":"SA WG2","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: S2-2209943","secretary_remarks":"Revision of S2-2209037r03. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11460,"status":"approved","reservation_date":"2022-10-18 14:23:35","uploaded":"2022-10-18 14:31:36","revisionof":"S2-2209037","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_153E_Electronic_2022-10\/Docs\/S2-2209944.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]