[{"name":"S2-2600010","title":"LS from CT WG4: LS on Clarification on 5G VN group","source":"CT WG4","contact":"RONG WANG","contact-id":87346,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 has studied some optimization solutions for UPF data collection in FS_PAIDC_UPF. For 5G VN group, CT WG4 would like to ask SA WG2 the following questions: Q1: Can a UE, that is not member (temporary\/permanently) of any 5G VN group, have an SM subsc","secretary_remarks":"Revision of (postponed) S2-2509925. Response drafted in S2-2600320. Noted in parallel session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"S2-2509925","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-253576","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600010.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600014","title":"LS from BBF: Recently published Broadband Forum Work Items (November 2025)","source":"BBF","contact":"Lincoln Lavoie","contact-id":39231,"tdoctype":"LS in","for":"Information","abstract":"The Broadband Forum is pleased the share our latest published work, which may be accessed directly through our online technical library (https:\/\/www.broadband-forum.org\/technical-library\/). {. . .} The Broadband Forum encourages our partner SDO's to review these materials, to ensure work their progress references these latest materials and avoids duplication of efforts. We look forward to the continued collaboration with our peers as we all continue to progress this important work. Sincerely, Lincoln Lavoie, Broadband Forum Technical Committee Chair","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SGs, IEEE 802, IETF, ETSI F5G, CableLabs, TM Forum,SA WG1, SA WG2, WBA, CCSA TC6 WG2","Cc":"","lsoriginalls":"LIAISE-725_rev-03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600014.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600015","title":"LS from ITU-T SG11: LS on consent of draft new Recommendation ITU-T Q.5016 (ex Q.FMSC-SA) 'Signalling architecture of fixed, mobile and satellite convergence for IMT-2020 networks and beyond'","source":"ITU-T SG11","contact":"Tejpal Singh","contact-id":70082,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs ITU-T SG13 and SA WG2 about the consent of draft new Recommendation ITU-T Q.5016 (ex Q.FMSC-SA) 'Signalling architecture of fixed, mobile and satellite convergence for IMT-2020 networks and beyond'.","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":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG13, SA WG2","Cc":"","lsoriginalls":"SG11-LS78","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600015.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600016","title":"LS from ITU-T SG13: LS on consent of draft new Recommendation ITU-T Y.3169 (ex Y.REOUPF) 'Resource Efficiency Optimization for managing User Plane Function in IMT-2020 networks and beyond'","source":"ITU-T SG13","contact":"Yushuang Hu","contact-id":96973,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs about the consent of new Recommendation ITU-T Y.3169 (ex Y.REOUPF) 'Resource Efficiency Optimization for managing User Plane Function in IMT-2020 networks and beyond'.","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":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, SG11, SA WG1, SA WG2, SA WG5, ETSI ISG MEC","Cc":"","lsoriginalls":"SG13-LS108","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600016.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600017","title":"LS from TSG SA: Reply LS on AI\/ML UE sided data collection","source":"TSG SA","contact":"David Gutierrez Estevez","contact-id":108111,"tdoctype":"LS in","for":"Action","abstract":"TSG SA thanks TSG RAN for their reply LS on AI\/ML UE sided data collection. TSG SA would like to inform TSG RAN and SA WG2, SA WG3, SA WG5 that, after discussing the above mentioned reply LS, TSG SA has reached the following agreement: There shall not be any further work on AI\/ML UE sided data collection for 5G-A Rel-20. TSG SA kindly asks TSG RAN and SA WG2, SA WG3, SA WG5 to take the TSG SA decision into account. Action: TSG SA kindly asks TSG RAN and SA WG2, SA WG3, SA WG5 to take the TSG SA decision into account.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"noted","reservation_date":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, SA WG2, SA WG3, SA WG5","Cc":"RAN WG2","lsoriginalls":"SP-251687","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600017.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600018","title":"LS from TSG SA: LS Response on external data channel content access requirements","source":"TSG SA","contact":"Atle Monrad","contact-id":79349,"tdoctype":"LS in","for":"Information","abstract":"SA thanks GSMA NG UPG for their LS on external data channel content access requirements. Based on input from SA WGs, SA would like to provide a consolidated reply covering SA WG1, SA WG3, SA WG4 and SA WG6. SA WG2 has already provided a separate reply directly to GSMA NG UPG. {. . .}","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":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG UPG","Cc":"TSG CT, SA WG1, SA WG2, SA WG3, SA WG4, SA WG6","lsoriginalls":"SP-251693","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600018.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600019","title":"LS from TSG SA: LS on completion of Study on AI\/ML consistency alignment","source":"TSG SA","contact":"Johannes Achter","contact-id":94365,"tdoctype":"LS in","for":"Action","abstract":"TSG SA conducted the Study on AI\/ML consistency alignment in TR 22.850 and the TR was approved in SA#110. The CR to TR 21.905 attached was approved and corresponds with these findings to define a consistent terminology to be used across all groups. There is no further work planned on this activity. Action: TSG SA asks to take the above into account.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"noted","reservation_date":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG CT, SA WGs, RAN WGs, CT WGs","Cc":"","lsoriginalls":"SP-251699","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600019.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600020","title":"LS from TSG SA: Reply LS on specification of dataset and model parameters exchange","source":"TSG SA","contact":"Laeyoung Kim","contact-id":58611,"tdoctype":"LS in","for":"Action","abstract":"TSG SA thanks TSG RAN for their Reply LS on specification of dataset and model parameters exchange. TSG SA acknowledges RAN agreements from the LS, as shown below - Way forward agreements - Remove RAN WG4 checkpoints and SA checkpoints - From RAN perspective, move forward with normative phase for both Direction A (3a-1, 4-1) with non-OTA solution and Direction C. - Indicate to SA the intention to move forward and ask SA to kindly decide on the best way forward and down selection between SA WG5 and SA WG2 options. - This does NOT imply that all three options will be done in 6G {. . .} Action: TSG SA kindly asks TSG RAN, SA WG2 and SA WG5 to take the above into account.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"noted","reservation_date":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, SA WG2, SA WG5","Cc":"RAN WG2","lsoriginalls":"SP-251707","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600020.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600034","title":"LS from RAN WG3: LS on definition of 'ground truth label' in AI\/ML-based Positioning Case 3a","source":"RAN WG3","contact":"Damiano Rapone","contact-id":99909,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 has discussed Stage 2 aspects for AI\/ML-based Positioning Case 3a, and agreed to introduce the following definition for 'ground truth label' in TS 38.305: Ground truth label: Represents the true value or target value of a location-related measurement (e.g., UL-RTOA) that the AI\/ML model is supposed to infer and is used, e.g., for model training or performance monitoring. RAN WG3 would like to ask RAN WG1 to consider the above RAN WG3 captured definition and provide feedback, if any.","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":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG1","Cc":"SA WG2, RAN WG2","lsoriginalls":"R3-258796","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600034.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600037","title":"LS from TSG RAN: Reply LS on specification of dataset and model parameters exchange","source":"TSG RAN","contact":"Diana Pani","contact-id":72069,"tdoctype":"LS in","for":"Information","abstract":"TSG RAN thanks SA WG WG5 and SA WG2 for their work and SA WG5 for their LS on specification of dataset and model parameters exchange. TSG RAN understands that at least SA WG5 has confirmed that non-OTA approaches involving OAM is feasible and that SA WG2 is still studying the feasibility. Therefore, TSG RAN has made the following agreements as a way forward. Way forward agreements - Remove RAN WG4 checkpoints and SA checkpoints - From RAN perspective, move forward with normative phase for both Direction A (3a-1, 4-1) with non-OTA solution and Direction C. - Indicate to SA the intention to move forward and ask SA to kindly decide on the best way forward and down selection between SA WG5 and SA WG2 options. - This does NOT imply that all three options will be done in 6G TSG RAN kindly asks TSG SA to take the agreement on moving forward with the normative phase of Direction A (3a-1, 4-1) with non-OTA solution into account and to decide how to move forward with the work in SA WG5 and\/or SA WG2 and down-selection between SA WG5 and SA WG2 options.","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":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG5","Cc":"RAN WG2, SA WG2","lsoriginalls":"RP-253846","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600037.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600038","title":"LS from TSG RAN: Reply LS on AI\/ML UE sided data collection","source":"TSG RAN","contact":"Diana Pani","contact-id":72069,"tdoctype":"LS in","for":"Action","abstract":"TSG RAN thanks SA WG WG2 for their work and LS on AI\/ML UE sided data collection. TSG RAN made the following agreements related to AI\/ML UE sided data collection for Rel-20: Way forward agreement on UE sided data collection: 1. To avoid parallel work in 5G and 6G, no normative work in Rel-20 for UE side data collection. Focus data collection framework work on 6G, and use the lesson learned across all the WGs to design something for 6G. 2. From RAN perspective, we see value for SA WG2\/SA WG5 and SA WG3 to complete\/finalize their study so we can use the lessons learned for 6G. 3. The fact that 5G didn't have normative phase does not preclude standardized solutions in 6G. Even though TSG RAN has agreed to not continue with normative phase for AI\/ML UE sided data collection in Rel-20 NR, we see value for SA WG2\/SA WG5 and SA WG3 to complete\/finalize their study so we can use the lesson learned for 6G. TSG RAN kindly asks TSG SA to take these agreements and RAN recommendation into account when deciding how to proceed with the completion of the study item phase in the respective groups. Action: TSG RAN kindly asks TSG SA to take the RAN recommendation into account","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"noted","reservation_date":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"RAN WG2, SA WG3, SA WG5","lsoriginalls":"RP-253847","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600038.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600041","title":"LS from SA WG1: Reply LS on external data channel content access requirements","source":"SA WG1","contact":"Zixuan Shen","contact-id":110072,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks NG UPG for their LS on the external data channel access. SA WG1 would like to answer Question 6: 6. Question 6 to SA WG1: Given the fact that IMS telephony services are subject to telecom regulation while HTML and JavaScript content is not a subject to such regulation what is SA WG1 view on if and what regulatory exceptions apply to 3GPP TS 26.114 defined IMS Data Channel applications in general and specifically when those applications are mixed with the external content. SA WG1 answer: When lMS Data Channel is used as a part of lMS telephony services, lMS Data Channel applications, including their HTML and JavaScript content, are expected to be subject to local telecom regulation, when used for other services, e.g. standalone Data Channel, they are subject to applicable regulations which could also include local telecom regulations. The existence of any exceptions is likewise contingent upon these regulations. However, it is not up to SA WG1 to decide to which specific regulation(s) HTML and JavaScript content would be subject to.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2026-01-14 14:27:34","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, SA WG3, SA WG4, SA WG6, TSG CT","lsoriginalls":"S1-254509","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600041.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600045","title":"LS from SA WG4: Reply LS on URL for downloading the DC Application list","source":"SA WG4","contact":"Bo Burman","contact-id":16624,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 thanks SA WG6 for their liaison on URL for downloading DC Application list in S4-251676 (S6-254794), and would like to provide the following answers to the questions in that document, for SA WG6's information and further consideration: {. . .}","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":"2026-01-14 14:27:35","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2","lsoriginalls":"S4-251998","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600045.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600049","title":"LS from SA WG4: LS reply about Requirements Concerning Automatic Resume Where You have Left","source":"SA WG4","contact":"Imed Bouazizi","contact-id":84417,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 thanks GSMA for their Liaison Statement discussing the feature for automatic resumption on IMS data channel applications. SA WG4 is considering the use case and is committed to address it as part of the DC Enhancements Study Item (FS_DCE_MED) in Release 20.","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":"2026-01-14 14:27:35","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA TSG IMSDCAS","Cc":"SA WG2","lsoriginalls":"S4-252144","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600049.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600051","title":"LS from SA WG5: LS reply to IETF Network Slice Application in 3GPP 5G End-to-End Network Slice","source":"SA WG5","contact":"Jose Antonio Ordo\u00f1ez Lucena","contact-id":105406,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 has reviewed the informational document 'IETF Network Slice Application in 3GPP 5G End-to-End Network Slice' [1], and would like to provide the following feedback points. {. . .} Action: SA WG5 kindly requests SA to consolidate all inputs from SA WG5, SA WG2 and SA WG3, and provide response to the IETF TEAS WG.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"noted","reservation_date":"2026-01-14 14:27:35","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, SA WG3, RAN WG3","lsoriginalls":"S5-255690","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600051.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600052","title":"LS from SA WG5: LS on MWAB-gNB Configurations","source":"SA WG5","contact":"Pengxiang Xie","contact-id":102614,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 is working to provide management support for MWAB in Rel-20. SA WG5 received the LS from SA WG2 (S2-2504380) with RAN WG3 copied. In the LS, SA WG2 specifies the following configuration requirements. {. . .}","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":"2026-01-14 14:27:35","uploaded":"2026-01-20 15:56:29","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2","lsoriginalls":"S5-255704","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600052.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600066","title":"LS from SA WG6: Reply LS on external data channel content access","source":"SA WG6","contact":"Yue Liu","contact-id":80533,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks NG UPG for their LS on the external data channel access. SA WG6 would like to answer Question 4: Question 4 to SA WG2 and SA WG6: Does SA WG2\/SA WG6 plan to define procedures and architecture for interworking between the IMS session and external (non-IMS) content sources allowing for example pulling information from a public API in a secure manner? SA WG6 answer: SA WG6 has not yet studied the procedures and architecture for interworking between the IMS domain and external (non-IMS) content sources. In the CAPIF framework defined by SA WG6 in 3GPP TS 23.222, third-party API providers are introduced. In this scenario, third-party API providers can securely expose their capabilities to other services under the control of the PLMN, meaning that the resources of third-party API providers can be securely utilized by other services. The architecture and corresponding procedures for these third-party API providers in non-3GPP systems could potentially serve as a reference for the procedures of interworking between the IMS session and external (non-IMS) content sources. SA WG6 will keep GSMA NG UPG informed of our progress.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2026-01-20 15:42:44","uploaded":"2026-01-20 16:10:16","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG CT, SA WG4, SA WG3, SA WG2, SA WG1","lsoriginalls":"S6-255643","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600066.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600067","title":"LS from SA WG6: LS to SA WG3 on FS_APCOT study","source":"SA WG6","contact":"Cristina Badulescu","contact-id":38298,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 is currently studying the application user consent and the latest draft TR is available at : Specification # 23.700-42. The TR is moving into phase 2 and we would like to inform SA WG3 so that we can coordinate any associated study work that needs to be done to cover the security and regulatory aspects in SA WG3 for this feature. SA WG6 kindly request SA WG3 to consider in the SA WG3 work the issues and requirements identified in the TR.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2026-01-20 15:43:10","uploaded":"2026-01-20 16:10:16","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2","lsoriginalls":"S6-255645","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600067.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600320","title":"[DRAFT] Reply LS on Clarification on 5G VN group","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"LS out","for":"Approval","abstract":"Replies to CT WG4's LS (S2-2600010 \/ C4-253576) on Clarification on 5G VN group.","secretary_remarks":"Response to S2-2600010. Revised to S2-2601168.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"revised","reservation_date":"2026-01-27 05:57:01","uploaded":"2026-01-30 09:00:34","revisionof":"","revisedto":"S2-2601168","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"FS_PAIDC_UPF"},{"winame":" GMEC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600320.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600638","title":"Availability of IMS Emergency Services","source":"Nokia, Ericsson, Samsung, BMN, AT&T, NEC, Charter, T-Mobile US","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In this CR, it is proposed to go with Option 2","secretary_remarks":"Revised to S2-2601113","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"revised","reservation_date":"2026-01-28 16:49:08","uploaded":"2026-01-29 18:47:41","revisionof":"","revisedto":"S2-2601113","release":"Rel-19","crspec":"23.167","crspecversion":"19.1.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI19"}],"crnumber":380.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600638.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2600736","title":"Clarification for supported V2X capabilities in 5GS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Replaced 'V2X capability' by 'V2X-Uu capability' in this specification. Clarify the general V2X capability contains both capability over Uu and PC5.","secretary_remarks":"Revised to S2-2601170.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"revised","reservation_date":"2026-01-29 13:46:45","uploaded":"2026-01-30 21:10:33","revisionof":"","revisedto":"S2-2601170","release":"Rel-19","crspec":"23.287","crspecversion":"19.0.0","workitem":[{"winame":"TEI19"},{"winame":" eV2XARC"}],"crnumber":200.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2600736.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":false,"clauses_affected":"4.2.3, 4.4.1, 4.4.7, 6.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601113","title":"Availability of IMS Emergency Services","source":"Nokia, Ericsson, BMN, AT&T, NEC, Charter, T-Mobile US","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In this CR, it is proposed to go with Option 2","secretary_remarks":"Revision of S2-2600638. Revised to S2-2601169 (withdrawn). Postponed in parallel session.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"postponed","reservation_date":"2026-01-30 19:42:00","uploaded":"2026-01-30 19:43:46","revisionof":"S2-2600638","revisedto":"S2-2601169","release":"Rel-19","crspec":"23.167","crspecversion":"19.1.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI19"}],"crnumber":380.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601113.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"H.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601167","title":"LS from SA WG3-LI: LS on LI requirements","source":"SA WG3-LI","contact":"Carmine Rizzo","contact-id":52778,"tdoctype":"LS in","for":"Action","abstract":"As part of its 6G discussion, SA WG3-LI has determined that all of the currently defined LI requirements contained in TS 33.126 shall still apply, and may be expanded to accommodate changes related to 6G work in SA WG2. While it is SA WG3-LI's task to specify the LI solution for 6G, SA WG3-LI kindly requests that SA WG2, SA WG3, SA WG4 and SA WG6 send LSs to SA WG3-LI on potential topics within SA WG2, SA WG3, SA WG4 and SA WG6 that may require input from SA WG3-LI before the 6G architecture is fully confirmed. It is the experience of SA WG3-LI that fully formed architecture with LI considerations made after development has the potential to cause issues and the system design may not be able to support LI requirements in all jurisdictions or legal frameworks. SA WG3-LI kindly requests that SA WG2, SA WG4 and SA WG6 take LI requirements, as they exist in TS 33.126 and any future 6G expansion into account as the 6G architecture is defined. SA WG3-LI kindly requests to include the following text at the end of clause 4.2 of TR 23.801-01 and to the TRs\/TSs under development for 6G in other WGs: - Lawful interception requirements shall be taken into account for all WTs and corresponding key issues in this study. For more details on LI requirements, see TS 33.126. Action: SA WG3-LI kindly requests the SA WG2 group to add reference to LI requirements to clause 4.2 of TR 23.801-01 with the text above. SA WG3-LI kindly requests SA WG2 to ask SA WG3-LI if SA WG2 requires clarification on any aspects of TS 33.126. SA WG3-LI kindly requests SA WG2 to inform SA WG3-LI if SA WG2 is aware of any issues in the solutions being considered in TR 23.801-01 which, in SA WG2's view, may prevent SA WG3-LI from defining solutions that comply with TS 33.126.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"postponed","reservation_date":"2026-06-02 06:25:36","uploaded":"2026-02-06 06:26:07","revisionof":"","revisedto":"","release":"Rel-20","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, SA WG4, SA WG6","Cc":"","lsoriginalls":"S3i260049","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601167.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601168","title":"[DRAFT] Reply LS on Clarification on 5G VN group","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"LS out","for":"Approval","abstract":"Replies to CT WG4's LS (S2-2600010 \/ C4-253576) on Clarification on 5G VN group.","secretary_remarks":"Revision of S2-2600320. Noted in parallel session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2026-02-16 09:16:23","uploaded":"2026-02-16 09:31:05","revisionof":"S2-2600320","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"GMEC"},{"winame":" FS_PAIDC_UPF"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601168.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601169","title":"Availability of IMS Emergency Services","source":"Nokia, Ericsson, BMN, AT&T, NEC, Charter, T-Mobile US","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In this CR, it is proposed to go with Option 2","secretary_remarks":"Revision of S2-2601113. WITHDRAWN","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"withdrawn","reservation_date":"2026-02-16 09:16:23","uploaded":null,"revisionof":"S2-2601113","revisedto":"","release":"Rel-19","crspec":"23.167","crspecversion":"19.1.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI19"}],"crnumber":380.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2601170","title":"Clarification for supported V2X capabilities in 5GS","source":"Ericsson, LG Electronics","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Replaced 'V2X capability' by 'V2X-Uu capability' in this specification. Clarify the general V2X capability contains both capability over Uu and PC5.","secretary_remarks":"Revision of S2-2600736. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"agreed","reservation_date":"2026-02-16 09:16:25","uploaded":"2026-02-16 09:31:05","revisionof":"S2-2600736","revisedto":"","release":"Rel-19","crspec":"23.287","crspecversion":"19.0.0","workitem":[{"winame":"TEI19"},{"winame":" eV2XARC"}],"crnumber":200.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-260085","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_173_Goa_2026-02\/Docs\/S2-2601170.zip","group":"S2","meeting":"S2-173","year":2026,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":false,"clauses_affected":"4.2.3, 4.4.1, 6.2.2","crsinpack":null,"crsinpacknumber":0}]