
Number of incoming LS documents: 18
This page is maintained by the Liaison co-ordinator
TO/CC |
Tdoc number |
Title |
Meeting |
source committee |
| TO SA4 Cc RAN4, RAN2, SA2, CT1 |
R1-2506541 | Reply LS on the RAN simulation assumptions for ULBC | 3GPPSA4#135 | RAN1, Qualcomm |
| TO SA2 Cc RAN2, SA4, CT1, SA3, SA1 |
R1-2508096 | Reply LS on issues related to support of IMS voice over NB-IoT NTN connected to EPC | 3GPPSA4#135 | RAN1, Qualcomm |
| TO SA4 Cc SA |
R1-2509596 | LS on traffic model for immersive communication | 3GPPSA4#135 | RAN1 |
| TO SA2 Cc SA4, CT1, SA3, SA1, RAN1 |
R2-2507784 | Reply LS on issues related to support of IMS voice over NB-IoT NTN connected to EPC | 3GPPSA4#135 | RAN2 |
| TO SA4 Cc RAN1, SA2, CT1 |
R2-2507790 | Reply LS on the RAN simulation assumptions, bundling period and SPS for ULBC | 3GPPSA4#135 | RAN2 |
| TO SA4 Cc RAN2, SA5 |
R3-255896 | Reply LS on MBS Communication Service Type | 3GPPSA4#135 | RAN3(Nokia) |
| TO SA WG4 Cc RAN1, RAN2, SA2 |
R4-2511782 | Response LS on the RAN simulation assumptions for ULBC | 3GPPSA4#135 | Xiaomi |
| TO SA2 Cc RAN2, SA4, CT1, SA3, RAN1 |
S1-254508 | LS reply to SA2 (cc RAN2, SA4, CT1, SA3, RAN1) on IMS voice over NB-IoT NTN connected to EPC | 3GPPSA4#135 | SA1 |
| TO SA Cc SA2, SA3, SA4, SA6, CT |
S1-254509 | Reply LS to SA (cc SA2, SA3, SA4, SA6, CT) on external data channel content access requirements | 3GPPSA4#135 | SA1 |
| TO SA WG4 Cc RAN WG1, RAN WG2, RAN WG4, SA WG1, CT WG1 |
S2-2507578 | Reply LS on the RAN simulation assumptions for ULBC | 3GPPSA4#135 | SA WG2 |
| TO RAN WG2, SA WG4, CT WG1, SA WG3, SA WG1, RAN WG1 | S2-2507636 | LS on issues related to support of IMS voice over NB-IoT NTN connected to EPC | 3GPPSA4#135 | SA WG2 |
| TO SA WG4 | S2-2510954 | LS on AI/ML for Media | 3GPPSA4#135 | SA WG2 |
| TO SA2 Cc RAN2, SA4, CT1, SA1, RAN1 |
S3-253797 | Reply LS on issues related to support of IMS voice over NB-IoT NTN connected to EPC | 3GPPSA4#135 | vivo |
| TO SA2, SA3-LI Cc SA4, CT1 |
S3-253806 | LS reply on LI requirements on IMS Data Channel | 3GPPSA4#135 | Nokia, Nokia Shanghai Bell |
| TO SA2 Cc SA4 |
S3-254551 | Reply to: Reply LS on Avatar Security Aspects | 3GPPSA4#135 | Ericsson |
| TO SA4, SA2 Cc CT1, SA3 |
s3i250185 | LS to SA4, SA2 (Cc. CT1, SA3) on LI requirements on IMS Data Channel | 3GPPSA4#135 | SA3-LI |
| TO SA Cc SA1, SA2, SA3, SA4, CT |
S6-255643 | Reply LS on external data channel content access | 3GPPSA4#135 | SA6 |
| TO All ITU Study Groups, IEC/ISO JSEG15, IEC TC57, IEC TC65, IEC TC79, IEC TC85, IEC TC100, IEC TC110, ISO TC68, ISO TC69, ISO TC133, ISO TC184, ISO TC 307, ISO/IEC JTC1/SC6, ISO/IEC JTC1/SC17, ISO/IEC JTC1/SC24, ISO/IEC JTC1/SC27, ISO/IEC JTC1/SC29, ISO/IEC JTC1/SC31, ISO/IEC JTC1/SC35, ISO/IEC JTC1/SC36, ISO/IEC JTC1/SC38, ISO/IEC JTC1/SC41, ISO/IEC JTC1/SC42, ISO/IEC JTC1/SC43, ISO/IEC JTC 1/SC2, IEEE SA, W3C, IETF, ETSI ISG-ARF, 3GPP TSG SA, 3GPP TSG SA WG1, 3GPP TSG SA WG4, IPv6 Forum, Broadband Forum, TMForum, INATBA, ITU IRG AVA, ETSI TC Cyber, World Metaverse Council, Metaverse Standards Forum, Open Metaverse Foundation, Digital Twin Consortium, VRM consortium, IOWN Global Forum, GI-AI4H, JCA-AHF, ASTAP, Khronos Group, Global Initiative on Virtual Worlds and AI – Discovering the Citiverse Cc TSAG |
JCA-MV-LS1 | LS on Invitation to Nominate Representatives to ITU-T JCA-MV and Provide Input to the Metaverse Standardization Roadmap | 3GPPSA4#135 | ITU-T JCA-MV |
page last updated: 2025-12-08 15:17