[{"name":"S2-2203634","title":"LS from GSMA: LS on enforcement of maximum number of UEs and maximum number of PDU sessions in a network slice","source":"GSMA","contact":"Alessio Casati","contact-id":82456,"tdoctype":"LS in","for":"Information","abstract":"GSMA NG ENSWI has discussed the following topics: 1) which PLMN (HPLMN or VPLMN) enforces the maximum number of UEs in a network slice when some of the UEs are roaming, and 2) which PLMN (HPLMN or VPLMN) enforces the maximum number of sessions in a network slice when some session in a network slice may be supported in LBO for roaming UEs. GSMA has agreed that the HPLMN is enforcing the maximum number in both cases and that the number of PDU sessions also includes the LBO sessions. As an option, Operators may configure the network slice to not include the LBO sessions and the roaming UEs in the total number enforced. In addition, GSMA has clarified that when EPS counting is required two options are supported: A. the maximum number of UEs limit in 5GS applies to the UEs which are registered in 5GS and so the restriction criterion is not uniform across EPS and 5GS as the UEs in EPS are counted when they have at least one PDU session. B. the maximum number of UEs limit applies to the UEs with at least one PDU session in 5GS, and at least one PDN connection in EPS, and so the restriction criterion is uniform across EPS and 5GS. In order to allow the two options, the NG.116 has been updated to add an attribute 'maximum number of UEs with at least one PDU session\/PDN connection'. So, option A applies when the 'maximum number of UEs' attribute with EPS counting enabled is in the NEST, while option B applies to when 'maximum number of UEs with at least one PDU sessions\/PDN connection' attribute in the NEST. Actions to SA WG2 and SA WG5: GSMA NG ENSWI kindly requests SA WG2 and SA WG5 to take the above into account.","secretary_remarks":"Revision of Postponed S2-2202800 from S2#150E. 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":"2022-04-21 14:48:20","uploaded":"2022-04-21 14:49:13","revisionof":"S2-2202800","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5","Cc":"","lsoriginalls":"ENSWI09_Doc006","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203634.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203667","title":"LS from CT WG4: LS on clarification on per access NSAC requirement","source":"CT WG4","contact":"Zhijun Li","contact-id":39295,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 is currently working on release-17 eNS_Ph2 to finish the work, and now finds ambiguity in stage 2 specification which has impacts to CT WG4 specification of TS29.536. See below: {. . .} CT WG4 had agreed in previous meetings that per-access quota may be configured, however after recent discussions, most companies in CT WG4 think that there is only one total quota configured for the entire PLMN, regardless the NSAC may be configured for one specific access type or for both access types. However, there is other opinion from one company that different quotas may additionally be configured for each access type in a PLMN. Thus, CT WG4 would like to ask SA WG2 to answer the question below: Q1: Is there any requirement to possibly configure different quotas for each access type in a PLMN, or there is only one total quota configured for the PLMN, if NSAC is configured in the network to control the number of UEs \/ PDU sessions? Q2: If the answer to Q1 is NO, what is the need of sending Access-Type in the response message of NSAC request? CT WG4 has agreed C4-223310 (CR#0011) in CT WG4#110E meeting and expects it to be approved in the CT#96 plenary meeting in June unless CT WG4\/CT receives any counter-indication from SA WG2. Action: CT WG4 kindly asks SA WG2 group to answer the above question. And, update their specifications accordingly, if needed.","secretary_remarks":"Response drafted in S2-2204723. Final response in S2-2204903","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11950,"status":"replied to","reservation_date":"2022-04-21 14:48:21","uploaded":"2022-05-17 15:54:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"TSG CT","lsoriginalls":"C4-223309","lsreply":"S2-2204903","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203667.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203668","title":"LS from CT WG3: LS on Clarifications related to UE-Slice-MBR handling","source":"CT WG3","contact":"Rajesh Babu Natarajan","contact-id":89232,"tdoctype":"LS in","for":"Action","abstract":"With reference to Ts 23.501, clause 5.15.4.1.1: The Configured NSSAI for the Serving PLMN includes the S-NSSAI values which can be used in the Serving PLMN and may be associated with mapping of each S-NSSAI of the Configured NSSAI to one or more corresponding HPLMN S-NSSAI values. And in clause 5.15.13: In roaming case, the UE-Slice-MBR is provided for the S-NSSAI of the VPLMN which maps to the S-NSSAI of the HPLMN and the AMF may first interact with the PCF for authorization of the Subscribed UE-Slice-MBR. If the AMF interacts with the PCF, the PCF may provide the Authorized UE-Slice-MBR that is used as UE-Slice-MBR by the AMF as described in clause 6.1.2.1 of TS 23.503 [45]. NOTE 1: For a roaming UE, the S-NSSAI of the VPLMN provided with UE-Slice-MBR should map to only one S-NSSAI of the HPLMN, to ensure the accuracy of performing data rate limitation for the corresponding slice of HPLMN. Question 1: Can SA WG2 kindly clarify whether 1:1 mapping between VPLMN S-NSSAI and HPLMN S-NSSAI is needed for assigning the appropriate UE-Slice-MBR for the VPLMN S-NSSAI for the UE during roaming in VPLMN?. Action: CT WG3 kindly asks SA WG2 to answer the above questions and update the SA WG2 specifications accordingly, where appropriate and if necessary.","secretary_remarks":"Postponed","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11980,"status":"postponed","reservation_date":"2022-04-21 14:48:21","uploaded":"2022-05-18 08:29:46","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-223476","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203668.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204523","title":"Clarification on roaming for NSAC procedure","source":"ZTE, Nokia, Nokia Shanghai Bell","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add clarification according to the GSMA requirements.","secretary_remarks":"CR Number missing on cover sheet. r04 agreed. Revised to S2-2204738.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11930,"status":"revised","reservation_date":"2022-05-06 15:02:47","uploaded":"2022-05-06 16:01:38","revisionof":"","revisedto":"S2-2204738","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3652.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204523.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204723","title":"[DRAFT] Response LS from CT WG4: LS on clarification on per access NSAC requirement","source":"ZTE","contact":"Jinguo Zhu","contact-id":78054,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: TSG CT","secretary_remarks":"Response to S2-2203667. CC#3: r09 agreed. Revised to S2-2204903.","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11960,"status":"revised","reservation_date":"2022-05-23 07:09:35","uploaded":"2022-05-24 08:11:20","revisionof":"","revisedto":"S2-2204903","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"TSG CT","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204723.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204738","title":"Clarification on roaming for NSAC procedure","source":"ZTE, Nokia, Nokia Shanghai Bell","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add clarification according to the GSMA requirements.","secretary_remarks":"Revision of S2-2204523r04. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11940,"status":"agreed","reservation_date":"2022-05-23 07:09:42","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2204523","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3652.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220401","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204738.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204903","title":"Reply LS on clarification on per access NSAC requirement","source":"SA WG2","contact":"Jinguo Zhu","contact-id":78054,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: TSG CT","secretary_remarks":"Revision of S2-2204723r09. Approved","agenda_item_sort_order":47,"ainumber":"8.4","ainame":"Enhancement of Network Slicing Phase 2 (eNS_Ph2)","tdoc_agenda_sort_order":11970,"status":"approved","reservation_date":"2022-05-23 07:10:55","uploaded":"2022-05-24 08:11:22","revisionof":"S2-2204723","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eNS_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2203667","lsto":"CT WG4","Cc":"TSG CT","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204903.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]