[{"name":"S2-2303915","title":"LS from Wi-Fi Alliance: Wi-Fi Alliance communication on methods for consistent QoS across 5G and Wi-Fi networks","source":"Wi-Fi Alliance","contact":"Consuelo Ortiz","contact-id":61067,"tdoctype":"LS in","for":"Information","abstract":"Dear SA WG2 Chair and Vice Chairs, Wi-Fi Alliance Operator Marketing Task Group, a group with a focus on the needs of Wi-Fi Network Operators, contributed to a paper published by Wi-Fi Alliance titled Analyzing operator QoS deployment scenarios between Wi-Fi and 5G (2022) . This paper advocates for a consistent quality of service approach across Wi-Fi and 5G networks for end-to-end QoS experience. We would like to make SA WG2 aware of this paper as this relates to enabling mapping between 5G QoS to Wi-Fi QoS across 5G and Wi-Fi access networks. The intent of the paper is to provide guidance to operators to assess methods to map QoS across 5G and Wi-Fi networks. The paper highlights different deployment scenarios for fixed mobile convergence (FMC) with 5G access used for backhaul connectivity. It advocates that the FMC is opening new opportunities for service operators, ISPs and MNOs to offer converged data services over wired or wireless access networks. The paper also advocates that the 3GPP defined convergence architecture for integrating Wi-Fi access into the 5G system via N3IWF\/TNGF\/TWIF enables operators to offer seamless connectivity over Wi-Fi and 5G for converged services. For both FMC and 3GPP defined Wi-Fi and 5G convergence deployment scenarios, paper recommends use of QoS mapping to provide consistent QoS treatment across wired, Wi-Fi, and 5G networks, and for the industry to adopt the features included in Wi-Fi CERTIFIED QoS Management to enable robust delivery of latency sensitive services. It recommends using IETF defined DSCP marking as a bridge between mapping 5G QoS to Wi-Fi QoS, by defining a mapping between 5QI to DSCP (and vice versa) and then mapping DSCP to 802.11 User Priority (UP). Wi-Fi Alliance would like to bring following items to SA WG2 attention and consideration: 10900-A Stonelake Boulevard, Suite 195 Austin, Texas 78759 U.S.A. Phone: +1-512-498-9434 (WIFI) Fax: +1-512-498-9435 www.wi-fi.org 3 1) Consideration of DSCP markings at UPF and UE In FMC deployment scenarios, service data flows from wireline core are marked with DSCP for QoS differentiation. The paper recommends that in the 5G core packet classification filters set on the UPF take into consideration DSCP along with other packet filtering criteria, to map these wireline service data flows to 5G QoS flows with desired 5QIs. For both FMC and 3GPP defined 5G and Wi-Fi integration architecture, paper recommends that the UE take into consideration DSCP markings of IP flows when mapping uplink service data flows to 5G QoS flows with desired 5Qis. 2) QoS Mapping at CPEs For FMC deployments, paper recommends that the customer premise equipment (CPEs) implement functionality for mapping service flows between 5G backhaul and Wi-Fi fronthaul access in both downlink and uplink, using 5QI to DSCP to UP mapping in downlink and DSCP to 5QI mapping in uplink. The paper also recommends that CPEs support Wi-Fi CERTIFIED QoS Management to provide their customers a consistent connectivity experience over wired or wireless networks. For more information, please contact Consuelo Ortiz cortiz@wi-fi.org . Sincerely, Wi-Fi Alliance","secretary_remarks":"Revision of postponed S2-2302181 from S2#155. Response drafted in S2-2304475. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10030,"status":"noted","reservation_date":"2023-03-04 14:37:46","uploaded":"2023-04-03 14:38:30","revisionof":"S2-2302181","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"20221202_WiFi_Alliance","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303915.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303916","title":"LS from CT WG1: LS on Handling of the Allowed PDU session status IE in Non-allowed service area","source":"CT WG1","contact":"Robert Zaus","contact-id":85311,"tdoctype":"LS in","for":"Action","abstract":"At CT WG1#139e, CT WG1 discussed certain requirements related to the UE behaviour in a non-allowed service area. CT WG1 would like to ask SA WG2 for guidance on an issue. The scenario is as follows: 1) The UE is registered to an AMF both via 3GPP and non-3GPP access. The UE is currently in a non-allowed area. The registration area (TAI list) for 3GPP access includes both TAs from the UE's non-allowed area and TAs from the allowed area. The UE is currently in a non-allowed area. 2) The UE has at least 1 PDU session activated via non-3GPP access which cannot be transferred to 3GPP access. 3) The UE is in IDLE mode both for 3GPP and non-3GPP access, when it receives a paging via 3GPP access indicating non-3GPP access and responds with a Service Request. CT WG1 understands that if the UE responds to the paging when it is in a TA belonging to the allowed area, then the UE needs to include the Allowed PDU session status IE (in 23.502 terminology: 'List Of Allowed PDU Sessions') indicating which of the PDU sessions associated with non-3GPP access can be transferred to 3GPP access and may include the Uplink data status IE if it has uplink data pending. Question 1: Does the UE need to include the Allowed PDU session status IE also if it responds to the paging when it is in a non-allowed area? Question 2: Is the UE allowed to include the Uplink data status IE if it has uplink data pending if it responds to the paging when it is in a non-allowed area?. Action: CT WG1 kindly ask SA WG2 to answer CT WG1's question.","secretary_remarks":"Revision of postponed S2-2302183 from S2#155. Responses drafted in S2-2304059, S2-2304589, S2-2305059, S2-2305391. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"postponed","reservation_date":"2023-03-04 14:37:46","uploaded":"2023-04-03 14:38:30","revisionof":"S2-2302183","revisedto":"S2-2306265","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-227197","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303916.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303918","title":"LS from SA WG5: Reply LS on reporting dynamic satellite backhaul parameters to CHF","source":"SA WG5","contact":"Yingying Liu","contact-id":94862,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 thanks SA WG2 for the LS on reporting dynamic satellite backhaul parameters to CHF. SA WG5 would like to inform SA WG2 that SA WG5 has agreed a study item which is proposed to investigate possible charging scenarios and potential charging requirements, as well as charging aspect of PCC\/QoS control enhancement related to the satellite backhaul. Further discussions are needed regarding reporting dynamic satellite backhaul parameters. SA WG5 will update SA WG2 after conclusion of further discussions. Action: SA WG5 kindly requests SA WG2 to take above information into consideration.","secretary_remarks":"Revision of postponed S2-2302192 from S2#155. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10420,"status":"noted","reservation_date":"2023-03-04 14:37:46","uploaded":"2023-04-03 14:38:30","revisionof":"S2-2302192","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S5-226685","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303918.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303923","title":"LS from GSMA 5GMRR: LS to 3GPP on GSMA requirements regarding intermediaries in the roaming ecosystem (Roaming Hub, IPX and RVAS Providers)","source":"GSMA 5GMRR","contact":"Kathleen Leach","contact-id":87129,"tdoctype":"LS in","for":"Action","abstract":"5GMRR would like to provide 3GPP with requirements, as requested by 3GPP, for the major intermediaries and services (Roaming Hub, IPX and RVAS Providers) needed within the roaming ecosystem. The requirements outline support for the use cases that are established in roaming to date and that are also required in 5G SA roaming and interconnect. Actions: GSMA NRG 5GMRR kindly requests 3GPP to consider the above entities in their specifications and the related service requirements for roaming ecosystem intermediaries per role (RH, IPX Provider, RVAS Provider) as provided per separate LSs. Please provide advice on how they can be supported using current specifications. Moreover, the group kindly requests SA WG1, SA WG2 and SA WG3 and CT WG4 to also consider updating their specifications at the earliest possible release in order to support requirements that are currently not covered. This will allow the GSMA to support the use cases that are established in roaming currently and that should be provided for 5G SA roaming and interconnect, too. Please note that the above roles can have overlapping requirements. 5GMRR would like to work together with 3GPP in order to develop solutions that meet these requirements while complying to the 5GS architecture and security specifications.","secretary_remarks":"Noted. CC#4: This was postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"postponed","reservation_date":"2023-03-04 14:37:46","uploaded":"2023-04-04 09:18:13","revisionof":"","revisedto":"S2-2306270","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG1, SA WG2, SA WG3","Cc":"CT WG4","lsoriginalls":"5GMRR Doc 41_37r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303923.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303924","title":"LS from GSMA 5GMRR: LS to 3GPP on IPX Requirements for 5GS Roaming","source":"GSMA 5GMRR","contact":"PRADEEP BHARDWAJ","contact-id":78621,"tdoctype":"LS in","for":"Action","abstract":"GSMA 5GMRR thanks SA WG3 for their reply LS (S3-231389) on PRINS middle boxes. This LS response focuses on the requirements from IPX providers, one of the roles in the roaming eco-system. Actions: GSMA 5GMRR kindly asks 3GPP to take the following actions: SA WG1 to update their specifications in order to support IPX provider requirements that are currently not covered. SA WG2 to enhance the 5G architecture to meet the IPX provider requirements. SA WG3 to define a security solution that includes the IPX providers requirements","secretary_remarks":"Noted. CC#4: This was postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"postponed","reservation_date":"2023-03-04 14:37:46","uploaded":"2023-04-04 09:18:13","revisionof":"","revisedto":"S2-2306271","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, SA WG3","Cc":"TSG SA, CT WG4","lsoriginalls":"5GMRR#41 Doc 38r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303924.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303925","title":"LS from GSMA 5GMRR: LS Roaming Value Added Service Requirements","source":"GSMA 5GMRR","contact":"Gery Verwimp","contact-id":20103,"tdoctype":"LS in","for":"Action","abstract":"This LS focusses on one of the three roles in the roaming eco-system, namely roaming value-added service (RVAS) providers. Actions: GSMA NRG 5GMRR kindly requests 3GPP to consider the attached service requirements from RVAS providers. GSMA 5GMRR kindly asks 3GPP to determine how the 5G specifications can be adapted to support these requirements. GSMA 5GMRR asks 3GPP to take note of the current sponsored roaming facilitation using dual or multi-IMSI profiles on the SIM, and advise on any concerns with respect to authentication or concealment algorithms. SA WG1, SA WG2, and SA WG3 are kindly asked to take into account the above requirements of GSMA 5GMRR to enable RVAS providers.","secretary_remarks":"Noted. CC#4: This was postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"postponed","reservation_date":"2023-03-04 14:37:46","uploaded":"2023-04-04 09:18:13","revisionof":"","revisedto":"S2-2306272","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, SA WG3","Cc":"TSG SA, CT WG4","lsoriginalls":"5GMRR Doc 41_39r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303925.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303926","title":"LS from GSMA 5GMRR: LS with Roaming Hubbing requirements and LS response to 3GPP SA3 LS (S3-214456) on 5GS Roaming Hubbing","source":"GSMA 5GMRR","contact":"Pieter Veenstra","contact-id":86411,"tdoctype":"LS in","for":"Action","abstract":"This LS lists Roaming Hubbing specific requirements and responds to SA WG3 LS on 5GS roaming hubbing (S3-214456). Actions: GSMA NRG 5GMRR kindly requests 3GPP to consider the above service requirements for roaming hubs and to provide advice on how these requirements can be supported using current specifications. Moreover, the group kindly requests SA WG1, SA WG2 and SA WG3, and CT WG4 to update their specifications in order to support requirements that are currently not covered to support the RH use cases that are established in roaming to date and that should be provided for 5G SA roaming and interconnect, too. 5GMRR would like to work together with 3GPP in order to develop solutions that meet these requirements while complying to the 5GS architecture and security specifications.","secretary_remarks":"Noted. CC#4: This was postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"postponed","reservation_date":"2023-03-04 14:37:46","uploaded":"2023-04-04 09:18:13","revisionof":"","revisedto":"S2-2306273","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, SA WG3","Cc":"TSG SA, CT WG4","lsoriginalls":"5GMRR Doc 41_40r4","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303926.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303927","title":"LS from GSMA 5GMRR: LS on GSMA 5GMRR Working solution assumption on L-PRINS and Data Session Control","source":"GSMA 5GMRR","contact":"Ahmad Muhanna","contact-id":84435,"tdoctype":"LS in","for":"Action","abstract":"This LS describes a working solution assumption aiming to converge the needs of a service provider and the security architecture as put forward in the 5G SA roaming eco-system. Action to SA WG2: GSMA 5GMRR kindly requests SA WG2 to consider the Service Provider Data Session Control call flow in this LS and to provide feedback.","secretary_remarks":"Noted. CC#4: This was postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"postponed","reservation_date":"2023-03-04 14:37:46","uploaded":"2023-04-04 09:18:13","revisionof":"","revisedto":"S2-2306274","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, CT WG4","Cc":"TSG SA, SA WG1","lsoriginalls":"5GMRR Doc 41_41r3","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303927.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303934","title":"LS from CT WG3: LS on API enhancement for GMEC services and AIMLSys services","source":"CT WG3","contact":"Parthasarathi Ravindran","contact-id":68434,"tdoctype":"LS in","for":"Action","abstract":"In Rel-18 group management, exposure and communication (GMEC), NEF enhanced to define a new dedicated NEF service API, i.e. Nnef_AFRequestForQoS, to support the provisioning of traffic characteristics and the monitoring of performance characteristics for a UE or a group of UEs. Also in Rel-18 and AI\/ML-based services (AIMLSys) service, a new multi member AF Session With QoS service i.e. Nnef_MultiMemberAFsessionWithQoS service API is introduced in the SA WG2#155 agreed TS 23.501 CR 4128 (S2-2303873) and TS 23.502 CR 3795 (S2-2303826). Questions: CT WG3 would like to kindly ask SA WG2: 1) Whether SA WG2 is planning to merge these two APIs into a single one? 2) What is the common part and\/or difference between the Nnef_AFRequestForQoS service API and the Nnef_MultiMemberAFsessionWithQoS service API?. Action: CT WG3 kindly asks SA WG2 to respond to the questions above.","secretary_remarks":"Responses drafted in S2-2304257, S2-2304440, S2-2304588, S2-2305040 (noted). Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"postponed","reservation_date":"2023-03-04 14:37:46","uploaded":"2023-04-04 09:18:13","revisionof":"","revisedto":"S2-2306275","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-230783","lsreply":"S2-2306705","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303934.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303937","title":"LS from CT WG4: LS Reply on PRINS middle boxes","source":"CT WG4","contact":"Shunsuke Dojiri","contact-id":96171,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 would like to thank GSMA 5GMRR for the LS on PRINS middle boxes (5GMRR#40 Doc 05 \/ C4-230038). CT WG4 would like to indicate the following points: 1) CT WG4 is willing to enhance the N32 error reporting and will work on it in the future meetings once requirements are specified by GSMA. 2) CT WG4 shares same view as SA WG3 regarding the requirement on messages being initiated by a middle box, i.e. SA WG3 would like to point out that this kind of session management as well as the concept of intermediaries originating signalling messages are not covered by the current 5G architecture. This applies regardless of whether PRINS or TLS is used over N32. 3) N32 protocol already allows operators to limit the N32 purposes applicable to a N32 connection. It should be up to operators or GSMA whether to define specific restriction in the combination of N32 purposes, if any. But CT WG4 does not intend to specify such restrictions in the protocol.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"noted","reservation_date":"2023-03-04 14:37:46","uploaded":"2023-04-04 09:18:13","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GMRR","Cc":"GSMA DESS, SA WG3, SA WG2","lsoriginalls":"C4-230547","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303937.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303938","title":"LS from CT WG4: LS on UE memory available for SMS","source":"CT WG4","contact":"Ulrich Wiehe","contact-id":73600,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 have agreed the attached CR to TS 29.503, allowing the SMSF to report the 'UE-Memory-available' indication to the UDM by means of the SMSF Registration Update service operation, as a trigger for the SMS Alerting. CT WG4 have noted that 23.502 in table 4.15.3.1-1 suggests that the 'UE memory available for SMS' event is determined and reported to UDM by the AMF, while actually this can only be done by the SMSF. Action: CT WG4 kindly ask SA WG2 to update 23.502 inline with the agreed attached CR.","secretary_remarks":"Response drafted in S2-2304381 (noted). Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"postponed","reservation_date":"2023-03-04 14:37:46","uploaded":"2023-04-04 09:18:13","revisionof":"","revisedto":"S2-2306276","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-230625","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303938.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303939","title":"LS from CT WG4: Reply LS on Identifier availability for Lawful Interception during Inter-PLMN handover","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks SA WG2 for their LS (S2-2302165) on Identifier availability for Lawful Interception during Inter-PLMN handover. CT WG4 has agreed the attached 29.274 CR to support the transfer of the MSISDN during Inter-MME\/AMF handover and TAU procedures. Action: CT WG4 kindly asks SA WG2 and SA WG3-LI to take the above information into account.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10440,"status":"noted","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 09:18:13","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3-LI","Cc":"SA WG3, CT WG3","lsoriginalls":"C4-230628","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303939.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303968","title":"LS from SA WG3: LS reply to TSG SA on LS 5G-ACIA-LS-2022-005 on 5G capabilities exposure for factories of the future \u2013 identified gaps from 5G ACIA","source":"SA WG3","contact":"Markus Staufer","contact-id":88693,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank 5G-ACIA for their LS 5G-ACIA-LS-2022-005 on '5G capabilities exposure for factories of the future identified gaps' and would like to thank SA WG for their effort to coordinate the response to 5G ACIA. SA WG3 has discussed the LS from 5G ACIA with a focus on Gaps G.1, G.3 and limitation L.6, which have been identified as being potentially relevant for SA WG3. The following conclusions have been agreed: G.1 Provisioning of subscriptions SA WG3 did not standardize or does not have plans to standardize a mechanism to provision information related to the identity of a subscription (i.e., UE Ids or authentication keys) into the 5G core. For the sake of clarity SA WG3 also points out that SA WG3 did not define and does not have plans to define a protocol for provisioning of subscription data to a UE. G.3 Provision of security event\/logging information SA WG3 interprets the terms event and logging information in such way, that it refers to events and logging information originating from the 5G core, but not to events and logging information originating from the UE. According to the understanding of SA WG3 security events and logging information include for instance information relating to successful and unsuccessful (primary, secondary, slice specific) authentications of UE and information relating to applied protection of user plane traffic. SA WG3 did not and does not have plans to standardize exposure of these events or logging information. SA WG3 proposes to take responses from other working groups (e.g., SA WG2, SA WG5) into account, when assessing this gap. Based on requirements from SA WG1 or proposals from member companies, SA WG3 can work on adding these events following the SA WG3 working procedures. Due to the sensitive nature of the information to be exposed, SA WG3 suggests being consulted, in case other working groups plan to standardize the exposure of the requested information. L.6 Fine-grained authorization SA WG3 points out that the authorization of Application Functions (AF) at the exposure point can be executed using the OAuth 2.0 procedures. The currently defined scopes allow authorization on the level of services. Vendors might define and make available additional scopes in their specific products. In addition to authorization based on OAuth 2.0, the exposure points might limit the scope of API calls in a fine granular way based on implementation specific policy checks as indicated in Clause 12.2 of TS 33.501.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10450,"status":"noted","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 11:14:06","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2, SA WG5, SA WG6, TSG CT","lsoriginalls":"S3-231387","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303968.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303969","title":"LS from SA WG3: LS Reply on PRINS middle boxes","source":"SA WG3","contact":"Alf Zugenmaier","contact-id":52494,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to thank GSMA 5GMRR for the LS on PRINS middle boxes (5GMRR#40 Doc 05 \/ S3-230606, see attached). 5GMRR LS states that: Sometimes, RHs are tasked with per-subscriber bandwidth management. In the event of exhaustion of a subscriber s data quota, the RH may need to trigger appropriate signalling, both towards the VPLMN SEPP and the HPLMN SEPP, without undue delay, that results in the disconnection of the subscriber s PDU session. SA WG3 would like to point out that this kind of session management as well as the concept of intermediaries originating signalling messages are not covered by the current 5G architecture. More generally, if there is a requirement for intermediaries to generate arbitrary messages within the context of other use cases that are currently not described, there may be further security issues, e.g. with subscriber privacy, if intermediaries are allowed to ask for subscriber location. SA WG3 would like to request SA WG2 to verify whether this kind of message injection would be aligned with 5G system architecture and procedures. Independently, SA WG3 would like to inform 5GMRR that SA WG3 believes that the potential for state mismatch between cNF and pNF may also have security impacts. SA WG3 would like to inform GSMA 5GMRR that SA WG3 is willing to work with 5GMRR to enable an end to end secure solution. However, a stable and comprehensive set of requirements is necessary. SA WG3 has included a potential solution (see attached S3-231419) that is under discussion (i.e. not agreed yet) to understand, whether this would provide the required features as required by GSMA 5GMRR. Further analysis of the solution will take place in SA WG3 to fully understand the security and privacy impact. As the error handling is considered stage 3 work, SA WG3 would like to request CT WG4 to consider specifying the mechanisms necessary for the error reporting requested by 5GMRR. Action: SA WG3 would like to kindly ask SA WG2 to consider whether the procedure proposed by GSMA is aligned with the 5G system architecture.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10460,"status":"postponed","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 11:14:06","revisionof":"","revisedto":"S2-2306279","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GMRR, CT WG4, SA WG2","Cc":"GSMA DESS","lsoriginalls":"S3-231389","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303969.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303970","title":"Reply LS on PLMN ID used in Roaming Scenarios","source":"SA WG3","contact":"Anja Jerichow","contact-id":68341,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks CT WG4 and SA WG2 on their observations and guidance in response to the SA WG3 LS on PLMN ID used in Roaming Scenarios. SA WG3 informs CT WG4 and SA WG2 that the Draft CR under discussion has been finalized in line with CT WG4 explanation, including the resolution of the two remaining editor s notes. SA WG3 would also like to inform GSMA 5GMRR on the 3GPP TS 33.501 updates related to identifying the PLMN ID of a SEPP. The term 3gpp-Sbi-Originating-Network-Id is used as defined in TS 29.500 as the mandatory custom header that can be always included by the sending NF from Rel-17 onwards. The included PLMN ID represents the serving PLMN ID. SA WG3 refers 5GMRR to CT WG4 stage 3 LS reply (S3-223152\/C4-224444) for further explanations. Further, SA WG3 would like SA WG2, CT WG4, and GSMA 5GMRR to acknowledge that requirements and explaining text are added to deal with the use case of NF and SCP not including the custom header, i.e., pre-release 17, as well as distinguishing the handling between SEPPs representing only one PLMN-ID and multiple PLMN-IDs. The related CRs S3-231606 and S3-231417 are attached. Action: Take the information into account.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10470,"status":"noted","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 11:14:06","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG4","Cc":"GSMA 5GMRR","lsoriginalls":"S3-231391","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303970.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303975","title":"LS from SA WG4: An Invitation to the SA WG4 Gender Diversity Committee Meetings","source":"SA WG4","contact":"Nikolai Leung","contact-id":38562,"tdoctype":"LS in","for":"Action","abstract":"The SA WG4 Gender Diversity Committee is an informal group that was initiated in 2018 by some delegates and an SA WG4 Vice Chair to discuss and improve gender diversity in SA WG4 and the industry at large. The Committee had been meeting regularly since then until COVID travel restrictions prevented in person meetings. Now, with face-to-face meetings resuming, the Committee has re-started its regular dinner meetings and also invited the SA WG2 and SA WG3 WGs to join at SA WG4#122 in Athens. The attached Tdoc provides the Committee meeting report provided as FYI. Based on interest expressed at this week s meeting, the Committee plans to meet every Tuesday evening (7:30-10:00pm) of our face-to-face meetings and invites everyone attending other co-located 3GPP WGs to join our dinner meetings. One instantiation of this effort is SA WG4 planning to send out an invitation for May 23, 2023 (7:30-10:00pm CEST) to the SA WGs co-located at the Berlin meetings. We would appreciate you sharing this information with your members so that we can gauge the level of interest soon. We are asking the meeting host to reserve us a hotel meeting room to have our dinner meeting on the 23rd. Action: The SA WG4 Gender Diversity Committee asks the SA WGs to take our invitation into consideration and, if interested, RSVP to any upcoming invitations at future co-located meetings.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10480,"status":"postponed","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 11:14:06","revisionof":"","revisedto":"S2-2306281","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG1, SA WG2, SA WG3, SA WG5, SA WG6","Cc":"","lsoriginalls":"S4-230431","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303975.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303976","title":"LS on management of AS by AF","source":"SA WG4","contact":"Richard Bradbury","contact-id":82569,"tdoctype":"LS in","for":"Action","abstract":"As part of its study on extensions to the 5G Media Streaming (5GMS) architecture, SA WG4 has identified a requirement for a 5GMS Application Function to manage a population of 5GMS Application Servers. During the course of the study, it has become apparent that the management relationship is also generally applicable to other classes of Application Function (AF) managing a population of Application Server (AS) instances. This relationship is particularly relevant in deployments where the AS and AF are supplied by different vendors and interoperability is therefore a relevant topic for standardisation. At SA WG4#122, it was agreed to add a Key Issue on this topic to TR 26.804 in Rel 18 and the relevant Change Request is attached for you reference. {. . .} Action: SA WG4 kindly requests SA WG2 to comment on the above proposal to define a generic, reusable service-based architecture and API for AS instance management by an AF. Action: SA WG4 kindly requests SA WG2 to inform it of any existing or planned work in this area.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10490,"status":"postponed","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 11:14:06","revisionof":"","revisedto":"S2-2306282","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG6","lsoriginalls":"S4-230436","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303976.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303978","title":"LS from SA WG5: Reply LS on CHF Logic Realization w.r.t. Spending Limits functionality","source":"SA WG5","contact":"Zhiwei Mo","contact-id":93813,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 thanks SA WG2 for the LS on CHF Logic Realization wrt\/ Spending Limits functionality and would like to provide the response as follows: Question 1: Is it necessarily the same CHF that handles both Session Management Spending Limits and access and mobility\/UE Spending Limits? SA WG5 Answer: It should use the same CCS (Converged Charging System) to handle both Session Management Spending Limits and access and mobility\/UE Spending Limits, however it is not specified in current specifications. Question 2: Is it necessarily the same CHF that handles Spending Limits for AM policy and UE Policy of a subscriber? SA WG5 Answer: It should use the same CCS to handle Spending Limits for AM policy and UE Policy of a subscriber, however it is not specified in current specifications. Question 3: Is it necessarily the same CHF that handles Spending Limits across all PDU sessions of a subscriber? SA WG5 Answer: It should use the same CCS to handle Spending Limits across all PDU sessions of a subscriber, however it is not specified in current specifications. Question 4: Can the same SL policy counter be used for AM policy control or\/and UE policy control or\/and SM policy control? SA WG5 Answer: How SL policy counters are used is not in scope of SA WG5. Question 5: Can an SL policy counter be used for specific services besides data connectivity service, e.g. SMS service? SA WG5 Answer: How SL policy counters are used is not in scope of SA WG5. Question 6: Does CHF need to obtain AMF charging reports in order to be able to support SL functionality? SA WG5 Answer: There is currently no restrictions on how the SL policy counters may be updated, there is no requirement to use charging reports from the AMF at present. Action: SA WG5 kindly requests SA WG2 to take above information into consideration.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10500,"status":"noted","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 11:14:06","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"S5-232735","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303978.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303979","title":"LS from SA WG5: LS on the provisioning services specified in SA WG5","source":"SA WG5","contact":"Song Zhao","contact-id":87845,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 is responsible for specification of various management and orchestration aspects related to 3GPP systems. As part of the on-going study on management aspects of NWDAF (FS_MANWDAF), we observed in TS 23.288-i00 the service, procedure and capability containing the term of 'provision' in their names, such as: - Nnwdaf_MLModelProvision services - Procedure for ML Model Provisioning - analytics metadata provisioning capability In OAM terminology the term 'provisioning' represents a combination of Life Cycle Management (LCM) and Configuration Management (CM). According to the SA WG5 TOR, the important areas where SA WG5 is actively involved include CM and LCM. Therefore, we perceive that specification of provisioning is within the scope of SA WG5. The specifications related to provisioning services include (but not limited to): TS 28.531, TS 28.532, TS 28.541. SA WG5 would like to know what provisioning requirements (to be satisfied by OAM specifications\/solutions) have been identified by SA WG2. Action: SA WG5 kindly requests SA WG2 to take into account the scope of responsibilities of SA WG5 (documented in the SA WG5 TOR) and share their expectations\/requirements for specification of provisioning services.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10510,"status":"postponed","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 11:14:06","revisionof":"","revisedto":"S2-2306283","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S5-232774","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303979.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303980","title":"LS from SA WG5: LS on 3GPP work on Energy Efficiency","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Action","abstract":"This attached document, endorsed by SA WG5 at its meeting#146-bis-e, aims at providing a comprehensive view of the ongoing work on Energy Efficiency (EE) in 3GPP. {. . .} Actions: To TSGs SA, RAN, CT, WGs SA WG1, SA WG2, SA WG3, SA WG4, SA WG6, RAN WG1, RAN WG2, RAN WG3, RAN WG4, CT WG1, CT WG3, CT WG4: Please correct and\/or complement the table present in the attached document if and where deemed appropriate, Please keep SA WG5 informed in case of new Rel-18 SI\/WI addressing energy efficiency and\/or energy saving and\/or digital sobriety, so that SA WG5 can maintain such information for the Rel-18 or later release timeframe.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10520,"status":"noted","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 11:14:06","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG RAN, TSG CT, SA WG1, SA WG2, SA WG3, SA WG4, SA WG6, RAN WG1, RAN WG2, RAN WG3, RAN WG4, CT WG1, CT WG3, CT WG4","Cc":"","lsoriginalls":"S5-232903","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303980.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303981","title":"LS from SA WG5: LS reply to Reply LS on Network federation interface for Telco edge consideration","source":"SA WG5","contact":"Deepanshu Gautam","contact-id":81664,"tdoctype":"LS in","for":"Information","abstract":"In the reply LS (S3-223914) SA WG3 mentioned the following 1. It would be better to give the details on how to define the procedures of the OAuth2 protocol and Client Credentials, such as which network function will take the OAuth Authorization server role, what will be included in the token, the details for the Client Credentials, etc. TS 33.501 clause 13.4 may be referred here for the details. With regards to what will be included in the token , SA WG5 would like to mention the following: 1. SA WG5 is working the E\/WBI API requirements as part of eECM and FS_MEC_ECM WID and SID respectively. 2. The authorization token shall represent the granular access authorizations for the Client (Consumer is SA WG5 terminology ) pertaining to the APIs (MnS in SA WG5 terminology) being accessed. The possible content of the token is described in 3GPP TR28.817, clause 7.1.4.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10530,"status":"noted","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 11:14:06","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, SA WG6","Cc":"SA WG2, TSG SA","lsoriginalls":"S5-233146","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303981.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303982","title":"LS from SA WG5: LS reply to Reply LS cc: SA WG5 on Network federation interface for Telco edge consideration","source":"SA WG5","contact":"Deepanshu Gautam","contact-id":81664,"tdoctype":"LS in","for":"Information","abstract":"S5-232047 (SP-221321) mentions the following as SA WG5 response SA WG5 is looking into solutions to support requirements on east\/west bound interface including edge federation in the edge computing management work and network slice management capability exposure in the management aspects of network slice management capability exposure work. SA WG5 would provide further updates as appropriate. SA WG5 would like to correct the above statement as follows SA WG5 is looking into solutions to support requirements on east\/west bound interface including edge federation in the edge computing management work (eECM) and network slice management capability exposure work (FS_NSCE). SA WG5 would provide further updates as appropriate.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10540,"status":"noted","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 11:14:06","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, SA WG6","lsoriginalls":"S5-233147","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303982.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303987","title":"LS from SA WG6: LS reply to TSG SA on LS 5G-ACIA-LS-2022-005 on 5G capabilities exposure for factories of the future \u2013 identified gaps from 5G ACIA","source":"SA WG6","contact":"Niranth Amogh","contact-id":39608,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 would like to thank 5G-ACIA for their LS 5G-ACIA-LS-2022-005 on '5G capabilities exposure for factories of the future identified gaps' and would like to thank SA WG for their effort to coordinate the response to 5G ACIA. SA WG6 has discussed the LS from 5G ACIA, and has identified gaps and limitations potentially relevant for SA WG6. The following aspects are provided for further consideration by 5G ACIA: G.4 Traffic profile (QoS) for network connections: SA WG6 has specified Network Resource Management service in 3GPP TS 23.434, Edge enabler service in 3GPP TS 23.558 and 5G Messaging service in 3GPP TS 23.554 which specifies procedures and APIs which can be used for this purpose. L.2 Dynamic solution for application centric-QoS: SA WG6 has specified Network Resource Management service in 3GPP TS 23.434 which specifies procedures and APIs which can be used for this purpose. L.3 Establishment of UE-to-UE (UNU) QoS bearer with a single API call: 5G ACIA recognizes that SEAL provides the support for this purpose. L.4 Monitoring of device connectivity, including the connection s QoS: SA WG6 has specified Network Resource Management service in 3GPP TS 23.434 which specifies procedures and APIs which can be used for this purpose. L.6 Fine-grained authorization on the level of specific services and resources: SA WG6 has enabled CAPIF to support Resource Owner Aware Access to resources served by service APIs. The procedures and APIs which can be used for this purpose are specified in 3GPP TS 23.222 for which SA WG3 is currently working on the detailed security procedures. SA WG6 kindly asks 5G ACIA to provide any feedback for the above aspects. SA WG6 would like to share the information of the following specifications which support the applications for Factories of the Future and may be of interest to 5G ACIA: 1. Application layer support for Factories of the Future (FF) specified in 3GPP TS 23.545. 2. SEAL services: a. Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows specified in 3GPP TS 23.434. b. SEAL Data Delivery enabler for vertical applications specified in 3GPP TS 23.433. c. Procedures for Network Slice Capability Exposure for Application Layer Enablement Service specified in 3GPP TS 23.435. d. Procedures for Application Data Analytics Enablement Service specified in 3GPP TS 23.436. 3. Common API Framework (CAPIF) for 3GPP Northbound APIs specified in 3GPP TS 23.222. 4. Architecture for enabling Edge Applications specified in 3GPP TS 23.558. 5. Application architecture for MSGin5G Service specified in 3GPP TS 23.554. Currently work is on-going for Rel.18 features for the above specifications and SA WG6 asks 5G ACIA to provide any feedback on the on-going work on the above specifications.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10550,"status":"noted","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 11:14:06","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2, SA WG3, SA WG5, TSG CT","lsoriginalls":"S6-231068","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303987.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303988","title":"LS from SA WG6: LS on SA WG6 V2X service support","source":"SA WG6","contact":"Emmanouil Pateromichelakis","contact-id":94983,"tdoctype":"LS in","for":"Information","abstract":"In SA WG6#52-bis-e, SA WG6 received (in cc) a Reply LS on QoS Sustainability analytics and V2X service adaptations (SP-221320) which provided a consolidated answers from SA WG1 and SA WG2 on the 5GAA LS on QoS Sustainability analytics and V2X service adaptations (S-220077). The 5GAA LS was pointing to a technical report (5GAA_T-220058_WI-PRESA-Technical-Report), which included some requirements and assumptions on the current 3GPP support to support these requirements. {. . .}","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10560,"status":"postponed","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 11:14:06","revisionof":"","revisedto":"S2-2306285","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2","lsoriginalls":"S6-231091","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303988.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303990","title":"LS from GSMA OPG: LS on publication of GSMA OPG and OPAG documents","source":"GSMA OPG","contact":"Sandra Ondrusova","contact-id":77474,"tdoctype":"LS in","for":"Action","abstract":"GSMA OPG would like to inform you that the groups (OPG and OPAG) have recently published a new version of several documents and a new document for User-Network Interface APIs. GSMA PRD OPG.02 Operator Platform Telco Edge Requirements version 4.0, available at https:\/\/www.gsma.com\/futurenetworks\/resources\/operator-platform-telco-edge-requirements\/ GSMA PRD OPG.03 Southbound Interface Network Resources APIs version 2.0, available at https:\/\/www.gsma.com\/futurenetworks\/resources\/southbound-interface-network-resources-apis\/ GSMA PRD OPG.04 East-Westbound Interface APIs version 2.0, available at https:\/\/www.gsma.com\/futurenetworks\/resources\/east-westbound-interface-apis\/ GSMA PRD OPG.05 User-Network Interface APIs, available at https:\/\/www.gsma.com\/futurenetworks\/resources\/gsma-operator-platform-group-user-network-interface-apis\/. Actions: GSMA OPG kindly ask you take the above information into consideration.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10570,"status":"noted","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-06 14:21:27","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5, SA WG6, ETSI ISG MEC, ETSI ISG NFV","Cc":"GSMA OPAG","lsoriginalls":"OPG_128_Doc_03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303990.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2303991","title":"LS from GSMA TSGUEWIFI: LS to 3GPP SA WG2 on 3GPP and non-3GPP interworking information for VoWiFi","source":"GSMA TSGUEWIFI","contact":"Di Zhang","contact-id":96672,"tdoctype":"LS in","for":"Information","abstract":"GSMA TSG UEWiFi work item is currently working on GSMA PRD 'TS.63 UE Wi-Fi calling specification requirements'. This document defines the minimum mandatory set of features that a 5G device is required to implement in order to guarantee high quality Wi-Fi calling service. Specifically, during the work on GSMA PRD TS.63, it has been found that there is gap existing between 3GPP\/GSMA specification and UE VoWiFi implementation when considering different network deployment. Different operators may have different cellular and Wi-Fi interoperability policy and this interoperability policy may evolve as time goes on. Some typical network deployments are listed as below: {. . .} Action: GSMA TSG UEWIFI group kindly requests SA WG2 to take the information above into account and provide standardized solutions.","secretary_remarks":"GSMA revision: This LS should indicate 'Supporting VoNR' in row 1 if the table. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"postponed","reservation_date":"2023-03-04 14:37:48","uploaded":"2023-04-06 14:39:04","revisionof":"","revisedto":"S2-2306286","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"GSMA NG","lsoriginalls":"UEWIFI07_003","lsreply":"S2-2306809","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303991.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304058","title":"Handling of the List of allowed PDU sessions IE when the UE is in a non-allowed area","source":"Apple (UK) Limited","contact":"Robert Zaus","contact-id":85311,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2023-04-04 13:42:21","uploaded":"2023-04-07 12:09:31","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304058.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304059","title":"[DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area","source":"Apple (UK) Limited","contact":"Robert Zaus","contact-id":85311,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC:","secretary_remarks":"Response to S2-2303916. Merged into S2-2305059 (Postponed)","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"postponed","reservation_date":"2023-04-04 13:46:54","uploaded":"2023-04-07 12:09:31","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304059.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304060","title":"UE handling of the List of allowed PDU sessions in non-allowed area","source":"Apple (UK) Limited","contact":"Robert Zaus","contact-id":85311,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For the setting of the List Of Allowed PDU Sessions the UE shall not take any service area restrictions into account.","secretary_remarks":"CR Cover sheet error! Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"noted","reservation_date":"2023-04-04 13:52:34","uploaded":"2023-04-07 12:09:31","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"TEI18"},{"winame":" 5GS_Ph1"}],"crnumber":4199.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304060.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304061","title":"UE handling of the List of allowed PDU sessions in non-allowed area","source":"Apple (UK) Limited","contact":"Robert Zaus","contact-id":85311,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the setting of the List Of Allowed PDU Sessions is independent of whether any service area restrictions apply in the current UE location (with a reference to clause 5.6.8 of TS 23.501 [2] which includes the mandatory UE requirement).","secretary_remarks":"CR Cover sheet error! Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2023-04-04 13:56:04","uploaded":"2023-04-07 12:09:31","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.0","workitem":[{"winame":"TEI18"},{"winame":" 5GS_Ph1"}],"crnumber":3958.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304061.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304189","title":"Non-allowed area clarification","source":"Ericsson, Samsung, LG Electronics","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Clarify the non-allowed area handling. Related to LS in S2-2302183","secretary_remarks":"Revision of S2-2302318 from S2#155. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2023-05-04 19:15:08","uploaded":"2023-04-07 15:57:34","revisionof":"S2-2302318","revisedto":"S2-2306665","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"5GProtoc18"},{"winame":" TEI18"}],"crnumber":3846.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304189.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.3.4.1.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304255","title":"R18 AIMLsys_GMEC Discussion on a general service operation for Group QoS","source":"Nokia, Nokia Shanghai Bell","contact":"Dongjoo Kim","contact-id":97472,"tdoctype":"discussion","for":"Discussion","abstract":"Discussing how to converge multiple QoS related APIs with the similar purposes being defined in multiple WIDs.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"noted","reservation_date":"2023-06-04 06:50:33","uploaded":"2023-04-07 08:11:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"GMEC"},{"winame":" AIMLsys"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304255.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304257","title":"[DRAFT] Reply LS to CT WG3 on Single SO for QoS","source":"Nokia, Nokia Shanghai Bell","contact":"Dongjoo Kim","contact-id":97472,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC:","secretary_remarks":"Response to S2-2303934. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"noted","reservation_date":"2023-06-04 06:52:46","uploaded":"2023-04-07 08:11:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"GMEC"},{"winame":" AIMLsys"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304257.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304379","title":"SMS memory available","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Complete the missing parts of UE memory available indication","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2023-06-04 11:58:53","uploaded":"2023-04-06 12:14:29","revisionof":"","revisedto":"S2-2307056","release":"Rel-17","crspec":23.502,"crspecversion":"17.8.0","workitem":[{"winame":"SMS_SBI"}],"crnumber":3996.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304379.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.13.3.9, 4.15.3.1, 5.2.3.2.1, 5.2.3.2.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304380","title":"SMS memory available","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Complete the missing parts of UE memory available indication","secretary_remarks":"CR Cover sheet error! Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"noted","reservation_date":"2023-06-04 11:58:54","uploaded":"2023-04-06 12:14:29","revisionof":"","revisedto":"S2-2307057","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"SMS_SBI"}],"crnumber":3997.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304380.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304381","title":"[DRAFT] LS on UE memory available for SMS","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"Inform CT WG4 and CT WG1 on UE memory available for SMS CRs","secretary_remarks":"Response to S2-2303938. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"noted","reservation_date":"2023-06-04 11:58:55","uploaded":"2023-04-06 12:14:29","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"SMS_SBI"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304381.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304440","title":"[DRAFT] ReplyLS on API enhancement for GMEC services and AIMLSys services","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"ReplyLS on API enhancement for GMEC services and AIMLSys services","secretary_remarks":"Response to S2-2303934. Merged into S2-2304257 (noted)","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"noted","reservation_date":"2023-06-04 13:55:37","uploaded":"2023-04-07 07:05:37","revisionof":"","revisedto":"S2-2307091","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"GMEC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304440.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304475","title":"[DRAFT] LS on Wi-Fi Alliance communication on methods for consistent QoS across 5G and Wi-Fi networks","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"LS on Wi-Fi Alliance communication on methods for consistent QoS across 5G and Wi-Fi networks","secretary_remarks":"Response to S2-2303915. r05 agreed. Revised to S2-2305730.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"revised","reservation_date":"2023-06-04 15:38:52","uploaded":"2023-04-07 15:11:11","revisionof":"","revisedto":"S2-2305730","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"WI-FI Alliance","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304475.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304588","title":"[DRAFT] Reply LS to CT WG3 on API enhancement for GMEC\/AIMLSys services","source":"Samsung","contact":"Dongeun Suh","contact-id":84836,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to CT WG3 on API enhancement for GMEC services and AIMLSys services","secretary_remarks":"Response to S2-2303934. Merged into S2-2304257 (noted)","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"noted","reservation_date":"2023-07-04 01:40:10","uploaded":"2023-04-07 07:38:31","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"AIMLsys"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304588.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304589","title":"[DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC:","secretary_remarks":"Response to S2-2303916. Merged into S2-2305059 (Postponed)","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"postponed","reservation_date":"2023-07-04 01:44:58","uploaded":"2023-04-07 04:13:29","revisionof":"","revisedto":"","release":"Rel-18","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_156E_Electronic_2023-04\/Docs\/S2-2304589.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305039","title":"Discussion the enhanced NEF API for AIMLSys and GMEC","source":"QUALCOMM JAPAN LLC.","contact":"Juan Zhang","contact-id":73274,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discussed the enhanced API to support AIMLSys and GMEC.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"noted","reservation_date":"2023-07-04 11:54:26","uploaded":"2023-04-07 12:59:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"AIMLsys"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305039.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305040","title":"[DRAFT] LS on API enhancement for GMEC services and AIMLSys services","source":"QUALCOMM JAPAN LLC.","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC:","secretary_remarks":"Response to S2-2303934. Merged into S2-2304257 (noted)","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"noted","reservation_date":"2023-07-04 12:00:20","uploaded":"2023-04-07 12:59:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"AIMLsys"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305040.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305057","title":"Discussion on Service area restrictions and emergency\/MCS\/MPX","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2023-07-04 12:26:52","uploaded":"2023-04-07 12:44:32","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305057.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305059","title":"[DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC:","secretary_remarks":"Response to S2-2303916. CC#4. r05 revised to S2-2306255. No agreement. Postponed.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"postponed","reservation_date":"2023-07-04 12:30:13","uploaded":"2023-04-07 12:44:32","revisionof":"","revisedto":"S2-2306255","release":"","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_156E_Electronic_2023-04\/Docs\/S2-2305059.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305105","title":"Support for 5QI Priority Level in QoS constraints","source":"Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA","contact":"Robert Streijl","contact-id":92467,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In 5.7.1.11 added 5QI Priority Level to the QoS constraints, and added a note that QoS constraints currently applies to the non-GBR default QoS Flow.","secretary_remarks":"Revision of S2-2209065 from 2022! r00 agreed. Revised to S2-2305731.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"revised","reservation_date":"2023-07-04 13:18:09","uploaded":"2023-04-07 18:04:18","revisionof":"S2-2209065","revisedto":"S2-2305731","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"TEI18"}],"crnumber":3748.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305105.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.7.1.11","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305109","title":"Support for 5QI Priority Level in QoS constraints","source":"Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile","contact":"Robert Streijl","contact-id":92467,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 4.3.2.2.2 changed the specification of QoS constraints to clause 5.7.1.11 of TS 23.501. In clause 5.2.5.4.2 and 5.2.8.2.2 changed the pointer to the QoS constraints specification from clause 4.3.2.2.2 to clause 5.7.1.11 of TS","secretary_remarks":"Revision of S2-2209191 from 2022! CR Cover sheet error! r00 agreed. Revised to S2-2305732.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"revised","reservation_date":"2023-07-04 13:21:00","uploaded":"2023-04-07 18:04:18","revisionof":"S2-2209191","revisedto":"S2-2305732","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"TEI18"}],"crnumber":3601.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305109.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305110","title":"Support for 5QI Priority Level in QoS constraints","source":"Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA","contact":"Robert Streijl","contact-id":92467,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 6.1.3.6, added discussion of how 5QI Priority Level will be handled across VPLMN\/HPLMN, and moved the pointer to the specification of QoS constraints from TS 23.502 to TS 23.501. In clause 6.4, added text to clarify that the P","secretary_remarks":"Revision of S2-2209067 from 2022! r03 agreed. Revised to S2-2305733.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"revised","reservation_date":"2023-07-04 13:23:04","uploaded":"2023-04-07 18:04:18","revisionof":"S2-2209067","revisedto":"S2-2305733","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"TEI18"}],"crnumber":757.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305110.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.3.6, 6.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305264","title":"Discussion on network 3GPP and non-3GPP interworking indication for VoWiFi","source":"China Telecommunications,Xiaomi","contact":"Ting Zhang","contact-id":81763,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"noted","reservation_date":"2023-07-04 18:20:39","uploaded":"2023-04-07 18:33:21","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305264.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305391","title":"[DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area","source":"OPPO","contact":"Peng Tan","contact-id":101478,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC:","secretary_remarks":"Response to S2-2303916. Merged into S2-2305059 (Postponed)","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"postponed","reservation_date":"2023-07-04 23:50:39","uploaded":"2023-04-07 23:53:07","revisionof":"","revisedto":"","release":"","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_156E_Electronic_2023-04\/Docs\/S2-2305391.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305394","title":"LS from TSG SA: Reply LS on 5G capabilities exposure for factories of the future - identified gaps","source":"TSG SA","contact":"Patrice H\u00e9d\u00e9","contact-id":25646,"tdoctype":"LS in","for":"Information","abstract":"TSG SA would like to thank 5G-ACIA for their LS (SP-230003\/SP-221005). TSG SA has tasked its WGs to analyze the gaps and limitations identified by 5G-ACIA, and would like to provide the results of our findings below: 1. For gaps and limitations identified by 5G-ACIA related to NEF exposure capability, please refer to SA WG2 analysis: Among the items in SA WG2 scope, several of them (e.g. G.1, G.4, L2, L.3, L.4, L.5) have already been discussed in SA WG2 since Rel-16 (Vertical_LAN, IIoT, GMEC). SA WG2 is currently busy completing Rel-18 and updating SA WG2 specifications with the Rel-18 features. The SA WG2 TSs that are primarily related to the 5G-ACIA items are TS 23.501, TS 23.502, and TS 23.503. SA WG2 would like to inform 5G-ACIA that SA WG2 has discussed the aspects highlighted by 5G-ACIA that are not supported by 5GS currently in Rel-18 but there are different views on such aspects being gaps, resulting in no consensus. 2. For gaps and limitations identified by 5G-ACIA related to security, please refer to SA WG3 analysis: SA WG3 has discussed the LS from 5G-ACIA with a focus on gaps G.1, G.3 and limitation L.6, which have been identified as being potentially relevant for SA WG3. The following conclusions have been agreed: G.1 Provisioning of subscriptions SA WG3 did not standardize or does not have plans to standardize a mechanism to provision information related to the identity of a subscription (i.e., UE Ids or authentication keys) into the 5G core. For the sake of clarity SA WG3 also points out that SA WG3 did not define and does not have plans to define a protocol for provisioning of subscription data to a UE. G.3 Provision of security event\/logging information SA WG3 interprets the terms event and logging information in such way, that it refers to events and logging information originating from the 5G core, but not to events and logging information originating from the UE. According to the understanding of SA WG3 security events and logging information include, for instance, information relating to successful and unsuccessful (primary, secondary, slice specific) authentications of UE and information relating to applied protection of user plane traffic. SA WG3 did not and does not have plans to standardize exposure of these events or logging information. Based on requirements from SA WG1 or proposals from member companies, SA WG3 can work on adding these events following the SA WG3 working procedures. L.6 Fine-grained authorization SA WG3 points out that the authorization of Application Functions (AF) at the exposure point can be executed using the OAuth 2.0 procedures. The currently defined scopes allow authorization on the level of services. Vendors might define and make available additional scopes in their specific products. In addition to authorization based on OAuth 2.0, the exposure points might limit the scope of API calls in a fine granular way based on implementation specific policy checks as indicated in Clause 12.2 of TS 33.501. 3. For gaps and limitations identified by 5G-ACIA related to service exposure enabler, please refer to SA WG6 analysis: SA WG6 has discussed the LS from 5G-ACIA, and has identified gaps and limitations potentially relevant for SA WG6. The following aspects are provided for further consideration by 5G-ACIA: G.4 Traffic profile (QoS) for network connections: SA WG6 has specified Network Resource Management service in 3GPP TS 23.434, Edge enabler service in 3GPP TS 23.558 and 5G Messaging service in 3GPP TS 23.554 which specifies procedures and APIs which can be used for this purpose. L.2 Dynamic solution for application centric-QoS: SA WG6 has specified Network Resource Management service in 3GPP TS 23.434 which specifies procedures and APIs which can be used for this purpose. L.4 Monitoring of device connectivity, including the connection s QoS: SA WG6 has specified Network Resource Management service in 3GPP TS 23.434 which specifies procedures and APIs which can be used for this pu","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10580,"status":"noted","reservation_date":"2023-11-04 11:33:24","uploaded":"2023-04-11 11:33:57","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"5GACIA","Cc":"SA WG1, SA WG2, SA WG3, SA WG5, SA WG6, TSG CT","lsoriginalls":"SP-230384","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305394.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305395","title":"LS from TSG SA: Alignment of activities on UE data collection reporting and event exposure","source":"TSG SA","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS in","for":"Information","abstract":"TSG SA discussed the work on UE data collection happening in SA WG2, SA WG4 and SA WG6 in order to avoid fragmentation on the solutions. TSG SA acknowledges that the system architecture, reference points, and high-level procedures regarding generic UE data collection, reporting and event exposure that are currently described in the stage 2 specification TS 26.531 and stage 3 specification TS 26.532 define the detailed procedures and associated APIs for the generic UE data collection and reporting functionality (this is referred to as 'EVEX framework' below for brevity). SA WG6 expressed in LS S6-231059 to SA WG4 the following additional requirements needed by the Application Service Provider (ASP) as described in the architecture defined in 3GPP TS 26.531: 1. The ASP shall be able to retrieve\/pull collected data on-demand (i.e. without need for setting up session) from the UE Application through a request\/response mechanism. 2. The UE Application shall be able to send\/push collected data on-demand (i.e. without need for setting up session) to ASP through a request\/response mechanism. 3. The ASP shall be able retrieve collected data from the UE Application through a subscribe\/notify mechanism. 4. The ASP shall be able to configure the subscription for the UE Application including the specific information to be reported, the triggering criteria and reporting configuration. In the context of rel.18 KI#2 of FS_AIMLsys, SA WG2 discussed (as one of the options out of multiple solutions) about the possibility to enhance the framework for data collection from the UE Application to also expose 5GC information to the UE. Note that SA WG2 concluded that no normative work will be progressed in rel.18 for Key Issue #2 of FS_AIMLsys. Considering the above, we ask for feedback from SA WG4, preferably before SA#100 makes final decision on how to best create a common framework for data collection and sharing information between UE and 5GC for all purposes needed across SA WGs: - Whether SA WG4 is willing to maintain and enhance the technical specifications that comprise the 'EVEX framework' and fulfil any changes necessary based on requirements from other WGs in rel. 18 and future releases that fall within the existing scope of the framework? - Whether SA WG4 is willing to extend the scope the 'EVEX framework', e.g. to fulfil any changes necessary based on requirements from other WGs in future releases? If SA WG4 is not willing to do changes in the 'EVEX framework' for UE data collection TSG SA will discuss further whether the architecture and related procedures are transferred and maintained by another WG (SA WG2 or SA WG6).This existing or new specification can focus on UE data collection in the future. None of the above considerations will disrupt existing Rel.18 activities e.g. 'Application Data Analytics Enablement Services (ADAES)' and 'Application service management in eSEAL2' work items of SA WG6, including the requirements and associated solutions. Also, Rel.18 conclusions of FS_AIMLsys would not be modified.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10590,"status":"noted","reservation_date":"2023-11-04 11:33:24","uploaded":"2023-04-11 11:33:57","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG2, SA WG6","lsoriginalls":"SP-230394","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305395.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305396","title":"LS from GSMA NG\/UPG: LS from NG to SA WG4 on IMS Data Channel (multiple application data channels support in a single SDP m=line)","source":"GSMA NG\/UPG","contact":"Xueqian Bai","contact-id":92286,"tdoctype":"LS in","for":"Information","abstract":"3GPP Rel-16 TS 26.114 has introduced data channel into IMS, and GSMA PRD NG.134 has discussed IMS data channel usage with stream ID numbering of multiple IMS data channels. There is thus a requirement to support the use of a single SDP m=line by multiple applications. GSMA NG\/UPG would like to understand the feasibility of such an approach using the current WebRTC1.0 specification. If this approach is feasible using the current WebRTC1.0 specification, GSMA would like to know how it can be accomplished. If this approach is not feasible using the current WebRTC1.0 specification, GSMA would like to request SA WG4 to consider additional specification to provide such support.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"noted","reservation_date":"2023-04-13 05:32:13","uploaded":"2023-04-13 05:32:49","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG2","lsoriginalls":"UPG06_110r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305396.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305730","title":"LS on Wi-Fi Alliance communication on methods for consistent QoS across 5G and Wi-Fi networks","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"To: WI-FI Alliance","secretary_remarks":"Revision of S2-2304475r05. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"approved","reservation_date":"2023-04-24 18:14:20","uploaded":"2023-04-24 18:51:12","revisionof":"S2-2304475","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2303915","lsto":"WI-FI Alliance","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305730.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305731","title":"Support for 5QI Priority Level in QoS constraints","source":"Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA","contact":"Robert Streijl","contact-id":92467,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In 5.7.1.11 added 5QI Priority Level to the QoS constraints, and added a note that QoS constraints currently applies to the non-GBR default QoS Flow.","secretary_remarks":"Revision of S2-2305092r01. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"agreed","reservation_date":"2023-04-24 18:14:20","uploaded":"2023-04-24 18:51:15","revisionof":"S2-2305105","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":3748.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-230490","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305731.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.7.1.11","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305732","title":"Support for 5QI Priority Level in QoS constraints","source":"Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA","contact":"Robert Streijl","contact-id":92467,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 4.3.2.2.2 changed the specification of QoS constraints to clause 5.7.1.11 of TS 23.501. In clause 5.2.5.4.2 and 5.2.8.2.2 changed the pointer to the QoS constraints specification from clause 4.3.2.2.2 to clause 5.7.1.11 of TS 23.501.","secretary_remarks":"Revision of S2-2305098r01. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"agreed","reservation_date":"2023-04-24 18:14:21","uploaded":"2023-04-24 18:51:15","revisionof":"S2-2305109","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":3601.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-230490","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305732.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.3.2.2.2, 5.2.5.4.2, 5.2.8.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305733","title":"Support for 5QI Priority Level in QoS constraints","source":"Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA","contact":"Robert Streijl","contact-id":92467,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 6.1.3.6, added discussion of how 5QI Priority Level will be handled across VPLMN\/HPLMN, and moved the pointer to the specification of QoS constraints from TS 23.502 to TS 23.501. In clause 6.4, added text to clarify that the PCF may provide a 5QI Priority Level value to override the standardized Default Priority Level value associated with either the Authorized default 5QI\/ARP or the Subsequent Authorized default 5QI\/ARP.","secretary_remarks":"Revision of S2-2305110r03. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"agreed","reservation_date":"2023-04-24 18:14:22","uploaded":"2023-04-24 18:51:15","revisionof":"S2-2305110","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":757.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-230490","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305733.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.3.6, 6.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306255","title":"[DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"LS out","for":"Approval","abstract":"WITHDRAWN: To: CT WG1. CC:","secretary_remarks":"Revision of S2-2305059r05. CC#4: WITHDRAWN","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"withdrawn","reservation_date":"2023-04-24 18:18:08","uploaded":null,"revisionof":"S2-2305059","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]