| TDoc | Title | Source |
|---|---|---|
| R3-253001 | RAN3#128 Meeting Agenda | RAN3 Chair |
| TDoc | Title | Source |
|---|---|---|
| R3-253002 | RAN3#127-bis Meeting Report | ETSI-MCC |
| TDoc | Title | Source |
|---|---|---|
| R3-253003 | Guidelines for RAN3 Meetings | RAN3 Chair, RAN3 Vice-Chairs |
| TDoc | Title | Source |
|---|---|---|
| R3-253004 | TR 30.531 v1.58.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| R3-253473 | Enrolment and contribution to RAN Git trial | Ericsson |
| R3-253559 | Discussion on Guidelines for RAN3 | Huawei, Ericsson, InterDigital |
| R3-253560 | Introduction of Remote Participants | Huawei, Ericsson, InterDigital |
| R3-253716 | Discussion on Guidelines for RAN3 | Huawei, Ericsson, InterDigital |
| TDoc | Title | Source |
|---|---|---|
| R3-253020 | Reply LS on clarification of UAV regulation from RAN3 | SA2(CMCC) |
| R3-253023 | Reply LS on per-UE UE performance metrics | SA5(NEC) |
| R3-253025 | Reply LS on Number of UEs in RRC_INACTIVE state with data transmission | RAN2(China Telecom) |
| R3-253027 | Reply LS on non-RedCap UE UL SRS frequency hopping for positioning | RAN2(ZTE) |
| R3-253032 | Reply LS on Signalling for 7 MHz Channel Bandwidth | RAN2(T-Mobile) |
| R3-253034 | LS on Rel-19 higher layers parameters list Post RAN1#120bis | RAN1(Ericsson) |
| R3-253144 | Tdoc | Nokia |
| R3-253161 | Discussion on per-UE UE performance metrics | ZTE Corporation |
| R3-253162 | Clarification of each UE performance metrics | ZTE Corporation |
| R3-253163 | Discussion on SRS Frequency Hopping | ZTE Corporation |
| R3-253164 | Correction on NRPPa for additional indication for the request of SRS frequency hopping [Pos_SRSHop] | ZTE Corporation, Ericsson, CATT, Samsung, China Telecom, CMCC |
| R3-253165 | Correction on F1AP for additional indication for the request of SRS frequency hopping [Pos_SRSHop] | ZTE Corporation, Ericsson, CATT, Samsung, China Telecom, CMCC |
| R3-253166 | Correction for additional indication for the request of SRS frequency hopping [Pos_SRSHop] | ZTE Corporation, Ericsson, CATT, Samsung, China Telecom, CMCC |
| R3-253167 | Reply LS on non-RedCap UE UL SRS frequency hopping for positioning | ZTE Corporation |
| R3-253416 | On per-UE UE performance metrics | Ericsson |
| R3-253417 | Reply LS on per-UE UE performance metrics | Ericsson |
| R3-253507 | Discussion on the reply LS from SA5 on UE throughput calculation in Rel-18 | Huawei, Lenovo, Deutsche Telekom, BT |
| R3-253508 | Correction on UE performance feedback | Huawei, Lenovo, Deutsche Telekom, BT |
| R3-253509 | Further discussion on UAV altitude information reporting | Huawei, Nokia |
| R3-253510 | Introduction of aerial UE's altitude information reporting | Huawei, Nokia |
| R3-253511 | Introduction of aerial UE's altitude information reporting | Huawei, Nokia |
| R3-253512 | Introduction of aerial UE's altitude information reporting | Huawei, Nokia |
| R3-253513 | Introduction of aerial UE's altitude information reporting | Huawei, Nokia |
| R3-253514 | [Draft] Reply LS on clarification of UAV regulation from RAN3 | Huawei, Nokia |
| R3-253580 | Per-UE UE Performance metrics in Rel-18 | Nokia |
| R3-253581 | Correction of Rel-18 Average UE Throughput DL/UL Semantics | Nokia |
| R3-253582 | [Draft] Reply LS on per-UE UE performance metrics | Nokia |
| R3-253736 | Clarification Number of active UEs in load balance | ZTE Corporation |
| R3-253737 | Reply LS on RRC_INACTIVE with ongoing SDT procedure | ZTE Corporation |
| R3-253744 | Response to R3-253163 - Discussion on SRS Frequency Hopping | Huawei |
| R3-253745 | Response to R3-253167 - Reply LS on non-RedCap UE | Huawei |
| R3-253747 | Response to R3-253736, R3-253737 | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R3-253350 | Support Aerial UE Flight Information Reporting to CN[UAS_Ph3] | ZTE Corporation, Ericsson, CATT, CMCC |
| R3-253389 | Remove the PWS support for IoT NTN | Nokia, Nokia Shanghai Bell, Huawei, Ericsson, Jio Platforms, Qualcomm Incorporated, Thales |
| R3-253449 | Remove the PWS Support for NR NTN | Ericsson, Huawei, Jio Platforms Limited, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Thales |
| R3-253452 | Support Aerial UE Flight Information Reporting to CN | Ericsson, CMCC, ZTE, CATT |
| R3-253467 | Support Aerial UE Flight Information Reporting [UAS_Ph3] | CATT, ZTE Corporation, Ericsson,CMCC |
| R3-253538 | Remove the PWS support for IoT NTN | Qualcomm Incorporated, Huawei, Ericsson, Jio Platforms, Nokia, Nokia Shanghai Bell, Thales |
| R3-253540 | Discussion on the support for PWS over satellite NGRAN in Rel-17 and beyond | Huawei, Ericsson, Jio Platforms, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Thales |
| R3-253541 | Remove the PWS support for NR NTN | Huawei, Ericsson, Jio Platforms , Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Thales |
| R3-253555 | Support Aerial UE Flight Information Reporting to CN | Ericsson, CMCC, ZTE, CATT |
| R3-253698 | Discussion on UAV information reporting | CMCC, Ericsson, ZTE, CATT |
| R3-253699 | Reply LS on clarification of UAV regulation from SA2 | CMCC |
| R3-253708 | Discussion on the support for PWS over satellite NGRAN in Rel-17 and beyond | Huawei, Ericsson, Jio Platforms, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Thales, Deutsche Telekom |
| R3-253709 | Remove the PWS support for NR NTN | Huawei, Ericsson, Jio Platforms Limited, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Thales, Deutsche Telekom |
| R3-253717 | Remove the PWS support for IoT NTN | Nokia, Nokia Shanghai Bell, Huawei, Ericsson, Jio Platforms, Qualcomm Incorporated, Thales, Deutsche Telekom |
| TDoc | Title | Source |
|---|---|---|
| R3-253201 | Discussion of L3 measurement triggered LTM | NEC |
| R3-253244 | F1 support for L3 measurements-based LTM | ZTE Corporation, Ericsson, CATT, Vodafone, Nokia, LG Electronics, Samsung |
| R3-253252 | Introduce eRedcap indication for eRedCap UE access control | ZTE Corporation, China Telecom, China Unicom |
| R3-253260 | Correction of gNB-CU-UP ID IE in the GNB-CU-UP CONFIGURATION UPDATE message | Huawei, Nokia, NEC |
| R3-253273 | Clarification for propagation of roaming and access restrictions | Samsung |
| R3-253279 | Discussion on SP SRS activation | Samsung, CMCC, ZTE |
| R3-253280 | Correction to SRS information | Samsung, ZTE Corporation, CATT, Nokia, China Telecom, Ericsson, Qualcomm, CMCC, Huawei |
| R3-253281 | Correction to SRS information | Samsung, ZTE Corporation, CATT, Nokia, China Telecom, Ericsson, Qualcomm, CMCC, Huawei |
| R3-253282 | Discussion on QMC coordination for RRC segmentation in NR-DC | Samsung, Nokia, ZTE, China Unicom, China Telecom, Lenovo |
| R3-253283 | Correction to QMC coordination for RRC segmentation in NR-DC | Samsung, Nokia, ZTE, China Unicom, China Telecom, Lenovo |
| R3-253300 | Discussion on L3 measurement report for SCell activation | CATT, China Telecom, CMCC, NTT Docomo |
| R3-253310 | Introduction to coordination for QoE RRC segmentation in NR-DC | ZTE Corporation,Samsung, China Unicom, China Telecom, Lenovo |
| R3-253337 | Correction for MDBV in alternative QoS | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CMCC |
| R3-253338 | Correction for MDBV in alternative QoS | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CMCC |
| R3-253339 | Correction for MDBV in alternative QoS | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CMCC |
| R3-253340 | Correction for MDBV in alternative QoS | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CMCC |
| R3-253341 | Discussion on Subcarrier Spacing for IAB | Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Lenovo |
| R3-253342 | Correction on Subcarrier Spacing for IAB | Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Lenovo |
| R3-253343 | Correction on Subcarrier Spacing for IAB | Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Lenovo |
| R3-253387 | MN-SN Coordination for Segmentation of QoE Reports | Ericsson India Private Limited |
| R3-253388 | Stage 2 updates for support of L3 measurements based LTM | CATT, Ericsson, Vodafone, ZTE, Google, Samsung, LG Electronics, NTT DoCoMo, Nokia |
| R3-253405 | F1 support of L3 measurements-based LTM | Ericsson, Vodafone, CATT, ZTE, NTT DoCoMo, Verizon Wireless, Nokia, Samsung, LG Electronics, Lenovo, Google, Huawei |
| R3-253406 | Discussion on supporting L3 measurement based LTM | CEWiT |
| R3-253408 | Correction of PEI and emergency PDU session | Huawei, Qualcomm, Ericsson, China Telecom, Nokia, CATT |
| R3-253409 | Correction of PEI and emergency PDU session | Huawei, Qualcomm, Ericsson, China Telecom, Nokia, CATT |
| R3-253410 | Correction of Security Indication and Security Result | Huawei, China Telecom, CMCC, Deutsche Telekom |
| R3-253411 | Correction of Security Indication and Security Result | Huawei, China Telecom, CMCC, Deutsche Telekom |
| R3-253474 | On packet loss metric in UE performance | Ericsson, Jio Platforms, Deutsche Telekom, InterDigital |
| R3-253475 | Correction to exclude Packet Loss as a UE Performance metric | Ericsson, Jio Platforms, Deutsche Telekom, InterDigital |
| R3-253529 | Clarification on the details of UE performance metrics | ZTE Corporation, Ofinno, CMCC, China Telecom, NEC, Samsung, CATT |
| R3-253542 | Alignment NG interface management function and NG Interface Management procedures | Huawei, CATT, Ericsson, Nokia, NNokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-253543 | Correction of NTN OAM Assistance information | Huawei, Ericsson, Thales, Nokia, Nokia Shanghai Bell, ETRI |
| R3-253567 | [F1-AP TP for 38.473] Unified solution to support L3 measurement based R18 LTM | Qualcomm Inc, Apple Inc, AT&T, NTT DOCOMO, Boost Mobile Networks (Dish),JIO Platforms, Rakuten, CEWiT, Vivo, Tejas Networks, Xiaomi, Fujitsu, Charter Communications |
| R3-253570 | Stage-2 (TS 38.300) correction to support L3 measurement based R18 LTM | Qualcomm Inc, AT&T, Apple Inc, NTT DOCOMO, JIO Platforms, Boost Mobile Networks (Dish), Rakuten, Tejas Networks, Vivo, Xiaomi, CEWiT, Fujitsu, Charter Communications |
| R3-253574 | Stage 2 (TS 38.401) CR to support L3 measurement based R18 LTM | Qualcomm Inc, AT&T, Apple Inc, NTT DOCOMO, JIO Platforms, Boost Mobile Networks (Dish), Rakuten, Tejas Networks, CEWiT, Vivo, Xiaomi, Fujitsu, Charter Communications |
| R3-253598 | Corrections on PDCP duplication for inter-DU multi-path relay | ZTE Corporation, Samsung, Nokia, Nokia Shanghai Bell, CATT |
| R3-253606 | Correction on the privacy indicator for MDT | Huawei, China Telecom, CMCC |
| R3-253610 | Correction of NPN network sharing with multiple cell-ID broadcast | Huawei, Nokia, China Telecom |
| R3-253611 | Correction of NPN network sharing with multiple cell-ID broadcast | Huawei, Nokia, China Telecom |
| R3-253612 | Correction of NPN network sharing with multiple cell-ID broadcast | Huawei, Nokia, China Telecom |
| R3-253613 | Correction of NPN network sharing with multiple cell-ID broadcast | Huawei, Nokia, China Telecom |
| R3-253614 | Correction of NPN network sharing with multiple cell-ID broadcast | Huawei, Nokia, China Telecom |
| R3-253615 | Correction of NPN network sharing with multiple cell-ID broadcast | Huawei, Nokia, China Telecom |
| R3-253623 | Discussion on the definition of UE Throughput | CATT,ZTE,Samsung |
| R3-253624 | Correction on the definition of UE Throughput - option 1 | CATT,ZTE,Samsung |
| R3-253625 | Correction on the definition of UE Throughput - option2 | CATT,ZTE, Samsung |
| R3-253657 | Support for PDU session-level indirect data forwarding in split PDU session scenarios | LG Electronics Inc., Huawei, ZTE |
| R3-253658 | Correction on PDU session-level indirect data forwarding in split PDU session scenarios [Indirect Data Forwarding] | LG Electronics Inc., Huawei, ZTE |
| R3-253707 | Further discussions on QMC Coordination for RRC Segmentation in NR-DC | Huawei |
| R3-253738 | Clarification for propagation of MDT Configuration in stage2 | ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei |
| R3-253743 | Discussion on compatibility issue for PEI and emergency | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R3-253037 | Correction of TSC Traffic Characteristics | Huawei, Nokia, China Telecom, Ericsson, ZTE |
| R3-253038 | Correction of MBS Distribution Setup | Nokia, CATT, Qualcomm Incorporated, Huawei, Ericsson, Orange, ZTE |
| R3-253039 | Correction of Emergency Call and eDRX | Nokia, ZTE, Huawei, Ericsson, Qualcomm Incorporated |
| R3-253040 | Correction to CPAC MCG configuration cancellation | Google, Nokia, ZTE Corporation, LG Electronics, Ericsson, Huawei |
| R3-253041 | Correction of TSC Traffic Characteristics | Huawei, Nokia, China Telecom, Ericsson, ZTE |
| R3-253042 | Correction of Conditional PSCell Change Cancel for S-CPAC | Huawei, Lenovo, LG Electronics, Google, Nokia, Ericsson, ZTE, China Telecom |
| R3-253043 | Miscellaneous corrections for non-3GPP access | ZTE Corporation, Nokia, Nokia Shanghai Bell, Samsung |
| R3-253044 | Corrections for multi-path relay | ZTE Corporation, China Telecom, Nokia, Nokia Shanghai Bell, Samsung, CATT |
| R3-253045 | Correction on PDCP packets discard in case of MBS broadcast path update | Huawei, CBN, CMCC, Qualcomm Incorporated, Ericsson, ZTE, Nokia |
| R3-253046 | Correction on the NRPPa positioning procedure | ZTE Corporation, Nokia, Ericsson, Huawei, CATT, CMCC, Samsung |
| R3-253047 | Correction of MBS Distribution Setup | Nokia, CATT, Qualcomm Incorporated, Huawei, Ericsson, Orange, ZTE |
| R3-253048 | Correction on Bearer Context NG-U TNL Information for an MBS Session | ZTE Corporation, Ericsson, Huawei, CATT, Lenovo, Nokia |
| R3-253049 | Correction of CPC Cancel and SN Release | Huawei, Lenovo, LG Electronics, Google, Nokia, Ericsson, ZTE, China Telecom |
| R3-253050 | Clarification on Carrier Bandwidth less than 5MHz | ZTE Corporation, China Telecom, CATT, China Unicom, Huawei, Qualcomm, Lenovo, LG Electronics, Ericsson, Nokia |
| R3-253051 | Clarification on Carrier Bandwidth less than 5MHz | ZTE Corporation, China Telecom, CATT, China Unicom, Huawei, Qualcomm, Lenovo, LG Electronics, Ericsson, Nokia |
| R3-253052 | Correction on S-CPAC for the presence of SN Security Key IE | ZTE Corporation, China Telecom, CATT, Huawei, Lenovo, Nokia, Ericsson, LG Electronics |
| R3-253053 | Correction of RRC Establishment Cause for CIoT | Huawei, Nokia, ZTE, Qualcomm Incorporated |
| R3-253054 | Clarification on data transmission for EDT | ZTE Corporation, China Telecom, Huawei, Nokia |
| R3-253055 | Correction on Served Cells To Update | Huawei, CMCC, China Unicom |
| R3-253056 | Correction of Old AMF and Backup AMF Name | Huawei, China Unicom, China Telecom, Vodafone, Nokia |
| R3-253057 | Clarification on Security indication during State Transition from RRC_INACTIVE to RRC_CONNECTED | China Telecom, Nokia, Huawei, LG Electronics, Lenovo, ZTE, CATT |
| R3-253058 | Correction of Emergency Call and eDRX | Nokia, ZTE, Huawei, Ericsson, Qualcomm Incorporated |
| R3-253059 | Correction to CPAC MCG configuration cancellation | Google, Nokia, ZTE Corporation, LG Electronics, Ericsson, Huawei |
| R3-253060 | Additional procedural text measured UE trajectory request | ZTE Corporation, Ericsson, InterDigital, Jio Platforms (JPL), CMCC |
| R3-253061 | Additional procedural text for data collection configuration | Ericsson, ZTE Corporation, Jio Platforms, InterDigital |
| R3-253062 | Correction on the mobile IAB procedures | Huawei, Lenovo, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R3-253568 | Update of R3-253038 | Nokia |
| R3-253569 | Update of R3-253047 | Nokia |
| R3-253571 | Update of R3-253039 | Nokia, ZTE, Huawei, Ericsson, Qualcomm Incorporated |
| R3-253572 | Update of R3-253058 | Nokia, ZTE, Huawei, Ericsson, Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R3-253063 | (BL CR to 36.300 for SON) Addition of SON enhancements | Lenovo |
| R3-253064 | (BL CR to 36.423) Addition of SON enhancements | CATT, Samsung, Lenovo, Huawei, Ericsson, ZTE, CMCC, Nokia, Jio Platforms |
| R3-253065 | (BL CR to 37.340 for SON) Addition of SON enhancements | CMCC |
| R3-253066 | (BL CR to 38.300 for SON) Addition of SON enhancements | China Unicom, ZTE Corporation, Samsung, Nokia, Lenovo |
| R3-253067 | (BL CR to 38.401 for SON) Addition of SON enhancements | ZTE Corporation, Nokia, Huawei, Lenovo, CATT, Ericsson, Samsung |
| R3-253068 | (BL CR to 38.413 for MDT) Addition of MDT enhancements | Nokia |
| R3-253069 | (BL CR to 38.423 for MDT) Addition of MDT enhancements | CATT |
| R3-253070 | (BL CR to 38.423 for SON) Addition of SON enhancements | ZTE Corporation, Samsung, Nokia, Lenovo, Jio |
| R3-253071 | (BL CR to 38.473 for SON) Addition of SON enhancements | Huawei, Nokia, Jio |
| R3-253151 | (BL CR to 38.423 for SON) Addition of SON enhancements | ZTE Corporation, Samsung, Nokia, Lenovo, Jio |
| R3-253631 | Workplan for Rel-19 SON_MDT Enhancement | China Unicom, CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-253142 | MRO enhancements for LTM | Qualcomm Incorporated |
| R3-253150 | (TP for SON BL CR for TS 38.473, TP for SON BL CR for TS 38.401, TP for SON BL CR for TS 38.300, TP for SON BL CR for TS 38.423) MRO Enhancements for LTM and CHO with Candidate SCG(s) | Nokia |
| R3-253185 | (TP for SON BL CR for TS 37.340) Reformulation of the forwarding mechanism and MRO Enhancements for optimisation of the S-CPAC selection | Nokia |
| R3-253188 | (TP for BL CR to 38.473 for SON) MRO enhancements for LTM | Ericsson |
| R3-253214 | (TP for SON BLCR of 38.473) Discussion on MRO for LTM | NEC |
| R3-253278 | (TP for SON BL CR for TS 38.473) Discussion on LTM MRO | |
| R3-253311 | (TP for SON BLCR for 38.473) Discussion on MRO for LTM | Lenovo |
| R3-253312 | (TP for SON BLCR for 38.423) Discussion on MRO for CHO with candidate SCG(s) and subsequent CPAC | Lenovo |
| R3-253351 | Ping-Pong | Huawei, CMCC, Qualcomm, Jio Platforms |
| R3-253352 | (TP for SON BLCR for 38.473) Ping-Pong | Huawei, CMCC, Qualcomm, China Unicom, Jio Platforms |
| R3-253353 | (TP for SON BLCR for 38.413) Ping-Pong | Huawei, CMCC, Qualcomm, Jio Platforms |
| R3-253354 | (TP for SON BLCR for 37.340) Ping-Pong | Huawei, CMCC, Qualcomm, China Unicom, Jio Platforms |
| R3-253355 | (TP for SON BLCR for 38.423) Ping-Pong | Huawei, CMCC, Qualcomm, Jio Platforms |
| R3-253356 | (TP for SON BLCR 38.401, 38.473) MRO for LTM | Huawei |
| R3-253357 | (TP for SON BLCR for 37.340) MRO for others | Huawei |
| R3-253439 | (TP for 38.473 and 38.401) MRO for Rel-18 LTM | CATT |
| R3-253440 | (TP for 38.423 and 38.300) MRO for CHO with Candidate SCG(s) and S-CPAC | CATT |
| R3-253626 | (TP to BL CR for TS38.473 and TS38.401) MRO for LTM | Samsung |
| R3-253627 | (BL CR to 38.420 for SON) Addition of SON enhancements | Samsung, ZTE, CATT, Lenovo, Cybecore |
| R3-253628 | (TP for SON BLCR TS38.300, TS37.340 and TS38.423) MRO for CHO with candidate SCGs and S-CPAC | Samsung, Jio Platforms |
| R3-253629 | Failure scenarios on MRO for CHO with candidate SCGs | Samsung, Cybercore, Lenovo |
| R3-253632 | Discussion on MRO Enhancements | China Unicom |
| R3-253696 | Discussion on MRO enhancements for LTM | CMCC |
| R3-253733 | (TP for SON BLCR for 38.401, 38.473, 38.413, 37.340, and 38.423)Discussion on MRO | ZTE Corporation |
| R3-253734 | (TP for SON BLCR for 38.300, 38.401, and 38.473) LTM failure and near failure caused by wrong beam | ZTE Corporation |
| R3-253735 | (TP for SON BLCR 38.300, 38.401 and 38.473)MRO for LTM outdated TA and TA acquisition type | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R3-253033 | Relay LS on MDT for NTN | RAN2(Qualcomm) |
| R3-253143 | SON MDT for NTN | Qualcomm Incorporated |
| R3-253186 | (SON TP to BL CR to TS 38.423) Solution to avoid restarting MRO in NTN deployments | Nokia |
| R3-253189 | SON-MDT enhancements for NTN | Ericsson |
| R3-253190 | (BL CR to 38.413 for SON) Addition of SON enhancements | Ericsson |
| R3-253221 | Discussion on SON/MDT enhancements for NTN | NEC |
| R3-253234 | (TPs to BL CR for 38.300, 38.413 and 38.423) Further discussion on SONMDT enhancements for NTN | ZTE Corporation |
| R3-253272 | (TP for MDT BLCRs for TS38.413, TS38.423) SON/MDT enhancements for NTN | Samsung |
| R3-253313 | Discussion on SON/MDT for NTN | Lenovo |
| R3-253358 | (TP for SON BLCR for 38.423) MRO for Intra-NTN mobility | Huawei |
| R3-253441 | (TP for 38.300 and 38.413) Intra-NTN mobility for SONMDT | CATT |
| R3-253602 | Discussion on SONMDT for Intra-NTN mobility | Huawei, CMCC, China Unicom |
| R3-253603 | (TP for MDT BLCR for TS38.413): MDT enhancement for NTN | Huawei, CMCC, China Unicom |
| R3-253604 | (TP for MDT BLCR for TS38.423): MDT enhancement for NTN | Huawei, CMCC, China Unicom |
| R3-253605 | (TP for MDT BLCR for TS37.320): MDT enhancement for NTN | Huawei, CMCC, China Unicom |
| R3-253633 | Discussion on SONMDT enhancements for NTN mobility | China Unicom |
| TDoc | Title | Source |
|---|---|---|
| R3-253006 | Reply LS on SON for Network Slicing and Enhanced Area Scope | CT4(Ericssson) |
| R3-253187 | (MDT TP to BL CR to TS 38.300) Retrieval of slice information after SHR and other slice-related enhancements | Nokia |
| R3-253191 | Data collection for slice coverage observability enhancement | Ericsson, BT, InterDigital, Deutsche Telekom, Jio Platforms (JPL), FiberCop |
| R3-253192 | (TP for BL CR to 38.413 for SON) – Data collection for slice coverage observability enhancement | Ericsson, BT, InterDigital, Deutsche Telekom, Jio Platforms (JPL), FiberCop |
| R3-253193 | MDT Enhancements for slice-focused measurement collection | Ericsson, Orange, InterDigital, Deutsche Telekom, Jio Platforms (JPL), FiberCop |
| R3-253194 | (TP for BL CR to 38.413 for MDT) Deferred MDT for slice-focused measurements collection | Ericsson, InterDigital, Deutsche Telekom, Jio Platforms (JPL), FiberCop |
| R3-253195 | (TP for BL CR to 38.423 for MDT) Deferred MDT for slice-focused measurements collection | Ericsson, InterDigital, Deutsche Telekom, Jio Platforms (JPL), FiberCop |
| R3-253359 | Network Slicing | Huawei |
| R3-253442 | Network slicing for SONMDT | CATT |
| R3-253634 | Discussion on SONMDT enhancements for network slicing | China Unicom |
| R3-253691 | Discussion on SON/MDT for network slicing | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-253196 | (TP for BL CR to 38.413 for SON) UHI for SCG activation and deactivation | Ericsson |
| R3-253314 | Discussion on UHI enhancement for SCG Deactivation or Activation | Lenovo |
| R3-253630 | (TP for SON BLCR for TS37.340) Rel-18 SON and MDT leftovers | Samsung, Jio Platforms |
| TDoc | Title | Source |
|---|---|---|
| R3-253072 | (BL CR to 37.480) Support of enhancements on AI/ML for NG-RAN | CATT, ZTE Corporation |
| R3-253073 | (BL CR to 37.483) Support of enhancements on AI/ML for NG-RAN | Samsung, ZTE Corporation |
| R3-253074 | (BL CR to 38.423) Support of enhancements on AI/ML for NG-RAN | ZTE Corporation, Qualcomm, China Unicom, Ericsson, Samsung, Nokia, Lenovo, CATT, Huawei, NEC, CMCC, China Telecom, Telecom Italia, Deutsche Telekom, Verizon Wireless, LGE, Jio Platforms (JPL), Rakuten, Orange, FiberCop, InterDigital |
| R3-253075 | (BL CR to TS 38.473) Support of enhancements on AI/ML for NG-RAN | Ericsson (Rapporteur), ZTE, NEC, Nokia, Huawei |
| R3-253525 | Work plan for enhancements for Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN | ZTE Corporation, NEC |
| TDoc | Title | Source |
|---|---|---|
| R3-253152 | Discussion on AI/ML assisted Network Slicing | ZTE Corporation |
| R3-253153 | [TP to 38.300] AI/ML assisted Network Slicing | ZTE Corporation, Lenovo, Samsung, China Unicom, Qualcomm |
| R3-253154 | [TP to 38.423] AI/ML assisted Network Slicing | ZTE Corporation, Qualcomm, China Unicom |
| R3-253202 | (TP for BLCR for TS38.300) Support of enhancements on AI/ML for NG-RAN | NEC, ZTE, Qualcomm, Samsung, CMCC |
| R3-253268 | Discussion on remaining issues for NG-RAN AI/ML for Network Slicing | Qualcomm Incorporated |
| R3-253418 | AI/ML enabled Network Slicing | Ericsson, JIO Platforms, InterDigital, Deutsche Telekom |
| R3-253419 | (TP to TS 38.423) AI/ML enabled Network Slicing | Ericsson, JIO Platforms, InterDigital, Deutsche Telekom |
| R3-253420 | (TP to TS 38.300) AI/ML support | Ericsson, FiberCop, Verizon, Jio Platforms, Deutsche Telekom, BT |
| R3-253421 | (TP to TS 38.401) AI/ML support | Ericsson, FiberCop, Verizon, Jio Platforms, Deutsche Telekom, BT |
| R3-253485 | (TP for AI/ML BLCR to TS 38.300) Capturing agreements in Stage 2 RAN specifications | Huawei, Orange, InterDigital, CATT, FiberCop, Deutsche Telekom, Jio Platforms |
| R3-253486 | (TP for AI/ML BLCR to TS 38.401) Capturing agreements in Stage 2 RAN specifications | Huawei, InterDigital, CATT, FiberCop, Deutsche Telekom, Jio Platforms |
| R3-253487 | (TP for AI/ML BLCR to TS 37.340) Capturing agreements in Stage 2 RAN specifications | Huawei, Qualcomm, InterDigital, FiberCop, Deutsche Telekom, Jio Platforms |
| R3-253488 | Discussion on per slice UE performance in AI/ML-based Network Slicing | Huawei, Jio Platforms, Deutsche Telekom |
| R3-253489 | Discussion on additional finer granularities for UE performance in AI/ML-based Network Slicing | Huawei, Jio Platforms, Deutsche Telekom |
| R3-253490 | (TP for AI/ML BLCR to TS 38.423) XnAP enhancements for AI/ML-based Network Slicing | Huawei, Jio Platforms, Deutsche Telekom |
| R3-253583 | AI/ML Slicing Discussion | Nokia, FiberCop, Deutsche Telekom, Jio Platforms (JPL) |
| R3-253584 | (TP to TS 38.423) AI/ML Slicing | Nokia, FiberCop, Deutsche Telekom, Jio Platforms (JPL) |
| R3-253585 | [Draft] LS on UE Performance metrics per S-NSSAI granularity | Nokia, FiberCop, Deutsche Telekom, Jio Platforms (JPL) |
| R3-253618 | (TP on 38.423)Discussion on Per S-NSSAI UE performance metrics | CATT |
| R3-253644 | Discussion on AI/ML enabled slicing | Samsung |
| R3-253683 | (TP to BLCR for 38.423) AIML enabled network slice | CMCC |
| R3-253718 | Additional Finer Granularity of UE Performance Feedback for AI/ML based Network Slicing | Rakuten Mobile, Inc |
| TDoc | Title | Source |
|---|---|---|
| R3-253203 | Open issues for AI/ML-based CCO | NEC |
| R3-253204 | TP to BLCR TS38.473 on AI/ML-based CCO | NEC |
| R3-253269 | Discussion on remaining issues in AI/ML enabled CCO | Qualcomm Incorporated |
| R3-253315 | Discussion on AI/ML based CCO | Lenovo |
| R3-253370 | Discussion on AI/ML based Coverage and Capacity Optimization | China Telecom |
| R3-253371 | (TP for BLCR to TS38.423) Support of AI/ML based Coverage and Capacity Optimization | China Telecom |
| R3-253372 | (TP for BLCR to TS38.473) Support of AI/ML based Coverage and Capacity Optimization | China Telecom |
| R3-253422 | AIML enabled CCO - Single predicted CCO issue resolution | Ericsson, Jio Platforms, Deutsche Telekom, InterDigital |
| R3-253423 | (TP to 38.473) - AIML enabled CCO - Single predicted CCO issue resolution | Ericsson, Jio Platforms, Deutsche Telekom, InterDigital |
| R3-253424 | AIML enabled CCO - Prediction validation and timing issues | Ericsson, Jio Platforms, Deutsche Telekom, InterDigital |
| R3-253425 | (TP to 38.423) - AIML enabled CCO - Prediction validation and timing issues | Ericsson, Jio Platforms, Deutsche Telekom, InterDigital |
| R3-253426 | AIML enabled CCO - Multiple CCO issues | Ericsson, Jio Platforms, Deutsche Telekom, InterDigital |
| R3-253427 | (TP to 38.423) - AIML enabled CCO – Multiple CCO issues | Ericsson, Jio Platforms, Deutsche Telekom, InterDigital |
| R3-253428 | (TP to 38.473) – AIML enabled CCO - Multiple CCO issues | Ericsson, Jio Platforms, Deutsche Telekom, InterDigital |
| R3-253491 | Discussion on AI/ML-based Coverage and Capacity Optimization | Huawei, Orange, Deutsche Telekom, Rakuten |
| R3-253492 | (TP for AI/ML BLCR to TS 38.423) XnAP enhancements for AI/ML-based Coverage and Capacity Optimization | Huawei, Orange, Deutsche Telekom |
| R3-253493 | (TP for AI/ML BLCR to TS 38.473) F1AP enhancements for AI/ML-based Coverage and Capacity Optimization | Huawei, Orange, Deutsche Telekom |
| R3-253515 | AI/ML enabled Coverage and Capacity Optimization | Ofinno, LLC |
| R3-253530 | (TP for BLCR to TS 38.473) Further discussion on energy efficient AI/ML-based CCO issue prediction in split architecture | Nokia, FiberCop, Jio Platforms |
| R3-253531 | (TP for BLCR to TS 38.473) Discussion on open points for AI/ML-based CCO | Nokia |
| R3-253577 | Discussion on open issues for AI/ML-based CCO | LG Electronics Inc. |
| R3-253578 | (TP for NR_AIML_NGRAN_enh-Core for TS 38.473) Discussion on open issues for AIML-based CCO | LG Electronics Inc. |
| R3-253619 | (TP on 38.473) Open issues on the CCO use case | CATT |
| R3-253645 | Discussion on AI/ML enabled CCO | Samsung |
| R3-253684 | (TP to BLCR for 38.401 and 38.473) AIML based CCO | CMCC |
| R3-253719 | Multiple CCO Issues in AI/ML-based Coverage and Capacity Optimization | Rakuten Mobile, Inc |
| R3-253720 | Timing Information for AIML based CCO | Rakuten Mobile, Inc |
| R3-253722 | Discussion on AI/ML assisted Coverage and Capacity Optimization | ZTE Corporation |
| R3-253723 | [TP to BLCR to TS 38.300] Support of AI/ML assisted CCO | ZTE Corporation, Lenovo, China Unicom, China Telecom |
| R3-253724 | [TP to 38.401] Support of AI/ML assisted CCO | ZTE Corporation, Lenovo, China Unicom, China Telecom |
| R3-253725 | [TP to 38.473] Support of AI/ML assisted Coverage and Capacity Optimization | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R3-253024 | Reply LS to LS on Continuous MDT | SA5(Huawei) |
| R3-253155 | (TP to 38.423) Addition of predicted PSCell ID within DC procedure | ZTE Corporation, Samsung, Qualcomm, China Unicom, CMCC, CATT, Ofinno |
| R3-253156 | Discussion on support of AI/ML for NG-RAN in split architecture | ZTE Corporation |
| R3-253157 | (TP to BLCR for TS 38.473) Support of AI/ML for NG-RAN in split architecture | ZTE Corporation, China Telecom, China Unicom |
| R3-253158 | (TP to BLCR for TS 37.483) Support of AI/ML for NG-RAN in split architecture | ZTE Corporation, China Telecom, China Unicom |
| R3-253159 | Discussion on Continuous MDT Collection | ZTE Corporation |
| R3-253160 | (TP to BLCR for TS 38.425) Support of AI/ML for NG-RAN in split architecture | ZTE Corporation, Lenovo, China Unicom |
| R3-253205 | (TP for BLCR for TS38.300) Continuous MDT collection | NEC |
| R3-253206 | [draft] Reply LS to Reply LS to LS on Continuous MDT | NEC |
| R3-253207 | NR-DC mobility optimization | NEC |
| R3-253208 | (TP to BLCR TS38.473) Split architecture support | NEC |
| R3-253270 | Discussion on UE Performance Reporting for Split Architecture | Qualcomm Incorporated |
| R3-253271 | Discussion on LS Response for Continuous MDT | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-253316 | (TP to BLCR 37.483) UE performance collection via E1 interface after HO | Lenovo |
| R3-253317 | Discussion on UE performance collection in AIML for NR-DC | Lenovo |
| R3-253318 | (TP to BLCR 37.340) AIML for NR-DC | Lenovo, CATT, ZTE Corporation, Samsung |
| R3-253319 | (TP to BLCR 38.401) AIML for RAN in split architecture | Lenovo, CATT, ZTE Corporation |
| R3-253373 | Discussion on Continuous MDT measurement | China Telecom |
| R3-253429 | AI/ML support for NR-DC | Ericsson, Jio Platforms, InterDigital |
| R3-253430 | (TP to TS 38.423) AI/ML support for NR-DC | Ericsson, Jio Platforms, InterDigital |
| R3-253431 | On packet loss metric in UE performance | Ericsson, Jio Platforms, Deutsche Telekom, InterDigital |
| R3-253432 | (TP to 38.423) On packet loss metric in UE performance | Ericsson, Jio Platforms, Deutsche Telekom, InterDigital |
| R3-253433 | On collection of delay measurements for UE performance | Ericsson, Jio Platforms, InterDigital |
| R3-253434 | (TP to 38.473) - Delay measurements for UE performance support in Split architecture | Ericsson, Jio Platforms, InterDigital |
| R3-253435 | (TP to 38.425) - Split architecture support for Release 18 use cases | Ericsson, Jio Platforms, InterDigital |
| R3-253436 | (TP to 37.483) - On collection of delay measurements for UE performance | Ericsson, Jio Platforms, InterDigital |
| R3-253437 | On collection of throughput measurements for UE performance | Ericsson, Jio Platforms, InterDigital |
| R3-253438 | (TP to 37.483) – Throughput measurements for UE performance support in Split architecture | Ericsson, Jio Platforms, InterDigital |
| R3-253472 | (DRAFT_LS) Discussion continuous MDT | CATT |
| R3-253476 | Discussion on the SA5 reply LS on the Continuous MDT | Ericsson, InterDigital, Deutsche Telekom, BT |
| R3-253477 | (TP for AI/ML BLCR to TS38.423) Continuous MDT collection targeting the same UE across RRC states | Ericsson, InterDigital, Deutsche Telekom, BT |
| R3-253478 | (TP to 37.320) - Continuous MDT collection targeting the same UE across RRC states | Ericsson, InterDigital, Deutsche Telekom, BT |
| R3-253479 | Reply LS to LS on Continuous MDT | Ericsson, InterDigital, Deutsche Telekom, BT |
| R3-253494 | Discussion on UE performance feedback for AI/ML-based Mobility Optimization in NR-DC | Huawei |
| R3-253495 | Discussion on assistance information for SN configuration in AI/ML-based Mobility Optimization in NR-DC | Huawei |
| R3-253496 | (TP for AI/ML BLCR to TS 38.423) XnAP enhancements for AI/ML-based Mobility Optimization in NR-DC | Huawei |
| R3-253497 | Discussion on split architecture support for Rel-18 “AI/ML for NG-RAN” use cases | Huawei, CMCC, China Unicom |
| R3-253498 | (TP for AI/ML BLCR to TS 38.473) F1AP enhancements for split architecture support for Rel-18 “AI/ML for NG-RAN” use cases | Huawei, CMCC, China Unicom |
| R3-253499 | (TP for AI/ML BLCR to TS 37.483) E1AP enhancements for split architecture support for Rel-18 “AI/ML for NG-RAN” use cases | Huawei, CMCC, China Unicom |
| R3-253500 | (TP for AI/ML BLCR to TS 38.425) NR user plane protocol enhancements for split architecture support for Rel-18 “AI/ML for NG-RAN” use cases | Huawei, CMCC, China Unicom |
| R3-253501 | [DRAFT] LS reply to LS on energy saving for split gNB | Huawei, CMCC, China Unicom |
| R3-253502 | Discussion on the Reply LS from SA5 on Continuous MDT for AI/ML | Huawei, FiberCop, Jio Platforms |
| R3-253503 | [DRAFT] Reply LS from SA5 on Continuous MDT for AI/ML | Huawei, FiberCop, Jio Platforms |
| R3-253516 | Mobility Optimization for NR-DC | Ofinno, LLC |
| R3-253517 | [Draft] Reply LS to SA5 on Continuous MDT Collection | ZTE Corporation |
| R3-253579 | Discussion on open issue for AI/ML-based mobility optimization in NR-DC | LG Electronics Inc. |
| R3-253586 | (TP for BLCR to TS 38.425) Procedures for Measuring UE Performance | Nokia, Jio Platforms (JPL) |
| R3-253587 | (TP for BLCR to TS 37.483, TP for BLCR to TS 38.473) UE Performance Reporting over E1 and over F1 | Nokia, Jio Platforms (JPL) |
| R3-253588 | (TP for BLCR to TS 38.473) Energy Cost Reporting over F1 | Nokia, FiberCop, Deutsche Telekom, Jio Platforms (JPL) |
| R3-253589 | (TP to TS 38.423) Remaining issues for AI/ML Mobility Optimization in NR-DC | Nokia |
| R3-253590 | Replying to LS from SA5 on Continuous MDT | Nokia, Qualcomm |
| R3-253591 | [Draft] Reply LS to LS on Continuous MDT | Nokia, Qualcomm |
| R3-253620 | (TP on 38.300/38.423)AI/ML in DC scenario | CATT |
| R3-253621 | Use non-UE procedure to request UE performance measurement in gNB-DU | CATT |
| R3-253622 | (TP on 38.473)AI/ML for split scenario | CATT |
| R3-253646 | Discussion on AI/ML for mobility in NR-DC | Samsung |
| R3-253647 | Discusson on AI/ML for NG-RAN in split architecture | Samsung |
| R3-253648 | Further Discussion on continuous MDT collection based on SA5 reply | Samsung |
| R3-253649 | Reply LS on continuous MDT | Samsung |
| R3-253680 | AI/ML based Mobility Optimization for NR-DC | Jio Platforms, Deutsche Telekom, FiberCop |
| R3-253681 | Discussion on AIML based Mobility Optimization for NR-DC | CMCC |
| R3-253682 | (TP to BLCR for 38.423) AIML based Mobility Optimization for NR-DC | CMCC |
| R3-253685 | Discussion on continuous MDT | CMCC |
| R3-253686 | (TP to BLCR for 38.401) OAM Requirements for Energy Saving for split architecture | CMCC, Samsung, Huawei, NEC, CATT, ZTE, Nokia, Ericsson |
| R3-253687 | (TP to BLCR for 38.425) F1-U enhancement for UE delay | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-253076 | (BL CR to 38.300 for Femto) Introduction of NR Femto Architecture and Protocol Aspects | Ericsson, Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, Huawei, LG Electronics, Samsung, Lenovo, Baicells, ZTE, NEC |
| R3-253077 | (BL CR to 38.305 for WAB) Support of Location Service Involving WAB-Nodes | ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, Lenovo, CATT, Samsung, Huawei, China Telecom |
| R3-253078 | (BL CR to 38.401 for WAB) Support for Wireless Access Backhaul | Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung, Lenovo, Qualcomm, Jio Platforms |
| R3-253079 | (BL CR to 38.410 for Femto) Introduction of NR Femto in NGAP list of functions | ZTE Corporation, Nokia, Baicells |
| R3-253080 | (BL CR to TS 38.413 for Femto) Support of NR Femto architecture with NR Femto Gateway | Nokia, Huawei |
| R3-253081 | (BL CR to 38.413 for WAB) Support for Wireless Access Backhaul | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, China Telecom, ZTE, Qualcomm, Samsung, CATT, Jio Platforms (JPL), Lenovo |
| R3-253082 | (BL CR to 38.423 for WAB) Support for Wireless Access Backhaul | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, LG Electronics, Qualcomm, Huawei, China Telecom, Samsung, Lenovo |
| R3-253083 | (BL CR to 38.455 for WAB) Support of Location Service Involving WAB-Nodes | Lenovo, ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, CATT, Samsung, Huawei, China Telecom, Jio Platforms (JPL) |
| TDoc | Title | Source |
|---|---|---|
| R3-253013 | Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) | SA2(Qualcomm) |
| R3-253018 | Reply LS on MWAB-gNB Configurations | SA2(Qualcomm) |
| R3-253019 | Reply LS on PWS enhancement for MWAB and MBSR | SA2(Ericsson) |
| R3-253131 | (TP for WAB BL CR for TS 38.401): Functional Aspects of WAB-Nodes | Ericsson, Jio Platforms |
| R3-253132 | WAB-Node Resource Coordination | Ericsson |
| R3-253168 | Remaining aspects of WAB | Qualcomm Inc. |
| R3-253169 | WAB radio resource coordination | Qualcomm Inc. |
| R3-253170 | BL draft CR to TS 38.300 on Support of WAB | Qualcomm, Ericsson, CATT, ZTE, Nokia, Nokia Shanghai Bell |
| R3-253175 | Further consideration on support of WAB | LG Electronics |
| R3-253176 | (TP to TS 38.401, 38.413 and 38.423) TP for WAB support | LG Electronics |
| R3-253211 | (TP to BL CR of 38.423 on WAB) Discussion on access and reliability for WAB | NEC |
| R3-253223 | Remaining aspects for the support of WAB | CANON Research Centre France |
| R3-253301 | [Draft] LS on Multi-hop Topology Avoidance for WAB | CATT, China Telecom, Huawei, NTT Docomo, Lenovo, Samsung, NEC |
| R3-253302 | (TP for BLCR to 38.401) On support of WAB | CATT |
| R3-253303 | (TP for BLCRs to 38.423, 38.473) On resource coordination and Xn management for WAB | CATT |
| R3-253320 | (TP to BL CR 38.423) Architecture and configuration for WAB-node | Lenovo |
| R3-253321 | (TP to BL CR 38.423) Radio resource configuration for WAB-node | Lenovo |
| R3-253344 | (TPs for WAB BL CRs) Architecture, Access Control and Additional ULI for WAB | Huawei |
| R3-253345 | (TP for WAB BL CRs) Radio Resource multiplexing Coordination for WAB-node | Huawei |
| R3-253390 | (TP to BL CR for TS 38.401) Discussion on NG/Xn management and other Stage-2 issues for WAB | Nokia, Nokia Shanghai Bell |
| R3-253391 | (TP to BL CR for TS 38.413 and TS 38.423) Enhancement for WAB | Nokia, Nokia Shanghai Bell |
| R3-253404 | (TP to 38.413, 38.401) Discussion on remaining issues for support of WAB | ZTE Corporation |
| R3-253412 | Discussion on Wireless Access Backhaul | NTT DOCOMO INC. |
| R3-253414 | Way Forward On Multi-hop Prevention for WAB | China Telecom, CATT, Huawei, DoCoMo, Lenovo, Samsung, NEC |
| R3-253415 | RAN2 impact of WAB | China Telecom |
| R3-253537 | (TP to 38.423 38.473) Supporting resource coordination in WAB | ZTE Corporation |
| R3-253635 | (TP to BLCR for TS 38.410) Discussion on WAB mobility | Samsung |
| R3-253636 | Discussion on the left issues for WAB | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R3-253021 | Reply LS on security verification related to NR Femtos | SA3(ZTE) |
| R3-253224 | [TP for BL CR NR Femto 38.300] Completion of Security Aspects of NR Femto | Nokia, TMO US, BT, AT&T, NTT Docomo |
| R3-253225 | Completion of other open points of NR Femto | Nokia |
| R3-253226 | [TP for BL CR NR Femto TS 38.413] Completion of other open points of NR Femto | Nokia |
| R3-253304 | Discussion on remain issue of NR Femto | CATT |
| R3-253305 | TP for BLCRs to 38.300, 38.410 for NR Femto | CATT |
| R3-253322 | Discussion on remaining issues for NR Femto | Lenovo |
| R3-253323 | (TP to BL CR 38.300) Function split for NR Femto | Lenovo |
| R3-253346 | (TP for Femto BL CR for TS 38.300/38.413) Discussion on remaining issues for NR Femto | Huawei |
| R3-253347 | (TP for Femto BL CR for TS 38.300) Security related issues for NR Femto | Huawei |
| R3-253364 | On remaining issues for NR Femto | China Telecom |
| R3-253403 | (TP to TS 38.300) On security verification related to NR Femtos based on the reply LS from SA3 | ZTE Corporation |
| R3-253413 | Discussion on 5G femto | NTT DOCOMO INC. |
| R3-253450 | Stage 2 Rapporteur Corrections for NR Femto | Ericsson |
| R3-253451 | Aligning SA3 Text to RAN3 Agreements | Ericsson |
| R3-253565 | Aligning SA3 Text to RAN3 Agreements | Ericsson |
| R3-253566 | Aligning SA3 Text to RAN3 Agreements | Ericsson LM |
| R3-253575 | Security verification related to NR Femtos | LG Electronics |
| R3-253576 | (TP to TS 38.300) Support of security verification in NR Femto | LG Electronics |
| R3-253637 | Discussion on the left issues for NR Femto | Samsung |
| R3-253638 | (TP to BLCR for TS 38.300) Functional split for NR Femto | Samsung |
| R3-253741 | (TP to TS 38.300) Discussion on IP version selection at Femto GW | ZTE Corporation |
| R3-253742 | [draft] Reply LS on security verification related to NR Femtos | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R3-253084 | (BL CR to 37.340) stage 2 for inter-CU LTM in NR-DC | CATT, China Telecom, Huawei, Nokia, LG Electronics, Google, Samsung, Ofinno, Ericsson, Lenovo, NEC, ZTE, Qualcomm |
| R3-253085 | (BL CR to 37.483) Introducing Rel-19 Mobility enhancement | LG Electronics Inc., Nokia, China Telecom, Google, Ericsson, CATT, Qualcomm, Samsung, CMCC, ZTE, Huawei, NTT Docomo, Lenovo, NEC, Ofinno, Jio Platforms (JPL) |
| R3-253086 | (BL CR to 38.300) Support for Inter-CU LTM | Nokia, Huawei, Google, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung, Ofinno |
| R3-253087 | (BL CR to 38.401) on conditional intra-CU LTM and intra-CU LTM | China Telecom, ZTE Corporation, NEC, Samsung, Nokia, Google, Huawei, Ericsson, LG Electronics, Qualcomm |
| R3-253088 | (BL CR to 38.420) Support for Inter-CU LTM | ZTE Corporation, China Telecom, Samsung, Nokia, CATT, NEC, LG Electronics, Ericsson, Huawei, Lenovo |
| R3-253089 | (BL CR to 38.423) Xn support for inter-CU LTM | Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC, ZTE, LG Electronics, Ofinno, Qualcomm |
| R3-253090 | (BL CR to 38.423 for DC) Xn support for inter-CU LTM in DC | Lenovo, Ericsson, CATT, Huawei, Ofinno, Nokia, NEC, LGE, China Telecom, Google, ZTE, Samsung |
| R3-253091 | (BL CR to 38.470) Support for Inter-CU LTM procedure | Samsung, Huawei, LG Electronics, Ericsson, China Telecom, Nokia, ZTE Corporation, CATT |
| R3-253092 | (BL CR to 38.473) Inter-CU LTM and intra-CU conditional LTM | Huawei, Nokia, Samsung, Google, NEC, China Telecom, Ericsson, LG Electronics, CATT, Ofinno, ZTE, Lenovo, Qualcomm Incorporated |
| R3-253149 | (BL CR to 38.473) Inter-CU LTM and intra-CU conditional LTM | Huawei, Nokia, Samsung, Google, NEC, China Telecom, Ericsson, LG Electronics, CATT, Ofinno, ZTE, Lenovo, Qualcomm Incorporated |
| R3-253174 | (BL CR to 38.470) Support for inter-CU LTM procedure | Samsung, Huawei, LG Electronics, Ericsson, China Telecom, Nokia, ZTE Corporation, CATT |
| R3-253184 | (BL CR to 38.300) Support for Inter-CU LTM | Nokia, Huawei, Google, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung, Ofinno |
| TDoc | Title | Source |
|---|---|---|
| R3-253008 | LS on the support of semi-persistent CSI-RS resource for LTM CSI acquisition for candidate cells | RAN1(Fujitsu) |
| R3-253009 | LS on RAN2 agreements for security key handling in inter-CU LTM | RAN2(ZTE) |
| R3-253136 | TP (BL CR TS 38.300, TS 38.401, TS 38.473, TS 38.423) Remaining issues on Inter-CU LTM procedure | Nokia |
| R3-253137 | Discussion on Inter-CU LTM with Dual Connectivity | Nokia |
| R3-253198 | (TP to BL CR for TS 38.423 and 38.473 on Inter-CU LTM) Rel-19 inter-CU LTM issues | NEC |
| R3-253199 | Discussion Rel-19 inter-CU LTM in DC scenario | NEC |
| R3-253249 | (TP for 38.423, 38.473, 38.401, 38.300) Inter-CU LTM Inter-CU LTM | ZTE Corporation |
| R3-253250 | (TP for 38.423, 37.340) SN initiate SCG LTM | ZTE Corporation |
| R3-253324 | [TP to BLCR for TS 38.401 and TS 38.423] Inter-CU LTM | Lenovo |
| R3-253325 | [TP to BLCR for TS 38.423] Inter-CU LTM in DC | Lenovo, Huawei, LG Electronics |
| R3-253365 | (TP for TS38.401) On support of inter-CU LTM | China Telecom |
| R3-253366 | Discussion on inter-CU LTM in DC scenario | China Telecom |
| R3-253468 | Discussion for general issues in Inter-CU LTM | CATT |
| R3-253469 | (TP for 37.340) Discussion for Inter-CU LTM in DC | CATT |
| R3-253482 | Further discussion on inter-CU LTM | Ericsson |
| R3-253483 | (TP for LTM BL CR for TS 38.423, TS 38.473, TS 38.300, TS 37.340) – Support for inter-CU LTM | Ericsson |
| R3-253518 | Data forwarding for Inter-CU LTM DC scenarios | Ofinno, LLC |
| R3-253519 | (TP for TS 38.423) Xn Support for Data forwarding for Inter-CU LTM DC scenarios | Ofinno, LLC |
| R3-253520 | Open Issues on SN initiated inter-CU SCG LTM | Ofinno, LLC |
| R3-253526 | (TP to BL CRs 38.300 and 37.340) Clarification on RS configuration and CSI Resource Configuration | |
| R3-253527 | (TP to BL CR 38.423) Clarification on RS configuration and CSI Resource Configuration for MCG LTM | |
| R3-253528 | (TP to BL CR 38.423) Clarification on RS configuration and CSI Resource Configuration for SCG LTM | |
| R3-253554 | gNB-DU initiated LTM resource reconfiguration | Rakuten Mobile, Qualcomm Inc, NTT Docomo Inc |
| R3-253561 | Signalling enhancements for Inter-CU LTM handover | Qualcomm India Pvt Ltd |
| R3-253599 | (TP for LTM BLCR for TS38.473, TS38.300): Further discussion on inter-CU LTM procedure | Huawei |
| R3-253600 | (TP for LTM BLCR for TS38.423): Essential updates to XnAP BLCR | Huawei |
| R3-253654 | Discussion on inter-gNB-CU LTM | Samsung |
| R3-253655 | (TP to BLCR for TS38.423 and TS38.473) Inter-gNB-CU LTM | Samsung |
| R3-253659 | (TP for NR_Mob_Ph4 TS 38.423 and TS 38.473) Discussions on remaining issues related to Inter-CU LTM security | LG Electronics Inc. |
| R3-253660 | Discussions on the remaining aspects of Inter-CU LTM | LG Electronics Inc. |
| R3-253676 | Discussion on inter-CU LTM for non-DC and DC cases | NTT DOCOMO INC.. |
| R3-253697 | Discussion on inter-CU LTM | CMCC |
| R3-253710 | Support for Semi-persistent CSI-RS transmission | Ericsson, Nokia, LG Electronics, Google, Jio Platforms |
| R3-253711 | (TP to BL CR for TS 38.423) Xn support for Semi-persistent CSI-RS transmission | Ericsson, Nokia, LG Electronics, Google, Jio Platforms |
| R3-253712 | (TP to BL CR for TS 38.473) F1 support for Semi-persistent CSI-RS transmission | Ericsson, Nokia, LG Electronics, Google, Jio Platforms |
| R3-253713 | PRACH resources for RACH-less LTM | Ericsson, NTT DoCoMo, Lenovo, Jio Platforms, Verizon Wireless, Charter Communications |
| R3-253714 | (TP to BL CR for TS 38.423) PRACH Resources for RACH-less LTM | Ericsson, NTT DoCoMo, Lenovo, Jio Platforms, Verizon Wireless, Charter Communications |
| R3-253715 | (TP to BL CR for TS 38.473) PRACH Resources for RACH-less LTM | Ericsson, NTT DoCoMo, Lenovo, Jio Platforms, Verizon Wireless, Charter Communications |
| TDoc | Title | Source |
|---|---|---|
| R3-253138 | TP (BL CR TS 38.473, BL CR TS 38.401) Conditional LTM in split architecture | Nokia |
| R3-253200 | (TP to BL CR for TS 38.401 and 38.473 on conditional intra-CU LTM) Discussion of Rel-19 intra-CU Conditional LTM | NEC |
| R3-253251 | (TP for 38.473, 38.401) Conditional intra-CU LTM | ZTE Corporation |
| R3-253326 | [TP to BLCR for TS 38.401] Conditional intra-CU LTM | Lenovo |
| R3-253367 | (TP to TS38.401) On support of intra-CU Conditional LTM | China Telecom |
| R3-253470 | (TP to 38.473)Discussion for C-LTM | CATT |
| R3-253484 | (TP to CLTM BL CR for TS 38.473, TS 38.401) – Further discussion on Intra-CU Conditional LTM | Ericsson |
| R3-253562 | Signalling enhancements for Intra-CU Conditional LTM | Qualcomm India Pvt Ltd |
| R3-253601 | (TP for LTM BLCR for TS38.473, TS38.401): Discussion on intra-CU conditional LTM | Huawei |
| R3-253656 | Continue\tdiscussion on Intra-CU Conditional LTM | Samsung |
| R3-253661 | (TP for NR_Mob_Ph4 TS 38.473) Discussions on the remaining aspects of Conditional Intra-CU LTM | LG Electronics Inc. |
| TDoc | Title | Source |
|---|---|---|
| R3-253093 | (BL CR to 38.300) Support for Regenerative Payload and MBS broadcast in NR NTN | Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei, Dish Networks, Echostar, Eutelsat Group, Xiaomi, Samsung, CMCC, LG Electronics, NEC, Lenovo, ETRI |
| R3-253094 | (BL CR to 38.410) Introduce NG Removal procedure | CMCC, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Qualcomm, Xiaomi, LG Electronics, China Telecom, Samsung, ZTE, NEC, ETRI |
| R3-253095 | Support for Regenerative Payload and MBS broadcast in NR NTN | CATT, Thales, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Qualcomm, Samsung, Xiaomi, CMCC, China Telecom, Jio, LG Electronics, NEC, ETRI, SES, ESA |
| TDoc | Title | Source |
|---|---|---|
| R3-253220 | Discussion on NR NTN leftover Issues | NEC |
| R3-253235 | Remaining issues for NR NTN | ZTE Corporation |
| R3-253236 | (TP to BL CR 38.300) Clarification on NG Removal | ZTE Corporation |
| R3-253237 | (TP to BL CR for 38.413) Support of regenerative payload | ZTE Corporation, CATT, Samsung, NEC, CMCC |
| R3-253265 | (TP for TS 38.300) Discussion on Hard FLSO in NR NTN Regenerative Payload | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Xiaomi, China Telecom, LG Electronics |
| R3-253284 | Further discussion on support of regenerative payload for NR NTN | Samsung |
| R3-253291 | Discussion on the remaining issues to support regenerative payload | CATT |
| R3-253292 | (TP to BL CR for TS38.300) Support for Regenerative Payload | CATT, ZTE Corporation, Samsung, CMCC, NEC |
| R3-253378 | (TP for TS 38.300) Support of regenerative payload | Xiaomi |
| R3-253379 | (Draft LS out) Support of NG transmission suspend resume | Xiaomi |
| R3-253384 | Further discussion on Support of NTN Regenerative payload | China Telecom |
| R3-253392 | (TP to BL CR for TS 38.413) Enhancement to support hard FLSO | Nokia, Nokia Shanghai Bell, Qualcomm, Xiaomi, China Telecom, LG Electronics |
| R3-253453 | On NG Suspension for Hard Feeder Link Switch | Ericsson, Thales, Huawei, Jio Platforms Limited, ESA |
| R3-253544 | (TP to BL CR for TS 38.300 and 38.413) Discussion on Suspend/Resume for hard FLSO and the interface management | Huawei, Ericsson |
| R3-253545 | (TP to BLCR for TS 38.413) Further discussion of MBS broadcast service and mapped cell and TAI pre-reconfiguration | Huawei |
| R3-253573 | Discussion on Hard Feeder Link Switchover | ETRI, Huawei, Ajou University |
| R3-253609 | Further Discussion on Support of NTN Regenerative Architecture | TCL |
| R3-253662 | OAM requirement for NG management | LG Electronics Inc., Nokia, Nokia Shanghai Bell |
| R3-253663 | (TP for NR_NTN_Ph3 TS 38.300 BL CR) OAM for NG management | LG Electronics Inc., Nokia, Nokia Shanghai Bell |
| R3-253732 | Discussion on support of regenerative payload for NR NTN | CSCN |
| TDoc | Title | Source |
|---|---|---|
| R3-253007 | Reply LS on maximum warning message size | CT4(CICT Mobile) |
| R3-253133 | (BL CR to 36.300) Support of full eNB as regenerative payload and Store&Forward mechanism for IoT NTN | ZTE Corporation, Samsung, CMCC, CATT, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Xiaomi, Qualcomm |
| R3-253134 | (BL CR to 36.410) Support of Full eNB as Regenerative payload | Samsung, Ericsson, Sateliot, Thales, ESA, Deutsche Telekom, Jio Platforms Limited, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-253135 | (BL CR to 36.413) Support of Full eNB as Regenerative Payload | Huawei, Ericsson, Thales, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, Xaomi, CATT, Samsung, Jio Platforms |
| R3-253238 | Updated Work Plan for IoT NTN | ZTE Corporation, CATT, MediaTek.Inc |
| TDoc | Title | Source |
|---|---|---|
| R3-253239 | (TPs to BL CR for 36.300 and 36.413) Remaining issues for IoT NTN | ZTE Corporation |
| R3-253240 | Support of Store and Forward satellite operation | ZTE Corporation, Samsung, CMCC, NEC, CATT, Xiaomi |
| R3-253266 | Discussion on Support for IoT NTN for Regenerative Payload | Qualcomm Incorporated |
| R3-253267 | (TP for TS 36.300) Align with NR NTN on Hard FLSO for IoT NTN | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Xiaomi, China Telecom, CATT, LG Electronics |
| R3-253285 | Further discussion on support of regenerative payload for IoT NTN | Samsung |
| R3-253383 | (TP for TS 36.300) Support of full eNB as regenerative payload | Xiaomi |
| R3-253385 | Further discussion on support of S&F in IoT NTN | China Telecom |
| R3-253393 | Discussion on the support of S&F and regenerative architecture | Nokia, Nokia Shanghai Bell |
| R3-253394 | (TP to BL CR for TS 36.413) Align with NR NTN on FLSO | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Xiaomi, China Telecom, LG Electronics, CATT |
| R3-253471 | Discussion about IoT NTN | CATT |
| R3-253536 | On S1 Suspension for Hard Feeder Link Switch | Ericsson, Jio Platforms Limited, Huawei |
| R3-253546 | (TP for TS 36.300) Support of Full eNB as Regenerative Payload - TNL & UP aspetcs | Huawei, Ericsson, CATT |
| R3-253547 | (TP for TS 36.300) Support of Full eNB as Regenerative Payload - General issues and LS response to SA2 | Huawei |
| R3-253595 | Add support for S1 context Suspend/Resume procedures in LTE/NTN (Store-and-Forward) | Jio Platforms Ltd (JPL) |
| R3-253596 | Add support for S1 context Suspend/Resume procedures in LTE/NTN (Store-and-Forward) | Jio Platforms Ltd (JPL) |
| R3-253688 | (TP to BLCR for 36.300 and 36.413) Introduce indicator for S1 suspend/resume | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-253096 | (BL CR to 38.300) Introduction of Ambient IoT | CMCC, Huawei, Nokia |
| R3-253097 | (BL CR to 38.401) Introduction of Ambient IoT | Ericsson, Huawei, Nokia |
| R3-253098 | (BL CR to 38.410) Introduction of Ambient IoT | ZTE Corporation, China Telecom, Huawei, Samsung, CMCC, Nokia, Xiaomi |
| R3-253099 | (BL CR to 38.412) Introduction of Ambient IoT | Xiaomi, Huawei, Nokia |
| R3-253100 | (BL CR to 38.413) Introduction of Ambient IoT | Huawei, Nokia |
| TDoc | Title | Source |
|---|---|---|
| R3-253015 | LS Reply on Ambient IoT progress of RAN3 | SA2(NEC) |
| R3-253016 | LS on the removal of service type information | SA2(Interdigital) |
| R3-253017 | LS on AIoT device identifier length | SA2(Huawei) |
| R3-253022 | Reply LS on Ambient IoT progress of RAN3 | SA5(Huawei) |
| R3-253029 | LS on paging ID length | RAN2(CATT) |
| R3-253030 | LS on byte-alignment of upper layer data SDU | RAN2(vivo) |
| R3-253031 | LS on D2R message size for inventory response | RAN2(Interdigital) |
| R3-253139 | Interface management procedures for A-IoT | Qualcomm Incorporated |
| R3-253140 | NG signaling to support Inventory and Command procedures for A-IoT | Qualcomm Incorporated |
| R3-253177 | Consideration on leftovers for Inventory and Command | Huawei |
| R3-253178 | (TPs for TS 38.300 38.401 38.413 BL CRs) Leftovers for Inventory and Command | Huawei |
| R3-253179 | (TPs for 38.300 38.410 38.413 38.412 BL CRs) Leftovers for Interface Management | Huawei |
| R3-253180 | (TPs for TS 38.300 38.410 38.413 BL CRs) The Release of A-IoT Session | Huawei |
| R3-253181 | [DRAFT] Reply LS on on Ambient IoT progress of RAN3 (Reply to S5-251771) | Huawei [to be RAN3] |
| R3-253217 | Discussion on the New A-IoT Area | NEC |
| R3-253218 | Draft LS A-IoT Supported Area | NEC |
| R3-253219 | Discussion on A-IoT Leftover Issues | NEC |
| R3-253227 | Resolution of open points and new signalling for Inventory | Nokia |
| R3-253228 | [TP for AIoT BL CR for TS 38.413] Resolution of open points and new signalling for Inventory | Nokia |
| R3-253229 | [TP for A-IoT BL CR 38.300] Identification of target A-IoT devices | Nokia |
| R3-253230 | [TP for AIoT BL CR for TS 38.413] Identification of target A-IoT devices | Nokia |
| R3-253245 | Discussion on Leftover issues on AIoT | ZTE Corporation, China Telecom |
| R3-253246 | (TP for BL CR to 38.412, 38.300, 38.410, 38.412, 38.401) Leftover issues on AIoT | ZTE Corporation, China Telecom |
| R3-253247 | ((TP for BL CR 38.413) New A-IoT procedures | ZTE Corporation, China Telecom |
| R3-253248 | (TP to BL CR 38.300, 38.410) New A-IoT procedures | ZTE Corporation, China Telecom |
| R3-253274 | [TP for BL CR 38.300, 38.401] on stage 2 related topics | Ericsson |
| R3-253275 | [TP for BL CR 38.412 and 38.413] Discussions on NG-C signalling transport for A-IoT | Ericsson |
| R3-253276 | [TP for BL CR 38.413] On NGAP NG-C interface management functions for A-IoT | Ericsson |
| R3-253277 | [TP for BL CR 38.413 and 38.410] A-IoT Session related topics | Ericsson |
| R3-253286 | (TP to BL CR for 38.413) Discussion on general issues for AIoT | Samsung |
| R3-253287 | (TP to BL CR for 38.300) Discussion on inventory and command related issues for AIoT | Samsung |
| R3-253288 | (TP to BL CR for 38.401) Discussion on device associations for AIoT | Samsung |
| R3-253293 | (TP to BL CR for TS38.413 and TS38.300) Consideration on A-IoT area | CATT |
| R3-253294 | (TP to BL CR for TS38.413 and TS38.300) A-IoT Inventory procedures | CATT |
| R3-253295 | (TP to BL CR for TS38.413 and TS38.300) A-IoT Command procedures | CATT |
| R3-253327 | Discussion on Open issues for A-IoT procedures | Lenovo |
| R3-253374 | (TP for 38.413) General aspects on support of AIoT | Xiaomi |
| R3-253375 | (Draft reply LS) Discussion on the liaisons from RAN2 SA2 | Xiaomi |
| R3-253376 | (TP for TS 38.300 and TS 38.413) Device context handling | Xiaomi |
| R3-253386 | Discussion on architecture and interface management for Ambient IoT | China Telecom |
| R3-253664 | AIoT supportable NGAP Interface Management | Tejas Network Limited |
| R3-253665 | Enhancement of Inventory/Command procedure | Tejas Network Limited |
| R3-253673 | Discussion on Inventory Procedures | China Unicom |
| R3-253674 | Discussion on Command Procedure | China Unicom |
| R3-253677 | Discussion on remaining open issues in A-IoT | LG Electronics |
| R3-253692 | (TP to TS 38.300) Discussion on RAN Architecture for Ambient IoT | CMCC |
| R3-253693 | Discussion on Inventory Procedure and Signaling | CMCC |
| R3-253694 | Discussion on Command Procedure and Signalling | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-253141 | Locating A-IoT devices and Proximity Determination | Qualcomm Incorporated |
| R3-253296 | Further Consideration on locating of A-IoT device | CATT |
| R3-253377 | (TPs for TS 38.300 and TS 38.413) location of the device | Xiaomi |
| R3-253695 | Discussion on A-IoT device location reporting | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-253005 | Reply LS on paging enhancement in R19 NES | CT1(Huawei) |
| R3-253101 | (BL CR to 38.300) Introduction of Network Energy Saving Enhancement | CATT, Ericsson, Huawei, Samsung, China Telecomm, Rakuten, ZTE, CMCC, Lenovo, Deutsche Telekom, Nokia |
| R3-253102 | Introduction of Network Energy Saving Enhancement | Ericsson, Huawei, CMCC, Samsung, Qualcomm, Nokia, ZTE, Lenovo, Deutsche Telekom, NEC |
| R3-253103 | (BL CR to 38.470) Introduction of Network Energy Saving Enhancement | Samsung, Huawei, NEC, CATT, ZTE, Ericsson |
| R3-253104 | (BL CR to 38.473) Introduction of Network Energy Saving Enhancement | Huawei, Ericsson, CMCC, Samsung, ZTE, Nokia, Deutsche Telekom, Lenovo, NEC, Jio |
| R3-253171 | BL CR to 38.401 on Introduction of Network Energy Saving Enhancement | Qualcomm Inc. |
| R3-253551 | WI Work plan for R19 Network Energy Savings | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-253209 | (TP to BLCR TS38.473) Support on-demand SSB | NEC |
| R3-253241 | (TP to BL CR for 38.473) Further discussion on on-demand SSB Scell operation | ZTE Corporation |
| R3-253258 | (TP to BLCR for TS 38.473 and TS 38.470) Discussion on on-demand SSB SCell operation | Huawei |
| R3-253306 | (TP for BLCRs to 38.423, 38.473) On support of OD-SSB | CATT |
| R3-253328 | Discussion on On-demand SSB for SCell | Lenovo |
| R3-253362 | (TP to 38.473) On support on-demand SSB SCell operation | China Telecom |
| R3-253532 | Open points on OD-SSB. Adaptation of common signals/channels | Nokia |
| R3-253549 | On-demand SSB SCell operation | Ericsson |
| R3-253639 | Discussion on on-demand SSB SCell operation in low-carbon green network | Samsung |
| R3-253671 | Discussion on On-Demand SSB SCell Operation | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-253172 | (TP to BL CR 38.401) Stage-2 procedures for OD SIB1 | Qualcomm Inc. |
| R3-253210 | Support on-demand SIB1 | NEC |
| R3-253242 | (TP to BL CR for 38.423) Further discussion on on-demand SIB1 | ZTE Corporation |
| R3-253243 | Introduction of Network Energy Saving Enhancement | ZTE Corporation, Samsung, Lenovo |
| R3-253259 | (TP to BLCR for TS 38.473 and TS 38.423) Discussion on on-demand SIB1 for UEs in idle or inactive mode | Huawei |
| R3-253307 | (TP for BLCR to F1AP) On support of OD-SIB1 for idle UE | CATT |
| R3-253329 | (TP to BL CR 38.423) Discussion on On-demand SIB1 for Idle/Inactive UE | Lenovo |
| R3-253363 | On support on-demand SIB1 | China Telecom |
| R3-253533 | (TP for BLCR to TS 38.423) Message definitions for inter-node signalling for On-Demand SIB1 | Nokia |
| R3-253539 | Xn impact of On-demand SIB1 for UEs in idle/inactive mode | Ericsson, Deutsche Telekom, China Unicom, Jio Platforms |
| R3-253548 | F1 impact of On-demand SIB1 for UEs in idle/inactive mode | Ericsson, Deutsche Telekom, China Unicom, Jio Platforms, China Telecom |
| R3-253640 | Discussion on on-demand SIB1 in low-carbon green network | Samsung |
| R3-253672 | (TPs to BL CRs) Support On-Demand SIB1 for UEs | CMCC |
| R3-253721 | End-to-End Xn and F1 Signalling to support OD-SIB1 | Rakuten Mobile, Inc |
| TDoc | Title | Source |
|---|---|---|
| R3-253407 | Further discussion on common signal adaptation | Huawei, NEC, CATT, CMCC |
| R3-253550 | Adaptation of common signal/channel transmissions | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-253105 | (BL CR to 38.300) Introduction of low-power wake-up signal and receiver for NR | vivo, NTT DOCOMO INC., Nokia, Samsung, Ericsson, ZTE, CATT, Huawei |
| R3-253106 | (BL CR to 38.413) Introduction of low-power wake-up signal and receiver for NR | ZTE Corporation, Nokia, Samsung, Ericsson, Huawei, CATT, NTT |
| R3-253107 | (BL CR to 38.423) Introduction of low-power wake-up signal and receiver for NR | Ericsson, Vivo, NTT Docomo, Huawei, ZTE, Nokia, Samsung, CATT |
| R3-253108 | (BL CR to 38.470) Introduction of low-power wake-up signal and receiver for NR | Nokia, Samsung, ZTE, Ericsson, Huawei, CATT |
| R3-253109 | (BL CR to 38.473) Introduction of low-power wake-up signal and receiver for NR | Huawei, Nokia, Samsung, Ericsson, CATT, ZTE, Vivo, NTT DOCOMO INC. |
| TDoc | Title | Source |
|---|---|---|
| R3-253012 | Reply LS on paging capability loss issue | RAN2(Huawei) |
| R3-253026 | LS on LP-WUS subgrouping progress | RAN2(NEC) |
| R3-253173 | Support LP-WUS subgrouping in RRC_IDLE/RRC_INACTIVE | Qualcomm Inc. |
| R3-253215 | Discussion on LP-WUS UE-ID | NEC |
| R3-253216 | Reply LS on LP-WUS subgrouping progress | NEC |
| R3-253231 | Conclusions for LP-WUS open points | Nokia |
| R3-253232 | [TP for BL CR LP-WUS TS 38.423] Further Extension of UE Identity Index Value for LP-WUS | Nokia, Ericsson, Huawei, ZTE, Vivo, CATT, NTT Docomo |
| R3-253233 | [TP for BL CR LP-WUS TS 38.423] Resolution of LP-WUS open points | Nokia |
| R3-253255 | (TP to BLCR for TS 38.413, TS 38.423 and TS 38.300) Discussion on Low-power wake-up signal and receiver for NR | Huawei |
| R3-253256 | (TP to BLCR for TS 38.473) Discussion on Low-power wake-up signal and receiver for NR | Huawei |
| R3-253257 | (TP to BLCR for TS 38.473) Addition of Further Extended UE Identity Index Value | Huawei, Ericsson, Nokia, ZTE, vivo, CATT, Qualcomm Inc, NTTDOCOMO, INC. |
| R3-253308 | Potential impacts of LP-WUS | CATT |
| R3-253309 | (TP for BLCR to 38.410) Introduction of LP-WUS | CATT, Nokia, Ericsson, Huawei, Vivo, ZTE, Qualcomm, NTT Docomo |
| R3-253400 | Discussion on remaining issues for LP-WUS | ZTE Corporation |
| R3-253401 | [draft] Reply LS on LP-WUS subgrouping | ZTE Corporation, Huawei, Nokia, Ericsson, vivo, CATT |
| R3-253457 | Discussion on remaining aspects on LP-WUS | Ericsson |
| R3-253458 | (TP for LP-WUS BL CR for TS38.413) Addition of Further Extended UE Identity Index Value | Ericsson, Huawei, Nokia, ZTE, Vivo, CATT, Qualcomm Inc., NTT DOCOMO |
| R3-253643 | [draft] Reply LS on LP-WUS subgrouping | Huawei |
| R3-253675 | Further discussion on LP-WUS | NTT DOCOMO INC.. |
| R3-253690 | Discussion on supporting LP-WUS Indicating Paging Monitoring | CMCC |
| R3-253739 | (TP to TS 38.413, 38.420) on support of LP-WUS | ZTE Corporation |
| R3-253746 | Response to R3-253255 | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-253110 | (BL CR for 38.300) introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD) | Ericsson, Huawei, Samsung, Qualcomm, ZTE, Huawei, CATT, Nokia, CMCC, LGE |
| R3-253111 | (BL CR to 38.401) introduction of Evolution of NR duplex operation | ZTE Corporation, Ericsson, Samsung, Qualcomm, Huawei, CATT, Nokia, CMCC, LGE |
| R3-253112 | (BL CR to 38.420) introduction of Evolution of NR duplex operation | CMCC, Ericsson, Huawei, Samsung, ZTE, Nokia |
| R3-253113 | (BL CR to 38.423) introduction of Evolution of NR duplex operation | Huawei, China Telecom, China Unicom, China Mobile, Ericsson, Qualcomm, Samsung, ZTE Corporation, LG Electronics, Nokia, Jio Platforms (JPL), CATT |
| R3-253114 | (BL CR to 38.470) introduction of Evolution of NR duplex operation | CATT, Ericsson, CMCC, Nokia, ZTE, Qualcomm, Samsung |
| R3-253115 | (BL CR to 38.473) introduction of Evolution of NR duplex operation | Samsung, Huawei, Ericsson, ZTE, LG Electronics Inc., Nokia, Qualcomm |
| TDoc | Title | Source |
|---|---|---|
| R3-253028 | LS on simultaneous configuration of SBFD and DC | RAN2(Huawei) |
| R3-253222 | Discussion on CLI Handling Support | NEC |
| R3-253443 | Discussion on Evolution of Duplex Operation | CATT |
| R3-253444 | (TP for 38.423 and 38.473) Support additional RACH configuration for SBFD | CATT |
| R3-253480 | Discussion on RAN3 impacts to support enhancements for CLI handling for SBFD | Ericsson, Jio Platforms, |
| R3-253481 | (TP to BLCR for 38.423 and 38.473) CLI Mitigation Solution in RAN3 | Ericsson, Jio Platforms, |
| R3-253534 | (TP for BLCRs to TS 38.300, 38.401, 38.420, 38.470) Stage 2 updates for Sub-band Full Duplex operation | Nokia |
| R3-253535 | (TP for BLCRs to TS 38.423, 38.473) Stage 3 updates for Sub-band Full Duplex operation | Nokia |
| R3-253563 | Signaling design to enable NR SBFD operation | Qualcomm Incorporated |
| R3-253597 | Introduction of dynamic CLI Mitigation procedure | Jio Platforms |
| R3-253607 | Discussion on Support for Cross-Link Interference (CLI) Handling | Jio Platforms Limited (JPL) |
| R3-253650 | Further discussion on information exchange for CLI handling | Samsung |
| R3-253651 | Text proposals to BLCRs of TS38.423 & TS38.473 on CLI handling | Samsung |
| R3-253689 | (TPs to BLCR for 38.423 and 38.473) Discussion on supporting CLI handling in SBFD | CMCC |
| R3-253700 | Discussion on information exchange between gNBs for SBFD | LG Electronics Inc. |
| R3-253701 | (TP for NR_duplex_evo-Core for TS 38.423) Discussion on information exchange between gNBs for SBFD | LG Electronics Inc. |
| R3-253703 | Further discussion on remaining open issues for SBFD | Huawei, China Telecom, China Unicom |
| R3-253704 | (TP to BL CR for 38.423 and 38.420) introduction of Evolution of NR duplex operation Sub-band full duplex (SBFD) | Huawei |
| R3-253705 | (TP to BL CR for 38.401) introduction of Evolution of NR duplex operation Sub-band full duplex (SBFD) | Huawei, China Telecom, China Unicom |
| R3-253706 | (TP to BL CR for 38.473 and 38.470) introduction of Evolution of NR duplex operation Sub-band full duplex (SBFD) | Huawei |
| R3-253726 | (TP for BLCR 38.423&473) SBFD | ZTE Corporation |
| R3-253727 | Discussion on information exchange for SBFD | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R3-253116 | (BL CR to 38.305) Introduction of AI/ML air | CATT, Ericsson, Nokia, Huawei, Xiaomi, ZTE, CMCC, Samsung, CEWiT |
| R3-253117 | (BL CR to 38.455) Introduction of AI/ML air | Ericsson |
| R3-253330 | Discussion on OAM centric data collection and non-OTA based dataset parameter sharing | Lenovo |
| R3-253522 | [Draft LS] Discussion on Relpy LSs from RAN2 | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R3-253010 | Reply LS on signalling feasibility of dataset and parameter sharing | RAN2(Xiaomi) |
| R3-253011 | LS on OAM-centric solution for NW-side data collection | RAN2(Huawei) |
| R3-253145 | (TP to BL CR for TS 38.455 and TS 38.305) Support of "Channel Measurement" for Case 3b and Stage 2 Support for Case 3a/3b | Qualcomm Incorporated |
| R3-253146 | Discussion on LS Response for R3-253010 and R3-253011 | Qualcomm Incorporated |
| R3-253212 | [TP for BL CR to TS 38.305 & TS 38.455] Discussion on AI/ML for positioning | NEC |
| R3-253213 | Discussion on dataset collection and sharing | NEC |
| R3-253261 | Further Discussions on Case 3a and Case 3b | CEWiT |
| R3-253297 | (TP to BL CR for TS38.305) RAN3 inputs for UE-based AI positioning | CATT, ZTE Corporation |
| R3-253298 | (TP to BL CRs) Support of gNB-based AI positioning | CATT |
| R3-253331 | AIML for gNB assisted positioning | Lenovo |
| R3-253368 | Discussion on support of AI/ML assisted positioning (Case 3a) | China Telecom |
| R3-253369 | (TP to TS38.305) On support of AIML assisted positioning | China Telecom |
| R3-253380 | (Draft LS out) Reply LS on signalling feasibility of dataset and parameter sharing | Xiaomi, MediaTek, Qualcomm Incorporated, Huawei, Apple, China Mobile |
| R3-253381 | (TPs for TS 38.305 and TS 38.455)Support of gNB-side model (case 3a) | Xiaomi |
| R3-253382 | (TP for TS 38.473) Support of Sample-based measurement (case 3b) | Xiaomi, Ericsson, ZTE, CATT, Samsung, Nokia |
| R3-253459 | Discussion on RAN2 LSs on AI/ML Data collection | Ericsson |
| R3-253460 | Reply LS on signalling feasibility of dataset and parameter sharing | Ericsson |
| R3-253461 | (TP for TS 38.455) Support of Sample-based measurement (case 3b) | Ericsson, Xiaomi, CATT, Nokia |
| R3-253462 | (TP for TS 38.455) Support of data collection procedure (case 3a) | Ericsson |
| R3-253504 | [DRAFT] Reply LS on OAM-centric solution for NW-side data collection | Huawei |
| R3-253505 | (TPs for AI/ML BLCR to TS 38.305, TS 38.455 and TS 38.413) Discussion on RAN3 impacts for NG-RAN node-assisted AI/ML positioning (Case 3a) | Huawei |
| R3-253506 | (Draft Reply LS to RAN2’s R3-253010 & TP for AI/ML BLCR to TS 38.455) Discussion on RAN2 LS on signalling feasibility of dataset and parameter sharing & RAN3 impacts for Direct AI/ML positioning (Case 3b) | Huawei |
| R3-253523 | [TP to 38.455] Support of AI/ML assisted Positioning (case 3a) | ZTE Corporation |
| R3-253524 | (TP to TS 38.401) Support of AI/ML assisted positioning | ZTE Corporation, Xiaomi, CATT, Ericsson |
| R3-253592 | (TP to TS 38.300) Stage 2 for case 3a | Nokia, CATT, Xiaomi, Ericsson, CMCC |
| R3-253593 | (TP to TS 38.305, TP to TS 38.455) Model Training at gNB for case 3a | Nokia |
| R3-253594 | Replying to R3-253011 and R3-253010 LSs from RAN2 | Nokia |
| R3-253652 | Discussion on Case 3a in AI/ML for positioning | Samsung |
| R3-253653 | Discussion on Case 3b in AI/ML for positioning | Samsung |
| R3-253667 | Support Direct AI ML Positioning | CMCC |
| R3-253668 | Support Assisted AI ML Positioning | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-253118 | (BL CR to 37.340) Support of XR enhancements | ZTE Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Inc, Lenovo, Huawei, Ericsson, CATT, CMCC, Samsung, Xiaomi, NEC, China Telecom |
| R3-253119 | (BL CR to 37.483) Support of XR enhancements | CMCC, Nokia, Nokia Shanghai Bell, Huawei, CATT, Xiaomi, Ofinno, China Telecom, ZTE, Ericsson, Qualcomm, Samsung, NEC |
| R3-253120 | (BL CR to 38.300) Support of XR enhancements | Nokia, Nokia Shanghai Bell, Lenovo, Qualcomm, Xiaomi, CATT, Ericsson, CMCC, Samsung, Huawei, China Telecom |
| R3-253121 | (BL CR to 38.413) Support of XR enhancements | Lenovo, Nokia, Nokia Shanghai Bell, CMCC, China Telecom, Huawei, ZTE, Ericsson, Samsung, Qualcomm, Ofinno |
| R3-253122 | (BL CR to 38.415) Support of XR enhancements | China Telecom, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CMCC, Ericsson, Samsung |
| R3-253123 | (BL CR to 38.423) Support of XR enhancements | CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC, NEC |
| R3-253124 | (BL CR to 38.425) Support of XR enhancements | Ericsson, AT&T, BT, T-Mobile USA, Charter Communications, Qualcomm, Huawei, Nokia, Nokia Shanghai Bell,China Telecom, CMCC, ZTE, CATT |
| R3-253125 | (BL CR to 38.473) Support of XR enhancements | Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi, Nokia, Nokia Shanghai Bell, China Telecom |
| R3-253197 | (BL CR to 37.340) Support of XR enhancements | ZTE Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Inc, Lenovo, Huawei, Ericsson, CATT, CMCC, Samsung, Xiaomi, NEC, China Telecom |
| R3-253395 | Rapporteur Inputs on workplan | Nokia, Qualcomm (Rapporteurs) |
| TDoc | Title | Source |
|---|---|---|
| R3-253014 | LS reply on uplink rate control | SA2(vivo) |
| R3-253035 | LS on the accuracy of PDU Set size and data burst size indication | SA4(Qualcomm) |
| R3-253036 | LS on Indicating Time to the Next Data Burst (TTNB) | SA4(Qualcomm) |
| R3-253264 | Discussion on XR rate control | vivo |
| R3-253332 | (TP to XR BL CR for 38.473) On RLC retransmission enhancements | Lenovo |
| R3-253333 | Discussion on Uplink Bit Rate Control | Lenovo |
| R3-253348 | (TP for XR BL CR for TS 38.473) Support of UL rate control | Huawei |
| R3-253349 | (TP for XR BL CRs) Discussion on the miscellaneous issues for XR | Huawei |
| R3-253396 | Discussion on the remaining issues of Rel-19 XR | Nokia, Nokia Shanghai Bell |
| R3-253397 | (TP to BL CR for TS 38.415, TS 38.425 and TS 38.413) Update for BSSize/TTNB and available data rate exposure | Nokia, Nokia Shanghai Bell |
| R3-253445 | Disccsion on NR XR Enhancements for others | CATT |
| R3-253446 | (TP for XR BL CR to 38.413) Support of XR enhancements | CATT |
| R3-253463 | (TP for XR BL CR for TS38.413) Support of PDU Set AQP | Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell |
| R3-253464 | Discussion on XR UL bit rate control | Ericsson |
| R3-253465 | [TP to XR BL CR for 38.413] RAN activation and support of Available data rate reporting | Ericsson, China Telecom |
| R3-253521 | Support of Uplink Rate Control for XR | Ofinno, LLC |
| R3-253564 | R19 XR Signaling Enhancements | Qualcomm Incorporated |
| R3-253617 | (TP for XR BL CR for TS 38.300) Support of UL rate control | Huawei, CMCC, China Telecom |
| R3-253641 | Discussion on other aspects for NR XR enhancements | Samsung |
| R3-253642 | (TP to BLCR for TS 38.473) NR XR enhancements | Samsung |
| R3-253666 | Discussion on Rate Control for XR | China Telecom |
| R3-253669 | Support of Exposure of Available Data Rate in Non-Homogeneous Deployment | CMCC |
| R3-253670 | Support of Uplink Congestion Signaling | CMCC |
| R3-253702 | Discussion on XR RAN Awareness and UL Rate Control | Meta |
| R3-253728 | Further discussion on XR uplink rate control with LS and TP to BLCR for 38473 | ZTE Corporation |
| R3-253729 | [TP to XR BL CR for 38.420] Dynamic traffic characteristics change | ZTE Corporation, Ericsson, CMCC, Nokia, Nokia Shanghai Bell, China Telecom, Qualcomm |
| R3-253730 | [TP to XR BL CR for 38.470] Dynamic traffic characteristics change | ZTE Corporation, Ericsson, CMCC, Nokia, Nokia Shanghai Bell, China Telecom, Qualcomm |
| R3-253731 | [TP for XR BL CRs to 38.413, 38.423, 38.473, 37.483, 38.415, 38.425] Discussion on Rel-19 XR enhancement with ultimate all in one TP | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R3-253126 | (BL CR to 38.401) Support of Multi-hop relay | LG Electronics Inc., ZTE, Nokia, Nokia Shanghai Bell, Ericsson, FirstNet, Huawei |
| R3-253127 | (BL CR to 38.413) Support of Multi-hop relay | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, LG Electronics, NEC, CATT, InterDigital, Samsung, ZTE, FirstNet, NIST |
| R3-253128 | (BL CR to 38.423) Support of Multi-hop relay | Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, Huawei, NEC, CATT, InterDigital, Samsung, ZTE, FirstNet, NIST |
| R3-253129 | (BL CR to 38.470) Support of Multi-hop relay | ZTE Corporation, Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell |
| R3-253130 | (BL CR to 38.473) Support of Multi-hop relay | Huawei, LG Electronics, Nokia, Nokia Shanghai Bell, NEC, CATT, Ericsson, Samsung, ZTE, Interdigital, FirstNet |
| TDoc | Title | Source |
|---|---|---|
| R3-253147 | (TP for TS 38.401 and 38.473) Support of Multi-hop relay | LG Electronics, FirstNet |
| R3-253148 | Discussion on service continuity in Multi-hop relay | LG Electronics, FirstNet |
| R3-253289 | Further discussion on multi-hop for SL relay | Samsung |
| R3-253290 | (TP to BL CR for 38.473) Support of multi-hop relay | Samsung |
| R3-253360 | (TP for 38.401) Multi-hop relay | Huawei |
| R3-253361 | (TP for 38.473) Multi-hop relay | Huawei |
| R3-253398 | Discussion on the support of multi-hop Layer-2 UE-to-Network relay | Nokia, Nokia Shanghai Bell |
| R3-253399 | (TP to BL CR for TS 38.401) update on ENs and protocol stack for multi-hop architecture | Nokia, Nokia Shanghai Bell |
| R3-253402 | Discussion on support of multi-hop SL relay | ZTE Corporation |
| R3-253447 | (TP for SL Relay 38.401) Support on Multi-hop U2N relay in stage 2 | CATT |
| R3-253448 | (TP for SL Relay 38.473) Support on Multi-hop U2N relay in stage 3 | CATT |
| R3-253556 | (TP to BL CR for TS 38.401) Stage-2 Updates for SL Multi-hop | Ericsson |
| R3-253557 | (TP to BL CR for TS 38.473) F1 support for SL Multi-hop | Ericsson |
| R3-253608 | Support of Enhanced Multi-Hop Layer-2 UE-to-Network Relay | Jio |
| R3-253616 | Bulk Multi-Hop Relay Configuration for NR Sidelink Relay | Jio Platforms Limited(JPL) |
| R3-253740 | (TP to TS 38.401, 38.473, 38.470) on support of multi-hop relay | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R3-253182 | Consideration on LTE-based 5G Broadcast Phase 2 | Huawei |
| R3-253183 | Introduction of LTE-based 5G Broadcast Phase 2 | Huawei |
| R3-253253 | Discussion on LTE-based 5G Broadcast | ZTE Corporation |
| R3-253254 | TPs for Signalling Support of LTE-based 5G Broadcast | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R3-253334 | Discussion on the PDCP SN gap report handling during UE’s handover | Huawei, LG Electronics, Qualcomm, China Telecom, CATT, Xiaomi, CMCC |
| R3-253335 | Correction for PDCP SN gap report during UE's handover - Alt 1 | Huawei, LG Electronics, Qualcomm, China Telecom, Xiaomi, CMCC |
| R3-253336 | Correction for PDCP SN gap report during UE's handover - Alt 2 | Huawei, China Telecom, CATT, Xiaomi |
| R3-253454 | Correction of IoT NTN OAM Assistance Information | Ericsson, Huawei, Thales, Jio Platforms Limited |
| R3-253552 | Terminating Non-MPS-Subcribed UE Handling | Peraton Labs, CISA ECD, AT&T, Verizon, Ericsson |
| R3-253553 | Terminating Non-MPS Subscribed UE Handling | Peraton Labs, CISA ECD, AT&T, Verizon, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-253262 | Correction on HSDN Cell Information over Xn interface[ANR_HSDN] | China Telecom, ZTE Corporation, China Unicom |
| R3-253263 | Correction on HSDN Cell Information over F1 interface[ANR_HSDN] | China Telecom, ZTE Corporation, China Unicom |
| R3-253299 | Correction on HSDN Cell Information over X2 interface[ANR_HSDN] | ZTE Corporation, China Telecom, China Unicom |
| R3-253455 | E-SMLC OAM Configuration for IoT NTN - Motivation | Ericsson, Huawei, Thales, Jio Platforms Limited |
| R3-253456 | E-SMLC OAM Configuration for IoT NTN | Ericsson, Huawei, Thales, Jio Platforms Limited |
| R3-253466 | E-CID measurement enhancement [ECID_enh1] | Ericsson |
| R3-253558 | Partial Data Collection Reporting | Ericsson, InterDigital, Jio Platforms (JPL), LG Electronics, BT |
| R3-253678 | Enhancement of NR to LTE mobility restriction | NTT DOCOMO INC., Nokia, Huawei, Vodafone, CATT, LG Electronics, NEC, Fujitsu, Qualcomm, SK Telecom, Deutsche Telekom, Rakuten |
| R3-253679 | Enhancement of NR to LTE mobility restriction [Enhanced Mobility] | NTTDOCOMO, INC., Nokia, Huawei, Vodafone, CATT, LG Electronics |