TDoc | Title | Source |
---|---|---|
R3-245001 | RAN3#125-bis Meeting Agenda | RAN3 Chair |
TDoc | Title | Source |
---|---|---|
R3-245002 | RAN3#125 Meeting Report | ETSI-MCC |
TDoc | Title | Source |
---|---|---|
R3-245003 | Guidelines for RAN3 Meetings | RAN3 Chair, RAN3 Vice-Chairs |
TDoc | Title | Source |
---|---|---|
R3-245004 | TR 30.531 v1.54.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
TDoc | Title | Source |
---|---|---|
R3-245008 | L3 measurement based LTM support over F1 | RAN2(Vodafone) |
R3-245010 | Reply LS on FS_XRM Ph2 | RAN2(VIVO) |
R3-245011 | Reply to RAN3 LS on UL PSI based PDU discarding in NR-DC | RAN2(Qualcomm) |
R3-245013 | Reply LS on Rel-18 higher-layers parameter list | RAN2(Ericsson) |
R3-245016 | LS Reply on "A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies" | SA2(Huawei) |
R3-245017 | LS reply on multi-modality awareness at RAN | SA2(Huawei) |
R3-245019 | LS Reply on FS_XRM_Ph2 | SA4(Nokia) |
R3-245020 | LS on Application-Layer FEC Awareness at RAN | SA4(Qualcomm) |
R3-245022 | Reply LS on MDT configuration control in NR-DC | SA5(Ericsson) |
R3-245023 | LS on terminology definitions for AI-ML in NG-RAN | SA5(NEC) |
R3-245024 | LS reply to IETF Traffic Engineering Architecture and Signaling Working Group on "A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies" | SA5(Huawei) |
R3-245025 | LS on Number of UEs in RRC_INACTIVE state with data transmission | SA5(China Telecom) |
R3-245026 | LS reply on AI/ML for NG-RAN Energy Saving Energy Cost index | SA5(Huawei) |
R3-245027 | LS on initiation of two new Recommendations ITU-T Y.NGNe-cp_mobility: “Mobility management and control framework in NGN evolution control plane” and ITU-T Y.NGNe-cp_na: “Network attachment control framework in NGN evolution control plane” | ITU-T SG13(China Telecom) |
R3-245039 | LS on AIML data collection | RAN(Interdigital) |
R3-245044 | Discussion on L3 based L1/2 Triggered Mobility | Nokia, LG Electronics, NTT Docomo |
R3-245095 | Discussion on AIML terminology | ZTE Corporation |
R3-245096 | [Draft] Reply LS on terminology definitions for AI-ML in NG-RAN | ZTE Corporation, Qualcomm, CMCC |
R3-245110 | Discussion on UL PSI based PDU discarding in NR-DC | CMCC |
R3-245111 | Discussion on on multi-modality awareness at RAN | CMCC |
R3-245161 | Discussion on remaining issues on R18 LTM | Samsung |
R3-245165 | Discussion on LS from SA2 on multi-modality | vivo |
R3-245169 | Discussion on the LS related to XR | Nokia, Nokia Shanghai Bell |
R3-245170 | [Draft] Reply LS on multi-modality awareness at RAN | Nokia |
R3-245189 | Discussion on XR LS R3-245011 and R3-245017 | CATT |
R3-245211 | Discussion on RAN2 and SA2 LS | ZTE Corporation |
R3-245212 | (draft reply LS) Reply to RAN2 LS on UL PSI based PDU discarding in NR-DC | ZTE Corporation |
R3-245213 | (draft reply LS)Reply LS to SA2 on multi-modality awareness at RAN | ZTE Corporation |
R3-245222 | DRAFT Reply LS on L3 measurement based LTM support over F1 | Vodafone GmbH |
R3-245238 | Discussion for support L3 based LTM | CATT |
R3-245239 | Support L3 mesauement based LTM(stage3) | CATT |
R3-245240 | Support L3 mesauement based LTM(stage2) | CATT |
R3-245278 | Discussion on Draft Reply LS on multi-modality awareness at RAN (Response to S2-2409444) | NEC |
R3-245279 | (Draft) Reply LS on multi-modality awareness at RAN | NEC |
R3-245342 | [Draft]Response reply LS on MDT configuration control in NR-DC | ZTE Corporation |
R3-245343 | Correction on definition of MDT measurements collection in MR-DC | ZTE Corporation |
R3-245352 | Corrections for L3 measurement triggered LTM cell switch | |
R3-245386 | Discussion on SA2’s LS (S2-2409444) on multi-modality awareness | Huawei |
R3-245387 | [Draft] Reply LS on multi-modality awareness at RAN | Huawei |
R3-245401 | LTM interwork with L3 measurements | Nokia, NTT Docomo |
R3-245411 | Discussion on the LS reply on AI/ML for NG-RAN Energy Saving Energy Cost index | Huawei |
R3-245412 | [Draft] LS on Rel-19 Enhancements of AI/ML for NG-RAN in split architecture | Huawei |
R3-245413 | Discussion on the LS on terminology definitions for AI-ML in NG-RAN | Huawei |
R3-245435 | Discussion on incoming LSs on XR | Lenovo |
R3-245466 | Discussion on SA2 LS regarding Multimodality application and protocol impacts | Ericsson |
R3-245467 | Addition of MMSID | Ericsson |
R3-245468 | Addition of MMSID | Ericsson |
R3-245469 | Addition of MMSID | Ericsson |
R3-245470 | LS reply on multi-modality awareness at RAN | Ericsson |
R3-245512 | Regarding the LS on number of UEs in SDT | Ericsson |
R3-245563 | Triggering LTM without L1 measurements UE capability | Ericsson, Vodafone |
R3-245564 | F1 support for L3 measurements-based LTM | Ericsson, Vodafone |
R3-245565 | Stage-2 updates for L3 measurements-based LTM | Ericsson, Vodafone |
R3-245596 | Discussion on the reply LS on Terminology Definitions for AI-ML in NG-RAN | Nokia |
R3-245597 | [Draft] Reply LS on terminology definitions for AI-ML in NG-RAN | Nokia |
R3-245598 | Correction on AI/ML Terminology | Nokia |
R3-245599 | Correction on AI/ML Terminology | Nokia |
R3-245600 | Discussion on the LS reply from SA5 on AI/ML for NG-RAN Energy Saving Energy Cost Index | Nokia |
R3-245601 | [Draft] Reply LS to LS reply on AI/ML for NG-RAN Energy Saving Energy Cost index | Nokia |
R3-245622 | Discusson on the reply LS on MDT configuration control in NR-DC | Huawei |
R3-245623 | [draft] Reply LS on MDT configuration control in NR-DC | Huawei |
R3-245624 | Correction on MDT configuration control in NR-DC | Huawei |
R3-245625 | Correction on MDT configuration control in NR-DC | Huawei |
R3-245626 | Discussion on L3 measurement based LTM support over F1 | Huawei |
R3-245627 | Support of L3 measurement based LTM over F1 | Huawei |
R3-245628 | Support of L3 measurement based LTM over F1 | Huawei |
R3-245629 | Support of L3 measurement based LTM over F1 | Huawei |
R3-245630 | [draft] Repy LS on L3 measurement based LTM support over F1 | Huawei |
R3-245631 | Support of L3 measurement based LTM over F1 | Huawei |
R3-245649 | Discusson on support of L3 measurement based LTM support over F1 | ZTE Corporation |
R3-245650 | Support L3 measurement based LTM support over F1 - TS38.473 | ZTE Corporation |
R3-245651 | Support L3 measurement based LTM support over F1 - TS38.401 | ZTE Corporation |
R3-245678 | Response to R3-245342 and R3-245343 | Ericsson |
R3-245682 | Reply LS on multi-modality awareness at RAN | RAN3(Nokia) |
R3-245683 | CB:#1_AI/ML-Training | ZTE |
R3-245684 | Reply LS on MDT configuration control in NR-DC | RAN3(Huawei) |
R3-245698 | summary of offline for CB#2 | Ericsson |
R3-245699 | DRAFT Reply LS on L3 measurement based LTM support over F1 | Vodafone GmbH |
R3-245710 | Reply LS on L3 measurement based LTM support over F1 | RAN3(Vodafone) |
R3-245772 | Correction on AI/ML Terminology | Nokia, Ericsson, ZTE, Huawei |
TDoc | Title | Source |
---|---|---|
R3-245012 | Reply LS on SDT signalling optimization for partial context transfer | RAN2(ZTE) |
R3-245021 | Reply LS on improved KPIs involving end-to-end data volume transfer time analytics | SA5(Ericsson) |
R3-245046 | Discussion on SDT signalling optimization for partial context transfer | ZTE Corporation |
R3-245065 | Consideration on SDT signalling optimization for partial context transfer | CATT |
R3-245319 | Switch to RRC Connected after SDT Partial Context Transfer | Nokia, Ericsson |
R3-245320 | Correction of switch to RRC connected after SDT Partial Context Transfer | Nokia, Ericsson |
R3-245321 | Correction of switch to RRC connected after SDT Partial Context Transfer | Nokia, Ericsson |
R3-245322 | Response LS on SDT signalling optimization for partial context transfer | Nokia |
R3-245414 | Discussion on the Reply LS on improved KPIs involving end-to-end data volume transfer time analytics | Huawei |
R3-245415 | [Draft] LS on per-UE UE performance metrics | Huawei |
R3-245511 | Reply LS on improved KPIs involving end-to-end data volume transfer time analytics | Ericsson |
R3-245591 | Consideration on SDT signalling optimization for partial context transfer [SDTnetworkSolution] | Huawei |
R3-245592 | Introduction of SDT network-based solution [SDTnetworkSolution] | Huawei |
R3-245593 | Introduction of SDT network-based solution [SDTnetworkSolution] | Huawei |
R3-245594 | Introduction of SDT Network-based solution [SDTnetworkSolution] | Huawei |
R3-245595 | [DRAFT] Reply LS on SDT signalling optimization for partial context transfer | Huawei |
R3-245677 | Response to R3-245065, R3-245319 and R3-245591 | ZTE Corporation |
R3-245680 | Response to R3-245511 | ZTE Corporation |
R3-245685 | CB:3_SDTNetworkBasedSolution | ZTE |
TDoc | Title | Source |
---|---|---|
R3-245168 | Support User Location Information reporting for NB-IoT NTN | Nokia, Nokia Shanghai Bell, Qualcomm |
R3-245241 | Discussion on UE Location Information for NB-IoT NTN with draft LS | CATT |
R3-245266 | Discussion on ENB Configuration Update procedure | CATT, Huawei, CMCC, NEC |
R3-245267 | Clarification on indication of dormant cell re-activation | CATT,Nokia,Huawei,CMCC,ZTE,NEC,Samsung |
R3-245339 | Correction of mapped cell support list | Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
R3-245359 | Discussion on UE Location Information for NB-IoT NTN | Huawei |
R3-245429 | (TP for TS 36.300) Discussion on UE Location for NTN NB-IoT UE | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
R3-245476 | [DRAFT] Reply LS on UE Location Information for NB-IoT NTN | Ericsson, Huawei, Apple, Thales |
R3-245482 | E-SMLC OAM Configuration for IoT NTN | Ericsson, Thales, Huawei |
R3-245484 | Coarse UE Location Information Reporting - S1AP Impacts | Ericsson |
R3-245485 | Correction of mapped cell support list | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
R3-245541 | X2 correction for EN-DC Resource Status Reporting Initiation | Ericsson, Jio, InterDigital |
R3-245542 | X2 correction for EN-DC Resource Status Reporting Initiation | Ericsson, Jio, InterDigital |
R3-245543 | X2 correction for EN-DC Resource Status Reporting Initiation | Ericsson, Jio, InterDigital |
R3-245544 | X2 correction for Resource Status Reporting Initiation | Ericsson, Jio, InterDigital |
R3-245545 | X2 correction for Resource Status Reporting Initiation | Ericsson, Jio, InterDigital |
R3-245546 | X2 correction for Resource Status Reporting Initiation | Ericsson, Jio, InterDigital |
R3-245547 | X2 correction for Resource Status Reporting Initiation | Ericsson, Jio, InterDigital |
R3-245659 | Further Discussion on UE Location Information for NB-IoT NTN | ZTE Corporation |
R3-245686 | CB:#4_NBIoTNTN | QC |
R3-245687 | Clarification on indication of dormant cell re-activation | CATT, Nokia, Huawei, CMCC, ZTE, NEC, Samsung |
R3-245688 | CB:#5_DeactivationIndication | CATT |
R3-245774 | Coarse UE Location Information Reporting from MME to eNB – S1AP Impacts | Ericsson, Huawei, Qualcomm Incorporated, CATT |
R3-245779 | [DRAFT] Reply LS on UE Location Information for NB-IoT NTN | Ericsson, Huawei, Apple, Thales |
R3-245793 | [Draft] Reply LS on UE Location Information for NB-IoT NTN | RAN3(Nokia) |
R3-245797 | Coarse UE Location Information Reporting from MME to eNB for NB-IoT Ues | Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT |
R3-245817 | Coarse UE Location Information Reporting from MME to eNB for NB-IoT Ues | Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT |
R3-245818 | Coarse UE Location Information Reporting from MME to eNB - S1AP Impacts | Ericsson, Huawei, Qualcomm Incorporated, CATT, ZTE |
R3-245819 | Reply LS on UE Location Information for NB-IoT NTN | RAN3(Nokia) |
TDoc | Title | Source |
---|---|---|
R3-245042 | Correction on configuration update for an inactive Multicast session | ZTE Corporation, Huawei, CATT, Nokia, Lenovo |
R3-245043 | Draft correction to group paging conflicts for multicast reception in RRC_INACTIVE | ZTE Corporation |
R3-245047 | Correction on Transmission Bandwidth less than 5MHz in TS38.423 | ZTE Corporation, China Telecom, CATT, China Unicom, Qualcom, Huawei, Nokia |
R3-245048 | Correction on Transmission Bandwidth less than 5MHz | ZTE Corporaton, China Telecom, CATT, China Unicom, Qualcom, Huawei, Nokia |
R3-245049 | Correction on Transmission Bandwidth less than 5MHz | ZTE Corporation, China Telecom, CATT, China Unicom |
R3-245062 | Correction to area-specific SRS activation | CATT, ZTE, Ericsson, China Telecom, Nokia, Samsung, Qualcomm Incorporated |
R3-245063 | Correction to area-specific SRS activation | CATT, ZTE, Ericsson, China Telecom, Nokia, Samsung, Qualcomm Incorporated |
R3-245064 | Support of UE specific SRS Reservation | CATT, Huawei, ZTE, Samsung |
R3-245075 | Correction on MBS Service Area | Huawei, CMCC, Ericsson, CBN |
R3-245076 | Correction on Retrieve UE Context Confirm [InterMNResume] | Huawei, Nokia, Qualcomm Incorporated |
R3-245077 | Correction on Retrieve UE Context Confirm [InterMNResume] | Huawei, Nokia, Qualcomm Incorporated |
R3-245078 | Correction on CIoT optimization with 5GC | Huawei, Ericsson, Qualcomm Incorporated, ZTE |
R3-245079 | Correction on CIoT optimization with 5GC | Huawei, Ericsson, Qualcomm Incorporated, ZTE |
R3-245080 | Correction on CIoT optimization with 5GC | Huawei, Ericsson, Qualcomm Incorporated, ZTE |
R3-245099 | Correction of Positioning SI for connected UE | ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi |
R3-245100 | Correction of Positioning SI for connected UE | ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi |
R3-245101 | Correction of Positioning SI for connected UE | ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi |
R3-245102 | Missing definition in RESOURCE STATUS REQUEST | ZTE Corporation, Samsung, CATT, China Telecom, CMCC, China Unicom |
R3-245103 | Missing definition in RESOURCE STATUS REQUEST | ZTE Corporation, Samsung, CATT, China Telecom, CMCC, China Unicom |
R3-245104 | Missing definition in RESOURCE STATUS REQUEST | ZTE Corporation, Samsung, CATT, China Telecom, CMCC, China Unicom |
R3-245105 | Support of UE specific SRS reservation | ZTE Corporation, CATT, Huawei, Samsung |
R3-245122 | Support of UE specific SRS reservation | Samsung, CATT, Huawei, ZTE |
R3-245123 | Discussion on QMC support in NR-DC for RRC segmentation | Samsung, ZTE, CATT, China Unicom, Lenovo |
R3-245124 | Corrections to QMC support in NR-DC for RRC Segmentation | Samsung, ZTE, CATT, Lenovo, China Unicom |
R3-245129 | Correction of SON for fast MCG recovery in stage 2 | Samsung, Lenovo, CATT, Nokia |
R3-245160 | Introduction to coordination for QoE RRC segmentation in NR-DC | ZTE Corporation, Samsung, Lenovo, China Unicom |
R3-245171 | Correction for the semantics description | Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei |
R3-245172 | Correction for the semantics description | Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei |
R3-245173 | Correction for the semantics description | Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei |
R3-245174 | Correction for the semantics description | Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei |
R3-245180 | Correction on conditional PSCell addition or change failure | CATT, CMCC, ZTE, Nokia, Nokia Shanghai Bell |
R3-245181 | Option1: Correction on DU collecting and reporting of DL LBT failure information | CATT, Ericsson, Nokia |
R3-245205 | Correction of the Signalling based MDT PLMN List IE | Huawei, China Unicom, China Telecom |
R3-245206 | Correction of the Signalling based MDT PLMN List IE | Huawei, China Unicom, China Telecom |
R3-245207 | Correction of the Signalling based MDT PLMN List IE | Huawei, China Unicom, China Telecom |
R3-245214 | Further miscellaneous corrections to QMC procedure | Huawei, China Unicom, Lenovo |
R3-245225 | Correction of mobility change procedure | Huawei, Nokia, Deutsche Telekom |
R3-245226 | Correction of mobility change procedure | Huawei, Nokia, Deutsche Telekom |
R3-245227 | Correction of mobility change procedure | Huawei, Nokia, Deutsche Telekom |
R3-245228 | Correcting IE reference in Cell Replacing Info | Huawei, Nokia, Deutsche Telekom, Ericsson, CMCC |
R3-245229 | Correcting IE reference in Cell Replacing Info | Huawei, Nokia, Deutsche Telekom, Ericsson, CMCC |
R3-245242 | Alignment for misalignment of early sync procedure | CATT, China Telecom, CMCC |
R3-245251 | QoE measurement handling in idle mode | CATT, Ericsson, ZTE, Xiaomi |
R3-245258 | Correction on IAB TMM | CATT, Nokia, Nokia Shanghai Bell |
R3-245259 | Correction on IAB TMM | CATT, Nokia, Nokia Shanghai Bell |
R3-245265 | Correction on CPAC failure states and detection mechanism in stage 2 | Nokia, CATT, Lenovo, CMCC, Qualcomm Incorporated, Huawei |
R3-245268 | Discussion on definition of UE performance metrics | CATT,Deutsche Telekom,China Unicom |
R3-245269 | [DRAFT] LS on UE level measurements | CATT,Deutsche Telekom,China Unicom[To be RAN3]] |
R3-245291 | Corrections for QoE intra-5GC inter-RATs mobility | NEC |
R3-245292 | Corrections for QoE intra-5GC inter-RATs mobility on XnAP | NEC |
R3-245301 | Corrections on MP relay based PDCP duplication | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell |
R3-245308 | Clarification of the usage of the UE History Information | Nokia, CMCC, Deutsche Telekom, Verizon, NTT Docomo, ZTE, Vodafone |
R3-245309 | --- | Nokia |
R3-245328 | Support positioning of L2 UE-to-network remote UE [PosL2RemoteUE] | Ericsson, CATT, Xiaomi, ZTE |
R3-245329 | Correction of TRP Geographical coordinates [PosLocalCoords] | Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia |
R3-245330 | Correction of TRP Geographical coordinates [PosLocalCoords] | Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia |
R3-245341 | L2 reset for intra-DU LTM | Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, Ericsson, CATT |
R3-245346 | Correction on Xn Setup message | ZTE Corporation |
R3-245347 | Correction on Xn Setup message | ZTE Corporation |
R3-245348 | Correction on Xn Setup message | ZTE Corporation |
R3-245349 | Correction on Xn Setup message | ZTE Corporation |
R3-245350 | Clarification on SpCell ID replacement | |
R3-245355 | Editorial correction on TNL Configuration Info | NTTDOCOMO, INC. |
R3-245356 | Editorial correction on TNL Configuration Info | NTTDOCOMO, INC. |
R3-245357 | Correction of mapped cell support list | Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
R3-245358 | Correction of mapped cell support list | Huawei, Nokia, Ericsson, Nokia Shanghai Bell |
R3-245363 | Support of UE specific SRS reservation | Huawei, CATT,Samsung, ZTE |
R3-245364 | Clarification on TRP ID for SRS Bandwidth Aggregation | Huawei, Nokia, CMCC, CUC, ZTE |
R3-245365 | Correction on Measurement Time Window | Huawei,CMCC, CUC, Ericsson |
R3-245366 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia |
R3-245367 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia |
R3-245368 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia |
R3-245369 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia |
R3-245370 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia |
R3-245371 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia |
R3-245376 | Correction of N3IWF user location information | Huawei, Nokia, Nokia Shanghai Bell, CATT |
R3-245377 | Correction of N3IWF user location information | Huawei, Nokia, Nokia Shanghai Bell, CATT |
R3-245378 | Correction of N3IWF user location information | Huawei, Nokia, Nokia Shanghai Bell, CATT |
R3-245379 | Introduction of AUN3 device access | Huawei, Nokia, Nokia Shanghai Bell, CATT |
R3-245380 | Introduction of AUN3 device access | Huawei, Nokia, Nokia Shanghai Bell, CATT |
R3-245382 | Corrections on SL relay procedure | LG Electronics, Samsung, Nokia, Nokia Shanghai Bell |
R3-245384 | Discussion on the PDCP SN gap report handling during UE’s handover | Huawei, CATT, Xiaomi, China Telecom, LG Electronics |
R3-245385 | Introduction of 2Rx XR devices support [2Rx_XR_Device] | Huawei, Qualcomm, Ericsson, Samsung, Nokia, Nokia Shanghai Bell, ZTE, China Telecom |
R3-245388 | Correction on BAP mapping configuration for IAB | Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT |
R3-245389 | Correction on BAP mapping configuration for IAB | Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT |
R3-245390 | Correction on BAP mapping configuration for IAB | Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT |
R3-245400 | Clarification of the usage of the UE History Information | Nokia, CMCC, Deutsche Telekom, Verizon, NTT Docomo, ZTE, Vodafone |
R3-245405 | Correction of Unavailable GUAMI in AMF Status Indication message | Huawei |
R3-245406 | Correction of Unavailable GUAMI in AMF Status Indication message | Huawei |
R3-245407 | Correction of Unavailable GUAMI in AMF Status Indication message | Huawei |
R3-245416 | Stage 3 corrections for UAV | Huawei, CATT, Nokia, ZTE |
R3-245462 | Correction to Requested DL PRS Transmission Characteristics | Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia |
R3-245463 | Correction to Requested DL PRS Transmission Characteristics | Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia |
R3-245464 | Support of UE specific SRS reservation | Huawei, CATT,Samsung, ZTE |
R3-245465 | Support of UE specific SRS reservation | Huawei, CATT,Samsung, ZTE |
R3-245471 | Correction of UE Rx-Tx Time difference measurements | Ericsson, Polaris, CATT, Huawei |
R3-245477 | Clarification of the description of the UE History Information | Nokia, ZTE, CMCC |
R3-245478 | Correction of a wrong description of the S-NG-RAN node Counter Check procedure | Nokia |
R3-245479 | Correction of a wrong description of the S-NG-RAN node Counter Check procedure | Nokia |
R3-245480 | Correction of a wrong description of the S-NG-RAN node Counter Check procedure | Nokia |
R3-245481 | Correction of a wrong description of the S-NG-RAN node Counter Check procedure | Nokia |
R3-245488 | Stage 2 correction for AI/ML for NG-RAN | Qualcomm Incorporated, ZTE, Reliance JIO |
R3-245513 | Discussion about Stage 2 corrections in AI/ML for NG-RAN | Ericsson, InterDigital, Nokia |
R3-245514 | Stage 2 correction for AI/ML for NG-RAN | Ericsson, Huawei, Nokia, InterDigital |
R3-245516 | Stage-2 support for LTM L2 reset | Ericsson, Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, CATT |
R3-245523 | Correction for the reference specification on UE History Information for Rel-16 | CMCC, Huawei, CATT, ZTE |
R3-245524 | Correction for the reference specification on UE History Information for Rel-17 | CMCC, Huawei, CATT, ZTE |
R3-245525 | Correction for the reference specification on UE History Information for Rel-18 | CMCC, Huawei, CATT, ZTE, Nokia |
R3-245548 | Xn correction for Data Collection Reporting Initiation | Ericsson, Jio, InterDigital |
R3-245549 | Xn correction for Resource Status Reporting Initiation | Ericsson, Jio, InterDigital |
R3-245550 | Xn correction for Resource Status Reporting Initiation | Ericsson, Jio, InterDigital |
R3-245551 | Xn correction for Resource Status Reporting Initiation | Ericsson, Jio, InterDigital |
R3-245552 | Stage 2 correction for network slice support during XN handover | Ericsson, Jio |
R3-245553 | Stage 2 correction for network slice support during XN handover | Ericsson, Jio |
R3-245554 | Stage 2 correction for network slice support during XN handover | Ericsson, Jio |
R3-245555 | Stage 2 correction for network slice support during XN handover | Ericsson, Jio |
R3-245566 | Rel-18 correction on LTM with gNB-CU-UP change | LG Electronics Inc. |
R3-245567 | Rel-18 correction on Intra-CU LTM procedure | LG Electronics Inc. |
R3-245577 | Support of AUN3 devices | Ericsson, BT, China Unicom |
R3-245578 | Support of AUN3 devices | Ericsson, BT, China Unicom |
R3-245587 | Addition of RRC segmentation information for NR-DC QMC | Nokia |
R3-245589 | Correction on broadcast reception for eRedCap UE [RedcapMBS] | Huawei, Qualcomm Incorporated, ZTE, CBN |
R3-245590 | Correction on broadcast reception for eRedCap UE [RedcapMBS] | Huawei, Qualcomm Incorporated, ZTE, CBN |
R3-245602 | OAM Requirements on Energy Cost index | Nokia, Jio, Telecom Italia |
R3-245614 | Discussion on Transmission Bandwidth less than 5MHz | China Telecom, ZTE |
R3-245615 | Correction on SCSs of 480kHz for FR2-2 in TS 36.423 | China Telecom,ZTE, CATT,China Unicom |
R3-245620 | Correction on SCSs of 480kHz for FR2-2 in TS 36.423 | China Telecom, ZTE, CATT, China Unicom |
R3-245632 | Option 2: Correction on DU collecting and reporting of DL LBT failure information | CATT, Ericsson, Nokia |
R3-245657 | Correction of IAB F1-C transfer in NR-DC | ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung |
R3-245658 | Correction of IAB F1-C transfer in NR-DC | ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung |
R3-245660 | Correction on UE History Information | ZTE Corporation, CMCC, CATT |
R3-245661 | Discussion on Location Reporting Control procedure for UPF Relocation | ZTE Corporation, CMCC, China Telecom |
R3-245662 | Correction on Location Reporting Control procedure for NR NTN | ZTE Corporation, CMCC, China Telecom |
R3-245663 | Correction on Location Reporting Control procedure for NR NTN | ZTE Corporation, CMCC, China Telecom |
R3-245669 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom |
R3-245670 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom |
R3-245671 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom |
R3-245672 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom |
R3-245673 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom |
R3-245674 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom |
R3-245679 | Response to R3-245123, R3-245124, R3-245160 and R3-245587 | Ericsson India Private Limited |
R3-245689 | Correction of TRP Geographical coordinates [PosLocalCoords] | Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia, ZTE |
R3-245690 | Correction of TRP Geographical coordinates [PosLocalCoords] | Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia, ZTE |
R3-245691 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT |
R3-245692 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT |
R3-245693 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT |
R3-245694 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT |
R3-245695 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT |
R3-245696 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT |
R3-245697 | Support positioning of L2 UE-to-network remote UE [PosL2RemoteUE] | Ericsson, CATT, Xiaomi, ZTE, Huawei, Qualcomm Inc. |
R3-245700 | Option 2: Correction on DU collecting and reporting of DL LBT failure information | CATT, Ericsson, Nokia, Huawei, Sumsung, ZTE |
R3-245701 | Correction of mobility change procedure | Huawei, Nokia, Deutsche Telekom |
R3-245702 | Correction of IAB F1-C transfer in NR-DC | ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung |
R3-245703 | Correction of IAB F1-C transfer in NR-DC | ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung |
R3-245704 | Correction for the semantics description | Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei |
R3-245705 | Correction for the semantics description | Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei |
R3-245706 | Correction for the semantics description | Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei |
R3-245707 | Correction for the semantics description | Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei |
R3-245708 | Corrections on SL relay procedure | LG Electronics, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT |
R3-245709 | CB:#8_AIMLforNG-RAN | Ericsson |
R3-245715 | CB: # 9_MobilityEnh | |
R3-245724 | Stage-2 support for LTM L2 reset | Ericsson, Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, CATT |
R3-245726 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE |
R3-245727 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE |
R3-245728 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom |
R3-245729 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE |
R3-245730 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE |
R3-245731 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom, Ericsson, Huawei,ZTE |
R3-245732 | introduction of Missing bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE |
R3-245733 | introduction of Missing bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE |
R3-245734 | introduction of Missing bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE |
R3-245735 | introduction of Missing bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE |
R3-245738 | Correction to Requested DL PRS Transmission Characteristics | Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia |
R3-245739 | Correction to Requested DL PRS Transmission Characteristics | Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia |
R3-245743 | Correction for the reference specification on UE History Information for Rel-18 | CMCC, Huawei, CATT, ZTE, Nokia |
R3-245749 | Clarification on SpCell ID replacement | Google, Ericsson, Huawei, CATT, Nokia, Samsung, CMCC, China Telecom, Lenovo, LG Electronics, NEC, NTT Docomo, Qualcomm, ZTE |
R3-245750 | Clarification on SpCell ID replacement | Google, Ericsson, Huawei, CATT, Nokia, Samsung, CMCC, China Telecom, Lenovo, LG Electronics, NEC, NTT Docomo, Qualcomm, ZTE |
R3-245751 | Clarification on SpCell ID replacement | Google, Ericsson, Huawei, CATT, Nokia, Samsung, CMCC, China Telecom, Lenovo, LG Electronics, NEC, NTT Docomo, Qualcomm, ZTE |
R3-245763 | Correction on BAP mapping configuration for IAB | Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT |
R3-245764 | Correction on BAP mapping configuration for IAB | Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT |
R3-245765 | Correction on BAP mapping configuration for IAB | Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT |
R3-245766 | [draft]LS on PDCP SN gap report handling during UE mobility | RAN3(Huawei) |
R3-245773 | OAM Requirements on Energy Cost index | Nokia, Jio, Telecom Italia, Ericsson, ZTE, Samsung, NEC, Huawei, Deutsche Telekom |
R3-245776 | Correction on broadcast reception for eRedCap UE [RedcapMBS] | Huawei, Qualcomm Incorporated, ZTE, CBN, Nokia, CATT |
R3-245777 | Correction on broadcast reception for eRedCap UE [RedcapMBS] | Huawei, Qualcomm Incorporated, ZTE, CBN, Nokia, CATT |
R3-245778 | Correction on MBS Service Area | Huawei, CMCC, Ericsson, CBN, Nokia |
R3-245780 | Correction on Retrieve UE Context Confirm | Huawei, Nokia, Qualcomm Incorporated |
R3-245781 | Correction on Retrieve UE Context Confirm | Huawei, Nokia, Qualcomm Incorporated |
R3-245782 | (Cancelled allocation) | MCC |
R3-245783 | Correction of N3IWF user location information | Huawei, Nokia, Nokia Shanghai Bell, CATT |
R3-245784 | Correction of N3IWF user location information | Huawei, Nokia, Nokia Shanghai Bell, CATT |
R3-245785 | Stage 2 correction for AI/ML for NG-RAN | Ericsson, Huawei, Nokia, InterDigital |
R3-245786 | Alignment of procedural text for LTM early sync procedure | CATT, China Telecom, CMCC, Huawei, Google, Nokia, LG Electronics, Ericsson, Samsung |
R3-245790 | Correction on LTM procedures for Inter-DU case and CU-UP change | LG Electronics, CATT, CMCC, China Telecom, Ericsson, Google, Huawei, Lenovo, NEC, Nokia, NTT Docomo, Samsung, Qualcomm, ZTE |
R3-245791 | Correction of TRP Geographical coordinates [PosLocalCoords] | Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia, ZTE |
R3-245792 | Correction of TRP Geographical coordinates [PosLocalCoords] | Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia, ZTE |
R3-245803 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE |
R3-245804 | introduction of Missing Bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE |
R3-245805 | introduction of Missing Bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE |
R3-245806 | introduction of Missing Bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE |
R3-245807 | introduction of Missing Bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE |
R3-245809 | Correction of IAB F1-C transfer in NR-DC | ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung |
R3-245810 | Correction of IAB F1-C transfer in NR-DC | ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung |
R3-245811 | Correction on BAP mapping configuration for IAB | Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT |
R3-245812 | Correction on BAP mapping configuration for IAB | Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT |
R3-245813 | Correction on BAP mapping configuration for IAB | Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT |
R3-245814 | Stage 2 correction for AI/ML for NG-RAN | Ericsson, Huawei, Nokia, InterDigital, ZTE, NEC, Deutsche Telekom |
R3-245816 | Correction of mobility change procedure | Huawei, Nokia, Deutsche Telekom |
R3-245825 | Correction of N3IWF user location information | Huawei, Nokia, Nokia Shanghai Bell, CATT |
TDoc | Title | Source |
---|---|---|
R3-245028 | (BL CR to 36.300 for SON) Addition of SON enhancements | Lenovo |
R3-245029 | (BL CR for SON to 36.423) on MRO for SCG failure | CATT, Samsung, Lenovo, Huawei, Ericsson, ZTE, CMCC, Nokia |
R3-245030 | (BL CR to 38.300 for SON) Addition of SON enhancements | China Unicom, ZTE, Samsung, Nokia, Lenovo |
R3-245031 | (BL CR to 38.413 for MDT) Addition of MDT enhancements | Nokia |
R3-245616 | Workplan for Rel-19 SON_MDT Enhancement | China Unicom, CMCC |
R3-245762 | LS to RAN3 on way forward on Rel-19 SONMDT | RAN2(China Unicom) |
R3-245851 | (BL CR for SON to 36.423) on MRO for SCG failure | CATT, Samsung, Lenovo, Huawei, Ericsson, ZTE, CMCC, Nokia |
R3-245853 | (BL CR to 38.300 for SON) Addition of SON enhancements | China Unicom, Nokia, Huawei, Lenovo, CATT, Ericsson, Qualcomm Inc., Samsung, LG Electronics Inc, ZTE Corporation |
R3-245855 | (BL CR to 38.413 for MDT) Addition of MDT enhancements | Nokia |
TDoc | Title | Source |
---|---|---|
R3-245112 | Discussion on MRO for LTM | Samsung |
R3-245130 | Failure scenarios on MRO for CHO with candidate SCGs | Samsung, Cybercore, Lenovo |
R3-245131 | Discussion on MRO for CHO with candidate SCGs and S-CPAC | Samsung |
R3-245145 | Discussion on MRO enhancements for LTM | China Telecom |
R3-245183 | (TP for 38.300 and 37.340) MRO for R18 mobility mechanisms | CATT |
R3-245230 | (TP for BLCR for SON for 38.300, 38.401,38.473, 37.340, 38.423) MRO enhancement for R18 mobility mechanisms | Huawei |
R3-245263 | Discussion on LTM MRO | |
R3-245277 | (TP for SON BL CR for TS 38.300) MRO Enhancements for LTM and CHO with Candidate SCG(s) | Nokia |
R3-245284 | (TP for SON BLCR of 38.473) Discussion on MRO for LTM | NEC |
R3-245310 | [TP to BL CR to 37.340, SON] Failure handling and optimal use of Subsequent CPAC | Nokia |
R3-245334 | MRO enhancements for R18 mobility mechanisms | Qualcomm Incorporated |
R3-245344 | (TP for TS 37.340 TS38.401)Discussion on MRO | ZTE Corporation |
R3-245395 | (TP for BLCR for SON for TS 38.300) MRO enhancements for LTM and CHO with candidate SCGs | Ericsson |
R3-245436 | (TP for SON BLCR for 38.300) Discussion on MRO for LTM | Lenovo |
R3-245437 | (TP for SON BLCR for 37.340) Discussion on MRO for subsequent CPAC and CHO with candidate SCG(s) | Lenovo |
R3-245526 | Discussion on MRO enhancements for LTM | CMCC |
R3-245617 | Discussion on MRO Enhancements | China Unicom |
R3-245646 | Open issues on MRO for LTM and CHO with candidate SCGs | LG Electronics Inc. |
R3-245755 | SoD of MRO for LTM | Ericsson |
R3-245756 | SoD of MRO for others | CATT |
R3-245787 | (TP for SON BL CR for TS 38.300) MRO Enhancements for LTM and CHO with Candidate SCG(s) | Nokia, Huawei, Lenovo, CATT, Ericsson, Qualcomm Inc., Samsung |
R3-245788 | (TP for TS 37.340 TS38.401)Discussion on MRO | ZTE Corporation, Nokia,Huawei, Lenovo, CATT, Ericsson |
R3-245789 | (TP for BLCR for SON for 38.473) MRO enhancement for R18 mobility mechanisms | Huawei, Nokia, CATT, Lenovo |
R3-245823 | (TP for SON BLCR TS37.340) on MRO for S-CPAC | Samsung, CATT |
R3-245830 | (TP for SON BL CR for TS 38.300) MRO enhancement for LTM | Nokia, Huawei, Lenovo, CATT, Ericsson, Qualcomm Inc., Samsung, LG Electronics Inc, ZTE Corporation |
R3-245831 | (TP for SON BL CR for TS 38.401) MRO enhancement for LTM | ZTE Corporation, Nokia, Huawei, Lenovo, CATT, Ericsson, Samsung |
R3-245832 | (TP for BLCR for SON for 38.473) MRO enhancement for R18 mobility mechanisms | Huawei, Nokia, CATT, Lenovo, Ericsson, Samsung, NEC |
R3-245834 | (TP for SON BLCR TS37.340) on MRO for S-CPAC | Samsung, CATT, Nokia, Ericsson, CMCC, Huawei, ZTE, Lenovo |
R3-245852 | (BL CR to 37.340 for SON) on MRO for S-CPAC | CMCC |
R3-245854 | (BL CR to 38.401 for SON) Addition of SON enhancements | ZTE Corporation, Nokia, Huawei, Lenovo, CATT, Ericsson, Samsung |
R3-245858 | (BL CR to 38.473 for SON) Addition of SON enhancements | Huawei, Nokia, Jio |
TDoc | Title | Source |
---|---|---|
R3-245184 | (TP for 38.300) Intra-NTN mobility for SONMDT | CATT |
R3-245192 | (TP to 38.300) Discussion on SONMDT enhancement for NTN | CMCC |
R3-245311 | [TP to BL CR to 38.423, SON] Solution to avoid restarting MRO in NTN deployments | Nokia |
R3-245335 | SON MDT for NTN | Qualcomm Incorporated |
R3-245353 | Discussion on SON enhancements for NTN | Samsung Electronics Nordic AB |
R3-245438 | Discussion on MRO for intra-NTN mobility | Lenovo |
R3-245618 | Discussion on SONMDT enhancements for NTN mobility | China Unicom |
R3-245621 | (TP for MDT BLCRs for TS38.413, TS38.423, TS37.320) SON for Intra-NTN mobility | Huawei |
R3-245654 | SON/MDT enhancements for NTN | Ericsson |
R3-245664 | (TP to BL CR for 38.300) Further discussion on SONMDT enhancement for NTN | ZTE Corporation |
R3-245757 | SoD of SONMDT NTN related | Huawei |
R3-245775 | LS on SON for NTN | RAN3(Huawei) |
TDoc | Title | Source |
---|---|---|
R3-245146 | Discussion on SON enhancements for network slicing | China Telecom |
R3-245185 | (TP for 38.413 and 38.423) Network slicing for SONMDT | CATT |
R3-245199 | Discussion on SONMDT for network slicing | CMCC |
R3-245231 | (TP for BLCR for MDT for 38.413) SON and MDT for Network Slicing | Huawei |
R3-245312 | [TP to BL CR to 38.300, MDT] MDT solution for slice support and slice-related mobility enhancements | Nokia |
R3-245336 | SON MDT for network slicing | Qualcomm Incorporated |
R3-245345 | Further consideration on SON/MDT for Slicing | ZTE Corporation |
R3-245396 | Discussion on SON enhancements for network slicing | Ericsson, AT&T, Jio |
R3-245397 | On MDT enhancements for Network Slicing | Ericsson, AT&T, Jio |
R3-245619 | Discussion on SONMDT enhancements for network slicing | China Unicom |
R3-245758 | SoD of SONMDT slicing related | China Unicom |
R3-245769 | (TP for BLCR for MDT for 38.413) SON and MDT for Network Slicing | Huawei |
R3-245770 | (TP for MDT for 38.423) Network slicing for SONMDT | CATT |
R3-245856 | (BL CR to 38.413 for MDT) Addition of MDT enhancements | CATT |
TDoc | Title | Source |
---|---|---|
R3-245009 | LS on MHI enhancement solution for SCG deactivation/activation | RAN2(China mobile) |
R3-245132 | (TP for SON BLCR for 38.423, 36.423) Rel-18 SON and MDT leftovers | Samsung |
R3-245186 | (TP for 37.340 and 38.413) SON enhancement for R18 leftover | CATT |
R3-245232 | (TP for BLCR for SON for 38.413, 36.423) Rel-18 SON and MDT leftovers | Huawei |
R3-245233 | [DRAFT] Reply LS on MHI enhancement solution for SCG deactivation/activation | Huawei, CMCC, Ericsson, ZTE [will be RAN3] |
R3-245337 | UHI enhancements for SCG (de)activation | Qualcomm Incorporated |
R3-245398 | Further discussion on RACH optimization for SDT | Ericsson |
R3-245399 | (TP for BLCR for SON for TS 38.413) UHI for SCG activation-deactivation | Ericsson |
R3-245439 | Discussion on MRO for R18 leftovers | Lenovo |
R3-245534 | MHI and UHI Enhancement for SCG Deactivation Activation | CMCC, Huawei, CATT, Ericsson, Lenovo, ZTE |
R3-245665 | (TP to BL CR for 38.413, 38.300, 38.423) Further discussion on Rel-18 leftovers | ZTE Corporation |
R3-245759 | SoD of SONMDT leftovers | CMCC |
R3-245821 | (TP for SON BLCR for 38.423) MR-DC SCG failure | Samsung, Nokia, ZTE, Lenovo |
R3-245822 | (TP for SON BLCR for 36.423) MR-DC SCG failure | Samsung, Nokia, Huawei, ZTE, Lenovo |
R3-245835 | (TP for SON BLCR for 36.423) MR-DC SCG failure | Samsung, Nokia, Huawei, ZTE, Lenovo |
R3-245857 | (BL CR to 38.423 for SON) Addition of SON enhancements | ZTE Corporation, Jio |
TDoc | Title | Source |
---|---|---|
R3-245634 | Work plan for enhancements for Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN | ZTE Corporation, NEC |
TDoc | Title | Source |
---|---|---|
R3-245089 | Discussion on AI/ML assisted Network Slicing | ZTE Corporation |
R3-245090 | [TP to BLCR 38.423] Support of AI/ML assisted Network Slicing | ZTE Corporation, Qualcomm, China Unicom |
R3-245113 | Discussion on AI/ML enabled slicing | Samsung |
R3-245190 | [TP to BLCR 38.300] Support of AI/ML assisted Network Slicing | ZTE Corporation, Lenovo, Samsung |
R3-245193 | Discussion on AI-based network slice | CMCC |
R3-245194 | TP to 38.423 AI/ML based Slice | CMCC |
R3-245270 | (TP on 38.423)Support of AI/ML enabled Slicing | CATT |
R3-245293 | (TP to TS38.423) General considerations on Enhancements for AI/ML for NG-RAN | NEC |
R3-245294 | Draft CR to TS38.300 on enhancements for AI/ML for NG-RAN | NEC |
R3-245295 | Draft CR to TS38.401 on enhancements for AI/ML for NG-RAN | NEC |
R3-245417 | (TP for AI/ML BLCR to TS 38.423) Discussion on the AI/ML-based Network Slicing | Huawei |
R3-245427 | Discussion on AIML based Network Slicing | Jio |
R3-245430 | Discussion on NG-RAN AI/ML for Network Slicing | Qualcomm Incorporated |
R3-245440 | (TP to BLCR 38.423) Discussion on AIML based network slicing | Lenovo |
R3-245499 | Support for AI/ML based Network Slicing | Ericsson, InterDigital |
R3-245500 | (TP for BLCR for AIML for 38.423) Support for AI/ML based Network Slicing | Ericsson, InterDigital |
R3-245556 | Discussion on AIML based Network Slicing | Jio |
R3-245603 | Extension of Data Collection Procedures for AI/ML Slicing | Nokia, Jio |
R3-245604 | AI/ML Slicing Support in Data Collection Reporting procedures | Nokia, Jio |
R3-245648 | Mobility Optimization with AI/ML based Network Slicing | Rakuten Mobile, Inc |
R3-245713 | CB:#AIRAN_Slicing | ZTE |
R3-245767 | [TP to BLCR 38.423] Support of AI/ML assisted Network Slicing | ZTE Corporation, Qualcomm, China Unicom, Ericsson, Samsung, Nokia, Lenovo, CATT, Huawei, NEC, CMCC, China Telecom, Telecom Italia, Deutsche Telekom, Verizon Wireless, LGE, Jio |
R3-245826 | [TP to BLCR 38.423] Support of AI/ML assisted Network Slicing | ZTE Corporation, Qualcomm, China Unicom, Ericsson, Samsung, Nokia, Lenovo, CATT, Huawei, NEC, CMCC, China Telecom, Telecom Italia, Deutsche Telekom, Verizon Wireless, LGE, Jio, Rakuten |
R3-245837 | [TP to BLCR 38.423] Support of AI/ML assisted Network Slicing | ZTE Corporation, Qualcomm, China Unicom, Ericsson, Samsung, Nokia, Lenovo, CATT, Huawei, NEC, CMCC, China Telecom, Telecom Italia, Deutsche Telekom, Verizon Wireless, LGE, Jio, Rakuten |
R3-245850 | (BLCR 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, Rakuten |
TDoc | Title | Source |
---|---|---|
R3-245091 | Discussion on AI/ML assisted Coverage and Capacity Optimization | ZTE Corporation |
R3-245092 | [TP to 38.423 and 38.473] Support of AI/ML assisted Coverage and Capacity Optimization | ZTE Corporation, China Unicom |
R3-245114 | Discussion on AI/ML enabled CCO | Samsung |
R3-245135 | Discussion on AI/ML based Coverage and Capacity Optimization | China Telecom |
R3-245136 | (TP to TS38.470) Support of AI/ML for NG-RAN | China Telecom |
R3-245137 | (TP to TS38.423) Support of AI/ML based Coverage and Capacity Optimization | China Telecom |
R3-245195 | Discussion on AI/ML-based CCO | CMCC |
R3-245223 | [TP to 38.300] Support of AI/ML assisted CCO | ZTE Corporation, Lenovo, China Unicom |
R3-245224 | [TP to 38.401] Support of AI/ML assisted CCO | ZTE Corporation, Lenovo, China Unicom |
R3-245271 | (TP on 38.423/38.473)Discussion on AI/ML based CCO | CATT |
R3-245354 | Discussion on AI/ML based CCO | Rakuten Mobile, Inc |
R3-245418 | AI/ML-based Coverage and Capacity Optimization | Huawei |
R3-245419 | TPs for AI/ML BLCR to TS 38.743 and AI/ML BLCR to TS 38.423 for AI/ML-based Coverage and Capacity Optimization | Huawei |
R3-245425 | Discussions on enhancements for AIML support for CCO | Jio |
R3-245426 | Further discussions on enhancements for AIML support for CCO | Jio, Deutsche Telekom |
R3-245431 | Discussion on AI/ML enabled CCO | Qualcomm Incorporated |
R3-245441 | (TP to BLCR 38.473) Discussion on AIML based CCO | Lenovo |
R3-245501 | AI/ML support for CCO | Ericsson, Deutsche Telekom, InterDigital |
R3-245502 | Signalling aspects of AI/ML support for CCO | Ericsson, Deutsche Telekom, InterDigital |
R3-245503 | (TP to 38.423) - AI/ML support for CCO | Ericsson, Deutsche Telekom, InterDigital |
R3-245504 | (TP to 38.473) - AI/ML support for CCO | Ericsson, Deutsche Telekom, InterDigital |
R3-245539 | Discussion on Timing Aspects for AIML support in CCO | Jio, NOKIA |
R3-245540 | Data Collection Aspects for AIML support in CCO | Jio |
R3-245557 | Scenarios and open points for AI/ML-based Coverage and Capacity Optimization (CCO) | Nokia, Jio, Telecom Italia |
R3-245558 | Initial discussion on stage 3 impact for AI/ML-based Coverage and Capacity Optimization (CCO) | Nokia, Jio, Deutsche Telekom |
R3-245559 | Introduction of AIML-based CCO | Nokia |
R3-245675 | Discussion on standard impacts on Xn interface for AI/ML-based CCO | LG Electronics Inc. |
R3-245716 | CB:#AIRAN2_CCO | Samsung |
R3-245722 | (TP to BL CR TS 38.423) AI/ML enabled CCO | Samsung |
TDoc | Title | Source |
---|---|---|
R3-245088 | (TP to 38.423) Discussion on Mobility Optimization for NR-DC | ZTE Corporation |
R3-245093 | (TP to 38.473, 37.483) Discussion on split architecture | ZTE Corporation |
R3-245094 | Discussion on continuous MDT collection | ZTE Corporation |
R3-245115 | Discussion on AI/ML for mobility in NR-DC | Samsung |
R3-245116 | Discussion on AI/ML for NG-RAN in split architecture | Samsung |
R3-245117 | (CR to 37.483) AI/ML for NG-RAN on split architecture | Samsung |
R3-245118 | Discussion on continuous MDT collection targeting the same UE across RRC states | Samsung |
R3-245138 | Discussion on Continuous MDT measurement | China Telecom |
R3-245147 | Discussion on AI/ML based Mobility Optimization for NR-DC | China Telecom |
R3-245148 | (TP to TS38.423) Support of AIML based Mobility Optimization for NR-DC | China Telecom |
R3-245191 | Discussion on AIML based Mobility Optimization for NR-DC | CMCC |
R3-245196 | Discussion on AIML for split architecure use cases | CMCC |
R3-245197 | Discussion on continuous MDT | CMCC |
R3-245243 | Scenario clarification for continuous MDT | CATT |
R3-245272 | Discussion on left over issues on DC and split architecture | CATT |
R3-245273 | (TP on TS37.480)Introducing data collection function into E1 | CATT |
R3-245274 | (TP on TS38.470) Introducing data collection function into F1 | CATT |
R3-245296 | (TP to TS38.423) Split architecture and NR-DC mobility optimization | NEC |
R3-245297 | Continuous MDT collection for AI/ML | NEC |
R3-245420 | AI/ML-based Mobility Optimization in NR-DC | Huawei |
R3-245421 | (TPs for AI/ML BLCR to TS 38.473 and AI/ML BLCR to TS 37.483) Split architecture support for Rel-18 “AI/ML for NG-RAN” use cases | Huawei |
R3-245422 | On Continuous MDT for AI/ML | Huawei |
R3-245428 | Enhancements for AI ML NG-RAN mobility | Jio |
R3-245432 | Discussion on Continuous MDT | Qualcomm Incorporated |
R3-245442 | (TP to BLCR 38.423) Discussion on UE performance feedback in AIML for NR-DC | Lenovo |
R3-245443 | (TP to BLCR 38.473 and 37.483) Discussion on split architecture related issues for Rel18 use cases | Lenovo |
R3-245444 | (TP to BLCR 37.340) AIML for NR-DC | Lenovo, CATT, ZTE Corporation, Samsung |
R3-245445 | (TP to BLCR 38.401) AIML for RAN in split architecture | Lenovo, CATT, ZTE Corporation |
R3-245505 | Split architecture support for Release 18 use cases | Ericsson, Jio, InterDigital |
R3-245506 | (TP to 38.473) - Split architecture support for Release 18 use cases | Ericsson, Jio, InterDigital |
R3-245507 | (TP to 37.483) - Split architecture support for Release 18 use cases | Ericsson, Jio, InterDigital |
R3-245508 | AI/ML support for NR-DC | Ericsson, Jio |
R3-245509 | (TP to 38.423) - AI/ML support for NR-DC | Ericsson, Jio |
R3-245510 | Discussion on Continuous MDT and improved KPIs involving end-to-end data volume transfer time analytics | Ericsson |
R3-245515 | (TP for AI/ML BLCR to TS38.423) Continuous MDT collection targeting the same UE across RRC states | Ericsson |
R3-245584 | Discussion on AIML for split architecture | NTT DOCOMO INC.. |
R3-245605 | Discussion on Energy Cost Reporting in Split Architecture | Nokia, Deutsche Telekom, Jio, Telecom Italia |
R3-245606 | Procedures over F1 for the exchange of Energy Cost index | Nokia, Deutsche Telekom, Jio, Telecom Italia |
R3-245607 | [Draft] LS on New Energy Consumption Measurement for gNB-DU | Nokia, Deutsche Telekom, Jio, Telecom Italia |
R3-245608 | Procedures for AI/ML Mobility Optimization in NR-DC | Nokia, Jio |
R3-245609 | Discussion on the Rel-18 UE Performance measurements | Nokia |
R3-245610 | [Draft] LS on the Feasibility of new measurement that Averages UE Throughput in the UL | Nokia |
R3-245611 | Continuous Management-based MDT | Nokia, Qualcomm, Jio, Telecom Italia, Deutsche Telekom |
R3-245717 | CB:#AIRAN3_NR-DC | Huawei |
R3-245718 | CB:#AIRAN4_SplitArchitecture | Lenovo |
R3-245719 | CB:#AIRAN5_ContinousMDT | Ericsson |
TDoc | Title | Source |
---|---|---|
R3-245372 | Work plan for Additional topological enhancements for NR | NTT DOCOMO INC., AT&T |
TDoc | Title | Source |
---|---|---|
R3-245155 | Discussion on WAB mobility | Samsung |
R3-245156 | Discussion on other aspects for the support of WAB | Samsung |
R3-245175 | (TP for TS 38.401) Discussion on high level aspects for WAB | Nokia, Nokia Shanghai Bell |
R3-245176 | (TP for TS 38.423) Discussion on WAB mobility | Nokia, Nokia Shanghai Bell |
R3-245247 | (draft Reply LS to SA2) Discussion on SA2 questions on multi-hop WAB and UE ULI | Qualcomm Inc. |
R3-245248 | Discussion on assumptions and architecture for WAB | Qualcomm Inc. |
R3-245252 | Discussion on stage-2 aspects for WAB | CATT |
R3-245253 | Other issues for WAB | CATT |
R3-245286 | (TP to BL CR of 38.423 on WAB) Discussion on the reliability and mobility for WAB | NEC |
R3-245381 | Discussion on Wireless Access Backhaul | NTTDOCOMO, INC. |
R3-245383 | Discussion on enhancements for WAB | CANON Research Centre France |
R3-245391 | (TPs for TS 38.300/38.413) Architecture and Access control for WAB | Huawei |
R3-245392 | (TP for TS 38.300) Discussion on WAB related procedures | Huawei |
R3-245402 | Functional Aspects of WAB-Nodes | Ericsson |
R3-245403 | Reply to SA2 Regarding WAB-MT Access Control and Additional ULI for WAB-Nodes | Ericsson |
R3-245446 | Architecture and configuration for WAB-node | Lenovo |
R3-245447 | Integration and migration for WAB node | Lenovo |
R3-245637 | Access control and location information in WAB | LG Electronics |
R3-245640 | Discussion on RAN2 impact of WAB | China Telecom |
R3-245641 | On Xn and NG interface management | China Telecom |
R3-245655 | (TP to 38.300) Discussion on supporting WAB and the reply LS to SA2 | ZTE Corporation |
R3-245656 | (TP to 38.305 38.455) Support of location service involving WAB | ZTE Corporation |
R3-245740 | Summary of Offline Discussion on additional topological enhancement | NTTDOCOMO, INC. |
R3-245752 | Draft reply LS to SA2 based on the agreement above | Qualcomm |
R3-245753 | CB:#WAB | NTT DOCOMO |
R3-245760 | Support for Wireless Access Backhaul | Ericsson |
R3-245820 | (BL draft CR to TS 38.300) the support of Wireless Access and Backhaul | Qualcomm, Ericsson |
R3-245836 | Support for Wireless Access Backhaul | Ericsson, ZTE, Nokia, Nokia Shanghai Bell |
R3-245838 | (TP to 38.305) Support of location service involving WAB | ZTE Corporation |
R3-245839 | (TP to 38.455) Support of location service involving WAB | ZTE Corporation |
R3-245840 | (BL CR to 38.401) Support for Wireless Access Backhaul | Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung, Lenovo, Qualcomm |
TDoc | Title | Source |
---|---|---|
R3-245018 | LS on Clarification regarding definition of 5G NR femto ownership | SA3(Nokia) |
R3-245151 | On NR Femto Architecture and functional split | China Telecom |
R3-245152 | On access control for NR Femtos | China Telecom |
R3-245157 | Discussion on NR Femto architecture | Samsung |
R3-245158 | Discussion on access control for NR Femto | Samsung |
R3-245254 | Discussion on 5G Femto in stage 2 | CATT |
R3-245255 | Impact to NG interface for 5G Femto | CATT |
R3-245298 | (TP to TS38.300) NR Femto | NEC |
R3-245305 | Discussion on NR Femto Architecture and Functionality | Baicells |
R3-245306 | TP to 38.300 for NR Femto | Baicells |
R3-245323 | Completion of Protocol and Functional aspects of NR Femto Architecture | Nokia |
R3-245324 | Introduction of NR Femto Architecture and Protocol Aspects | Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter |
R3-245325 | Introduction of Functional aspects of NR Femto architecture | Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter |
R3-245326 | Introduction of NR Femto architecture with optional NR Femto Gateway | Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter |
R3-245327 | LS on Security Verifications related to NR Femtos | Nokia |
R3-245393 | (TP for TS 38.300) Discussion on the architecture for NR Femto | Huawei |
R3-245394 | (TP for TS 38.300) Access control for NR Femto | Huawei |
R3-245448 | Architecture and access control for NR Femto | Lenovo |
R3-245449 | (TP to 38.300) On NR Femto | Lenovo |
R3-245486 | NR Femto - Stage 2 Aspects | Ericsson |
R3-245487 | NR Femto - Stage 2 TP | Ericsson |
R3-245535 | Discussion on architecture and access control for NR Femto | ZTE corporation |
R3-245536 | (TP for BLCR 38.300&38.410)NR Femto | ZTE corporation |
R3-245636 | (TP for TS 38.300) Support of 5G Femto | LG Electronics |
R3-245639 | Discussion on 5G femto | NTTDOCOMO, INC. |
R3-245720 | TP for BL CR on Introduction of NR Femto Architecture and Protocol Aspects | Nokia |
R3-245754 | TP for BL CR on Introduction of NR Femto Architecture and Protocol Aspects | Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, Huawei, LG Electronics, Samsung, Lenovo, Baicells |
R3-245864 | (BL CR to 38.300) Introduction of NR Femto Architecture and Protocol Aspects | Ericsson, Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, Huawei, LG Electronics, Samsung, Lenovo, Baicells |
TDoc | Title | Source |
---|---|---|
R3-245032 | (BL CR to 38.300) Support for Inter-CU LTM | Nokia, Huawei, Google, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung |
R3-245859 | (BL CR to 38.300) Support for Inter-CU LTM | Nokia, Huawei, Google, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung |
TDoc | Title | Source |
---|---|---|
R3-245007 | LS on security key update of inter-CU SCG LTM | RAN2(CATT) |
R3-245040 | Discussion on Rel-19 Inter-CU LTM | Nokia |
R3-245041 | Discussion on Inter-CU LTM Dual Connectivity | Nokia |
R3-245045 | TP (BL CR TS 38.401) L1/2 Triggered Mobility (LTM) Procedures | Nokia |
R3-245050 | Discussion on inter-CU LTM | ZTE Corporation |
R3-245142 | Discussion on signaling enhancement for inter-CU LTM | China Telecom |
R3-245143 | Discussion on support of inter-CU LTM in NR-DC scenario | China Telecom |
R3-245144 | (TP for TS38.300) On support of inter-CU LTM | China Telecom |
R3-245162 | Discussion on inter-gNB-CU LTM | Samsung |
R3-245163 | Additional discussion on Inter-gNB-CU LTM | Samsung |
R3-245164 | (TP to BLCR for TS 38.401) Procedure on Inter-gNB-CU LTM | Samsung |
R3-245201 | Discussion on the PDCP anchor based solution | Huawei, Ericsson, CATT, China Telecom, CMCC,Samsung |
R3-245202 | Discussion on Inter-CU LTM procedure | Huawei |
R3-245203 | (TP for LTM BLCR for TS38.300): Update on inter-CU LTM basic procedure | Huawei |
R3-245204 | (TP for LTM BLCR for TS 38.473): F1 impact for Inter-CU LTM | Huawei |
R3-245244 | Discussion for Inter-CU LTM | CATT |
R3-245245 | Discussion for Inter-CU LTM in DC | CATT |
R3-245246 | TP for LTM BLCR for TS38.300 | CATT |
R3-245264 | Discussion on Early Sync and CFRA resource configurations in inter-CU LTM | |
R3-245280 | inter-CU LTM issues | NEC |
R3-245281 | (TP to 38.423 on inter-CU LTM) inter-CU LTM related information | NEC |
R3-245313 | Signalling enhancements for inter-CU LTM HO | Qualcomm Incorporated, Vodafone, Bharti Airtel (India) |
R3-245314 | Enabling subsequent inter-gNB LTM by decoupling of cell and anchor changes | Qualcomm Incorporated, Vodafone, NTT DOCOMO, Sony, Bharti Airtel (India) |
R3-245315 | Impact analysis of coupling LTM cell switch and CU anchor changes on subsequent inter-gNB LTM | Qualcomm Incorporated, Vodafone, NTT DOCOMO, Sony, Bharti Airtel (India) |
R3-245316 | Further discussion on XnAP signaling for inter-CU LTM | Ericsson |
R3-245317 | (TP for TS 38.423) Xn support for inter-CU LTM | Ericsson |
R3-245318 | (TP for TS 38.300) Stage-2 signalings for inter-CU LTM | Ericsson |
R3-245458 | [TP to BLCR for TS 38.300] Inter-CU LTM | Lenovo |
R3-245459 | [TP for TS 38.423] Inter-CU LTM | Lenovo |
R3-245460 | General aspects of inter-CU SCG LTM | Lenovo |
R3-245521 | Discussion on inter-CU LTM | CMCC |
R3-245522 | (TP to BL CR for TS 38.300) Inter-CU LTM procedure | CMCC |
R3-245568 | Continuing discussions on Inter-CU LTM signaling design | LG Electronics Inc. |
R3-245569 | Baseline CR for introducing Rel-19 Mobility enhancement in E1AP | LG Electronics Inc., Nokia, China Telecom, Google, Ericsson, CATT, Qualcomm, Samsung, CMCC, ZTE, Huawei, NTT Docomo, Lenovo |
R3-245570 | (TP for NR_Mob_Ph4 TS 38.423) | LG Electronics Inc. |
R3-245585 | Discussion on inter-CU LTM non-DC case | NTT DOCOMO INC.. |
R3-245643 | Data forwarding and transmission in Inter-CU LTM | Rakuten Mobile, Inc |
R3-245645 | Initial considerations on Inter-CU LTM | Rakuten Mobile, Inc |
R3-245652 | TP to 38.423 for inter-CU LTM | ZTE Corporation |
R3-245653 | TP to 38.300 for inter-CU LTM | ZTE Corporation |
R3-245676 | Response to R3-245201 | Qualcomm Incorporated |
R3-245744 | Signalling enhancements for inter-CU LTM HO | Qualcomm Incorporated, Vodafone, Bharti Airtel (India), Jio |
R3-245745 | Enabling subsequent inter-gNB LTM by decoupling of cell and anchor changes | Qualcomm Incorporated, Vodafone, NTT DOCOMO, Sony, Bharti Airtel (India), Jio |
R3-245746 | Impact analysis of coupling LTM cell switch and CU anchor changes on subsequent inter-gNB LTM | Qualcomm Incorporated, Vodafone, NTT DOCOMO, Sony, Bharti Airtel (India), Jio |
R3-245747 | CB:#MobilityEnh_LTM | China Telecom, Lenovo |
R3-245748 | Summary of offline for two solutions for Inter-CU LTM | Lenovo |
R3-245798 | (TP for LTM BLCR for TS38.300): Update on inter-CU LTM basic procedure | Huawei |
R3-245833 | (TP for TS 38.423) Xn support for inter-CU LTM | Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC |
R3-245841 | (TP for LTM BLCR for TS38.300): Update on inter-CU LTM basic procedure | Huawei, Nokia, China Telecom, Samsung, NTT Docomo, Ericsson,CATT, Lenovo, NEC, ZTE, Google, LG Electronics |
R3-245842 | (TP for TS 38.423) Xn support for inter-CU LTM | Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC, ZTE, LG Electronics |
R3-245860 | (BL CR to 38.423) Xn support for inter-CU LTM | Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC, ZTE, LG Electronics |
TDoc | Title | Source |
---|---|---|
R3-245033 | (BL CR to 38.300) Support for Regenerative Payload 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 |
R3-245761 | (BL CR to 38.300) Support for Regenerative Payload 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-245861 | (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 |
TDoc | Title | Source |
---|---|---|
R3-245056 | (TP to BL CR for TS 38.413) Support of MBS broadcast service for NR NTN | CATT |
R3-245084 | (TP to BL CR for TS 38.413) Support of Broadcast service | Xiaomi |
R3-245125 | Further discussion on support MBS broadcast service for NR NTN | Samsung |
R3-245139 | Support of MBS broadcast service | China Telecom |
R3-245177 | (TP for TS 38.300) Discussion on the support of MBS Broadcast Service | Nokia, Nokia Shanghai Bell |
R3-245208 | (TP for TS 38.413 and TS 38.300) Discussion on NTN broadcast service supporting | ZTE Corporation |
R3-245287 | (TP for TS 38.300 and TS 38.413) Discussion on NR NTN supporting MBS broadcast service | NEC |
R3-245360 | (TP for TS 38.413 and TS 38.300) Support MBS broadcast service | Huawei |
R3-245374 | Discussion on Support of MBS Broadcast Service | TCL |
R3-245433 | (TP for TS38.300) Discussion on Support for NR NTN MBS Broadcast Service | Qualcomm Incorporated |
R3-245450 | Broadcast service area indication and service continuity in NTN | Lenovo |
R3-245490 | Broadcast Service Area for NR NTN | Ericsson, SES, ESA |
R3-245491 | Broadcast Service Area for NR NTN - NGAP Impacts | Ericsson, SES, ESA |
R3-245520 | Discussion on Supporting MBS broadcast service for NR NTN | CMCC |
R3-245794 | [Draft] LS on Supporting MBS broadcast service for NR NTN | RAN3(Xiaomi) |
R3-245795 | (TP to BL CR for TS 38.300) Supporting MBS broadcast service for NR NTN | Huawei, Nokia, Nokia Shanghai Bell, Ericsson, Xiaomi, NEC, ZTE |
R3-245796 | (TP to BL CR for TS 38.413) Supporting MBS broadcast service for NR NTN | Ericsson, SES, ESA, Nokia, Nokia Shanghai Bell |
R3-245843 | (TP to BL CR for TS 38.413) Supporting MBS broadcast service for NR NTN | Ericsson, SES, ESA, Nokia, Nokia Shanghai Bell, Xiaomi, Huawei, ZTE |
R3-245844 | LS on Supporting MBS broadcast service for NR NTN | RAN3(Xiaomi) |
TDoc | Title | Source |
---|---|---|
R3-245057 | (TP to BL CRs) Support of regenerative payload | CATT |
R3-245085 | Support of regenerative payload | Xiaomi |
R3-245126 | Further discussion on support of regenerative payload for NR NTN | Samsung |
R3-245140 | Support of regenerative payload in NR NTN | China Telecom |
R3-245178 | (TP for TS 38.300) Discussion on the support of Regenerative payload | Nokia, Nokia Shanghai Bell |
R3-245179 | (TP for TS 38.413) Introduce NG Removal procedure | Nokia, Nokia Shanghai Bell, Huawei, CATT, CMCC, Ericsson, Qualcomm, Xiaomi |
R3-245288 | (TP for TS 38.300) Discussion on regenerative payload enhancement for NR NTN | NEC |
R3-245340 | Discussion on support of regenerative payload for NR NTN | CSCN |
R3-245361 | (TP for BLCR for TS 38.300) Support of regenerative payload (including LS responses to SA2) | Huawei |
R3-245362 | (TP for TS 38.410) Introduce NG Removal procedure | Huawei, Nokia, Nokia Shanghai Bell, CATT, CMCC, Ericsson, Qualcomm, Xiaomi |
R3-245373 | Discussion on Support of NTN Regenerative Architecture | TCL |
R3-245404 | Discussion on interfaces mobility aspects for regenerative payload | THALES |
R3-245410 | Discussion on UE-Sat-UE communications | THALES |
R3-245434 | (TP for TS 38.300) Discussion on RAN Signaling impacts for NR NTN Regenerative Payload | Qualcomm Incorporated |
R3-245451 | Interface management for regenerative payload in NTN | Lenovo |
R3-245493 | NG Removal – Stage 2 Description | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Xiaomi, CATT, Qualcomm Incorporated |
R3-245494 | Further Discussion on NTN Regenerative Payload Issues in Rel-19 | Ericsson, Thales, SES, ESA, Sateliot |
R3-245495 | [DRAFT] Reply LS on Support of Regenerative Payload Issues in Rel-19 | Ericsson |
R3-245519 | Discussion on Support of regenerative payload for NR NTN | CMCC |
R3-245571 | Discussions on NG management and Inactive support | LG Electronics Inc. |
R3-245572 | (TP for NR_NTN_Ph3 TS 38.300) | LG Electronics Inc. |
R3-245586 | Discussion on Xn impact for NR NTN regenerative payload | NTT DOCOMO INC.. |
R3-245588 | Discussion on NG interface management through ISL | ETRI |
R3-245666 | Further discussion on support of regenerative payload | ZTE Corporation |
R3-245768 | CB:#NRNTN2_RegenerativePayload | CATT |
R3-245799 | (TP for TS 38.413) Introduce NG Removal procedure | Nokia, Nokia Shanghai Bell, Huawei, CATT, CMCC, Ericsson, Qualcomm, Xiaomi, LG Electronics, China Telecom, Samsung, ZTE, NEC, ETRI |
R3-245800 | (TP for TS 38.410) Introduce NG Removal procedure | Huawei, Nokia, Nokia Shanghai Bell, CATT, CMCC, Ericsson, Qualcomm, Xiaomi, LG Electronics, China Telecom, Samsung, ZTE, NEC, ETRI |
R3-245801 | NG Removal – Stage 2 Description | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Xiaomi, CATT, Qualcomm Incorporated, LG Electronics Inc., China Telecom, Samsung, ZTE, NEC, ETRI |
R3-245802 | LS on OAM requirements to support regenerative payload | RAN3(CATT) |
R3-245845 | LS on OAM requirements to support regenerative payload | RAN3(CATT) |
R3-245862 | (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-245863 | (BL CR to 38.413) 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-245005 | Reply LS on Clarification of requirements for Ambient IoT | RAN1(Ericsson) |
R3-245015 | Reply LS on Clarification of requirements for Ambient IoT | SA1(Ericsson) |
R3-245069 | (BL pCR to TR 38.769) Study on solutions for Ambient IoT in NR | Huawei, CMCC |
R3-245529 | Work Plan for Ambient IoT SI | CMCC, Huawei, T-Mobile USA |
R3-245849 | (BL pCR to TR 38.769) Study on solutions for Ambient IoT in NR | Huawei, CMCC, Ericsson, ZTE, CATT, NEC, Xiaomi, Lenovo |
TDoc | Title | Source |
---|---|---|
R3-245051 | Discussion on Unified logical system architecture for topology 1 and 2 | ZTE Corporation |
R3-245052 | (TP for TR38.769) Unified logical system architecture for Topology 1 and Topology 2 | ZTE Corporation |
R3-245058 | (TP to TR 38.769) A-IoT architecture aspects | CATT |
R3-245070 | (TP to TR 38.769) A-IoT RAN Architecture aspects | Huawei |
R3-245071 | (TP to TR 38.769) Protocol Stacks of Topology 2 solutions | Huawei, CMCC, ZTE, CATT, NEC, Xiaomi |
R3-245081 | (TP to BL CR for TR 38.769) AIoT RAN architecture | Xiaomi |
R3-245127 | Further discussion on RAN architecture for Ambient IoT | Samsung |
R3-245141 | (TP to TR 38.769) RAN architecture for Ambient-IoT | China Telecom |
R3-245289 | (TP for TR 38.769) Discussion on Architecture of Ambient IoT | NEC |
R3-245331 | Architecture, interfaces and transport for Ambient IoT | Qualcomm Incorporated |
R3-245452 | On RAN architecture of ambient IoT | Lenovo |
R3-245530 | Discussion on RAN Architecture for Ambient IoT | CMCC |
R3-245573 | [TP for TR 38.769] Protocol Stack Option for Topology 2 | Nokia |
R3-245579 | Further discussionis on AIoT RAN architecture | Ericsson |
R3-245580 | [TP for TR 38.769] on AIoT Architecture aspects | Ericsson |
R3-245638 | Discussion on RAN impact for Ambient IoT | LG Electronics |
R3-245721 | CB:#AIoT1_ProtocolStack | Huawei |
R3-245828 | (TP to TR 38.769) A-IoT RAN Architecture aspects | Huawei |
R3-245829 | (TP to TR 38.769) Protocol Stacks of Topology 2 solutions | Huawei, CMCC, ZTE, CATT, NEC, Xiaomi |
R3-245846 | (TP to TR 38.769) A-IoT RAN Architecture aspects | Huawei |
R3-245847 | (TP to TR 38.769) Protocol Stacks of Topology 2 solutions | Huawei, CMCC, ZTE, CATT, NEC, Xiaomi, Lenovo |
TDoc | Title | Source |
---|---|---|
R3-245053 | (TP for TR38.769) Text description for AIoT Signalling and Procedures | ZTE Corporation, Huawei, NEC, Nokia, CATT, China Telecom |
R3-245054 | (TP for TR38.769) content for Ambient-IoT Inventory procedure | ZTE Corporation |
R3-245059 | (TP to TR 38 769) Procedures for AIoT Command | CATT |
R3-245060 | (TP to TR 38 769) Information exchange between AIoT CN and AIoT RAN | CATT |
R3-245072 | (TP to TR 38.769) A-IoT Signalling and Procedures for Topology 1 | Huawei |
R3-245073 | (TP to TR 38.769) A-IoT Signalling and Procedures for Topology 2 | Huawei |
R3-245082 | (TP to BL CR for TR 38.769)) AIoT interface impacts between RAN and CN | Xiaomi |
R3-245128 | Further discussion on RAN-CN interface impact for Ambient IoT | Samsung |
R3-245290 | Discussion on RAN-CN interface impact on Ambient IoT | NEC |
R3-245307 | (TP for TR38.769) Text description for AIoT Signalling and Procedures | ZTE Corporation, Huawei, NEC, Nokia, CATT, China Telecom, CMCC |
R3-245332 | Inventory and Command related procedures for Ambient IoT | Qualcomm Incorporated |
R3-245453 | On basic procedures of ambient IoT | Lenovo |
R3-245454 | Context Management and Data Transport of Ambient IOT | Lenovo |
R3-245531 | Discussion on signalling procedure for topology1 | CMCC |
R3-245532 | Discussion on signalling procedure for topology2 | CMCC |
R3-245574 | Inventory Signalling reusing Paging procedures for AIoT Topology 2 | Nokia |
R3-245575 | [TP for TR 38.769] Inventory Signalling reusing Paging procedures for AIoT Topology 2 | Nokia |
R3-245576 | [TP for TR 38.769] Data Transport and Context Management for AIoT | Nokia |
R3-245581 | [TP for TR 38.769] Elements for AIoT RAN – AIoT CN communication and overall signalling | Ericsson |
R3-245644 | Discussion on RAN-CN interface for Ambient IoT | China Telecom |
R3-245723 | [TP for TR 38.769] CB:#AIoT2_RANCNinterface | Ericsson |
R3-245848 | [TP for TR 38.769] CB:#AIoT2_RANCNinterface | Ericsson LM |
TDoc | Title | Source |
---|---|---|
R3-245055 | (TP for TR38.769) Locating an AIoT device | ZTE Corporation |
R3-245061 | (TP to TR 38.879) Locating of A-IoT device | CATT |
R3-245074 | (TP to TR 38.769) A-IoT Device Locating | Huawei |
R3-245083 | (TP to BL CR for TR 38.769)) Locating AIoT device | Xiaomi |
R3-245333 | Methods for locating Ambient IoT devices | Qualcomm Incorporated |
R3-245533 | Discussion on locating Ambient IoT device | CMCC |
R3-245582 | [TP for TR 38.769] On locating AIoT devices | Ericsson |
R3-245725 | CB:#AIoT3_Location | Nokia |
R3-245827 | (TP for TR 38.769] TP for Locating Ambient IoT devices | Nokia |
TDoc | Title | Source |
---|---|---|
R3-245483 | WI Work plan for R19 Network Energy Savings | Ericsson |
TDoc | Title | Source |
---|---|---|
R3-245106 | (TP for TS 38.473) Discussion on On-Demand SSB SCell Operation | CMCC |
R3-245119 | Discussion on on-demand SSB SCell operation in low-carbon green network | Samsung |
R3-245153 | On support on-demand SSB SCell operation | China Telecom |
R3-245218 | (TP for TS 38.473) Discussion on on-demand SSB SCell operation | Huawei |
R3-245256 | On support on-demand SSB SCell operation | CATT |
R3-245299 | Support on-demand SSB operation | NEC |
R3-245455 | Discussion on On-demand SSB for SCell | Lenovo |
R3-245560 | On-Demand SSB SCell operation for UEs in connected mode | Nokia |
R3-245667 | (TP to BL CR for TS38.473) Further discussion on on-demand SSB Scell operation | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R3-245107 | Support On-Demand SIB1 for UEs | CMCC |
R3-245120 | Discussion on on-demand SIB1 in low-carbon green network | Samsung |
R3-245219 | (TP for TS 38.473) Discussion on on-demand SIB1 for UEs in idle or inactive mode | Huawei |
R3-245249 | Aspects of on-demand SIB1 for NES enhancements | Qualcomm Inc. |
R3-245257 | On support on-demand SIB1 for idle UE | CATT |
R3-245300 | Support on-demand SIB1 | NEC |
R3-245456 | Discussion on On-demand SIB1 for Idle/Inactive UE | Lenovo |
R3-245498 | Xn impact of On-demand SIB1 for UEs in idle/inactive mode | Ericsson |
R3-245517 | F1 impact of On-demand SIB1 for UEs in idle/inactive mode | Ericsson |
R3-245561 | Further thoughts on open Issues in support of On-Demand SIB1 | Nokia |
R3-245647 | Discussion on OD-SIB1 | Rakuten Mobile, Inc |
R3-245668 | Further discussion on on-demand SIB1 | ZTE Corporation |
R3-245737 | CB:#R19ES | Ericsson |
TDoc | Title | Source |
---|---|---|
R3-245166 | Discussion on signaling design for LP-WUS subgrouping | vivo, NTT DOCOMO INC. |
R3-245167 | BLCR for TS 38.300 on support of LP-WUS | vivo, NTT DOCOMO INC. |
R3-245200 | Discussion on Low-power wake-up signal and receiver for NR | CMCC |
R3-245220 | (TP for TS 38.413 and TS 38.423) Discussion on Low-power wake-up signal and receiver for NR | Huawei |
R3-245221 | Introduction of low-power wake-up signal and receiver for NR | Huawei |
R3-245234 | Support of LP-WUS | Nokia |
R3-245235 | Support of LP-WUS | Nokia |
R3-245250 | Support LP-WUS subgrouping in RRC_IDLE/RRC_INACTIVE | Qualcomm Inc. |
R3-245275 | Potential RAN3 impacts of LP-WUS | CATT |
R3-245276 | TP on TS 38.300 for LP-WUS | CATT |
R3-245285 | (TP to 38.413, 38.423, 38.473 on LP-WUS) Discussion on the support of LP-WUS indicating paging monitoring | NEC |
R3-245302 | (TP to TS 38.413, 38.473, 38.423) Discussion on RAN3 impacts for LP-WUS | ZTE Corporation |
R3-245303 | [draft LS] to SA2/CT1 on support of LP-WUS subgrouping | ZTE Corporation |
R3-245338 | Introduction of LP-WUS paging monitoring | Ericsson |
R3-245475 | Discussion of LPWUS impacts on NG-RAN architecture | Ericsson |
R3-245518 | (TP to BL CR for TS 38.423) support of LP-WUS | CMCC |
R3-245633 | Discussion on LP-WUS subgrouping | Samsung |
R3-245635 | (TP to BLCR for TS 38.413, 38.423, 38.473) LP-WUS Assistance Information to support subgrouping | Samsung |
TDoc | Title | Source |
---|---|---|
R3-245215 | Workplan for Rel-19 WI on Evolution of NR duplex operation: Sub-band full duplex (SBFD) | Huawei |
TDoc | Title | Source |
---|---|---|
R3-245006 | LS to RAN3 on PHY/L1 aspects of information exchange among gNBs for CLI mitigation | RAN1(Ericsson) |
R3-245068 | Signaling design to enable NR SBFD operation | Qualcomm Incorporated |
R3-245133 | Discussion on information exchange among gNBs for CLI handling | Samsung |
R3-245134 | TPs to BLCRs of TS38.473 and TS38.423 on CLI handling | Samsung |
R3-245154 | TPs to BLCRs of TS38.473 and TS38.423 on CLI handling | Samsung |
R3-245187 | Discussion on Evolution of Duplex Operation | CATT |
R3-245188 | (TP for 38.423 and 38.473) Support SBFD Operation | CATT |
R3-245198 | Discussion on supporting CLI handling in SBFD | CMCC |
R3-245216 | General discussion on RAN3 impacts by the RAN1 agreements | Huawei |
R3-245217 | BL CR on the introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD) | Huawei |
R3-245283 | Discussion on CLI handling support | NEC |
R3-245496 | Discussion on RAN3 impacts to support enhancements for CLI handling for SBFD | Ericsson |
R3-245497 | Enhancements for CLI handling in SBFD | Ericsson |
R3-245537 | Discussion on Information exchange for SBFD | ZTE corporation |
R3-245538 | (TP for BLCR 38.300&420&423&473-36.423-37.340) SBFD | ZTE corporation |
R3-245562 | Initial discussion on RAN3 work on Evolution of NR duplex operation: Sub-band full duplex (SBFD) | Nokia |
R3-245583 | RAN3 issues related to SBFD | Charter Communications, Inc |
TDoc | Title | Source |
---|---|---|
R3-245014 | LS on AIML data collection | RAN(Interdigital) |
R3-245472 | Work Plan for Rel-19 on AI/ML for PHY (Positioning) | Ericsson (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R3-245066 | Discussion on AIML assisted positioning | CATT |
R3-245067 | Discussion on Direct AIML positioning | CATT |
R3-245086 | Discussion on AI-based positioning | Xiaomi |
R3-245087 | (TP to BL CR for TS 38.455) Support of gNB-side model training | Xiaomi |
R3-245097 | Discussion on AIML assisted Positioning (Case 3a) | ZTE Corporation |
R3-245098 | Discussion on Direct Positioning (Case 3b) | ZTE Corporation |
R3-245108 | Support AIML Assisted Positioning | CMCC |
R3-245109 | Support Direct AIML Positioning | CMCC |
R3-245121 | Discussion on AI/ML for positioning | Samsung |
R3-245149 | Discussion on support of direct AI/ML positioning (Case 3b) | China Telecom |
R3-245150 | Discussion on support of AI/ML assisted positioning (Case 3a) | China Telecom |
R3-245282 | Discussion on AIML based Positioning Accuracy Enhancements | NEC |
R3-245304 | Discussion on AI-ML based positioning accuracy enhancement | Baicells |
R3-245423 | Discussion on RAN3 impacts for Direct AI/ML positioning | Huawei |
R3-245424 | Discussion on RAN3 impacts for AI/ML assisted positioning | Huawei |
R3-245457 | AIML for gNB assisted positioning | Lenovo |
R3-245461 | AI/ML based positioning accuracy enhancements | Qualcomm Incorporated |
R3-245473 | Discussion on RAN3 impacts to support AI/ML Positioning accuracy enhancements | Ericsson |
R3-245474 | Support of AI/ML Positioning | Ericsson |
R3-245612 | Support for AI/ML Positioning | Nokia |
R3-245613 | AI/ML Assisted positioning case 3a | Nokia |
R3-245736 | CB:#AIPHY | Ericsson |
TDoc | Title | Source |
---|---|---|
R3-245034 | (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 |
R3-245035 | (BL CR to 38.423) Support of XR enhancements | CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC, NEC |
R3-245036 | (BL CR to 38.425) XR enhancements for NR-NR DC | Ericsson, AT&T, BT, T-Mobile USA, Charter Communications, Qualcomm, Huawei, Nokia, Nokia Shanghai Bell,China Telecom, CMCC, ZTE, CATT |
R3-245037 | (BL CR to 38.300) Support of XR enhancements | Nokia, Nokia Shanghai Bell, Lenovo, Qualcomm, Xiaomi, CATT, Ericsson, CMCC, Samsung, Huawei |
R3-245038 | Support for DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi, Nokia, Nokia Shanghai Bell, China Telecom |
R3-245714 | (BL CR to 38.423) Support of XR enhancements | CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC, NEC |
R3-245741 | (BL CR to 38.425) Support of XR enhancements | Ericsson, AT&T, BT, T-Mobile USA, Charter Communications, Qualcomm, Huawei, Nokia, Nokia Shanghai BellChina Telecom, CMCC, ZTE, CATT |
R3-245742 | (BL CR to 38.473) Support of XR enhancements | Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi, Nokia, Nokia Shanghai Bell, China Telecom |
TDoc | Title | Source |
---|---|---|
R3-245159 | Correction on UAI for support XR in DC | Samsung, Ericsson, Cybercore |
R3-245182 | Indicating configuration of PSI-based discard in SN-triggered modification procedure | CATT |
R3-245236 | Correction of MBS PDCP packets discard | Nokia |
R3-245237 | Exchange of MBS multicast services in RRC inactive | Nokia, Huawei, CATT, Qualcomm Incorporated |
R3-245408 | Correction of message level criticality of E1AP procedures | Huawei |
R3-245409 | Correction of IE criticality in Bearer Context Setup Response and Modification Response message | Huawei |
R3-245489 | Discussion on Time Reference Distribution Subscription for UEs in LTE | Qualcomm Incorporated, Vodofone Group Plc, Vodofone Telekomünikasyon A.S. |
R3-245492 | uRLLC | Qualcomm Incorporated |
R3-245642 | Time Reference Distribution Information in S1AP | Qualcomm, Vodafone Group Plc, Vodafone Telekomünikasyon A.S. |
R3-245711 | Indicating configuration of PSI-based discard in SN-triggered modification procedure | CATT, ChinaTelecom |
R3-245712 | Correction of message level criticality of E1AP procedures | Huawei |
R3-245771 | Time Reference Distribution Information in S1AP | Qualcomm, Vodafone Group Plc, Vodafone Telekomnikasyon A.S. |
TDoc | Title | Source |
---|---|---|
R3-245209 | Correction to enhancing QoS Monitoring with Per-Packet Granularity | ZTE Corporation |
R3-245210 | Enhancing QoS Monitoring with Per-Packet Granularity | ZTE Corporation |
R3-245260 | Support cell DTXDRX for NES | CATT, ZTE, NEC |
R3-245261 | Support Cell DTX/DRX for NES | CATT, ZTE, NEC |
R3-245262 | Support cell DTXDRX for NES | CATT, ZTE, NEC |
R3-245351 | Support Cell DTX/DRX for NES | CATT, ZTE, NEC |
R3-245375 | Inactivity Timer for Fixed Wireless Access | Nokia |
R3-245527 | Discussion on mechanism for UAV regulation | CMCC, ZTE, CATT, China Telecom, NTT DOCOMO |
R3-245528 | Correction on mechanism for UAV regulation | CMCC |
R3-245681 | Response to R3-245375 | Ericsson |
R3-245808 | [Draft] LS on UAV regulation | CMCC [to be RAN3] |
R3-245815 | LS on UAV regulation | RAN3(CMCC) |
TDoc | Title | Source |
---|---|---|
R3-245824 | LS on Invitation to Join a Basketball Game | RAN3(ZTE) |