TDoc | Title | Source |
---|---|---|
R3-247001 | RAN3#126 Meeting Agenda | RAN3 Chair |
TDoc | Title | Source |
---|---|---|
R3-247002 | RAN3#125-bis Meeting Report | ETSI-MCC |
TDoc | Title | Source |
---|---|---|
R3-247003 | Guidelines for RAN3 Meetings | RAN3 Chair, RAN3 Vice-Chairs |
TDoc | Title | Source |
---|---|---|
R3-247004 | TR 30.531 v1.55.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
TDoc | Title | Source |
---|---|---|
R3-247005 | LS on Multicast MBS session restoration procedure for N3mb path failure | CT4(Nokia) |
R3-247009 | Reply to SA2 LS on multi-modality awareness | RAN2(Huawei) |
R3-247010 | Reply to SA5 LS on Number of UEs in RRC_INACTIVE state with data transmission | RAN2(Huawei) |
R3-247011 | LS on UL RRC message segmentation for UECapabilityInformation | RAN2(Qualcomm) |
R3-247015 | Reply on FS_XRM_Ph2 | RAN2(Nokia) |
R3-247113 | LS for PDU Set Information Marking Support without QoS parameters | SA2(Vivo) |
R3-247114 | LS to RAN3 on renewable energy based LBO | SA5(Huawei) |
R3-247115 | LS on AI/ML Model transfer/delivery to UE | SA5(NEC) |
R3-247117 | Discussion on UL RRC message segmentation for UECapabilityInformation | ZTE Corporation |
R3-247118 | NGAP on UL RRC message segmentation for UECapabilityInformation | ZTE Corporation |
R3-247119 | NGAP on UL RRC message segmentation for UECapabilityInformation | ZTE Corporation |
R3-247120 | Draft LS to SA2 on UL RRC message segmentation for UECapabilityInformation | ZTE Corporation |
R3-247121 | Recovery of N3mb path failure for unicast transport of multicast session | ZTE Corporation |
R3-247167 | Discussion on the support of semi-persistent CSI-RS resource for LTM candidate cells | ZTE Corporation |
R3-247168 | [DRAFT] Reply LS on the support of semi-persistent CSI-RS resource for LTM candidate cells | ZTE Corporation |
R3-247169 | [DRAFT] Reply LS on Early TA acquisition for the inter-DU scenario | ZTE Corporation |
R3-247170 | Discussion on support of intra-SN SCPAC in MN format | ZTE Corporation |
R3-247171 | Support intra-SN SCPAC in MN format - TS37.340 | ZTE Corporation |
R3-247172 | Support intra-SN SCPAC in MN format over Xn - TS38.423 | ZTE Corporation |
R3-247174 | Discussion on L3 measurement based LTM support over F1 | ZTE Corporation |
R3-247175 | Support L3 measurement based LTM support over F1 - TS38.401 | ZTE Corporation |
R3-247176 | Support L3 measurement based LTM support over F1 - TS38.473 | ZTE |
R3-247177 | Support L3 measurement based LTM support over F1 - TS38.470 | ZTE Corporation |
R3-247178 | [Draft]reply LS on L3 measurement based LTM support over F1 | ZTE Corporation |
R3-247240 | Recovery of N3mb failure for Multicast Session | Nokia |
R3-247245 | Discussion on PDU Set Information Marking Support without QoS parameters | CMCC |
R3-247246 | Discussion on on RAN3 support of multi-modality awareness | CMCC |
R3-247247 | Recovery of N3mb path failure for unicast transport of multicast session | Nokia |
R3-247248 | Recovery of N3mb path failure for unicast transport of multicast session | Nokia |
R3-247249 | Recovery of N3mb path failure for unicast transport of multicast session | Nokia |
R3-247250 | Reply LS on Multicast MBS Session Restoration procedure for N3mb path failure | Nokia |
R3-247251 | Consideration on Multicast MBS session restoration procedure for N3mb path failure | Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated |
R3-247252 | Support of Multicast MBS session restoration procedure for N3mb path failure | Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated |
R3-247253 | Support of Multicast MBS session restoration procedure for N3mb path failure | Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated |
R3-247254 | [Draft] Reply LS on Multicast MBS session restoration procedure for N3mb path failure (Reply to C4-244467) | Huawei |
R3-247255 | Discussion on LS on XR from SA2 | vivo |
R3-247307 | NR UE capability storing limitation discussion and draft reply LS | Qualcomm Incorporated |
R3-247335 | Discussion on the UL RRC message segmentation for UECapabilityInformation | Nokia, Nokia Shanghai Bell |
R3-247336 | Introduction of the signalling of UE capability size of the AMF | Nokia, Nokia Shanghai Bell |
R3-247337 | Introduction of the signalling of UE capability size of the AMF | Nokia, Nokia Shanghai Bell |
R3-247338 | [DRAFT] Reply LS on UL RRC message segmentation for UECapabilityInformation | Nokia, Nokia Shanghai Bell |
R3-247339 | Discussion on the LS related to XR | Nokia, Nokia Shanghai Bell |
R3-247340 | [Draft] Reply LS for PDU Set Information Marking Support without QoS parameters | Nokia, Nokia Shanghai Bell |
R3-247359 | Discussion on the usage of multi-modality information | Huawei |
R3-247360 | [draft] Reply LS on usage of multi-modality information | Huawei |
R3-247361 | Discussion on the PDU set information marking support without PDU set QoS parameters | Huawei |
R3-247362 | [draft] Reply LS on PDU set information marking support without PDU set QoS parameters | Huawei |
R3-247408 | UL RRC message segmentation for UECapabilityInformation | Huawei |
R3-247409 | Introduction of Allowed UE Radio Capability Size for UECapabilityInformation [UL_Capa_Segmentation] | Huawei |
R3-247410 | Introduction of Allowed UE Radio Capability Size for UECapabilityInformation [UL_Capa_Segmentation] | Huawei |
R3-247411 | [draft] Reply LS on UL RRC message segmentation for UECapabilityInformation | Huawei |
R3-247528 | Reply LS on Renewable energy based LBO | Ericsson |
R3-247568 | Discussion on LS from SA5 on renewable energy based LBO | Nokia |
R3-247571 | Discussion on SA2 LS regarding PDU Set Information Marking Support without QoS parameters | Ericsson |
R3-247572 | LS reply on PDU Set Information Marking Support without QoS parameters | Ericsson |
R3-247589 | On the RAN2 LS on "UL RRC message segmentation for UECapabilityInformation" | Ericsson |
R3-247597 | Counting number of RRC_INACTIVE SDT UEs | Nokia |
R3-247599 | Response LS on number of UEs in RRC_INACTIVE state with data transmission | Nokia |
R3-247631 | Discussion on renewable energy based LBO | Huawei |
R3-247632 | [draft] Reply LS on renewable energy based LBO | Huawei |
R3-247659 | Discussion on SA2 LS on PDU Set Information | ZTE Corporation |
R3-247660 | [Draft]Reply LS to SA2 for PDU Set Information Marking Support without QoS parameters | ZTE Corporation |
R3-247663 | [Draft] Reply LS on renewable energy based LBO | Nokia |
R3-247700 | Discussion on renewable energy based LBO | ZTE Corporation |
R3-247701 | [Draft]Reply LS on renewable energy based LBO | ZTE Corporation |
R3-247718 | Disccsion on LS for PDU Set Information Marking Support without QoS parameters | CATT |
R3-247720 | Restoration of N3mb Failure for MBS multicast | Ericsson |
R3-247721 | Restoration of N3mb Failure for MBS multicast | Ericsson |
R3-247748 | Recovery of N3mb path failure for unicast transport of multicast session | ZTE Corporation |
R3-247752 | Response to R3-247597 and R3-247599 | ZTE Corporation |
R3-247759 | LS on draft-ietf-raw-technologies, "Reliable and Available Wireless Technologies" | IETF |
R3-247764 | Support of Multicast MBS session restoration procedure for N3mb path failure | Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated |
R3-247767 | [draft] Reply LS on usage of multi-modality information | Huawei |
R3-247768 | Reply LS on renewable energy based LBO | RAN3(ZTE) |
R3-247769 | Reply LS on UL RRC message segmentation for UECapabilityInformation | RAN3(Qualcomm) |
R3-247770 | CB:#4_N3mb | Nokia |
R3-247781 | Recovery of N3mb path failure for unicast transport of multicast session | Nokia |
R3-247782 | Recovery of N3mb path failure for unicast transport of multicast session | ZTE |
R3-247783 | Reply LS on Multicast MBS Session Restoration procedure for N3mb path failure | Nokia |
R3-247802 | Support of Multicast MBS session restoration procedure for N3mb path failure | Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated, Nokia |
R3-247836 | SoD : CB: # 1_XRIncomingLS | Qualcomm |
R3-247849 | Reply LS to SA2 for PDU Set Information Marking Support without QoS parameters | RAN3(ZTE) |
R3-247874 | Reply LS on multi-modality awareness | RAN3(Huawei) |
R3-247875 | Reply LS to SA2 for PDU Set Information Marking Support without QoS parameters | RAN3(ZTE) |
R3-247876 | Support of Multicast MBS session restoration procedure for N3mb path failure | Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated, Nokia |
R3-247877 | Recovery of N3mb path failure for unicast transport of multicast session | Nokia, Ericsson, Huawei |
R3-247878 | Recovery of N3mb path failure for unicast transport of multicast session | ZTE Corporation, Nokia, Huawei, CATT |
R3-247879 | Reply LS on Multicast MBS Session Restoration procedure for N3mb path failure | RAN3(Nokia) |
TDoc | Title | Source |
---|---|---|
R3-247784 | Reply LS to SA5 on AIML data collection | RAN2(Nokia) |
R3-247798 | Reply LS to SA2 on AIML data collection | RAN2(Interdigital) |
TDoc | Title | Source |
---|---|---|
R3-247163 | Introduction of SDT network-based solution | Huawei, Nokia, Ericsson, LG Electronics |
R3-247164 | Introduction of SDT network-based solution | Huawei, Nokia, Ericsson, LG Electronics |
R3-247179 | Discussion on SDT signalling optimization for partial context transfer | ZTE Corporation |
R3-247180 | [DRAFT] LS on network-based solution for SDT signalling optimization | ZTE Corporation |
R3-247290 | Further discussion on support of SDT network-based solution | CATT |
R3-247291 | Support of SDT network-based solution | CATT, Nokia |
R3-247292 | Support of SDT network-based solution | CATT |
R3-247295 | Issues for network based solution for SDT partial UE context transfer | Qualcomm Incorporated, ZTE |
R3-247503 | Introduction of SDT network-based solution | Nokia, Ericsson, Huawei, LG Electronics |
R3-247504 | Introduction of SDT network-based solution | Nokia, Huawei, Ericsson, LG Electronics |
R3-247505 | Response LS on SDT signalling optimization for partial context transfer | Nokia |
R3-247506 | Further discussion related to the Reply LS on improved KPIs | Ericsson |
R3-247507 | Reply to Reply LS on improved KPIs involving end-to-end data volume transfer time analytics | Ericsson |
R3-247508 | Correction of existing reference to TS28.552 by updating it to TS28.558 | Ericsson |
R3-247573 | Introduction of SDT network-based solution | Ericsson, Nokia, Huawei, LG Electronics |
R3-247613 | Discussion on Improved KPIs involving end-to-end data volume transfer time analytics | Nokia |
R3-247614 | [Draft] Reply LS on Improved KPIs involving end-to-end data volume transfer time analytics | Nokia |
R3-247754 | Response to R3-247613, R3-247506 | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R3-247341 | Correction of mapped cell support list | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Thales |
R3-247449 | Correction of mapped cell support list | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Thales |
R3-247450 | E-SMLC OAM Configuration for IoT NTN | Ericsson, Thales, Huawei |
R3-247451 | E-SMLC OAM Configuration for IoT NTN - Motivation | Ericsson, Huawei, Thales |
R3-247464 | Discussion on Configuration Update procedure | CATT |
R3-247475 | Correction of MT-EDT | Nokia, Peraton Labs |
R3-247476 | Correction of MT-EDT | Nokia, Peraton Labs |
R3-247477 | Correction of MT-EDT | Nokia, Peraton Labs |
R3-247734 | Correction on criticality of Measurement Result | ZTE Corporation, China Unicom |
R3-247735 | Correction on criticality of Measurement Result | ZTE Corporation, China Unicom |
R3-247736 | Correction on criticality of Measurement Result | ZTE Corporation, China Unicom |
R3-247739 | Discussion on criticality of measurement result | ZTE Corporation, CATT, China Telecom, China Unicom |
R3-247740 | Correction on criticality of Measurement Result for Data Collection | ZTE Corporation, Lenovo, CMCC, China Telecom, China Unicom |
R3-247866 | Correction on Neighbour Information | CATT |
R3-247867 | Correction on Neighbour Information | CATT |
R3-247880 | Correction on neighbour information | CATT,China Telecom,Nokia,CMCC |
R3-247881 | Correction on neighbour information | CATT,China Telecom,Nokia,CMCC |
R3-247927 | Correction on neighbour information | CATT,China Telecom,Nokia,CMCC |
TDoc | Title | Source |
---|---|---|
R3-247012 | Reply LS on intra-SN SCPAC in MN format | RAN2(ZTE) |
R3-247013 | L3 measurement based LTM support over F1 | RAN2(Vodafone) |
R3-247014 | Reply LS on Early TA acquisition for the inter-DU scenario | RAN2(Google) |
R3-247105 | Discussion on L3 L1/2 Triggered Mobility | Nokia, LG Electronics, NTT Docomo |
R3-247106 | L3 based L1/2 Triggered Mobility | Nokia, NTT Docomo, LG Electronics |
R3-247107 | L3 based L1/2 Triggered Mobility | Nokia |
R3-247122 | Draft CR with rethinking on Rel-18 group paging design | ZTE Corporation, China Telecom, CMCC, Lenovo |
R3-247124 | Corrections for Early TA acquisition for PDCCH order in LTM | Google, ZTE, Huawei, Ericsson, Nokia, CATT, China Telecom, LG Electronics |
R3-247125 | Corrections for L3 measurement triggered LTM cell switch | |
R3-247133 | Clarification of the chapter title to match the description of the UE History Information | Nokia, ZTE, CMCC |
R3-247134 | Correction of a wrong description of the S-NG-RAN node Counter Check procedure | Nokia |
R3-247135 | Correction of a wrong description of the S-NG-RAN node Counter Check procedure | Nokia |
R3-247136 | Correction of a wrong description of the S-NG-RAN node Counter Check procedure | Nokia |
R3-247137 | Correction of a wrong description of the S-NG-RAN node Counter Check procedure | Nokia |
R3-247155 | Correction on CIoT optimization with 5GC | Huawei, Ericsson, Qualcomm Incorporated, ZTE, Nokia |
R3-247156 | Correction on CIoT optimization with 5GC | Huawei, Ericsson, Qualcomm Incorporated, ZTE, Nokia |
R3-247157 | Correction on CIoT optimization with 5GC | Huawei, Ericsson, Qualcomm Incorporated, ZTE, Nokia |
R3-247165 | Editorial correction on TNL Configuration Info | NTTDOCOMO, INC. |
R3-247166 | Editorial correction on TNL Configuration Info | NTTDOCOMO, INC. |
R3-247173 | [DRAFT] Reply LS on intra-SN SCPAC in MN format | ZTE Corporation |
R3-247194 | Periodic E-CID measurement procedure | Jio |
R3-247199 | Correction on IAB RESOURCE COORDINATION | ZTE Corporation, Lenovo, Nokia, Nokia Shanghai Bell, Samsung |
R3-247200 | Correction on IAB RESOURCE COORDINATION | ZTE Corporation, Lenovo, Nokia, Nokia Shanghai Bell, Samsung |
R3-247218 | Corrections for QoE intra-5GC inter-RATs mobility | NEC |
R3-247219 | Corrections for QoE intra-5GC inter-RATs mobility on XnAP | NEC |
R3-247237 | Signaling enhancements for L3 measurement based R18 LTM | Qualcomm Incorporated, Reliance JIO, Bharti Airtel |
R3-247259 | Clarification on resumption of non-SDT bearer in SDT termination | |
R3-247265 | Discussion on L3 measurement based LTM support over F1 (CRs included) | Huawei |
R3-247266 | Correction on the Signalling based MDT PLMN List | Huawei |
R3-247267 | QoE measurement handling in idle mode | CATT, Ericsson, ZTE, Xiaomi |
R3-247274 | Correction for resource configuration | CATT |
R3-247275 | Correction for resource configuration | CATT |
R3-247288 | Correction to area-specific SRS activation | CATT, ZTE, Ericsson, China Telecom, Nokia, Samsung, Qualcomm Incorporated, Xiaomi, Huawei |
R3-247289 | Correction to area-specific SRS activation | CATT, ZTE, Ericsson, China Telecom, Nokia, Samsung, Qualcomm Incorporated, Xiaomi, Huawei |
R3-247333 | Correction on Positioning SRS Resource in TS38.455 | China Telecom, ZTE,CATT |
R3-247334 | Correction on Positioning SRS Resource in TS38.473 | China Telecom, ZTE,CATT |
R3-247349 | Discussion on L3 measurement based LTM | Samsung |
R3-247358 | Discussion on the PDCP SN gap report handling during UE’s handover | Huawei, CATT, Xiaomi, China Telecom, LG Electronics |
R3-247394 | Correction on the presence issue of TCI states configuration List | CATT,Google, Huawei, Nokia, China Telecom, CMCC |
R3-247395 | Correction of mapped cell support list | Huawei, Ericsson, Nokia, Thales |
R3-247396 | Correction of mapped cell support list | Huawei, Ericsson, Nokia, Thales |
R3-247397 | Correction on Measurement Time Window | Huawei, CMCC, CUC, Ericsson, Nokia |
R3-247406 | Introduction of AUN3 device access | Huawei, Nokia, Nokia Shanghai Bell, CATT |
R3-247407 | Introduction of AUN3 device access | Huawei, Nokia, Nokia Shanghai Bell, CATT |
R3-247412 | On Rel-18 UE performance feedback for AI/ML for NG-RAN | Huawei, Lenovo, Deutsche Telekom, Telecom Italia, BT, InterDigital, Nokia |
R3-247413 | [Draft] LS on per-UE UE performance metrics | Huawei, Lenovo, Deutsche Telekom, Telecom Italia, BT, InterDigital, Nokia |
R3-247460 | Stage 2 updates for support of L3 measurements based LTM | CATT, Ericsson, Vodafone |
R3-247465 | Discussion on definition of UE performance metrics | CATT,Deutsche Telekom,China Unicom,ZTE,China Telecom,Jio |
R3-247466 | [DRAFT] LS on UE level measurements | CATT,Deutsche Telekom,China Unicom,ZTE,China Telecom,Jio |
R3-247478 | Correction of MBS PDCP packets discard | Nokia, Huawei, Qualcomm, CMCC, CBN, China Broadnet |
R3-247479 | Correction on PDCP packets discard in case of MBS broadcast path update | Nokia, Huawei, Qualcomm Incorporated, CMCC, CBN, Chnia Broadnet |
R3-247481 | Correction of MBS PDCP packets discard in case of MBS broadcast path update | Nokia, Huawei, Qualcomm Incorporated, CMCC, CBN, China Broadnet |
R3-247509 | On the special case of Nrb 12 and Nrb 20 Transmission Bandwidth configurations | Ericsson, Strict, Qualcomm |
R3-247510 | Stage 2 correction for network slice support during XN handover | Ericsson, Jio, AT&T, Rakuten, Telecom Italia, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia |
R3-247511 | Stage 2 correction for network slice support during XN handover | Ericsson, Jio, AT&T, Rakuten, Telecom Italia, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia |
R3-247512 | Stage 2 correction for network slice support during XN handover | Ericsson, Jio, AT&T, Rakuten, Telecom Italia, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia |
R3-247513 | Stage 2 correction for network slice support during XN handover | Ericsson, Jio, AT&T, Rakuten, Telecom Italia, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia |
R3-247514 | Correction for Data Collection Reporting procedure’s interaction with Handover Request procedure | Ericsson, Jio, AT&T, InterDigital, Lenovo |
R3-247515 | Corrections on Xn Setup Duplication | Ericsson |
R3-247516 | Corrections on Xn Setup Duplication | Ericsson |
R3-247517 | Corrections on Xn Setup Duplication | Ericsson |
R3-247518 | Corrections on Xn Setup Duplication | Ericsson |
R3-247530 | Discussion on Periodic E-CID Measurement Procedure | Jio |
R3-247532 | Periodic E-CID measurement procedure | Jio |
R3-247540 | Clarification on NTN time-based handover over NG | ZTE Corporation. CMCC, China Telecom |
R3-247541 | Clarification on NTN time-based handover over S1 | ZTE Corporation, CMCC, China Telecom |
R3-247542 | Discussion on Location Reporting Control procedure for UPF Relocation | ZTE Corporation, CMCC, China Telecom |
R3-247543 | Correction on Location Reporting Control procedure for NR NTN | ZTE Corporation, CMCC, China Telecom |
R3-247544 | Correction on Location Reporting Control procedure for NR NTN | ZTE Corporation, CMCC, China Telecom |
R3-247553 | Support MUSIM capability restriction over XnAP | Ericsson, Qualcomm Incorporated, Xiaomi |
R3-247554 | Support MUSIM capability restriction | Ericsson, Qualcomm Incorporated, Xiaomi |
R3-247555 | Support MUSIM capability restriction over NGAP | Ericsson, Qualcomm Incorporated, Xiaomi |
R3-247562 | NR-DC QMC Coordination for RRC Segmentation | Nokia, ZTE, Samsung |
R3-247570 | Correction of UE Rx-Tx Time difference measurements | Ericsson, Polaris Wireless, CATT, Huawei |
R3-247574 | Corrections to Stage-2 for XR awareness | Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung, ZTE, China Telecom, Xiaomi, CATT, CMCC, Lenovo |
R3-247575 | Correction on Measurement Time Window | Ericsson, Huawei, CMCC, CUC, Nokia |
R3-247583 | Support of AUN3 devices | Ericsson, BT, China Unicom |
R3-247584 | Support of AUN3 devices | Ericsson, BT, China Unicom |
R3-247605 | Support of UE specific SRS reservation | Samsung, CATT, Huawei, ZTE, Ericsson, Nokia, Xiaomi |
R3-247606 | Corrections to QMC support in NR-DC for RRC Segmentation | Samsung, ZTE Corporation, Nokia, China Unicom, China Telecom |
R3-247633 | Correction of Unavailable GUAMI in AMF Status Indication message | Huawei, China Telecom, China Unicom |
R3-247634 | Correction of Unavailable GUAMI in AMF Status Indication message | Huawei, China Telecom, China Unicom |
R3-247635 | Correction of Unavailable GUAMI in AMF Status Indication message | Huawei, China Telecom, China Unicom |
R3-247638 | Further miscellaneous corrections to QMC procedure | Huawei, China Unicom, Lenovo |
R3-247644 | Addition of procedural description of CPAC Configuration | ZTE Corporation, Samsung, China Telecom |
R3-247655 | Introduction to coordination for QoE RRC segmentation in NR-DC | ZTE Corporation, Samsung, Nokia, China Unicom, China Telecom |
R3-247656 | Discussion on NR-DC QMC Coordination for RRC Segmentation | ZTE Corporation, Samsung, Nokia, China Unicom, China Telecom |
R3-247690 | Clarification on the name of AP ID over Xn interface for Rel-15 | CMCC, CATT, Huawei, ZTE |
R3-247691 | Clarification on the name of AP ID over Xn interface for Rel-16 | CMCC, CATT, Huawei, ZTE |
R3-247692 | Clarification on the name of AP ID over Xn interface for Rel-17 | CMCC, CATT, Huawei, ZTE |
R3-247693 | Clarification on the name of AP ID over Xn interface for Rel-18 | CMCC, CATT, Huawei, ZTE |
R3-247704 | Discussion on abnormal case of Xn setup procedure | ZTE Corporation |
R3-247705 | Correction on Xn Setup message | ZTE Corporation |
R3-247706 | Correction on Xn Setup message | ZTE Corporation |
R3-247707 | Correction on Xn Setup message | ZTE Corporation |
R3-247708 | Correction on Xn Setup message | ZTE Corporation |
R3-247711 | Correction on DL LBT failure information | CATT |
R3-247725 | F1 support for L3 measurements-based LTM | Ericsson, Vodafone, CATT |
R3-247728 | Triggering LTM without L1 measurements UE capability | Ericsson, Vodafone, CATT |
R3-247729 | Stage-2 updates for intra-SN S-CPAC with MN involvement | Ericsson, Nokia, CATT |
R3-247737 | Correction on criticality of Time Window Information SRS | ZTE Corporation, CATT, Ericsson, Huawei, Nokia |
R3-247738 | Support of UE specific SRS reservation | ZTE Corporation, CATT, Huawei, Samsung, Nokia, Ericsson, Xiaomi |
R3-247742 | Correction on "S-CPAC Request" IE description for Intra-SN S-CPAC in MN format | LG Electronics Inc. |
R3-247743 | Correction on the UE Initial Access procedure | Ericsson |
R3-247744 | Correction on the UE Initial Access procedure | Ericsson |
R3-247745 | Correction on the UE Initial Access procedure | Ericsson |
R3-247746 | Correction on the UE Initial Access procedure | Ericsson |
R3-247765 | Correction for resource configuration | CATT |
R3-247766 | Correction for resource configuration | CATT |
R3-247772 | Corrections for Early TA acquisition for PDCCH order in LTM | Google, ZTE, Huawei, Ericsson, Nokia, CATT, China Telecom, LG Electronics, Samsung |
R3-247773 | Stage-2 updates for intra-SN S-CPAC with MN involvement | Ericsson, Nokia, CATT |
R3-247774 | CB:#7_L3LTM | Vodafone |
R3-247775 | LS on per-UE UE performance metrics | RAN3(Huawei) |
R3-247776 | Support of UE specific SRS reservation | ZTE Corporation, CATT, Huawei, Samsung, Nokia, Ericsson, Xiaomi |
R3-247777 | Correction on Measurement Time Window | Huawei, CMCC, CUC, Ericsson, Nokia, China Telecom, ZTE, CATT |
R3-247778 | Correction on Measurement Time Window | Ericsson, Huawei, CMCC, CUC, Nokia, China Telecom, ZTE, CATT |
R3-247779 | Correction of UE Rx-Tx Time difference measurements | Ericsson, Polaris Wireless, CATT, Huawei, ZTE, China Telecom |
R3-247780 | CB:#12_MultipleXnSetup | ZTE |
R3-247792 | LS on Update of Broadcast MCCH Information | RAN3(Nokia) |
R3-247807 | Correction on PDCP packets discard in case of MBS broadcast path update | Nokia, Huawei, Qualcomm Incorporated, CMCC, CBN, Chnia Broadnet |
R3-247808 | Correction of MBS PDCP packets discard in case of MBS broadcast path update | Nokia, Huawei, Qualcomm Incorporated, CMCC, CBN, China Broadnet |
R3-247817 | Corrections to Stage-2 for XR awareness | Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung, ZTE, China Telecom, Xiaomi, CATT, CMCC, Lenovo |
R3-247818 | CB:#26_PDCPSN | Huawei |
R3-247850 | Correction on CIoT optimization with 5GC | Huawei, Ericsson, Qualcomm Incorporated, ZTE, Nokia |
R3-247851 | Correction on CIoT optimization with 5GC | Huawei, Ericsson, Qualcomm Incorporated, ZTE, Nokia |
R3-247852 | Correction on AMF CP Relocation Indication | Huawei, Ericsson, Qualcomm Incorporated, ZTE, Nokia |
R3-247853 | Correction on CIoT optimization with 5GC | Huawei, Ericsson, Qualcomm Incorporated, ZTE, Nokia |
R3-247854 | LS on QMC Coordination for RRC Segmentation in NR-DC | RAN3(ZTE) |
R3-247862 | Stage 2 updates for support of L3 measurements based LTM | CATT, Ericsson, Vodafone, ZTE, Google, Samsung, LG Electronics, NTT DoCoMo, Nokia |
R3-247863 | Support of L3 measurement based LTM | Huawei |
R3-247868 | F1 support for L3 measurements-based LTM | Ericsson, Vodafone, CATT |
R3-247869 | [Draft] LS on PDCP SN gap report handling during UE mobility | Huawei |
R3-247870 | Correction on Positioning SRS Resource | China Telecom, ZTE,CATT, China Unicom, Ericsson, Huawei, Nokia |
R3-247871 | Correction on Positioning SRS Resource | China Telecom, ZTE,CATT, China Unicom, Ericsson, Huawei, Nokia |
R3-247882 | Stage-2 updates for intra-SN S-CPAC with MN involvement | Ericsson, Nokia, CATT, LG Electronics, Huawei, ZTE, Samsung |
R3-247884 | Correction on Positioning SRS Resource | China Telecom, ZTE, CATT, China Unicom, Ericsson, Huawei, Nokia |
R3-247885 | Correction on Positioning SRS Resource | China Telecom, ZTE,CATT, China Unicom, Ericsson, Huawei, Nokia |
R3-247886 | Correction of UE Rx-Tx Time difference measurement | Ericsson, Polaris Wireless, CATT, Huawei, ZTE, China Telecom, Nokia |
R3-247888 | LS on QMC Coordination for RRC Segmentation in NR-DC | RAN3(ZTE) |
R3-247891 | LS on PDCP SN gap report handling during UE mobility | RAN3(Huawei) |
R3-247892 | LS on Update of Broadcast MCCH Information | RAN3(Nokia) |
R3-247893 | Addition of procedural description of CPAC Configuration | ZTE Corporation, Samsung, China Telecom, Nokia |
TDoc | Title | Source |
---|---|---|
R3-247037 | Correction on configuration update for an inactive Multicast session | ZTE Corporation, Huawei, CATT, Nokia, Lenovo |
R3-247038 | Correction of Positioning SI for connected UE | ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi |
R3-247039 | Correction of Positioning SI for connected UE | ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi |
R3-247040 | Correction of Positioning SI for connected UE | ZTE Corporation, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi |
R3-247041 | Correction on conditional PSCell addition or change failure | CATT, CMCC, ZTE, Nokia, Nokia Shanghai Bell |
R3-247042 | Correcting IE reference in Cell Replacing Info | Huawei, Nokia, Deutsche Telekom, Ericsson, CMCC |
R3-247043 | Correcting IE reference in Cell Replacing Info | Huawei, Nokia, Deutsche Telekom, Ericsson, CMCC |
R3-247044 | Corrections on MP relay based PDCP duplication | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell |
R3-247045 | Clarification of the usage of the UE History Information | Nokia, CMCC, Deutsche Telekom, Verizon, NTT Docomo, ZTE, Vodafone |
R3-247046 | L2 reset for intra-DU LTM | Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, Ericsson, CATT |
R3-247047 | Introduction of 2Rx XR devices support [2Rx_XR_Device] | Huawei, Qualcomm, Ericsson, Samsung, Nokia, Nokia Shanghai Bell, ZTE, China Telecom |
R3-247048 | Clarification of the usage of the UE History Information | Nokia, CMCC, Deutsche Telekom, Verizon, NTT Docomo, ZTE, Vodafone |
R3-247049 | Clarification on indication of dormant cell re-activation | CATT, Nokia, Huawei, CMCC, ZTE, NEC, Samsung |
R3-247050 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT |
R3-247051 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT |
R3-247052 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT |
R3-247053 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT |
R3-247054 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT |
R3-247055 | Positioning measurement correction related to "shall, if supported" | Huawei, CMCC, CUC, Nokia, Samsung, ZTE, Ericsson, CTC, CATT |
R3-247056 | Support positioning of L2 UE-to-network remote UE [PosL2RemoteUE] | Ericsson, CATT, Xiaomi, ZTE, Huawei, Qualcomm Inc. |
R3-247057 | Option 2: Correction on DU collecting and reporting of DL LBT failure information | CATT, Ericsson, Nokia, Huawei, Samsung, ZTE |
R3-247058 | Correction for the semantics description | Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei |
R3-247059 | Correction for the semantics description | Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei |
R3-247060 | Correction for the semantics description | Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei |
R3-247061 | Correction for the semantics description | Nokia, Nokia Shanghai Bell, CATT, ZTE, Huawei |
R3-247062 | Corrections on SL relay procedure | LG Electronics, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT |
R3-247063 | Stage-2 support for LTM L2 reset | Ericsson, Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, CATT |
R3-247064 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-247065 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-247066 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-247067 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-247068 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom, Ericsson, Huawei,ZTE, Nokia, Nokia Shanghai Bell |
R3-247069 | Correction to Requested DL PRS Transmission Characteristics | Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia |
R3-247070 | Correction to Requested DL PRS Transmission Characteristics | Qualcomm Incorporated, CATT, Ericsson, Huawei, Nokia |
R3-247071 | Correction for the reference specification on UE History Information for Rel-18 | CMCC, Huawei, CATT, ZTE, Nokia |
R3-247072 | Clarification on SpCell ID replacement | Google, Ericsson, Huawei, CATT, Nokia, Samsung, CMCC, China Telecom, Lenovo, LG Electronics, NEC, NTT Docomo, Qualcomm, ZTE |
R3-247073 | Clarification on SpCell ID replacement | Google, Ericsson, Huawei, CATT, Nokia, Samsung, CMCC, China Telecom, Lenovo, LG Electronics, NEC, NTT Docomo, Qualcomm, ZTE |
R3-247074 | Clarification on SpCell ID replacement | Google, Ericsson, Huawei, CATT, Nokia, Samsung, CMCC, China Telecom, Lenovo, LG Electronics, NEC, NTT Docomo, Qualcomm, ZTE |
R3-247075 | Correction on AI/ML Terminology | Nokia, Ericsson, ZTE, Huawei |
R3-247076 | OAM Requirements on Energy Cost index | Nokia, Jio, Telecom Italia, Ericsson, ZTE, Samsung, NEC, Huawei, Deutsche Telekom |
R3-247077 | Correction on broadcast reception for eRedCap UE [RedcapMBS] | Huawei, Qualcomm Incorporated, ZTE, CBN, Nokia, CATT |
R3-247078 | Correction on broadcast reception for eRedCap UE [RedcapMBS] | Huawei, Qualcomm Incorporated, ZTE, CBN, Nokia, CATT |
R3-247079 | Correction on MBS Service Area | Huawei, CMCC, Ericsson, CBN, Nokia |
R3-247080 | Correction on Retrieve UE Context Confirm | Huawei, Nokia, Qualcomm Incorporated |
R3-247081 | Correction on Retrieve UE Context Confirm | Huawei, Nokia, Qualcomm Incorporated |
R3-247082 | Correction of N3IWF user location information | Huawei, Nokia, Nokia Shanghai Bell, CATT |
R3-247083 | Alignment of procedural text for LTM early sync procedure | CATT, China Telecom, CMCC, Huawei, Google, Nokia, LG Electronics, Ericsson, Samsung |
R3-247084 | 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-247085 | Correction of TRP Geographical coordinates [PosLocalCoords] | Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia, ZTE |
R3-247086 | Correction of TRP Geographical coordinates [PosLocalCoords] | Ericsson, Qualcomm Inc., CATT, Xiaomi, Huawei, Nokia, ZTE |
R3-247087 | Correction on FR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-247088 | introduction of Missing Bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-247089 | introduction of Missing Bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-247090 | introduction of Missing Bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-247091 | introduction of Missing Bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-247092 | Correction of IAB F1-C transfer in NR-DC | ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung |
R3-247093 | Correction of IAB F1-C transfer in NR-DC | ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung |
R3-247094 | Correction on BAP mapping configuration for IAB | Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT |
R3-247095 | Correction on BAP mapping configuration for IAB | Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT |
R3-247096 | Correction on BAP mapping configuration for IAB | Huawei, NEC, Nokia, Nokia Shanghai Bell, CATT |
R3-247097 | Stage 2 correction for AI/ML for NG-RAN | Ericsson, Huawei, Nokia, InterDigital, ZTE, NEC, Deutsche Telekom |
R3-247098 | Correction of mobility change procedure | Huawei, Nokia, Deutsche Telekom |
R3-247099 | Coarse UE Location Information Reporting from MME to eNB for NB-IoT Ues | Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT |
R3-247100 | Coarse UE Location Information Reporting from MME to eNB – S1AP Impacts | Ericsson, Huawei, Qualcomm Incorporated, CATT, ZTE |
R3-247101 | Correction of N3IWF user location information | Huawei, Nokia, Nokia Shanghai Bell, CATT |
R3-247123 | Correction on configuration update for an inactive Multicast session | ZTE Corporation, Huawei, CATT |
R3-247127 | introduction of Missing Bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-247128 | introduction of Missing bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-247129 | introduction of Missing bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-247130 | introduction of Missing bandwidths in FR1 SRS Bandwidth | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-247810 | Introduction of 2Rx XR devices support [2Rx_XR_Device] | Huawei, Qualcomm, Ericsson, Samsung, Nokia, Nokia Shanghai Bell, ZTE, China Telecom |
R3-247811 | L2 reset for intra-DU LTM | Samsung, LG Electronics, NEC, Nokia, Google, ZTE, Huawei, Ericsson, CATT |
R3-247812 | Option 2: Correction on DU collecting and reporting of DL LBT failure information | CATT, Ericsson, Nokia, Huawei, Samsung, ZTE |
R3-247813 | Correction for the reference specification on UE History Information | CMCC, Huawei, CATT, ZTE, Nokia |
R3-247814 | Clarification on indication of dormant cell re-activation | CATT, Nokia, Huawei, CMCC, ZTE, NEC, Samsung |
R3-247815 | Coarse UE Location Information Reporting from MME to eNB for NB-IoT Ues | Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT |
R3-247816 | Coarse UE Location Information Reporting from MME to eNB - S1AP Impacts | Ericsson, Huawei, Qualcomm Incorporated, CATT, ZTE |
R3-247821 | Correction onFR1 SRS Bandwidth in Requested SRS Transmission Characteristics | China Telecom, CATT, China Unicom, Ericsson, Huawei, ZTE,Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R3-247019 | (BL CR to 36.300 for SON) Addition of SON enhancements | Lenovo |
R3-247020 | (BL CR to 36.423) Addition of SON enhancements | CATT, Samsung, Lenovo, Huawei, Ericsson, ZTE, CMCC, Nokia |
R3-247021 | (BL CR to 37.340 for SON) on MRO for S-CPAC | CMCC |
R3-247022 | (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-247023 | (BL CR to 38.401 for SON) Addition of SON enhancements | ZTE Corporation, Nokia, Huawei, Lenovo, CATT, Ericsson, Samsung |
R3-247024 | (BL CR to 38.413 for MDT) Addition of MDT enhancements | Nokia |
R3-247025 | (BL CR to 38.423 for MDT) Addition of MDT enhancements | CATT |
R3-247026 | (BL CR to 38.423 for SON) Addition of SON enhancements | ZTE Corporation, Samsung, Nokia, Lenovo, Jio |
R3-247027 | (BL CR to 38.473 for SON) Addition of SON enhancements | Huawei, Nokia, Jio |
R3-247681 | Workplan for Rel-19 SON_MDT Enhancement | CMCC, China Unicon |
R3-247865 | (BL CR to 38.401 for SON) Addition of SON enhancements | ZTE Corporation, Nokia, Huawei, Lenovo, CATT, Ericsson, Samsung |
R3-247930 | (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-247931 | (BL CR to 38.401 for SON) Addition of SON enhancements | ZTE Corporation, Nokia, Huawei, Lenovo, CATT, Ericsson, Samsung |
TDoc | Title | Source |
---|---|---|
R3-247151 | MRO enhancements for R18 mobility mechanisms | Qualcomm Incorporated |
R3-247159 | (TP for BLCR for SON for 38.300, 38.401,38.473, 38.413, 37.340, 38.423) MRO enhancement for R18 mobility mechanisms | Huawei |
R3-247223 | (TP for SON BLCR of 38.473) MRO for LTM with RLF-report unavailible | NEC |
R3-247296 | (TP to BL CR TS38.401) MRO for LTM | Samsung |
R3-247308 | (TP for SON BL CR for TS 38.473)Discussion on LTM MRO | |
R3-247309 | Failure scenarios on MRO for CHO with candidate SCGs | Samsung, Cybercore, Lenovo |
R3-247310 | (TP for SON BLCR TS38.300, TS37.340 and TS38.423) MRO for CHO with candidate SCGs and S-CPAC | Samsung |
R3-247321 | (TP for SON BL CR for TS 38.473 and for TS 37.340) MRO Enhancements for LTM, CHO with Candidate SCG(s) and S-CPAC | Nokia |
R3-247424 | (TP for SON BLCR for 38.401) Discussion on MRO for LTM | Lenovo |
R3-247425 | (TP for SON BLCR for 37.340) Discussion on MRO for subsequent CPAC and CHO with candidate SCG(s) | Lenovo |
R3-247494 | (TP for BL CR to 38.300 for SON) MRO enhancements for LTM | Ericsson |
R3-247601 | Discussion on MRO enhancements for LTM | LG Electronics Inc. |
R3-247645 | Discussion on MRO Enhancements | China Unicom |
R3-247702 | (TP for TS 38.401 TS38.473) Discussion on MRO | ZTE Corporation |
R3-247712 | (TP 37.340) MRO for R18 mobility mechanisms | CATT |
R3-247837 | SoD of MRO for LTM | Ericsson |
R3-247838 | SoD of MRO for others | Samsung |
R3-247859 | (TP to BL CR TS38.401) MRO for LTM | Samsung, Nokia, ZTE, Lenovo, Ericsson |
R3-247864 | (TP for SON BLCR TS38.300) MRO for CHO with candidate SCGs | Samsung, Nokia, CATT, Lenovo |
R3-247896 | LS on RAN3 agreements with impact on UE for Rel-19 SON/MDT | RAN3(Samsung) |
R3-247905 | (TP for SON BLCR TS38.300) MRO for CHO with candidate SCGs | Samsung, Nokia, CATT, Lenovo |
R3-247908 | LS on RAN3 agreements with impact on UE for Rel-19 SON/MDT | RAN3(Samsung) |
TDoc | Title | Source |
---|---|---|
R3-247131 | [TP to BL CR to 38.423, SON] Solution to avoid restarting MRO in NTN deployments | Nokia |
R3-247152 | SON MDT for NTN | Qualcomm Incorporated |
R3-247225 | Discussion on SON/MDT enhancements for NTN | NEC |
R3-247264 | (TP for MDT BLCRs for TS38.413, TS38.423, TS37.320) SON for Intra-NTN mobility | Huawei |
R3-247426 | Discussion on MRO for intra-NTN mobility | Lenovo |
R3-247495 | SON-MDT enhancements for NTN | Ericsson |
R3-247545 | (TP to BL CR for 38.300) Further discussion on SONMDT enhancement for NTN | ZTE Corporation |
R3-247612 | Discussion on SON enhancements for NTN | Samsung Electronics Polska |
R3-247646 | Discussion on SONMDT enhancements for NTN mobility | China Unicom |
R3-247666 | (TP to 38.300) Discussion on SONMDT enhancement for NTN | CMCC |
R3-247713 | (TP for 38.300 and 38.413) Intra-NTN mobility for SONMDT | CATT |
R3-247839 | SoD of SONMDT NTN related | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R3-247132 | [TP to BL CR to 38.300, MDT] MDT solution for slice support and slice-related mobility enhancements | Nokia |
R3-247153 | SON MDT for network slicing | Qualcomm Incorporated |
R3-247160 | SON and MDT for Network Slicing | Huawei |
R3-247496 | On MDT enhancements for Network Slicing | Ericsson, T-Mobile US, InterDigital, Jio, Telecom Italia, Deutsche Telekom |
R3-247497 | On SON enhancements for Network Slicing | Ericsson, InterDigital, Jio |
R3-247498 | (TP for BLCR for MDT for TS 38.413) Addition of MDT enhancements | Ericsson |
R3-247650 | Discussion on SONMDT enhancements for network slicing | China Unicom |
R3-247668 | Discussion on SONMDT for network slicing | CMCC |
R3-247703 | Further consideration on SON/MDT for Slicing | ZTE Corporation |
R3-247714 | Network slicing for SONMDT | CATT |
R3-247840 | SoD of SONMDT Slicing related | Nokia |
R3-247855 | Enhancements to logged MDT to support SON for network slicing | RAN3(Nokia) |
TDoc | Title | Source |
---|---|---|
R3-247154 | UHI enhancements for SCG (de)activation | Qualcomm Incorporated |
R3-247161 | (TP for BLCR for SON for 38.413, 36.423) Rel-18 SON and MDT leftovers | Huawei |
R3-247162 | [DRAFT] Reply LS on MHI enhancement solution for SCG deactivation/activation | Huawei, CMCC, ZTE, CATT [will be RAN3] |
R3-247311 | (TP for SON BLCR TS38.423 and TS36.423) Rel-18 SON and MDT leftovers | Samsung |
R3-247322 | MHI/UHI Enhancement for SCG Deactivation/Activation | Nokia |
R3-247427 | Discussion on MRO for R18 leftovers | Lenovo |
R3-247499 | Further discussion on RACH optimization for SDT | Ericsson, CATT, ZTE Corporation |
R3-247500 | (TP for BL CR to 38.413 for SON) UHI for SCG activation and deactivation | Ericsson |
R3-247546 | (TPs to BL CR for 38.300, 38.413) Further discussion on Rel-18 leftovers | ZTE Corporation |
R3-247682 | MHI and UHI Enhancement for SCG Deactivation Activation | CMCC, Huawei, CATT, Lenovo, ZTE |
R3-247694 | Discussion on RACH optimization for SDT | China Telecom |
R3-247715 | (TP for 37.340, 38.423, 36.423 and 38.413) SON enhancement for R18 leftover | CATT |
R3-247841 | SoD of SONMDT leftovers | Huawei |
R3-247843 | [DRAFT] LS on SDT enhancements for SON | Huawei |
R3-247873 | [DRAFT] Reply LS on MHI enhancement solution for SCG deactivation/activation | Huawei, CMCC, ZTE, CATT [will be RAN3] |
R3-247906 | Reply LS on MHI enhancement solution for SCG deactivation/activation | Huawei, CMCC, ZTE, CATT [will be RAN3] |
TDoc | Title | Source |
---|---|---|
R3-247028 | (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 |
R3-247741 | Work plan for Rel-19 Enhancements for AI/ML for NG-RAN | ZTE Corporation, NEC |
R3-247928 | (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-247138 | Discussion on AI/ML assisted Network Slicing | ZTE Corporation |
R3-247139 | [TP to 38.423] AI/ML assisted Network Slicing | ZTE Corporation, Qualcomm, China Unicom |
R3-247201 | (TP for BLCR for TS38.300) Support of enhancements on AI/ML for NG-RAN | NEC, ZTE, Qualcomm, Samsung, CMCC |
R3-247202 | (TP for BLCR for TS38.401) Support of enhancements on AI/ML for NG-RAN | NEC |
R3-247203 | (TP to BLCR TS38.423) AI/ML-based Slicing | NEC |
R3-247297 | Discussion on AI/ML enabled slicing | Samsung |
R3-247323 | UE Performance Data for AI/ML based Network Slicing | Rakuten Mobile, Inc |
R3-247325 | Discussion on NG-RAN AI/ML for Network Slicing | Qualcomm Incorporated |
R3-247414 | (TP for AI/ML BLCR to TS 38.423) Discussion on the AI/ML-based Network Slicing | Huawei |
R3-247442 | (TP to BLCR 38.423) Discussion on AIML based network slicing | Lenovo |
R3-247453 | (TP to TR 38.743) AI/ML assisted Network Slicing | Tejas Network Limited |
R3-247467 | (TP on 38.423)Support of AI/ML enabled Slicing | CATT |
R3-247469 | Enhancement of UE performance metrics | CATT, Jio, Qualcomm, CBN |
R3-247533 | Support for AI/ML enabled Network Slicing | Ericsson, InterDigital |
R3-247534 | (TP to TS38.423) AIML enabled Network Slicing | Ericsson, InterDigital |
R3-247596 | Discussion on AIML based Network Slicing | Jio |
R3-247604 | Discussion for AI/ML based Network Slicing | Rakuten Mobile, Inc |
R3-247615 | AI/ML Slicing Discussion | Nokia |
R3-247616 | (TP to BLCR to TS 38.423) AI/ML Slicing | Nokia |
R3-247677 | Discussion on AI-based network slice | CMCC |
R3-247678 | (TP for 38.423) AIML based slice | CMCC |
R3-247785 | CB:#AIRAN1_Slicing | Lenovo |
R3-247823 | (TP to BLCR 38.423) AIML based network slicing | Lenovo |
R3-247900 | (TP to BLCR 38.423) AIML based network slicing | Lenovo, Samsung, Huawei, Jio |
R3-247926 | (TP to BLCR 38.423) AIML based network slicing | Lenovo, Ericsson, CATT, Nokia, ZTE, LG Electronics, Samsung, Huawei, Jio |
TDoc | Title | Source |
---|---|---|
R3-247204 | (TP to BLCR TS38.423) AI/ML-based CCO | NEC |
R3-247233 | Discussions on enhancements for AIML support for CCO | Jio |
R3-247236 | Further Enhancements on AIML support for CCO | Jio |
R3-247238 | Discussion on Timing Aspects for AIML support in CCO | Jio |
R3-247298 | (TP to BL CR TS38.423) AI/ML enabled CCO | Samsung |
R3-247326 | Discussion on AI/ML enabled CCO | Qualcomm Incorporated |
R3-247374 | Discussion on AI/ML based Coverage and Capacity Optimization | China Telecom |
R3-247375 | (TP to TS38.423) Support of AI/ML based Coverage and Capacity Optimization | China Telecom |
R3-247415 | Timing information and feedback for AI/ML-based Coverage and Capacity Optimization | Huawei |
R3-247416 | (TPs for AI/ML BLCR to TS 38.423 and AI/ML BLCR to TS 38.473) Signalling details for AI/ML-based Coverage and Capacity Optimization | Huawei |
R3-247448 | (TP to BLCR 38.473) Discussion on AIML based CCO | Lenovo |
R3-247468 | (TP on 38.423/38.473) Open issues on the CCO use case | CATT |
R3-247521 | AI/ML support for CCO | Ericsson, InterDigital, Deutsche Telekom |
R3-247522 | (TP to 38.473) - AI/ML support for CCO | Ericsson, InterDigital, Deutsche Telekom |
R3-247523 | (TP to 38.423) - AI/ML support for CCO | Ericsson, InterDigital, Deutsche Telekom |
R3-247563 | A contribution to energy efficient AI/ML-based CCO issue prediction in split architecture | Nokia, Jio, Telecom Italia |
R3-247564 | Discussion on signalling for AI/ML-based CCO | Nokia, Jio |
R3-247651 | Discussion on AI/ML assisted Coverage and Capacity Optimization | ZTE Corporation |
R3-247652 | [TP to 38.401] Support of AI/ML assisted CCO | ZTE Corporation, Lenovo, China Unicom |
R3-247653 | [TP to 38.423 and 38.473] Support of AI/ML assisted Coverage and Capacity Optimization | ZTE Corporation |
R3-247679 | Discussion on AI/ML-based CCO | CMCC |
R3-247695 | Discussion on Xn and F1 impacts for AI/ML-based CCO | LG Electronics Inc. |
R3-247696 | (TP for NR_AIML_NGRAN_enh-Core for TS 38.423) Discussion on Xn and F1 impacts for AI/ML-based CCO | LG Electronics Inc. |
R3-247697 | (TP for NR_AIML_NGRAN_enh-Core for TS 38.473) Discussion on Xn and F1 impacts for AI/ML-based CCO | LG Electronics Inc. |
R3-247749 | Discussion of AI/ML based CCO | Rakuten Mobile, Inc |
R3-247750 | Data Collection Aspects for AIML support in CCO | Jio |
R3-247787 | CB:#AIRAN2_CCO | Qualcomm |
R3-247856 | [TP to 38.473] Support of AI/ML assisted Coverage and Capacity Optimization | ZTE Corporation, Qualcomm Incorporated, Samsung, Ericsson, LG Electronics, Nokia |
R3-247883 | (TP for BLCR of TS 38.423) AI/ML enabled CCO | Qualcomm Incorporated, ZTE, Samsung, Ericsson, Lenovo,CATT |
R3-247915 | (TP for BLCR of TS 38.423) AI/ML enabled CCO | Qualcomm Incorporated, ZTE, Samsung, Ericsson, Lenovo, CATT, LG Electronics, Nokia, Reliance JIO, Huawei, Deutsche Telekom, Telecom Italia, CMCC |
R3-247916 | [TP to 38.473] Support of AI/ML assisted Coverage and Capacity Optimization | ZTE Corporation, Qualcomm Incorporated |
R3-247917 | (TP to BLCR of 38.473) for AI/ML assisted Coverage and Capacity Optimization | ZTE Corporation, Qualcomm Incorporated, Samsung, Ericsson, LG Electronics, Nokia, Reliance JIO, CATT, CMCC, Lenovo, Deutsche Telekom, Telecom Italia |
R3-247929 | (BL CR to 38.473) Support of enhancements on AI/ML for NG-RAN | Ericsson, ZTE |
TDoc | Title | Source |
---|---|---|
R3-247140 | (TP to 38.423) Addition of predicted PSCell ID within DC procedure | ZTE Corporation, CATT, Samsung |
R3-247141 | (TP to 38.423) Discussion on Mobility Optimization for NR-DC | ZTE Corporation |
R3-247142 | (TP to 38.473, 37.483) Discussion on split architecture | ZTE Corporation |
R3-247143 | Discussion on continuous MDT collection | ZTE Corporation |
R3-247144 | Discussion on requirements for Continuous MDT solution | Telecom Italia, Jio, BT, Deutsche Telekom |
R3-247205 | Continuous MDT collection for AI/ML | NEC |
R3-247206 | (TP to BLCR TS38.423) NR-DC mobility optimization | NEC |
R3-247207 | (TP to BLCR TS38.473) Split architecture support | NEC |
R3-247299 | Discussion on AI/ML for mobility in NR-DC | Samsung |
R3-247300 | Discussion on AI/ML for NG-RAN in split architecture | Samsung |
R3-247301 | (CR to 37.483) AI/ML for NG-RAN on split architecture | Samsung |
R3-247302 | Discussion on continuous MDT collection targeting the same UE across RRC states | Samsung |
R3-247327 | Discussion on Continuous MDT | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
R3-247370 | Discussion on AI/ML based Mobility Optimization for NR-DC | China Telecom |
R3-247371 | (TP to TS38.423) Support of AIML based Mobility Optimization for NR-DC | China Telecom |
R3-247376 | (TP to TS38.470) Support of AI/ML for NG-RAN split architecutre | China Telecom |
R3-247377 | Discussion on Continuous MDT measurement | China Telecom |
R3-247393 | Discussion on measurement correlation for continuous MDT | CATT |
R3-247417 | (TP for AI/ML BLCR to TS 38.423) AI/ML-based Mobility Optimization in NR-DC | Huawei |
R3-247418 | (TP for AI/ML BLCR to TS 38.473) Split architecture support for Rel-18 “AI/ML for NG-RAN” use cases | Huawei |
R3-247419 | On Continuous MDT for AI/ML | Huawei |
R3-247443 | (TP to BLCR 38.423) Discussion on UE performance feedback in AIML for NR-DC | Lenovo |
R3-247444 | (TP to BLCR 38.473 and 37.483) Discussion on split architecture related issues for Rel18 use cases | Lenovo |
R3-247445 | TP to BLCR 37.340 AIML for NR-DC | Lenovo, CATT, ZTE Corporation, Samsung |
R3-247446 | TP to BLCR 38.401 AIML for RAN in split architecture | Lenovo, CATT, ZTE Corporation |
R3-247470 | AI/ML in DC scenario | CATT |
R3-247471 | (TP for TS 38.423) Introducing essentially per-DRB UE performance result for DC | CATT |
R3-247472 | (TP on 38.470/37.480) AI/ML in split gNBs | CATT |
R3-247524 | Split architecture support for Release 18 use cases | Ericsson, AT&T, Verizon |
R3-247525 | (TP to 37.483) - Split architecture support for Release 18 use cases | Ericsson, AT&T, Verizon |
R3-247526 | (TP to 38.473) - Split architecture support for Release 18 use cases | Ericsson, AT&T, Verizon |
R3-247527 | (TP to 38.423) - Split architecture support for Release 18 use cases | Ericsson, AT&T, Verizon |
R3-247535 | AI/ML support for NR-DC | Ericsson |
R3-247536 | (TP to TS38.423) - AI/ML support for NR-DC | Ericsson |
R3-247537 | Additional discussions on Continuous MDT | Ericsson, InterDigital, Jio |
R3-247538 | (TP to TS38.423) Continuous MDT collection targeting the same UE across RRC states | Ericsson, InterDigital, Jio |
R3-247539 | LS on correlation identifiers for Continuous MDT | Ericsson, InterDigital, Jio |
R3-247603 | Discussion on AIML for split architecture | NTT DOCOMO INC.. |
R3-247617 | Discussion on Energy Cost Reporting in Split Architecture | Nokia, Telecom Italia, Jio, Deutsche Telekom |
R3-247618 | Procedures over F1 for the exchange of Energy Cost index | Nokia, Telecom Italia, Jio, Deutsche Telekom |
R3-247619 | [Draft] LS on New Energy Consumption Measurement for gNB-DU | Nokia, Telecom Italia, Jio, Deutsche Telekom |
R3-247620 | Procedures for AI/ML Mobility Optimization in NR-DC | Nokia |
R3-247621 | (TP to BLCR to TS 38.423) AI/ML Mobility for NR-DC | Nokia |
R3-247622 | Discussion on Rel-18 UE Performance measurements | Nokia |
R3-247623 | Continuous Management-based MDT | Nokia, Qualcomm, Jio, Deutsche Telekom |
R3-247667 | (TP to 38.423) Discussion on AIML based Mobility Optimization for NR-DC | CMCC |
R3-247671 | Discussion on AIML for split architecure use casesv1 | CMCC, ZTE, CATT |
R3-247672 | Discussion on transferring Energy Cost for split architecure | CMCC, Samsung |
R3-247673 | (TP to 38.401) OAM requirement for Energy Saving for split architecure | CMCC, Samsung |
R3-247788 | CB:#AIRAN3_NRDC | ZTE |
R3-247789 | CB:#AIRAN4_SplitArch | CMCC |
R3-247790 | CB:#AIRAN5_ContinuousMDT | Ericsson |
R3-247827 | (TP to 38.423) Discussion on Mobility Optimization for NR-DC | ZTE Corporation |
R3-247860 | (TP to 38.473) Transfer Measured EC via F1 for split architecture | CMCC |
R3-247861 | LS on energy saving for split gNB | RAN3(CATT) |
R3-247895 | (TP to BLCR of 38.423) Mobility Optimization for NR-DC | ZTE Corporation, CATT, CMCC, Lenovo, Ericsson, Samsung, LG \tElectronics, Qualcomm Incorporated, Nokia, Huawei, NEC |
R3-247901 | LS on energy saving for split gNB | RAN3(CATT) |
R3-247907 | LS on energy saving for split gNB | RAN3(CATT) |
TDoc | Title | Source |
---|---|---|
R3-247029 | Support for Wireless Access Backhaul | Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung, Lenovo, Qualcomm |
R3-247030 | (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 |
R3-247825 | (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 |
R3-247936 | (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-247109 | (TP for WAB BL CR for TS 38.401): Functional Aspects of WAB-Nodes | Ericsson |
R3-247110 | Reply to SA2 Regarding UE Access Control and Additional ULI for WAB-Nodes | Ericsson |
R3-247195 | (TP to 38.401 36.300) Discussion on supporting WAB | ZTE Corporation |
R3-247196 | Discussion on other aspects for WAB and the reply LS to SA2 | ZTE Corporation |
R3-247197 | (TP to 38.305) Support of location service involving WAB-nodes | ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, Lenovo, CATT |
R3-247198 | (TP to 38.455) Support of location service involving WAB-nodes | ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, Lenovo, CATT |
R3-247222 | (TP to BL CR of 38.423 on WAB) Discussion on mobility and reliability for WAB | NEC |
R3-247226 | Discussion on enhancements for WAB | CANON Research Centre France |
R3-247227 | (draft Reply LS to SA2 – TP to BL CR 38.401) Discussion on SA2 questions on multi-hop WAB and UE ULI | Qualcomm Inc. |
R3-247228 | (TP to BL CR 38.401) Discussion of aspects related to WAB | Qualcomm Inc. |
R3-247229 | BL draft CR to TS 38.300 on Support of WAB | Qualcomm, Ericsson, CATT, ZTE, Nokia, Nokia Shanghai Bell |
R3-247268 | (draft Reply LSs to SA2) On support of WAB | CATT |
R3-247269 | Discussion on enhancements for WAB | CATT |
R3-247279 | Discussion on Wireless Access Backhaul | NTT DOCOMO INC. |
R3-247342 | (TP for TS 38.401) Discussion on NG management and Xn management for WAB | Nokia, Nokia Shanghai Bell |
R3-247343 | (TP for TS 38.423) Discussion on WAB mobility | Nokia, Nokia Shanghai Bell |
R3-247353 | (TP to BLCR for TS 38.410) Discussion on WAB mobility | Samsung |
R3-247354 | Discussion on other aspects for the support of WAB | Samsung |
R3-247363 | (TPs for TS 38.413) Architecture and Access control for WAB | Huawei |
R3-247364 | (TP for TS 38.401) Discussion on WAB related procedures | Huawei |
R3-247428 | Architecture and configuration for WAB-node | Lenovo |
R3-247429 | Discussion on WAB node migration | Lenovo |
R3-247627 | Discussion on RAN2 Impact and Functional Aspects of WAB | China Telecom |
R3-247628 | Discussion on Multi-hop Prevention and Authorization for WAB | China Telecom |
R3-247722 | Further consideration on support of WAB | LG Electronics |
R3-247723 | (TP to TS 38.401 and 38.423) TP for WAB support | LG Electronics |
R3-247771 | Reply to SA2 Regarding UE Access Control and Additional ULI for WAB-Nodes | Ericsson |
R3-247793 | Summary of Offline Discussion on additional topological enhancement | NTTDOCOMO, INC. |
R3-247826 | Reply LS on FS_VMR_Ph2 solution impacts to RAN (Access Control and Additional ULI) | RAN3(Samsung) |
R3-247828 | CB: WAB | DoCoMo |
R3-247872 | Reply LS on FS_VMR_Ph2 solution impacts to RAN | RAN3(Qualcomm) |
R3-247909 | Reply LS on FS_VMR_Ph2 solution impacts to RAN (Access Control and Additional ULI) | RAN3(Samsung) |
R3-247910 | Reply LS on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility) | RAN3(Qualcomm) |
TDoc | Title | Source |
---|---|---|
R3-247018 | Reply LS on Clarification regarding definition of 5G NR femto ownership | SA2(LGE) |
R3-247208 | Open issues for NR Femto | NEC |
R3-247270 | Discussion on stage-2 NR Femto | CATT |
R3-247271 | Impact to NGAP for NR Femto | CATT |
R3-247280 | Discussion on 5G femto | NTT DOCOMO INC. |
R3-247355 | (TP to TS 38.300) Discussion on NR Femto architecture and functional split | Samsung |
R3-247356 | (TP to TS 38.300) Discussion on access control for NR Femto | Samsung |
R3-247365 | (TP for TS 38.300/38.413) Architecture and functional split for NR Femto | Huawei |
R3-247366 | (TP for TS 38.300) Access control for NR Femto | Huawei |
R3-247388 | On NR Femto Architecture and functional split | China Telecom |
R3-247430 | Architecture and access control for NR Femto | Lenovo |
R3-247431 | TP to 38.300 for NR Femto | Lenovo |
R3-247452 | NR Femto - Further Stage 2 Aspects | Ericsson LM |
R3-247454 | NR Femto - Stage 2 TP | Ericsson |
R3-247482 | Completion of Functional aspects of NR Femto Architecture | Nokia |
R3-247486 | [TP for BL CR NR Femto 38.300] Introduction of Functional aspects of NR Femto architecture | Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, ZTE |
R3-247487 | Introduction of NR Femto architecture with optional NR Femto GW | Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, ZTE |
R3-247488 | LS on Security verifications related to NR Femtos | Nokia |
R3-247648 | Discussion on NR Femto Architecture and Functionality | Baicells |
R3-247649 | TP to BL CR for TS 38.300 on NR Femto | Baicells |
R3-247724 | (TP for TS 38.300) Functional split and Access control on 5G Femto | LG Electronics |
R3-247730 | TP for access control for NR Femto | ZTE corporation, Nokia |
R3-247731 | TP for 38.300&38.410 NR Femto | ZTE corporation |
R3-247791 | [TP for BL CR NR Femto 38.300] Introduction of Functional aspects of NR Femto architecture | Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, ZTE |
R3-247796 | (TP to 38.410) AMF selection for NR Femto | ZTE |
R3-247799 | (TP for TS 38.300) Architecture and Protocol stack for NR Femto | Huawei |
R3-247800 | (TP for TS 38.413) Functional split for NR Femto | Huawei, Nokia |
R3-247804 | (TP to 38.300) Architecture | ZTE |
R3-247809 | Access Control with NR Femto – Stage 2 TP | Ericsson |
R3-247819 | LS on NR Femto | RAN3(ZTE) |
R3-247829 | Access Control with NR Femto – Stage 2 TP | Ericsson, Huawei, Nokia, China Telecom, Lenovo, Samsung, NTT DOCOMO, ZTE, Verizon, BT |
R3-247832 | [TP for BL CR NR Femto 38.300] Introduction of Functional aspects of NR Femto architecture | Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, ZTE, Ericsson, Huawei, NTT Docomo, China Telecom, Samsung, Baicells, Lenovo |
R3-247833 | (TP for TS 38.413) Functional split for NR Femto | Huawei, Nokia, NEC |
R3-247834 | (TP to 38.410) AMF selection for NR Femto | ZTE |
R3-247937 | (BL CR to 38.410 for Femto) Introduction of NR Femto in NGAP list of functions | ZTE Corporation |
R3-247938 | (BL CR to 38.413 for Femto) Support of NR Femto architecture with NR Femto Gateway | Nokia, Huawei, NEC |
TDoc | Title | Source |
---|---|---|
R3-247031 | (BL CR to 38.300) Support for Inter-CU LTM | Nokia, Huawei, Google, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung |
R3-247032 | (BL CR to 38.423) Xn support for inter-CU LTM | Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC, ZTE, LG Electronics |
R3-247820 | (BL CR to 38.423) Xn support for inter-CU LTM | Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC, ZTE, LG Electronics |
R3-247932 | (BL CR to 38.300) Support for Inter-CU LTM | Nokia, Huawei, Google, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung |
R3-247933 | (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-247006 | LS on the support of semi-persistent CSI-RS resource for LTM candidate cells | RAN1(Fujitsu) |
R3-247102 | Discussion on Inter-gNB-CU LTM Procedure | Nokia |
R3-247103 | Discussion on Inter-CU LTM Dual Connectivity | Nokia |
R3-247104 | TP (BL CR TS 38.401) L1/2 Triggered Mobility (LTM) Procedures | Nokia |
R3-247108 | Discussion on semi-persistent CSI-RS resource for LTM | Nokia |
R3-247111 | LS on RAN2 agreements for inter-CU LTM | RAN2(ZTE) |
R3-247112 | Support of Multiple Reference Configurations | Nokia. KDDI, LG Electronics, ZTE, Rakuten, Fujitsu |
R3-247126 | (TP to BL CR to 38.300 and 38.423) Support for reference configurations in the inter-CU MCG LTM | |
R3-247181 | (BL CR to 38.420) Support for Inter-CU LTM | ZTE Corporation |
R3-247182 | TP for SN initiated inter-SN LTM | ZTE Corporation |
R3-247183 | Discussion on inter-CU LTM | ZTE Corporation |
R3-247211 | discussion of Rel-19 inter-CU LTM issues | NEC |
R3-247212 | Rel-19 inter-CU LTM in DC scenario | NEC |
R3-247213 | (TP to 38.423 on inter-CU LTM) inter-CU LTM related information | NEC |
R3-247232 | Comparison of RRC/PDCP anchor and anchor switch-based solutions for inter-gNB LTM | Qualcomm Incorporated, Reliance JIO, Vodafone, NTT DoCoMo, Sony |
R3-247234 | Impact analysis of coupling LTM cell switch and CU anchor changes on subsequent inter-gNB LTM | Qualcomm Incorporated, Reliance JIO, Vodafone, NTT DoCoMo, Sony, Bharti Airtel |
R3-247235 | Signalling enhancements for inter-CU LTM HO | Qualcomm Incorporated, Reliance JIO, Vodafone, NTT DoCoMo, Sony, Bharti Airtel |
R3-247239 | Inter-gNB/CU LTM typical deployment scenarios and operational requirements | Jio, Qualcomm, Sony, Bharti Airtel, NTT Docomo, Telstra |
R3-247260 | Further analysis on the PDCP anchor based solution | Huawei, Ericsson, CATT, China Telecom, CMCC,Samsung |
R3-247261 | (TP for LTM BLCR for TS38.473): Further discussion on inter-CU LTM procedure | Huawei |
R3-247262 | (TP for LTM BLCR for TS38.300): Update on inter-CU LTM basic procedure | Huawei |
R3-247263 | [DRAFT] Reply LS on the support of semi-persistent CSI-RS resource for LTM candidate cells | Huawei |
R3-247350 | Discussion on inter-gNB-CU LTM | Samsung |
R3-247351 | Additional discussion on Inter-gNB-CU LTM | Samsung |
R3-247352 | (TP to BLCR for TS 38.401) Procedure on Inter-gNB-CU LTM | Samsung |
R3-247367 | Discussion on signaling enhancement for inter-CU LTM | China Telecom |
R3-247368 | Discussion on support of inter-CU LTM in NR-DC scenario | China Telecom |
R3-247369 | (TP for TS38.300) On support of inter-CU LTM | China Telecom |
R3-247389 | (draft reply LS) Discussion on support of semi-persistent CSI-RS resource | CATT |
R3-247390 | Discussion for Inter-CU LTM | CATT |
R3-247391 | Discussion for Inter-CU LTM in DC | CATT |
R3-247432 | [TP to BLCR for TS 38.300] Inter-CU LTM | Lenovo |
R3-247433 | [TP to BLCR for TS 38.423] Inter-CU LTM | Lenovo |
R3-247434 | General aspects of inter-CU SCG LTM | Lenovo |
R3-247483 | Comprehensive analysis of inter-CU LTM | Ericsson |
R3-247484 | (TPs to BL CRs for TS 38.300 and 38.423) – Support for inter-CU LTM | Ericsson |
R3-247485 | Network coordination for transmission of semi-persistent CSI-RS | Ericsson |
R3-247590 | 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, NEC |
R3-247591 | Keep continuing discussions on Inter-CU LTM signaling design | LG Electronics Inc. |
R3-247592 | (TP for NR_Mob_Ph4 TS 38.423 BL CR) | LG Electronics Inc. |
R3-247629 | Discussion on inter-CU LTM non-DC case | NTT DOCOMO INC.. |
R3-247630 | [Draft] Reply LS on the support of semi-persistent CSI-RS resource for LTM candidate cells | NTT DOCOMO INC.. |
R3-247661 | Comparison of RRC/PDCP anchor and anchor switch-based solutions for inter-gNB LTM | Qualcomm Incorporated, Reliance JIO, Vodafone, NTT DOCOMO, Sony, Bharti Airtel |
R3-247680 | Discussion on inter-CU LTM | CMCC |
R3-247709 | Initial considerations on Inter-CU LTM | Rakuten Mobile, Inc |
R3-247710 | Data forwarding and transmission in Inter-CU LTM | Rakuten Mobile, Inc |
R3-247747 | Inter-gNB/CU LTM typical deployment scenarios and operational requirements | Jio, NTT DOCOMO, Qualcomm Incorporated, Vodafone, Sony, Bharti Airtel, Telstra |
R3-247751 | Discussion on inter-CU LTM DC case | NTT DOCOMO INC.. |
R3-247755 | Response to R3-247260 | Qualcomm Incorporated |
R3-247757 | Reply LS on security handling for inter-CU LTM in non-DC cases | SA3(Samsung) |
R3-247758 | Reply LS on security key update of inter-CU SCG LTM | SA3(Xiaomi) |
R3-247762 | Response to R3-247111 and R3-247112 | LG Electronics Inc, ZTE, Fujitsu, KDDI, KT Corp., ITRI, Rakuten, ETRI, SK Telecom, LG Uplus |
R3-247822 | Reply LS for LS on the support of semi-persistent CSI-RS resource for LTM candidate cells | RAN3(CATT) |
R3-247824 | CB:#25_MobilityEnh | China Telecom |
R3-247887 | (BL CR to 38.420) Support for Inter-CU LTM | ZTE Corporation, China Telecom, Samsung, Nokia, CATT, NEC, LG Electronics, Ericsson, Huawei |
R3-247889 | (TP for LTM BLCR for TS38.300): Update on inter-CU LTM basic procedure | Huawei |
R3-247890 | (TP to BL CR for TS 38.423) – Further updates for inter-CU LTM | Ericsson, LG Electronics, CATT, Huawei, Nokia, Google, China Telecom |
R3-247911 | Reply LS for LS on the support of semi-persistent CSI-RS resource for LTM candidate cells | RAN3(CATT) |
R3-247912 | (TP for LTM BLCR for TS38.300): Update on inter-CU LTM basic procedure | Huawei, LG Electronics, Nokia, ZTE, Ericsson, Samsung, CATT, NEC, China Telecom, Google, Lenovo |
R3-247913 | (TP to BL CR for TS 38.423) – Further updates for inter-CU LTM | Ericsson, LG Electronics, CATT, Huawei, Nokia, Google, China Telecom, NEC |
R3-247914 | (BL CR to 38.420) Support for Inter-CU LTM | ZTE Corporation, China Telecom, Samsung, Nokia, CATT, NEC, LG Electronics, Ericsson, Huawei, Lenovo |
TDoc | Title | Source |
---|---|---|
R3-247033 | (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-247034 | (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-247035 | 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 |
R3-247835 | (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-247934 | (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-247935 | (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-247214 | (TP for TS 38.300 and TS 38.413) Discussion on NR NTN supporting MBS broadcast service | NEC |
R3-247282 | Support of MBS broadcast service for NR NTN | CATT |
R3-247344 | (TP to BL CR for TS 38.300 and TS 38.413) Discussion on the support of MBS Broadcast Service | Nokia, Nokia Shanghai Bell |
R3-247379 | Support of MBS broadcast service for NTN | China Telecom |
R3-247383 | Support of MBS broadcast service for NTN | China Telecom |
R3-247399 | (TP for TS 38.300 and TS 38.413) Support MBS broadcast service | Huawei |
R3-247435 | Broadcast service continuity in NTN | Lenovo |
R3-247607 | Further discussion on support broadcast service for NR NTN | Samsung |
R3-247641 | Further Discussion on Support of MBS Broadcast Service | TCL |
R3-247654 | (TP for TS 38.300) Discussion on NTN broadcast service supporting | ZTE Corporation |
R3-247674 | (TP to 38.300) Discussion on Supporting MBS broadcast service for NR NTN | CMCC |
R3-247842 | CB:#NRNTN1_MBS | Nokia |
R3-247847 | (TP to BL CR for TS 38.300) support of MBS Broadcast Service | Nokia, Nokia Shanghai Bell, CATT, Huawei, Xiaomi, NEC, Qualcomm, ZTE, Ericsson |
R3-247848 | (TP to BL CR for TS 38.413) support of MBS Broadcast Service | Huawei, Nokia, Nokia Shanghai Bell |
R3-247899 | (TP to BL CR for TS 38.413) support of MBS Broadcast Service | Huawei, Nokia, Nokia Shanghai Bell, Ericsson, Xiaomi, CATT, NEC, ZTE |
TDoc | Title | Source |
---|---|---|
R3-247016 | Reply LS on Support of Regenerative-based Satellite Access | SA2(Qualcomm) |
R3-247215 | (TP for TS 38.300) Discussion on regenerative payload enhancement for NR NTN | NEC |
R3-247283 | (TP to BL CR for 38.413) Support of regenerative payload | CATT |
R3-247316 | Support of Inactive UE mobility NTN | Xiaomi, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, China Telecom, Lenovo |
R3-247317 | (TP for TS 38.300) Support of regenerative payload | Xiaomi |
R3-247328 | (TP for TS 38.300) NR NTN Regenerative Payload Architecture | Qualcomm Incorporated, Xiaomi, LGE, NTT Docomo |
R3-247329 | (TP for TS 38.300) Discussion on RAN Signaling impacts for NR NTN Regenerative Payload | Qualcomm Incorporated |
R3-247330 | Draft Reply for LS on Support of Regenerative-based Satellite Access | Qualcomm Incorporated |
R3-247345 | (TP for TS 38.300) Discussion on the support of Regenerative payload | Nokia, Nokia Shanghai Bell |
R3-247380 | Discussion on regenerative payload enhancement | China Telecom |
R3-247384 | Discussion on regenerative payload enhancement | China Telecom |
R3-247398 | (TP for BLCR for TS 38.300) Correction on stage 2 | Huawei, Nokia, Nokia Shanghai Bell, Thales, CATT |
R3-247400 | (TP for TS 38.300) Support of regenerative payload | Huawei |
R3-247436 | Interface management for regenerative payload in NTN | Lenovo |
R3-247461 | Considerations on NG Interface Management over the Feeder Link | Ericsson, Thales |
R3-247462 | Making the Case for Location-Based CHO in Rel-19 | Ericsson, Thales, ESA, Inmarsat, Viasat |
R3-247463 | Location-Based CHO in Rel-19 - XnAP Aspects | Ericsson, Thales, ESA, Inmarsat, Viasat |
R3-247547 | Further discussion on support of regenerative payload | ZTE Corporation |
R3-247593 | Discussions on NG management from satellite gNB and Inactive support | LG Electronics Inc. |
R3-247594 | (TP for NR_NTN_Ph3 TS 38.300 BL CR) | LG Electronics Inc. |
R3-247600 | Discussion on NG interface management through ISL | ETRI |
R3-247608 | Further discussion on support of regenerative payload for NR NTN | Samsung |
R3-247642 | Discussion on Support of NTN Regenerative Architecture | TCL |
R3-247675 | Discussion on support of regenerative payload for NR NTN | CMCC |
R3-247844 | CB:#NRNTN2_Regenerative | CATT |
TDoc | Title | Source |
---|---|---|
R3-247548 | Updated Work Plan for IoT NTN | ZTE Corporation, CATT, MediaTek.Inc |
TDoc | Title | Source |
---|---|---|
R3-247008 | LS on PWS support for NB-IoT NTN | RAN2(InterDigital) |
R3-247318 | Support of Store and Forward in IoT NTN | Xiaomi |
R3-247331 | Discussion on Support for IoT NTN for Regenerative Payload | Qualcomm Incorporated |
R3-247346 | Discussion on the support of IoT NTN | Nokia, Nokia Shanghai Bell |
R3-247378 | Support for IoT NTN with regenerative payload | China Telecom |
R3-247382 | Support for IoT NTN with regenerative payload | China Telecom |
R3-247392 | Discussion for IoT NTN | CATT |
R3-247401 | (TP for TS 36.300) Support of store and forward for IoT NTN | Huawei |
R3-247455 | How to Specify Store & Forward (S&F) Architecture in RAN3 | Ericsson, Sateliot, Thales, ESA, Deutsche Telekom |
R3-247456 | Store & Forward (S&F) Architecture - Stage 2 Impacts | Ericsson, Sateliot, Thales, ESA, Deutsche Telekom |
R3-247457 | Store & Forward (S&F) Architecture - S1 Removal | Ericsson, Sateliot, Thales, ESA, Deutsche Telekom |
R3-247458 | Store & Forward (S&F) Architecture - S1AP Impacts | Ericsson, Sateliot, Thales, ESA, Deutsche Telekom |
R3-247531 | PWS Support for NB-IoT NTN | Ericsson LM |
R3-247549 | Further discussion on support of store and forward satellite operation for IoT NTN | ZTE Corporation |
R3-247595 | Further discussions on support of Store and Forward operations in NTN | THALES, Sateliot, Novamint |
R3-247609 | Discussion on support of regenerative payload for IoT NTN | Samsung |
R3-247676 | Discussion on support of IoT NTN | CMCC |
TDoc | Title | Source |
---|---|---|
R3-247036 | (BL pCR to TR 38.769) Study on solutions for Ambient IoT in NR | Huawei, CMCC, Ericsson, ZTE, CATT, NEC, Xiaomi, Lenovo |
R3-247192 | [DRAFT] LS on RAN3 outcome of Ambient IoT study | Huawei |
R3-247683 | Work Plan for Ambient IoT SI | CMCC, Huawei, T-Mobile USA |
R3-247684 | (TP to TR 38.769) RAN3 Conclusions and Recommendations | CMCC, T-Mobile USA, Huawei |
R3-247685 | (TP to TR 38.769) Uncritical Editor's Note Removal | CMCC, Huawei, Samsung, CATT, Lenovo, Xiaomi, ZTE, NEC, China Telecom |
R3-247761 | Response to R3-247684 | Nokia |
R3-247902 | SoD of CB: # AIoT4_SIConclusionandTR | CMCC |
R3-247903 | (TP to TR 38.769) RAN3 Conclusions and Recommendations | CMCC, Huawei, T-Mobile USA |
R3-247904 | (TP to TR 38.769) Uncritical Editor's Note Removal | CMCC, Huawei, Samsung, CATT, Lenovo, Xiaomi, ZTE, NEC, China Telecom |
R3-247921 | (TP to TR 38.769) Removal of Editor's Note | CMCC, Huawei, Samsung, CATT, Lenovo, Xiaomi, ZTE, NEC, China Telecom |
R3-247922 | (TP to TR 38.769) RAN3 Conclusions and Recommendations | CMCC, Huawei, T-Mobile USA |
R3-247923 | LS on RAN3 outcome of Ambient IoT study | RAN3(Huawei) |
R3-247924 | (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-247147 | (TP to 38.769) Conclusion for Topology 1 and updates to terminologies | Qualcomm Incorporated |
R3-247148 | (TP to 38.769) Conclusion for Topology 2 | Qualcomm Incorporated |
R3-247184 | (TP for TR38.769) some leftover issues on RAN architecture aspects | ZTE Corporation |
R3-247189 | (TP to TR 38.769) A-IoT RAN Architecture aspects | Huawei |
R3-247190 | (TP to TR 38.769) Protocol Stacks for Topology 2 NAS/UP based solutions | Huawei, CMCC, ZTE, CATT, NEC, Xiaomi, Lenovo, China Telecom, Samsung, Qualcomm |
R3-247216 | (TP to TR38.769) Discussion on architecture of Ambient IoT | NEC |
R3-247284 | (TP to TR 38.769) A-IoT architecture aspects | CATT |
R3-247312 | Discussion on AIoT RAN architecture | Xiaomi |
R3-247381 | A-IoT architecture aspects | China Telecom |
R3-247385 | A-IoT architecture aspects | China Telecom |
R3-247437 | Considerations on bistatic mode of operation | Lenovo |
R3-247438 | (TP to TR 38.769) Protocol Stack of UP based Solution for Topology 2 | Lenovo |
R3-247585 | Further aspects on AIoT Architecture | Ericsson |
R3-247586 | [TP for TR 38.769] on AIoT Architecture aspects | Ericsson |
R3-247610 | Remaining issues on RAN architecture for Ambient IoT | Samsung |
R3-247686 | Discussion on RAN Architecture for Ambient IoT | CMCC |
R3-247726 | Discussion on RAN impact for Ambient IoT | LG Electronics |
R3-247794 | CB:#AIoT1_ProtocolStack | Huawei |
R3-247830 | (TP to TR 38.769) A-IoT RAN Architecture aspects | Huawei |
R3-247831 | (TP to TR 38.769) Protocol Stacks for Topology 2 NAS/UP based solutions | Huawei, CMCC, ZTE, CATT, NEC, Xiaomi, Lenovo, China Telecom, Samsung, Qualcomm |
R3-247918 | (TP to TR 38.769) Protocol Stacks for Topology 2 NAS/UP based solutions | Huawei, CMCC, ZTE, CATT, NEC, Xiaomi, Lenovo, China Telecom, Samsung, Qualcomm |
TDoc | Title | Source |
---|---|---|
R3-247149 | (TP to 38.769) Inventory and Command related procedures for Ambient IoT | Qualcomm Incorporated |
R3-247185 | (TP to TR 38.769) Signaling and Procedures for NAS/UP based Topology 2 | ZTE Corporation, Huawei, Xiaomi, NEC, Nokia, China Telecom, CATT, CMCC |
R3-247186 | (TP to TR 38.769) Completion of Signaling and Procedures for Topology 2 | ZTE Corporation |
R3-247187 | (TP for TR38.769) Inventory content for Ambient-IoT | ZTE Corporation |
R3-247191 | (TP to TR 38.769) A-IoT Signalling and Procedures for Topology 1 | Huawei |
R3-247217 | (TP to TR38.769) Discussion on RAN-CN interface impact on Ambient IoT | NEC |
R3-247285 | (TP to TR 38 769) A-IoT Procedures and Information exchange between A-IoT CN and RAN | CATT |
R3-247286 | (TP to TR 38.879) A-IoT reader selection | CATT |
R3-247313 | AIoT interface impacts between RAN and CN | Xiaomi |
R3-247314 | (TP for TR 38.769) Procedures for A-IoT command | Xiaomi, Huawei, ZTE, CATT, CMCC |
R3-247439 | Radio resource allocation and UE reader selection for topology 2 | Lenovo |
R3-247489 | [TP for TR 38.769] Information exchanged between AIoT RAN and AIoT CN | Nokia |
R3-247490 | [TP for TR 38.769] Reader Selection Principles in AIoT Topology 2 | Nokia |
R3-247491 | [TP for TR 38.769] Data Transport and Context Management for AIoT | Nokia |
R3-247587 | [TP for TR 38.769] Elements for AIoT RAN – AIoT CN communication and overall signalling | Ericsson |
R3-247611 | Remaining issues on RAN-CN interface impact for Ambient IoT | Samsung |
R3-247643 | Discussion on Signalling Procedure Based on Topology 1 | China Telecom |
R3-247687 | Discussion on coordination between CN and RAN | CMCC |
R3-247786 | (TP to TR 38.769) Signaling and Procedures for NAS/UP based Topology 2 | ZTE Corporation, Huawei, Xiaomi, NEC, Nokia, China Telecom, CATT, CMCC |
R3-247795 | [TP for TR 38.769] CB:#AIoT2_SignallingFlow | Ericsson |
R3-247919 | [TP for TR 38.769] for signalling flow | Ericsson |
TDoc | Title | Source |
---|---|---|
R3-247150 | (TP to 38.769) Locating Ambient IoT devices | Qualcomm Incorporated |
R3-247188 | (TP for TR38.769) Locating an AIoT device | ZTE Corporation |
R3-247193 | Consideration on A-IoT Device Locating | Huawei |
R3-247287 | (TP to TR 38.879) Locating of A-IoT device | CATT |
R3-247315 | (TP for TR 38.769)) Locating AIoT device | Xiaomi |
R3-247492 | [TP for TR 38.769] Locating AIoT Devices | Nokia |
R3-247588 | [TP for TR 38.769] On locating AIoT devices | Ericsson |
R3-247688 | Discussion on locating Ambient IoT device | CMCC |
R3-247689 | (TP to TR 38.769) locating ambient IoT devices | CMCC, Huawei, ZTE, CATT, Xiaomi, Nokia, LG Electronics, China Telecom |
R3-247727 | Further discussion on locating A-IoT Device | LG Electronics |
R3-247797 | CB:AIoT3_LocationReport | Nokia |
R3-247845 | [TP for TR 38.769] Locating AIoT Devices | Nokia |
R3-247920 | [TP for TR 38.769] Locating AIoT Devices | Nokia |
TDoc | Title | Source |
---|---|---|
R3-247558 | WI Work plan for R19 Network Energy Savings | Ericsson |
TDoc | Title | Source |
---|---|---|
R3-247209 | Support on-demand SSB operation | NEC |
R3-247241 | (TP to BL CR for TS 38.473) Discussion on On-Demand SSB SCell Operation | CMCC |
R3-247272 | On support on-demand SSB SCell operation | CATT |
R3-247303 | Discussion on on-demand SSB SCell operation in low-carbon green network | Samsung |
R3-247386 | On support on-demand SSB SCell operation | China Telecom |
R3-247402 | (TP for TS 38.473) Discussion on on-demand SSB SCell operation | Huawei |
R3-247440 | Discussion on On-demand SSB for SCell | Lenovo |
R3-247550 | (TP to BL CR for 38.473) Further discussion on on-demand SSB Scell operation | ZTE Corporation |
R3-247805 | CB:#ES1_OndemandSSB | Huawei |
TDoc | Title | Source |
---|---|---|
R3-247158 | Discussion on OD-SIB1 | Rakuten Mobile, Inc |
R3-247210 | Support on-demand SIB1 | NEC |
R3-247230 | Aspects of on-demand SIB1 for NES enhancements | Qualcomm Inc. |
R3-247242 | Support On-Demand SIB1 for UEs | CMCC |
R3-247273 | On support on-demand SIB1 for idle UE | CATT |
R3-247304 | Discussion on on-demand SIB1 in low-carbon green network | Samsung |
R3-247324 | On-demand SIB1 for UEs in idle/inactive mode | Fujitsu |
R3-247387 | On support on-demand SIB1 | China Telecom |
R3-247403 | (TP for TS 38.473 and TS 38.423) Discussion on on-demand SIB1 for UEs in idle or inactive mode | Huawei |
R3-247441 | Discussion on On-demand SIB1 for Idle/Inactive UE | Lenovo |
R3-247480 | Discussion on gaps in Cell-A coverage for OD-SIB1 and automatic recovery | Ericsson |
R3-247551 | (TP to BL CR for 38.423) Further discussion on on-demand SIB1 | ZTE Corporation |
R3-247552 | F1 impact of On-demand SIB1 for UEs in idle/inactive mode | Ericsson |
R3-247559 | Xn impact of On-demand SIB1 for UEs in idle/inactive mode | Ericsson, Deutsche Telekom, China Unicom |
R3-247565 | Xn signalling for On-Demand SIB1 | Nokia |
R3-247626 | Discussion of new procedures to support OD-SIB1 | Rakuten Mobile, Inc |
R3-247806 | CB:#ES2 | Ericsson |
R3-247857 | Introduction of Network Energy Saving Enhancement | Ericsson, Huawei |
R3-247858 | Introduction of Network Energy Saving Enhancement | Huawei, Ericsson |
R3-247897 | Introduction of Network Energy Saving Enhancement | Ericsson, Huawei, CMCC, Samsung, Qualcomm, Nokia, ZTE, Lenovo, Deutsche Telekom, NEC |
R3-247898 | Introduction of Network Energy Saving Enhancement | Huawei, Ericsson, CMCC, Samsung, ZTE, Nokia, Deutsche Telekom, Lenovo, NEC, Jio |
TDoc | Title | Source |
---|---|---|
R3-247566 | Initial discussion on adaptation of common signals/channels | Nokia |
TDoc | Title | Source |
---|---|---|
R3-247256 | Work plan for Rel-19 WI on LP-WUSWUR | vivo |
TDoc | Title | Source |
---|---|---|
R3-247007 | LS on LP-WUS subgrouping | RAN2(vivo) |
R3-247145 | Discussion on RAN3 impacts for LP-WUS | ZTE Corporation |
R3-247146 | (TP to TS 38.413, 38.473, 38.423) on support of LP-WUS | ZTE Corporation |
R3-247220 | (TP to 38.413, 38.423, 38.473 on LP-WUS) LP-WUS RAN3 related aspect | NEC |
R3-247231 | Support LP-WUS subgrouping in RRC_IDLE/RRC_INACTIVE | Qualcomm Inc. |
R3-247257 | Discussion on LP-WUS for NR | vivo, NTT DOCOMO INC. |
R3-247258 | BLCR for TS 38.300 on support of LP-WUS | vivo, NTT DOCOMO INC. |
R3-247404 | (TP for TS 38.413 and TS 38.423) Discussion on Low-power wake-up signal and receiver for NR | Huawei |
R3-247405 | Introduction of low-power wake-up signal and receiver for NR | Huawei |
R3-247473 | Potential RAN3 impacts of LP-WUS | CATT |
R3-247474 | [Draft] Reply to LS on LP-WUS subgrouping | CATT |
R3-247493 | Support of LP-WUS | Nokia |
R3-247501 | Support of LP-WUS | Nokia |
R3-247569 | Introduction of LP-WUS paging monitoring | Ericsson |
R3-247579 | Discussion of LPWUS impacts on NG-RAN architecture | Ericsson |
R3-247636 | Further discussion on LP-WUS subgrouping | NTT DOCOMO INC.. |
R3-247637 | (TP to TS 38.413 and 38.473) Further discussion on LP-WUS subgrouping | NTT DOCOMO INC.. |
R3-247669 | Discussion on supporting LP-WUS Indicating Paging Monitoring | CMCC |
R3-247670 | (TP to BL CR for 38.473) support of LP-WUS | CMCC |
R3-247719 | (TP to BLCR for TS 38.413, 38.423, 38.473) Discussion on LP-WUS subgrouping | Samsung |
TDoc | Title | Source |
---|---|---|
R3-247224 | Discussion on CLI handling support | NEC |
R3-247281 | Signaling design to enable NR SBFD operation | Qualcomm Incorporated |
R3-247347 | Discussion on information exchanges among gNBs for CLI handling | Samsung |
R3-247348 | TPs to BLCRs of TS38.423 and TS38.473 on CLI handling | Samsung |
R3-247519 | Discussion on RAN3 impacts to support enhancements for CLI handling for SBFD | Ericsson |
R3-247520 | TP to TS38.423 on enhancements for CLI handling for SBFD | Ericsson |
R3-247567 | Further discussion on inter-gNB CLI mitigation for SBFD operation | Nokia |
R3-247598 | SBFD related CLI measurement configuration, CLI mitigation and CLI testing | Charter Communications |
R3-247639 | Further discussions on SBFD related information exchange | Huawei |
R3-247640 | BL CR on the introduction of Evolution of NR duplex operation Sub-band full duplex (SBFD) | Huawei |
R3-247664 | Discussion on supporting CLI handling in SBFD | CMCC |
R3-247665 | (TP for TS 38.423) Support CLI handling | CMCC |
R3-247698 | Open issues on CLI handling in SBFD | LG Electronics Inc. |
R3-247699 | (TP for NR_duplex_evo-Core for TS 38.423 and TS 38.473) Open issues on CLI handling in SBFD | LG Electronics Inc. |
R3-247716 | Discussion on Evolution of Duplex Operation | CATT |
R3-247717 | (TP for 38.420, 38.423, 37.340 and 38.473) Support SBFD Operation | CATT |
R3-247732 | Discussion on Information exchange for SBFD | ZTE corporation |
R3-247733 | (TP for BLCR 38.300&401&420&423&473-36.423-37.340) SBFD | ZTE corporation |
TDoc | Title | Source |
---|---|---|
R3-247017 | Reply LS on AIML data collection | SA2(InterDigital) |
R3-247116 | Reply LS on AIML Data Collection | SA5(ZTE) |
R3-247332 | Draft Reply for LS on AIML data collection | Qualcomm Incorporated |
R3-247420 | Discussion on the LS reply from SA2 on AI/ML Data Collection | Huawei |
R3-247422 | [Draft LS] Discussion on reply LS on AIML data collection | ZTE Corporation |
R3-247576 | Work Plan for Rel-19 on AI/ML for PHY (Positioning) | Ericsson (Rapporteur) |
R3-247577 | Analysis and discussion on the Reply LS on AIML data collection | Ericsson |
R3-247625 | Discussion on the LS on AI/ML Data Collection from SA2 | Nokia |
R3-247801 | Reply LS on AIML data collection | RAN3(ZTE) |
TDoc | Title | Source |
---|---|---|
R3-247221 | Discussion on AIML based Positioning Accuracy Enhancements | NEC |
R3-247243 | Support AIML Assisted Positioning | CMCC |
R3-247244 | (TP to BL CR for TS 38.455) Support Direct AI/ML Positioning | CMCC |
R3-247293 | Discussion on Direct AIML positioning | CATT |
R3-247294 | Discussion on AIML assisted positioning | CATT |
R3-247305 | Discussion on Case 3a in AI/ML for positioning | Samsung |
R3-247306 | Discussion on Case 3b in AI/ML for positioning | Samsung |
R3-247319 | (TP for TS 38.455) Support of gNB-side model (case 3a) | Xiaomi |
R3-247320 | (TP for TS 38.455) Support of LMF-side model (case 3b) | Xiaomi |
R3-247372 | Discussion on support of direct AI/ML positioning (Case 3b) | China Telecom |
R3-247373 | Discussion on support of AI/ML assisted positioning (Case 3a) | China Telecom |
R3-247421 | Discussion on RAN3 impacts for AI/ML positioning | Huawei |
R3-247423 | Discussion on AIML assisted Positioning (Case 3a&3b) | ZTE Corporation |
R3-247447 | AIML for gNB assisted positioning | Lenovo |
R3-247459 | AI/ML based positioning accuracy enhancements | Qualcomm Incorporated |
R3-247529 | AI/ML-Assisted Positioning Focused on Cases 3a and 3b | Jio |
R3-247578 | Discussion on NRPPa signalling design for AI/ML for PHY | Ericsson |
R3-247624 | AI/ML Positioning for Case 3a and Case 3b | Nokia |
R3-247647 | Discussion on support of AIML assisted positioning (Case 3a) | Baicells |
R3-247662 | Discussion on AI/ML-based Positioning Accuracy Enhancements | CEWiT |
R3-247803 | CB:#AIPHY | Ericsson |
TDoc | Title | Source |
---|---|---|
R3-247357 | Correction on UAI for support XR in DC | Samsung, Ericsson, Cybercore, Qualcomm |
R3-247502 | Exchange of MBS multicast services in RRC inactive | Nokia, Huawei, CATT, Qualcomm Incorporated |
R3-247756 | Response to R3-247502 on the need to exchange multicast services on XnAP | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R3-247276 | Support cell DTXDRX for NES | CATT, ZTE, NEC |
R3-247277 | Support Cell DTXDRX for NES | CATT, ZTE, NEC |
R3-247278 | Support Cell DTXDRX for NES | CATT, ZTE, NEC |
R3-247556 | Referencing Fronthaul Interface in 38.401 | Ericsson, Qualcomm, AT&T, Orange, Verizon, Deutsche Telekom, NTT Docomo, Vodafone, T-Mobile |
R3-247557 | Referencing Fronthaul Interface in 38.401 | Ericsson, Qualcomm, AT&T, Orange, Verizon, Deutsche Telekom, NTT Docomo, Vodafone, T-Mobile |
R3-247560 | Disabling Inactivity Monitoring over E1 | Ericsson |
R3-247561 | Disabling Inactivity Monitoring over E1 | Ericsson |
R3-247580 | Discussion on improving E-CID positioning accuracy | Ericsson, NTT DOCOMO, Nokia, Polaris Wireless |
R3-247581 | E-CID measurement enhancement | Ericsson, NTT Docomo, Nokia, Polaris Wireless |
R3-247582 | E-CID measurement enhancement | Ericsson, NTT Docomo, Nokia, Polaris Wireless |
R3-247602 | Inactivity Timer for Fixed Wireless Access | Nokia |
R3-247657 | Correction to enhancing QoS Monitoring with Per-Packet Granularity | ZTE Corporation, China Telecom, China Unicom, CMCC |
R3-247658 | Enhancing QoS Monitoring with Per-Packet Granularity | ZTE Corporation, China Telecom, China Unicom, CMCC |
R3-247753 | Response to R3-247602 | ZTE Corporation |
R3-247760 | Response to R3-247276, R3-247277, R3-247278 | Nokia, Ericsson, BT |
R3-247763 | Reply LS on RAN3 vs RAN2 Basketball Match | RAN2(Oppo) |
TDoc | Title | Source |
---|---|---|
R3-247846 | CB:#30_Lsreply - Reply LS | ZTE |
R3-247894 | (MCC-Cancelled allocation) | MCC |
R3-247925 | Reply LS on RAN3 vs RAN2 Basketball Match | RAN3(ZTE) |