[{"name":"S2-2411285","title":"LS from GSMA OPG: LS on GSMA OPG PRDs publication and document restructuring","source":"GSMA OPG","contact":"Sandra Ondrusova","contact-id":77474,"tdoctype":"LS in","for":"Information","abstract":"GSMA OPG would like to notify 3GPP and ETSI of the recent release of several GSMA PRDs:. - OPG.02 Operator Platform: Requirements and Architecture version 7.0. - OPG.04 East-Westbound Interface APIs version 5.0. - OPG.09 NBI APIs Realisation in the SBI version 2.0. GSMA OPG and its subgroups started working on the new releases of the documents mentioned above. Several topics are being discussed: - Document restructuring: The idea is to split the requirements from the GSMA PRD OPG.02 into several documents. OPG.02 would be dedicated to the platform requirements only, while new documents would focus on edge related requirements and other services. - Aggregator routing requirements - OP roles and functional definitions - Operate APIs from TM Forum. Actions: GSMA OPG kindly ask 3GPP and ETSI to take the above into consideration.","secretary_remarks":"Revision of postponed S2-2409620 from SA WG2#165. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2024-10-25 13:46:53","uploaded":"2024-10-25 13:52:50","revisionof":"S2-2409620","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":"TSG SA","lsoriginalls":"OPG_197_Doc_03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411285.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411299","title":"LS from RAN WG2: Reply LS on the maximum number of devices supported in SLPP","source":"RAN WG2","contact":"Xiang Pan","contact-id":91367,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks CT WG1 for the Reply LS on the maximum number of devices supported in SLPP. RAN WG2 will align with CT WG1 by clarifying that the maximum number of other UEs (i.e., UEs 2 to n) for sidelink positioning is also 63 in the stage 2 specification (see attachment).","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2024-10-25 13:46:54","uploaded":"2024-10-25 13:52:49","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4, SA WG2","lsoriginalls":"R2-2409252","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411299.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411308","title":"LS from SA WG5: LS on 3GPP_Correlation information for API volume-based charging","source":"SA WG5","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks GSMA OPAG for their LS response to Correlation information for API volume-based charging. SA WG5 has discussed the received feedback and would like to provide GSMA OPAG with the current status of their discussion. Regarding the Correlation information for API volume based charging related requirement: Based on GSMA OPAG is considering the SCEF\/NEF related architecture and services specified in SA WG2 TS 23.502 ' Procedures for the 5G System (5GS); Stage 2', SA WG5 would like to bring the following clarifications: - SA WG5 NEF charging available under 3GPP TS 32.254: 'Telecommunication management; Charging management; Exposure function Northbound Application Program Interfaces (APIs) charging' is suitable for charging API invocation\/Notification to the NEF. This NEF charging is specified in a generic way to cover any exposed services therefore will remain applicable to future exposed services. - 3GPP TS 32.254 also specifies SCEF charging for T8 transactions. - Currently, NEF charging is specified in SBI architecture using converged charging system, and SCEF charging is specified in Diameter based architecture. - SA WG5 would like to inform GSMA OPAG that further charging evolution will be considered under SBI framework only, there is no plan to evolve in Diameter interface application for upcoming releases. - Regarding the additional information to be included in the charging requests for the purpose of correlation between API invocations to the NEF and corresponding service(s) delivered within the Operator's Network (e.g. SMF PDU session): this correlation information is currently not available for transfer to the charging system.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2024-10-25 13:46:54","uploaded":"2024-10-25 14:50:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPG Operator Platform API Group","Cc":"GSMA OPG, TSG SA, SA WG2","lsoriginalls":"S5-245977","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411308.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411312","title":"LS from GSMA 5G VoWiFi TF: LS to 3GPP SA1 on support of multiple access technologies based on the IMS service type","source":"GSMA 5G VoWiFi TF","contact":"Yan Li","contact-id":98414,"tdoctype":"LS in","for":"Information","abstract":"GSMA 5G VoWiFi Task Force is currently working on new scenarios and features of VoWiFi aspect to improve the QoE of Wi-Fi calling service. One of the use cases to be discussed is the support of multiple access technologies based on the IMS service type. {. . .} GSMA 5G VoWiFi Task Force would like to ask SA WG1 the questions below. Question 1: For the 1st requirement above, is the traffic type mentioned in the requirement sufficient enough to distinguish different types of IMS service (e.g. audio, video, different IMS DC service, etc.)? Question 2: For the 2nd requirement above, can the granularity of service type mentioned in the requirement be applied to different types of IMS service or furthermore different types of IMS DC services?","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2024-10-25 13:46:54","uploaded":"2024-10-31 07:27:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG2, CT WG1","lsoriginalls":"5GVoWiFi#07a_006r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411312.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412130","title":"LS from IETF DetNet: LS on draft-ietf-raw-technologies, Reliable and Available Wireless Technologies","source":"IETF DetNet","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Action","abstract":"The IETF Deterministic Networking Working Group (DetNet) would like to inform you of our draft on 'Reliable and Available Wireless Technologies' [1], which includes a brief description on 5G in section 6. The draft has been developed in the former Reliable Available Wireless (RAW) WG [2], which has been merged into the Deterministic Networking (DetNet) WG [3]. The charter of the DetNet WG includes defining how DetNet solutions operate over networks that include wired and wireless network technologies. 5G is one of the wireless technologies to provide reliable wireless for deterministic networking. Therefore, section 6 of the 'Reliable and Available Wireless Technologies' draft is dedicated to 5G. Section 6 includes a brief overview of 5G, including system architecture, radio, scheduling, QoS, and Time-Sensitive Communication features. The draft is in IETF Last Call, which is the final review stage at the IETF. Please let us know if you have comments on the draft, e.g., directly on the email list of the DetNet WG [4]. We look forward to continued collaboration between our organizations.","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":"2024-08-11 13:37:50","uploaded":"2024-11-08 14:16:58","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, SA WG2, SA WG3","Cc":"","lsoriginalls":"liaison-denet-draft-ietf-raw-technologies","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412130.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412131","title":"LS from GSMA URSPWI: Clarification request on usage and control of UE Local Configuration","source":"GSMA URSPWI","contact":"Michele Zarri","contact-id":96831,"tdoctype":"LS in","for":"Information","abstract":"GSMA URSPWI is in the process of profiling URSP rules in NG.141 and would like to request a clarification about the control and usage of the UE local configuration. The questions asked are based on the following understanding of clause 4.2.2.2 of TS 24.526 Release 19. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2024-08-11 13:38:30","uploaded":"2024-11-08 14:16:58","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"URSPWI 15_003r3","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412131.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412364","title":"LS from SA WG3: Reply-LS on Internal 5G Core information expose to trusted AF","source":"SA WG3","contact":"Zander Lei","contact-id":46558,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank SA WG6 for the LS on Clarification related to Internal 5G Core information expose to trusted AF. SA WG3 has discussed the questions raised by SA WG6 and the answers are provided as follows: - Q1: Whether a trusted AF of an 3GPP operator is considered within the operator's domain; If yes, whether it is possible to expose Internal 5G Core information such as DNN, S-NSSAI, etc. to a trusted AF (e.g., a NSCE server). [SA WG3]: No, a 'trusted AF' is not equivalent to an 'AF within the operator's domain'. The term 'trusted AF' is neither defined nor used in SA WG3 specifications. From the security\/SA WG3 perspective, it is not well-defined and not recommended to be used in 3GPP specifications without a proper definition. As far as information exposure to an AF is of concerns, it is allowed to expose 'Internal 5G Core information' to an AF within the operator's domain. Besides, it is also possible to expose internal 5G Core information to an AF outside the operator's domain after proper security protection or privacy protection. For example, an 'S-NSSAI' can be mapped to an AF-Service-Identifier before exposing to an AF outside the 3GPP operator domain (i.e., the 'S-NSSAI' shall not be exposed directly in this case to be in line with the security requirements specified in the TS 33.501). - Q2: Whether the NSI (i.e., Network Slice Instance) and\/or NSI ID can be exposed to the trusted AF. [SA WG3]: An NSI or an NSI ID is an internal slice instance\/ID used in 5G Core and it has not been considered with respect to exposure to an AF in SA WG3 specifications. The NSI\/NSI ID can be exposed directly if the AF is within the 3GPP operator domain but the case of the NSI\/NSI ID being exposed to an AF outside the 3GPP operator domain has not been considered in security specifications.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2024-11-17 14:17:36","uploaded":"2024-11-17 14:18:13","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG5, CT WG3, SA WG2","lsoriginalls":"S3-2445141","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412364.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500029","title":"LS from 5G-ACIA: 5G-ACIA LS on Enhancements for 5G System Operating as Logical (TSN) Bridge(s) in Integrated IEEE\/3GPP Networks","source":"5G-ACIA","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"5G-ACIA is glad to inform TSG SA and TSG SA working groups SA WG1 and SA WG2 about conducted work on the 5G system operating as logical (TSN) bridge(s) in integrated IEEE\/3GPP networks. The provided description identifies and analyses the capabilities of 3GPP 5G specifications related to configuration of the 5G system, reaction on relevant 5G-VN\/TSN related dynamic events, and to the integration with IEEE\/IEC 60802 industrial communication networks. The analysis is based on relevant service flows used currently in deployed and operational industrial communication networks. Identified missing capabilities have been evaluated. Multiple gaps have been identified where improvements or enhancements to 3GPP specifications are needed in order to achieve a flexible integration of the 5GS bridge model with IEEE 802.1 and TSN based industrial communication networks. {. . .} Actions: Please consider the provided findings for future 3GPP standardization work and work planning related to 5G system operating as logical (TSN) bridge(s) in integrated IEEE\/3GPP networks, especially in Release 20, so that 3GPP Individual Members are supported in providing corresponding contributions for improvements and enhancements to 3GPP specifications in order to achieve a flexible integration of the 5GS bridge model with IEEE 802.1 and TSN based industrial communication networks.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2024-12-06 13:48:12","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, TSG SA","Cc":"","lsoriginalls":"5G-ACIA-LS-2024-008","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500029.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500030","title":"LS from ITU-D SG2: Liaison statement from ITU-D Study Group 2 Question 4\/2 to IEEE, ISO, IEC, ETSI, 3GPP, GSMA, IETF, Wi-Fi Alliance, International Laboratory Accreditation Cooperation, and International Accreditation Forum on draft final report of ITU-D","source":"ITU-D SG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"The objective of ITU-D Study Group 2 for Question 4\/2 is to assist developing countries for implementing conformance and interoperability (C&I) programmes and combating counterfeit ICT equipment and theft of mobile devices. Details of Question 4\/2 is available at this link. The draft Final Report of Question 4\/2 for the ITU-D study period 2022-2025 is available as Document 2\/280 and attached to this liaison statement. ITU-D Question 4\/2 invites your organization for any comment and revision proposal on the draft Final Report. Please feel free to provide any other suggestions and documents for our study. The next meeting of ITU-D Study Group 2 including Question 4\/2 will be held on 5-9 May 2025 in Geneva as indicated in Document 2\/ADM\/1 (Rev. 4). We look forward to continuing collaboration with your organization.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2024-12-06 13:48:12","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IEEE, ISO, IEC, ETSI, 3GPP, GSMA, IETF, Wi-Fi Alliance, International Laboratory Accreditation Cooperation, International Accreditation Forum","Cc":"","lsoriginalls":"D22-SG02-C-0342","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500030.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500033","title":"LS from CT WG1: Reply to Reply LS on CENs requirements for eCall over IMS","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA for the liaison in SP-241421 and SA WG2 for the liaison in S2-2411246 concerning 3GPP alignment with 9 different cases of requirements from CEN for eCall over IMS. Based on the SA WG2 LS, CT WG1 is adding additional support for a PSAP callback to an eCall over IMS and for a test eCall. Attached are the related agreed CT WG1 CRs. With the attached CRs, CT WG1 believes that we have sufficiently covered CEN cases 1 to 5. Action: CT WG1 asks SA and SA WG2 to take the above answers into account.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2024-12-06 13:48:12","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG CT, SA WG1, SA WG3","lsoriginalls":"C1-246950","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500033.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500034","title":"LS from CT WG1: Reply LS on Clarification request on usage and control of UE Local Configuration","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks GSMA for their LS (C1-246144) on Clarification request on usage and control of UE Local Configuration. CT WG1 has discussed the questions raised by GSMA and provides the following response. {. .}. Action: CT WG1 asks SA WG2 to take the above information into account, confirm the responses and provide any further updates to GSMA.","secretary_remarks":"Responses drafted in S2-2500219, S2-2500519, S2-2500778, S2-2501027. FInal response in S2-2501276","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"replied to","reservation_date":"2024-12-06 13:48:12","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA URSPWI","Cc":"GSMA TSG","lsoriginalls":"C1-247121","lsreply":"S2-2501276","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500034.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500057","title":"LS from SA WG1: Reply LS on CEN requirements for eCall over IMS","source":"SA WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 thanks SA for their LS, based on which SA WG1 has agreed the attached alignment CR. Action: Please take the above into consideration.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2024-12-29 10:58:22","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, CT WG1","Cc":"TSG CT, SA WG3","lsoriginalls":"S1-244755","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500057.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500059","title":"LS from SA WG1: Reply LS on UAV regulation","source":"SA WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks RAN WG3 for the LS on providing flight information from RAN to CN for R18 UAV UEs and pre-R18 non-UAV devices. RAN WG3 asked the following question to SA WG2: RAN WG3 would like to ask for the guidance from SA WG2 whether it is a requirement for NG-RAN node to provide flight information to CN for the following cases: 1. R18 UAV UEs; 2. Legacy devices (non-UAV device); SA WG1 would like to reply that there are no explicit service requirements for this function for these devices in TS 22.125.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2024-12-29 10:58:22","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"TSG RAN, TSG SA","lsoriginalls":"S1-244759","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500059.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500060","title":"LS from SA WG1: Reply LS on support of multiple access technologies based on the IMS service type","source":"SA WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"GSMA has sent a LS (S1-244052) asking for clarification on the SA WG1 requirements regarding the support of multiple access technologies based on the IMS service type. SA WG1 would like to ask SA WG2 to provide feedback to SA who will coordinate response to GSMA on whether the existing mechanisms in Stage 2 could fulfill the use case from GSMA. Action: SA WG1 kindly asks SA WG2 to provide feedback to SA who will coordinate response to GSMA on whether the existing mechanisms in Stage 2 could fulfill the use case from GSMA.","secretary_remarks":"Responses drafted in S2-2500786, S2-2500943. FInal response in S2-2501277","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"replied to","reservation_date":"2024-12-29 10:58:22","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"S1-244916","lsreply":"S2-2501277","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500060.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500067","title":"LS from SA WG5: LS on Usage of Charging Characteristics and CHF Group ID","source":"SA WG5","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"The Charging Characteristics can today be either locally configured or received from the UDM and used in SMF and AMF to indicate the default CHF address (e.g., primary and secondary CHF Address, Instance ID, Set ID), CHF selection method (e.g., local configuration, NRF), charging method (i.e., 'online', 'offline', or 'offline only'), charging service (i.e., converged or offline only charging), metering method (e.g., duration, volume, or duration and volume, none), triggers (e.g., tariff time, time limit, volume limit, number of charging condition changes) etc., see TS 32.255 annex A, and TS 32.256 annex A. It is proposed to extend the indication of CHF addresses to also allow it to indicate a CHF Group ID, which would then be used in the NRF to discover the CHFs. {. .}. Action: SA WG5 asks SA WG2 and CT WG4 to provide guidance regarding the two questions above.","secretary_remarks":"Postponed in e-mail session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"postponed","reservation_date":"2024-12-29 10:58:22","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"S2-2501375","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S5-246956","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500067.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500073","title":"LS from SA WG6: Reply LS on clarifications on consent management","source":"SA WG6","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"With reference to the GSMA LS (S6-242012) titled 'LS on clarifications on consent management', question 2, requested clarification on relationship between CAPIF's RNAA and UDM's user consent information and plan\/roadmap for unified approach. SA WG6 provided initial response in S6-242504 and opined that it is in the realm of SA WG3 to provide the response. Further, SA WG3 provided response in S6-243008 clarifying that user consent information in UDM\/UDR and resource owner authorization in CCF are independent from each other. {. . .}","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2024-12-29 10:58:23","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, SA WG3, CT WG4","lsoriginalls":"S6-245716","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500073.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500075","title":"LS from TSG SA: Reply LS on clarifications on consent management.","source":"TSG SA","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"TSG SA thanks GSMA OPG for their LS on clarifications on consent management. TSG SA would like to clarify that SA WG6 has specified the support of RNAA (Resource owner-aware Northbound API Access), as part of CAPIF in Rel.18 in TS 23.222, and the detailed security specification for CAPIF RNAA has been specified by SA WG3 in TS 33.122 (CAPIF). SA SA WG WG6 completed a Rel.19 study, which includes in its scope further enhancements to CAPIF for resource owner authorisation management (RNAA). GSMA OPG is invited to provide any feedback to the conclusions of the studies captured in TR 23.700-22 (SA WG6) and TR 33.700-22 (SA WG3). {. . .}","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2024-12-29 10:58:23","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPG","Cc":"SA WG2, SA WG3, SA WG6, CT WG4","lsoriginalls":"SP-241934","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500075.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500076","title":"LS from ETSI TC CYBER: Update on ETSI TC Cyber middlebox work","source":"ETSI TC CYBER","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"1. Overall description In a previous Liaison Statement CYBER(23)35d008r1, TC Cyber informed GSMA about the existing middlebox specification (TLMSP, TS 103 523-2 [1]) and the then ongoing work on a TR to provide guidance on TLMSP usage in different use-cases. TC Cyber wished to point in particular to some use-cases related to potential use of TLMSP on the 5G roaming interfaces such as that described in the Liaison Statement S3-234467 from GSMA to SA WG3. ETSI is pleased to inform GSMA about the completion of the latter work and hereby attach the completed TR [2] for reference. 2. Brief summary of the TR The TR [2] contains the following main components 1. An overview of the TLMSP protocol and its features. 2. Description of a set of use-cases for TLMSP and a guidance how the TLMSP features can be configured to support those use-cases. 3. Description of how to make use of TLMSP in conjunction with some specific application layer protocols. 4. Mapping of TLMSP to zero-trust (ZT) architectures. 5. TLMSP implementation guidance. Item (2) can be found in clause 6 of [2] and comprises the following 5G\/telecom-oriented use-cases which might be of particular relevance for GSMA: application of TLMSP to the N32 interface (both with and without roaming hubs), application to service based architecture (SBA) with service communication proxy (SCP), and Lawful Intercept.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2024-12-29 10:58:23","uploaded":"2025-01-13 07:15:45","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA FASG, GSMA 5GMRR, GSMA 5GPKIWP","Cc":"SA WG2, SA WG3","lsoriginalls":"CYBER(24)39d006r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500076.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500077","title":"LS from GSMA TSGNS: OSAppID usage by AppToken use case","source":"GSMA TSGNS","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"GSMA TSGNS is a working group of GSMA in charge of maintaining PRD TS.62 'UE requirements related to Network Slicing using URSP'. PRD TS.62 provides requirements to the mobile industry on the design, development, and implementation of network slicing using URSP in 5G UEs. In the context of the wider activity on network slicing, GSMA recently approved the specification of the App Token. App Token was introduced in PRD TS.43 'Service Entitlement' which defines the MNOs Entitlement Server procedures. An Entitlement Server builds the interface between an MNO and a devices OS, and is used globally for e.g., eSIM activation, VoLTE\/VoWiFi configuration, DataPlan Info, and more configuration data. A device is expected to interact with its home MNO's Entitlement Server, also when roaming or in wifi, using HTTP REST. The App Token is a piece of information that the UE OS can obtain from specific applications and allows to uniquely identify an application across the complete ecosystem (application developer, MNO, subscriber UE) whilst protecting the end user privacy. This means that the UE OS does not need to use the information it has about the identity of an application when comparing against the OSAppID field from the URSP rules received from the MNO, but to use an anonymous identifier received from the MNO through TS.43 interface for that comparison. GSMA TSGNS is currently working to define in TS.62 how UE OS should behave when managing App Tokens with applications. The proposed end-to-end flow is as follows (boxes in green reflects standard procedures already defined by 3GPP or by GSMA in TS.43, red box is the CR to TS.62 being discussed in GSMA TSGNS): {. . .}","secretary_remarks":"Response drafted in S2-2500962. Postponed in e-mail session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"postponed","reservation_date":"2024-12-29 10:58:23","uploaded":"2025-01-13 07:15:45","revisionof":"","revisedto":"S2-2501377","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"","lsoriginalls":"TSGNS44_003v6","lsreply":"S2-2501809, S2-2502143","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500077.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500219","title":"[DRAFT] Reply LS on Clarification request on usage and control of UE Local Configuration","source":"Nokia","contact":"Srinivas Garikipati","contact-id":100437,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Clarification request on usage and control of UE Local Configuration","secretary_remarks":"Response to S2-2500034. r07 agreed. Revised in e-mail session to S2-2501276, merging S2-2500519, S2-2500778 and S2-2501027","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"revised","reservation_date":"2025-01-10 12:57:50","uploaded":"2025-01-13 15:44:25","revisionof":"","revisedto":"S2-2501276","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, GSMA URSPWI","Cc":"GSMA TSG","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500219.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500519","title":"[DRAFT] Reply LS on Clarification request on usage and control of UE Local Configuration","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Clarification request on usage and control of UE Local Configuration.","secretary_remarks":"Response to S2-2500034. Merged into S2-2501276","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"merged","reservation_date":"2025-01-14 04:06:39","uploaded":"2025-01-14 16:55:20","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, GSMA URSPWI","Cc":"GSMA TSG","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500519.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500778","title":"[DRAFT] Reply LS on Clarification request on usage and control of UE Local Configuration","source":"Samsung","contact":"Jicheol Lee","contact-id":87580,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA URSPWI, CT WG1. CC: GSMA TSG. Attachments: None.","secretary_remarks":"Response to S2-2500034. Merged into S2-2501276","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"merged","reservation_date":"2025-01-14 10:34:00","uploaded":"2025-01-14 10:44:08","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA URSPWI, CT WG1","Cc":"GSMA TSG","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500778.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500786","title":"[DRAFT] Reply LS on support of multiple access technologies based on the IMS service type","source":"China Telecom","contact":"Yan Li","contact-id":103694,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG1, SA. CC: CT WG1. Attachments: S1-244052.","secretary_remarks":"Response to S2-2500060. Merged into S2-2501277","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"merged","reservation_date":"2025-01-14 10:46:22","uploaded":"2025-01-14 10:50:57","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500786.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500943","title":"[DRAFT] Reply LS on support of multiple access technologies based on the IMS service type","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG1. CC: CT WG1, SA. Attachments:.","secretary_remarks":"Response to S2-2500060. r04 agreed. Revised in e-mail session to S2-2501277, merging S2-2500786","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"revised","reservation_date":"2025-01-14 15:00:03","uploaded":"2025-01-14 15:48:05","revisionof":"","revisedto":"S2-2501277","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"CT WG1, SA WG","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500943.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500962","title":"[DRAFT] Reply LS for OSAppID usage by AppToken use case","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS for OSAppID usage by AppToken use case","secretary_remarks":"Response to S2-2500077. Postponed in e-mail session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"postponed","reservation_date":"2025-01-14 15:29:29","uploaded":"2025-01-14 15:41:26","revisionof":"","revisedto":"S2-2501523","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA TSGNS","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500962.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501027","title":"[DRAFT] Reply LS on Clarification request on usage and control of UE Local Configuration","source":"Google","contact":"Pavan Nuggehalli","contact-id":81647,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA URSPWI. CC: CT WG1, GSMA TSG. Attachments: -.","secretary_remarks":"Response to S2-2500034. Merged into S2-2501276","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"merged","reservation_date":"2025-01-14 17:59:48","uploaded":"2025-01-14 18:41:55","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA URSPWI","Cc":"CT WG1, GSMA TSG","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501027.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501276","title":"Reply LS on Clarification request on usage and control of UE Local Configuration","source":"SA WG2","contact":"Srinivas Garikipati","contact-id":100437,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, GSMA URSPWI. CC: GSMA TSG","secretary_remarks":"Revision of S2-2500219r07, merging S2-2500519, S2-2500778 and S2-2501027. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"approved","reservation_date":"2025-01-25 09:55:52","uploaded":"2025-01-27 09:03:58","revisionof":"S2-2500219","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2500034","lsto":"CT WG1, GSMA URSPWI","Cc":"GSMA TSG","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501276.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501277","title":"Reply LS on support of multiple access technologies based on the IMS service type","source":"SA WG2","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG SA, SA WG1. CC: CT WG1","secretary_remarks":"Revision of S2-2500943r04, merging S2-2500786. Approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"approved","reservation_date":"2025-01-25 09:55:53","uploaded":"2025-01-27 09:03:58","revisionof":"S2-2500943","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2500060","lsto":"TSG SA, SA WG1","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501277.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]