| TDoc | Title | Source |
|---|---|---|
| R3-244001 | RAN3#125 Meeting Agenda | RAN3 Chair |
| TDoc | Title | Source |
|---|---|---|
| R3-244002 | RAN3#124 Meeting Report | ETSI-MCC |
| TDoc | Title | Source |
|---|---|---|
| R3-244003 | Guidelines for RAN3 Meetings | RAN3 Chair, RAN3 Vice-Chairs |
| TDoc | Title | Source |
|---|---|---|
| R3-244004 | TR 30.531 v1.53.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| R3-244648 | TR 30.531 v1.53.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| TDoc | Title | Source |
|---|---|---|
| R3-244005 | Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | CT1(Huawei) |
| R3-244006 | Reply LS on 5GS missing CBC support for shared networks | CT1(Ericsson) |
| R3-244007 | Reply LS on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | RAN1(Ericsson) |
| R3-244013 | Reply LS on Rel-18 higher-layers parameter list | RAN2(Ericsson) |
| R3-244015 | Reply LS RP-240891 on NTZ solution impacts to RAN. | TSG RAN(Interdigital) |
| R3-244016 | LS on Avoiding Cross-TSG TEI | TSG RAN(NECLab) |
| R3-244017 | Reply LS on Restoration of N3mb Failure for MBS broadcast | SA2(Ericsson) |
| R3-244021 | LS on NTZ solution impacts to RAN | SA2(Ericsson) |
| R3-244023 | Reply LS on the MBS broadcast service continuity and MBS session identification | SA4(Qualcomm) |
| R3-244026 | LS on RFC 9543, "A Framework for Network Slices in Networks Built from IETF Technologies" | IETF |
| R3-244027 | LS on "A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies" | IETF |
| R3-244501 | Discussion on the Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies | Huawei |
| R3-244502 | [draft] Reply LS on the Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies | Huawei |
| R3-244613 | Discuss LS on A Realization of Network Slices for 5G Networks Using Current IPMPLS Technologies | ZTE Corporation |
| R3-244614 | [Draft]Reply LS on A Realization of Network Slices for 5G Networks Using Current IPMPLS Technologies | ZTE Corporation |
| R3-244660 | [draft] Reply LS on the Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies | Huawei |
| R3-244785 | Reply LS on the Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies | RAN3(Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R3-244052 | Discussion on emergency call support for (e)RedCap and 2RX XR UEs in barred cells | ZTE Corporation, China Telecom, China Unicom |
| R3-244053 | Introduction of barring exemption for (e)RedCap and 2RX XR UEs [EM_Call_Exemption] | ZTE Corporation, China Telecom, China Unicom |
| R3-244054 | [Draft] Reply LS on emergency call support for (e)RedCap in barred cells | ZTE Corporation |
| R3-244078 | Introduction of barring exemption for (e)RedCap and 2RX XR UEs | China Telecom, ZTE, China Unicom |
| R3-244126 | Switch to RRC Connected after SDT Partial Context Transfer | Nokia, Ericsson |
| R3-244127 | Correction of switch to RRC connected after SDT Partial Context Transfer | Nokia, Ericsson |
| R3-244128 | Correction of switch to RRC connected after SDT Partial Context Transfer | Nokia, Ericsson |
| R3-244130 | Response LS on SDT signalling optimization for partial context transfer | Nokia, Ericsson |
| R3-244131 | Support of Emergency Calls for (e)RedCap UEs in barred cells | Nokia |
| R3-244132 | Support of Emergency Calls for (e)RedCap UEs in barred cells | Nokia |
| R3-244133 | Support of Emergency Calls for (e)RedCap UEs in barred cells | Nokia |
| R3-244134 | Reply LS on Support of Emergency Calls for (e)RedCap UEs in barred cells | Nokia |
| R3-244220 | Discussions on UE's awareness of MBS Communication Service Type for QMC | Huawei |
| R3-244282 | MBS Communication Service Type for QMC | Ericsson |
| R3-244283 | [DRAFT] LS on MBS Communication Service Type | Ericsson |
| R3-244285 | Discussion on Emergency call Support for (e)RedCap UEs | Qualcomm Incorporated |
| R3-244398 | Considerations on RAN2 LS on emergency call support for UE in barred cells | Ericsson |
| R3-244399 | Introduction of barring exemption for UE in emergency calls [EM_Call_Exemption] [RedCap_EM_Call] | Ericsson |
| R3-244400 | Introduction of barring exemption for UE in emergency calls [EM_Call_Exemption] [RedCap_EM_Call] | Ericsson |
| R3-244401 | Introduction of barring exemption for UE in emergency calls [EM_Call_Exemption] [RedCap_EM_Call] | Ericsson |
| R3-244402 | [DRAFT]Response LS on LS on emergency call support for (e)RedCap in barred cells | Ericsson |
| R3-244496 | Emergency call support in barred cells | Huawei |
| R3-244497 | Introduction of Emergency call support in barred cells [RedCap_EM_Call] | Huawei |
| R3-244498 | Introduction of Emergency call support in barred cells [RedCap_EM_Call] | Huawei |
| R3-244499 | Introduction of Emergency call support in barred cells [RedCap_EM_Call] | Huawei |
| R3-244500 | [draft] Reply LS on Emergency call support in barred cells | Huawei |
| R3-244585 | Discussion on support barring exemption for emergency calls | CMCC |
| R3-244586 | Draft Reply LS on support barring exemption for emergency calls | CMCC |
| R3-244587 | Introduction of barring exemption for emergency calls | CMCC |
| R3-244588 | Introduction of barring exemption for emergency calls | CMCC |
| R3-244643 | Response to R3-244126, R3-244127, R3-244128, R3-244130 | Huawei |
| R3-244647 | Response to R3-244220 on UE awareness of MBS QoE | ZTE Corporation |
| R3-244649 | Introduction of barring exemption for (e)RedCap and 2RX XR UEs [EM_Call_Exemption] | ZTE Corporation, China Telecom, China Unicom |
| R3-244650 | Introduction of barring exemption for (e)RedCap and 2RX XR UEs | China Telecom, ZTE, China Unicom |
| R3-244651 | Introduction of Emergency call support in barred cells [EM_Call_Exemption] | Huawei, ZTE, China Telecom, China Unicom, Nokia, Qualcomm Incorporated, Ericson, CMCC, CATT |
| R3-244711 | Reply LS on Support of Emergency Calls for (e)RedCap UEs in barred cells | Nokia |
| R3-244735 | (CB:#3_MBSType) SoD to capture the agreements | Ericsson |
| R3-244736 | UE awareness of MBS communication service type for QMC | RAN3(Ericsson) |
| R3-244786 | Introduction of barring exemption for (e)RedCap and 2RX XR UEs [EM_Call_Exemption] | ZTE Corporation, China Telecom, China Unicom, Nokia, Qualcomm Incorporated, Ericson, Huawei, CMCC, CATT |
| R3-244787 | Introduction of barring exemption for (e)RedCap and 2RX XR UEs [EM_Call_Exemption] | China Telecom, ZTE, China Unicom, Nokia, Qualcomm Incorporated, Ericson, Huawei, CMCC, CATT |
| R3-244788 | Reply LS on Support of Emergency Calls for (e)Redcap UEs in barred cells | RAN3(Nokia) |
| R3-244789 | LS on MBS Communication Service Type | RAN3(Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R3-244286 | (TP for TS36.300) Discussion on UE Location for NTN NB-IoT UE | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Inmarsat, Thales |
| R3-244345 | Support User Location Information reporting for NB-IoT NTN | Nokia, Nokia Shanghai Bell, Qualcomm |
| R3-244358 | Discussion on UE Location Information for NB-IoT NTN | Huawei, Ericsson |
| R3-244367 | [DRAFT] Reply LS on UE Location Information for NB-IoT NTN | Ericsson, Huawei, Apple, Thales |
| R3-244368 | E-SMLC OAM Configuration for IoT NTN | Ericsson, Thales, Huawei |
| R3-244403 | Correction on inter-system S1/NG-handover | Ericsson, Qualcomm Inc., China Telecom, Vodafone, ZTE |
| R3-244404 | Correction on inter-system S1/NG-handover | Ericsson, Qualcomm Inc., China Telecom, Vodafone, ZTE |
| R3-244506 | Clarification on indication of cell re-activation | CATT, Nokia, Huawei, CMCC |
| R3-244601 | Correction of TS 36.300 on UE location information for NB-IoT NTN | CMCC, China Telecom, China Unicom |
| R3-244602 | Discussion on UE location information for NB-IoT NTN | CMCC, China Telecom, China Unicom |
| R3-244603 | Draft Reply LS to UE location information for NB-IoT NTN | CMCC, China Telecom, China Unicom |
| R3-244610 | Clarification on indication of dormant cell re-activation | CATT, Nokia, Huawei,CMCC |
| R3-244612 | Correction on mapping of tracking area and fixed geographical area for NB-IoT NTN | ZTE Corporation |
| R3-244637 | Draft Reply for LS on UE Location Information for NB-IoT NTN | Qualcomm Incorporated |
| R3-244652 | CB:#4_CoarseLocationInfor | Ericsson |
| R3-244751 | (CB: # 5_NewCauseValue) Summary of Offline discussion | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-244048 | Correction on IAB-node authorization | ZTE Corporation |
| R3-244049 | Correction on IAB-node authorization | ZTE Corporation |
| R3-244050 | Correction on mobile IAB-node authorization | ZTE Corporation |
| R3-244064 | Triggering reporting of requested DL LBT information | Nokia, Ericsson, Huawei, ZTE, Samsung |
| R3-244074 | Correction of QoS Flow List | Huawei, Deutsche Telekom, CATT, Ericsson, ZTE |
| R3-244075 | Correction of PDU Sessions List To Be Released - UPError | Huawei, Nokia, ZTE, Ericsson |
| R3-244079 | Correction on new SIB17bis for TRS in Idle and Inactive | China Telecom,ZTE,CATT,China Unicom |
| R3-244080 | Correction on new SIB17bis for TRS in Idle and Inactive | China Telecom |
| R3-244081 | Update of stage 2 positioning information | Nokia, CATT, Ericsson, Huawei, Samsung, Xiaomi, ZTE |
| R3-244083 | Handling of authorization for (mobile) IAB node | ZTE Corporation |
| R3-244090 | LTM interwork with L3 measurements | Nokia |
| R3-244091 | F1AP support for sub 1s location information reporting periodicity [Sub_1s_periodicity] | ZTE Corporation, Ericsson, CATT |
| R3-244092 | Discussion on Uu Relay RLC channel setup during UE context setup procedure | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell |
| R3-244093 | Corrections on Uu Relay RLC channel configuration | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell |
| R3-244094 | Corrections on Uu Relay RLC channel configuration | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell |
| R3-244097 | Correction on PDCP packets discard in case of MBS broadcast path update | Huawei, CBN, CMCC, Qualcomm Incorporated, Ericsson |
| R3-244098 | Correction on Multicast Group Paging | Huawei, CBN, Samsung, Nokia, CMCC, Qualcomm Incorporated, CATT, Ericsson |
| R3-244099 | Correction on Multicast Group Paging | Huawei, CBN, Samsung, Nokia, CMCC, Qualcomm Incorporated, CATT, Ericsson |
| R3-244100 | Correction on S-CPAC Complete Configuration Indicator | Huawei, LG Electronics, ZTE, CMCC, Ericsson |
| R3-244110 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom |
| R3-244111 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE,CATT,China Unicom |
| R3-244112 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom |
| R3-244113 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom |
| R3-244114 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom, ZTE, CATT, China Unicom, Ericsson, Nokia, Huawei |
| R3-244115 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom, ZTE, CATT, China Unicom, Ericsson, Nokia, Huawei |
| R3-244116 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom |
| R3-244117 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom |
| R3-244122 | Stage 2 correction for reporting of requested DL LBT information | Ericsson, Nokia, Samsung, Huawei, ZTE |
| R3-244125 | NRPPa support for sub 1s location information reporting periodicity [Sub_1s_periodicity] | Ericsson, ZTE, CATT |
| R3-244129 | Use of Establishment Cause to determine DSCP | Peraton Labs, CISA ECD, Verizon |
| R3-244135 | Correction of MBS in TS 38.401 | Nokia, Huawei, CATT, Qualcomm Incorporated, ZTE, Ericsson |
| R3-244136 | Correction of Extended UE Identity Index Value | Nokia, Huawei, Qualcomm Incorporated, CATT |
| R3-244137 | Correction of recovery of split PDU Session | Nokia |
| R3-244149 | Security Indication behavior | NEC |
| R3-244150 | Correction for Security Indication behavior | NEC |
| R3-244151 | Correction for Security Indication behavior | NEC |
| R3-244174 | Corrections on information element to support both CPAC and S-CPAC | ZTE Corporation, Ericsson, CATT, China Telecom, CMCC, Samsung, Nokia, Lenovo, NEC, Google, LG Electronics, Huawei |
| R3-244175 | Correction on Transmission Bandwidth less than 5MHz | ZTE Corporation, China Telecom, CATT, China Unicom |
| R3-244176 | Correction on Transmission Bandwidth less than 5MHz | ZTE Corporaton, China Telecom, CATT, China Unicom |
| R3-244177 | Discussion for Early TA acquisition and Preamble Resources for PDCCH order in LTM | |
| R3-244178 | Corrections for Early TA acquisition and Preamble Resources for PDCCH order in LTM | Google, CATT |
| R3-244179 | Clarification on SpCell ID replacement | |
| R3-244187 | Support of pre-configured SRS activation | CATT, Huawei, ZTE, Samsung |
| R3-244188 | Support of UE specific SRS Reservation | CATT, Huawei, ZTE, Samsung |
| R3-244189 | Corrections to Positioning SRS BW Aggregation and Tx Hopping | CATT, Ericsson, ZTE, Samsung |
| R3-244190 | Support of the pre-Configured SRS activation | Xiaomi, Ericsson, Nokia, Qualcomm Incorporated |
| R3-244205 | Support of preconfigured SRS activation | ZTE Corporation, CATT, Huawei, Samsung |
| R3-244206 | Support of UE specific SRS reservation | ZTE Corporation, CATT, Huawei, Samsung |
| R3-244216 | Support of UE specific SRS reservation | Samsung, CATT, Huawei, ZTE |
| R3-244217 | Correction on the QMC information in the SN modification required message | Huawei, China Unicom, Ericsson, Lenovo |
| R3-244218 | Further miscellaneous corrections to 38.300 | Huawei, China Unicom, Lenovo |
| R3-244219 | Further miscellaneous corrections to 37.340 | Huawei, China Unicom, Lenovo |
| R3-244221 | Correction on SPR retrieval and forwarding | Samsung, Lenovo, Cybercore, Qualcomm |
| R3-244222 | Correction of SON for fast MCG recovery in stage 2 | Samsung, Lenovo, CATT, Nokia |
| R3-244226 | Support of pre-configured SRS activation | Huawei, CATT, ZTE, Samsung |
| R3-244227 | Support of UE specific SRS reservation | Huawei, CATT,Samsung, ZTE |
| R3-244230 | QoE measurement handling in RRC_IDLE and RRC_INACTIVE states | CATT, Ericsson, ZTE, Xiaomi |
| R3-244239 | Correction on IAB authorization | CATT, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244240 | Correction on IAB authorization | CATT, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244241 | Correction of Served Cell Specific Info Request in NG-RAN node configuration update procedure | Huawei, Nokia, CMCC |
| R3-244242 | Correction of Served Cell Specific Info Request in NG-RAN node configuration update procedure | Huawei, Nokia, CMCC |
| R3-244243 | Correction of TSC Traffic Characteristics in the PDU Session Resource Modification Info - MN terminated | Huawei, Nokia, Deutsche Telekom |
| R3-244244 | Correction on CPA failure states and detection mechanism in stage 2 | Nokia, CATT, CMCC, Qualcomm Inc. |
| R3-244261 | Correction on successful PSCell Addition/Change Report | CATT, Lenovo |
| R3-244262 | Correction on conditional PSCell addition or change failure | CATT, CMCC, ZTE |
| R3-244263 | Adding ECN reporting status in RAN-triggered modification procedure | CATT, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244275 | Discussion on supporting Tag ID Pointer for LTM | CATT |
| R3-244276 | Missing agreement about UE conext release required | CATT, CMCC, ZTE |
| R3-244281 | Aligning procedure code between releases | Huawei, Ericsson, Nokia |
| R3-244284 | Correction on configuration update for an inactive Multicast session | ZTE Corporation, CATT, Ericsson, Nokia |
| R3-244300 | Stage 2 correction for AI/ML for NG-RAN | Ericsson, Huawei, Nokia, InterDigital, NEC, CATT, Lenovo, Deutsche Telekom |
| R3-244305 | Correction on inter MN handover without SN change for QMC | Lenovo, Huawei |
| R3-244336 | Changing presence of IE extension for QoE related IE | Nokia, Ericsson, Huawei, CATT, Samsung, ZTE |
| R3-244346 | Introduction of cell DTX/DRX information | Ericsson, Nokia, BT |
| R3-244353 | LTM stage 2 corrections for split architecture | Ericsson |
| R3-244354 | LTM stage 2 corrections for non-split architecture | Ericsson |
| R3-244359 | Value UE Rx-Tx Time Difference ASN.1 presence correction | Huawei, Nokia, CATT, ZTE, Samsung, Ericsson |
| R3-244360 | Positioning ASN.1 correction (AggregatedPRSResourceSetList, kminus values) | Huawei, Nokia, CATT, ZTE, Samsung, Ericsson |
| R3-244361 | Correction on Measurement Time Window | Huawei |
| R3-244362 | Clarification on TRP ID for SRS Bandwidth Aggregation | Huawei |
| R3-244376 | QoE/RVQoE measurement continuity for SCG failure scenarios | Nokia |
| R3-244382 | Introduction of cell DTX/DRX information | Nokia, Ericsson, BT |
| R3-244384 | Changing presence of IE extensions for MBS related IEs | Ericsson, Nokia, Huawei, CATT, Samsung, ZTE |
| R3-244385 | Changing presence of IE extensions for MBS related IEs | Ericsson, Nokia, Huawei, CATT, Samsung, ZTE |
| R3-244386 | Changing presence of IE extensions for QoE related IEs | Ericsson, Nokia, Huawei, CATT, Samsung, ZTE |
| R3-244391 | Missing procedure description for pre-configured SRS activation | Qualcomm Incorporated, Ericsson, Nokia, Xiaomi |
| R3-244393 | Correction to Requested DL PRS Transmission Characteristics | Qualcomm Incorporated, Huawei |
| R3-244397 | Correction to SRS for positioning aggregation | Qualcomm Incorporated |
| R3-244405 | Positioning correction to F1AP | Ericsson, CATT, ZTE, Samsung |
| R3-244406 | Support positioning of L2 UE-to-network remote UE [PosL2RemoteUE] | Ericsson, CATT, Xiaomi, ZTE |
| R3-244407 | Correction of TRP Geographical coordinates [PosLocalCoords] | Ericsson, Qualcomm Inc., CATT, Xiaomi |
| R3-244408 | Correction of TRP Geographical coordinates [PosLocalCoords] | Ericsson, Qualcomm Inc., CATT, Xiaomi |
| R3-244412 | Support of pre-Configured SRS activation using full context relocation | Ericsson, Xiaomi, Nokia, Qualcomm Incorporated |
| R3-244413 | Issue with AoI Reporting for Slice subject to Area Restriction | Nokia, Deutsche Telekom, ZTE |
| R3-244455 | Missing Iuant interface reference in NR specification | Ericsson |
| R3-244456 | Correction on Location Reporting Control procedure for NR NTN_R17 | ZTE Corporation, CMCC, China Telecom |
| R3-244457 | Correction on Location Reporting Control procedure for NR NTN_R18 | ZTE Corporation, CMCC, China Telecom |
| R3-244458 | Correction on Location Reporting Control procedure for IoT NTN_R17 | ZTE Corporation, CMCC, China Telecom |
| R3-244459 | Correction on Location Reporting Control procedure for IoT NTN_R18 | ZTE Corporation, CMCC, China Telecom |
| R3-244467 | Correction of Extended UE Identity Index Value | Nokia, Huawei, Qualcomm Incorporated, CATT |
| R3-244473 | Correction on PDU session-level indirect data forwarding [Indirect Data Forwarding] | LG Electronics Inc., Huawei |
| R3-244474 | Rel-18 correction on LTM with gNB-CU-UP change | LG Electronics Inc. |
| R3-244475 | Correction on the CHO Initiation IE name | LG Electronics Inc. |
| R3-244486 | Correction of the Signalling based MDT PLMN List IE | Huawei, China Unicom, China Telecom |
| R3-244487 | Correction of the Signalling based MDT PLMN List IE | Huawei, China Unicom, China Telecom |
| R3-244488 | Correction of the Signalling based MDT PLMN List IE | Huawei, China Unicom, China Telecom |
| R3-244489 | Further clarification on MIMO with 2TA in LTM | Huawei, China Unicom, CMCC |
| R3-244490 | Correction on MIMO with 2TA in LTM | Huawei, China Unicom, CMCC |
| R3-244491 | Correction on MIMO with 2TA in LTM | Huawei, China Unicom, CMCC |
| R3-244492 | [DRAFT] LS on MIMO with 2 TA in LTM | Huawei |
| R3-244493 | Correction of CP Transport Layer Information and DL UP TNL Information | Huawei, China Unicom, China Telecom |
| R3-244494 | Correction of CP Transport Layer Information and DL UP TNL Information | Huawei, China Unicom, China Telecom |
| R3-244495 | Correction of CP Transport Layer Information and DL UP TNL Information | Huawei, China Unicom, China Telecom |
| R3-244503 | Clarification of UE performance | CATT, Huawei, Nokia, Qualcomm, Deutsche Telekom, NTT Docomo, Lenovo, NEC, China Telecom, China Unicom, Ericsson, ZTE, Samsung, InterDigital |
| R3-244504 | Add Cause IE in MULTICAST CONTEXT NOTIFICATION REFUSE message | CATT, Nokia, ZTE, Ericsson,Huawei,Samsung |
| R3-244505 | Handling GTP-U exceptions for tunnels delivering PDCP PDU | CATT |
| R3-244517 | Discussion on the PDCP SN gap report handling during UE’s handover | Huawei, CATT, Xiaomi, China Telecom |
| R3-244518 | Discussion on DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi |
| R3-244519 | Correction on DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi |
| R3-244520 | Correction on DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi |
| R3-244521 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT |
| R3-244522 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT |
| R3-244523 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT |
| R3-244524 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT |
| R3-244525 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT |
| R3-244549 | Discussion on QMC support in NR-DC for RRC segmentation | Samsung, ZTE, CATT, China Unicom, Lenovo |
| R3-244550 | Corrections to QMC support in NR-DC for RRC Segmentation (Option 1) | Samsung, Lenovo, Ericsson |
| R3-244551 | Correction to QMC support in NR-DC for RRC segmentation (Option 2) | Samsung, ZTE, CATT, Lenovo |
| R3-244557 | LTM supports feature of MIMO with 2TA | Samsung, Nokia, CATT, Huawei, ZTE, Ericsson, LG Electronics, Google, CMCC, NEC, Lenovo |
| R3-244558 | Discussion on remaining issues on R18 LTM | Samsung |
| R3-244582 | Correction on Early Sync Information from DU to CU | CMCC, ZTE, NEC, CATT, Huawei |
| R3-244583 | Correction on XR PSI based SDU Discard | CMCC, Huawei, CATT, Lenovo |
| R3-244597 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom, ZTE, CATT, China Unicom |
| R3-244598 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom, ZTE, CATT, China Unicom, Ericsson, Nokia, Huawei |
| R3-244599 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom |
| R3-244600 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE,CATT,China Unicom |
| R3-244608 | PDCP version information over the E1 interface | Samsung |
| R3-244609 | Discussion on providing the PDCP version from the eNB-CP to the eNB-UP over the E1 interface | Samsung |
| R3-244617 | Correction on Area of Interest RAN Node for location report | ZTE Corporation |
| R3-244618 | Correction on Area of Interest RAN Node for location report | ZTE Corporation |
| R3-244619 | Correction on Area of Interest RAN Node for location report | ZTE Corporation |
| R3-244620 | Correction on Area of Interest RAN Node for location report | ZTE Corporation |
| R3-244621 | Correction on Area of Interest RAN Node for location report | ZTE Corporation |
| R3-244622 | Correction on Area of Interest RAN Node for location report | ZTE Corporation |
| R3-244623 | Correction on Area of Interest RAN Node for location report | ZTE Corporation |
| R3-244624 | Correction on Area of Interest RAN Node for location report | ZTE Corporation |
| R3-244627 | Introduction of cell DTX/DRX information | Nokia, Ericsson, BT |
| R3-244628 | Corrections on Uu Relay RLC channel setup | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell |
| R3-244629 | Corrections on PEI subgrouping | ZTE Corporation, China Unicom, Samsung |
| R3-244630 | Corrections on PEI subgrouping | ZTE Corporation, China Unicom, Samsung |
| R3-244640 | Correction on IAB-node authorization | ZTE Corporation, Lenovo, Xiaomi |
| R3-244641 | Correction on IAB-node authorization | ZTE Corporation, Lenovo, Xiaomi |
| R3-244642 | Correction on mobile IAB-node authorization | ZTE Corporation, Lenovo, Xiaomi |
| R3-244653 | Update of stage 2 positioning information | Nokia, CATT, Ericsson, Huawei, Samsung, Xiaomi, ZTE |
| R3-244654 | Value UE Rx-Tx Time Difference ASN.1 presence correction | Huawei, Nokia, CATT, ZTE, Samsung, Ericsson, Xiaomi |
| R3-244655 | Positioning ASN.1 correction (AggregatedPRSResourceSetList, kminus values) | Huawei, Nokia, CATT, ZTE, Samsung, Ericsson, Xiaomi |
| R3-244656 | NRPPa support for sub 1s location information reporting periodicity [Sub_1s_periodicity] | Ericsson, ZTE, CATT |
| R3-244657 | F1AP support for sub 1s location information reporting periodicity [Sub_1s_periodicity] | ZTE Corporation, Ericsson, CATT |
| R3-244658 | CB:#7_Positioning | CATT |
| R3-244659 | Stage 2 correction for reporting of requested DL LBT information | Ericsson, Nokia, Samsung, Huawei, ZTE |
| R3-244661 | Correction on SPR retrieval and forwarding | Samsung, Lenovo, Cybercore, Qualcomm, Nokia, Ericsson, Huawei, ZTE, CATT |
| R3-244662 | Correction on CPA failure states and detection mechanism in stage 2 | Nokia, CATT, CMCC, Qualcomm Incorporated, Huawei, ZTE Corporation, Lenovo |
| R3-244663 | Corrections on information element to support both CPAC and S-CPAC | ZTE Corporation, Ericsson, CATT, China Telecom, CMCC, Samsung, Nokia, Lenovo, NEC, Google, LG Electronics, Huawei |
| R3-244664 | LTM supports feature of MIMO with 2TA | Samsung, Nokia, CATT, Huawei, ZTE, Ericsson, LG Electronics, Google, CMCC, NEC, Lenovo |
| R3-244665 | Correction on S-CPAC Complete Configuration Indicator | Huawei, LG Electronics, ZTE, CMCC, Ericsson, Nokia |
| R3-244666 | CB:#8_MobilityEnh | Samsung |
| R3-244667 | Correction on the QMC information in the SN modification required message | Huawei, China Unicom, Ericsson, Lenovo |
| R3-244668 | Changing presence of IE extensions for MBS related IEs | Ericsson, Nokia, Huawei, CATT, Samsung, ZTE |
| R3-244669 | Changing presence of IE extensions for MBS related IEs | Ericsson, Nokia, Huawei, CATT, Samsung, ZTE |
| R3-244670 | Correction on configuration update for an inactive Multicast session | ZTE Corporation, CATT, Ericsson, Nokia |
| R3-244671 | Corrections on Uu Relay RLC channel setup | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell |
| R3-244672 | Corrections on Uu Relay RLC channel configuration | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell |
| R3-244673 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT |
| R3-244674 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT |
| R3-244675 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT |
| R3-244676 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT |
| R3-244677 | Correction of PDU Sessions List To Be Released - UPError | Huawei, Nokia, ZTE, Ericsson |
| R3-244678 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244679 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244680 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244681 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244682 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom, ZTE, CATT, China Unicom |
| R3-244683 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244684 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom, ZTE, CATT,China Unicom, Ericsson, Nokia, Huawei |
| R3-244685 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244686 | CB:#12_DLPSI | Huawei |
| R3-244687 | Correction on Multicast Group Paging | Huawei, CBN, Samsung, Nokia, CMCC, Qualcomm Incorporated, CATT, Ericsson, ZTE |
| R3-244688 | Correction on Multicast Group Paging | Huawei, CBN, Samsung, Nokia, CMCC, Qualcomm Incorporated, CATT, Ericsson, ZTE |
| R3-244689 | CB:#13_UEIdentityIndex | Nokia |
| R3-244690 | Corrections on PEI subgrouping | ZTE Corporation, China Unicom, Samsung, Huawei, Ericsson, Nokia |
| R3-244691 | Corrections on PEI subgrouping | ZTE Corporation, China Unicom, Samsung, Huawei, Ericsson, Nokia |
| R3-244692 | Correction on new SIB17bis for TRS in Idle and Inactive | China Telecom,ZTE,CATT,China Unicom |
| R3-244693 | Correction on new SIB17bis for TRS in Idle and Inactive | China Telecom |
| R3-244695 | Correction on SPR retrieval and forwarding | Samsung, Lenovo, Cybercore, Qualcomm, Nokia, Ericsson, Huawei, ZTE, CATT |
| R3-244704 | Correction of QoS Flow List | Huawei, Deutsche Telekom, CATT, Ericsson, ZTE, Nokia |
| R3-244707 | Correction of recovery of split PDU Session | Nokia |
| R3-244709 | Corrections to QMC support in NR-DC for RRC Segmentation | Samsung, Lenovo, Ericsson, ZTE |
| R3-244713 | CB:#25_LocationReport | ZTE |
| R3-244714 | Correction of CP Transport Layer Information and DL UP TNL Information | Huawei, China Unicom, China Telecom, Nokia |
| R3-244717 | Correction of recovery of split PDU Session | Nokia |
| R3-244723 | Correction on MIMO with 2TA in LTM | Huawei, China Unicom, CMCC |
| R3-244724 | Correction on the term of complete configuration | Huawei |
| R3-244725 | Correction on Complete Candidate Configuration | Huawei, Ericsson, LG Electronics, Samsung |
| R3-244740 | Correction of Served Cell Specific Info Request in NG-RAN node configuration update procedure | Huawei, Nokia, CMCC |
| R3-244741 | Correction of Served Cell Specific Info Request in NG-RAN node configuration update procedure | Huawei, Nokia, CMCC |
| R3-244752 | Correction on IAB authorization | CATT, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244753 | Correction on IAB-node authorization | ZTE Corporation, Lenovo, Xiaomi |
| R3-244754 | Correction on mobile IAB-node authorization | ZTE Corporation, Lenovo, Xiaomi |
| R3-244755 | Correction of IAB F1-C transfer in NR-DC | ZTE Corporation |
| R3-244756 | Correction of IAB F1-C transfer in NR-DC | ZTE Corporation |
| R3-244757 | Correction of recovery of split PDU Session | Nokia, Ericsson, Huawei, ZTE |
| R3-244758 | Further miscellaneous corrections to QMC procedure | Huawei, China Unicom, Lenovo, Ericsson |
| R3-244759 | Missing Iuant interface reference in NR specification | Ericsson |
| R3-244761 | Correction on XR PSI based SDU Discard | CMCC, Huawei, CATT, Lenovo, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-244763 | Correction on Early Sync Information from DU to CU | CMCC, ZTE, NEC, CATT, Huawei, Nokia, LG Electronics, Samsung, Ericsson |
| R3-244765 | Aligning procedure code between releases | Huawei, Ericsson, Nokia |
| R3-244772 | Support of pre-configured SRS activation | Huawei, CATT, ZTE, Samsung, Xiaomi, Qualcomm Incorporated, Nokia, Ericsson |
| R3-244773 | Correction of Extended UE Identity Index Value | Nokia, Huawei, Qualcomm Incorporated, CATT |
| R3-244774 | Correction of Extended UE Identity Index Value | Nokia, Huawei, Qualcomm Incorporated, CATT |
| R3-244775 | QoE measurement handling in RRC_IDLE and RRC_INACTIVE states | CATT, Ericsson, ZTE, Xiaomi |
| R3-244776 | LS on Early TA acquisition for the inter-DU scenario | RAN3(Google) |
| R3-244778 | Support of the pre-Configured SRS activation | Xiaomi, Ericsson, Nokia, Qualcomm Incorporated, Huawei, ZTE Corporation, CATT, Samsung |
| R3-244779 | Positioning corrections to F1AP | Ericsson, CATT, ZTE, Samsung, Qualcomm Incorporated, China Telecom, Huawei, Nokia, Xiaomi |
| R3-244780 | LTM stage 2 corrections for split architecture | Ericsson, LG Electronics, Samsung, CATT, Huawei, Nokia, ZTE |
| R3-244781 | Stage 2 correction for AI/ML for NG-RAN | Ericsson, Huawei, Nokia, InterDigital, NEC, CATT, Lenovo, Deutsche Telekom |
| R3-244783 | Corrections to Positioning SRS BW Aggregation and Tx Hopping | CATT, Ericsson, ZTE, Samsung, Qualcomm Incorporated, China Telecom, Huawei, Nokia, Xiaomi |
| R3-244784 | Missing procedure description for pre-configured SRS activation | Qualcomm Incorporated, Ericsson, Nokia, Xiaomi, Huawei, CATT |
| R3-244791 | Correction on MIMO with 2TAs in LTM | Huawei, China Unicom, CMCC, Nokia, LG Electronics, CATT, Ericsson |
| R3-244793 | LS on Early TA acquisition for the inter-DU scenario | RAN3(Google) |
| R3-244794 | Correction on S-CPAC Complete Configuration Indicator | Huawei, LG Electronics, ZTE, CMCC, Ericsson, Nokia |
| R3-244795 | Correction on Complete Candidate Configuration | Huawei, Ericsson, LG Electronics, Samsung, Nokia |
| R3-244796 | Correction on Early Sync Information from DU to CU | CMCC, ZTE, NEC, CATT, Huawei, Nokia, LG Electronics, Samsung, Ericsson, Google |
| R3-244797 | LTM stage 2 corrections for split architecture | Ericsson, LG Electronics, Samsung, CATT, Huawei, Nokia, ZTE, NEC |
| R3-244798 | Correction on IAB authorization | CATT, ZTE, Samsung, Nokia, Nokia Shanghai Bell |
| R3-244799 | Correction on IAB-node authorization | ZTE Corporation, Lenovo, Xiaomi |
| R3-244800 | Further miscellaneous corrections to QMC procedure | Huawei, China Unicom, Lenovo, Ericsson, Nokia, Samsung, ZTE |
| R3-244801 | Correction on mobile IAB-node authorization | ZTE Corporation, Lenovo, Xiaomi, Samsung |
| R3-244802 | Correction of IAB-node authorization | CATT, ZTE, Samsung, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244803 | Correction on IAB-node authorization | ZTE Corporation, Lenovo, Xiaomi, Samsung, CATT, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244805 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244806 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-244817 | Correction on new SIB17bis for TRS in Idle and Inactive | China Telecom,ZTE,CATT,China Unicom |
| R3-244818 | Correction on new SIB17bis for TRS in Idle and Inactive | China Telecom,ZTE,CATT,China Unicom |
| R3-244860 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| TDoc | Title | Source |
|---|---|---|
| R3-244532 | Workplan for Rel-19 SON_MDT Enhancement | China Unicom, CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-244065 | [TP for TS 37.340 BL CR, SON] Failure handling and optimal use of Subsequent CPAC | Nokia |
| R3-244160 | MRO for LTM | NEC |
| R3-244207 | Discussion on MRO for LTM | Samsung |
| R3-244223 | Failure scenarios on MRO for CHO with candidate SCGs | Samsung, Cybercore, ZTE |
| R3-244224 | Discussion on MRO for CHO with candidate SCGs and S-CPAC | Samsung |
| R3-244256 | Discussion on MRO enhancements for LTM | China Telecom |
| R3-244264 | Discussion on MRO for mobility | CATT |
| R3-244278 | (TP for SON BLCR for 38.300, 38.401, 38.473, 37.340) MRO enhancement for R18 mobility mechanisms | Huawei |
| R3-244306 | Discussion on MRO for LTM | Lenovo |
| R3-244307 | (TP for SON BLCR for 37.340) Discussion on MRO for subsequent CPAC and CHO with candidate SCG(s) | Lenovo |
| R3-244335 | MRO Enhancements for LTM and CHO with Candidate SCG(s) | Nokia |
| R3-244430 | MRO enhancements for R18 mobility mechanisms | Qualcomm Incorporated |
| R3-244433 | MRO enhancements for LTM and CHO with candidate SCGs | Ericsson |
| R3-244533 | Discussion on MRO Enhancements | China Unicom |
| R3-244536 | Discussion on MRO issues related to LTM | LG Electronics Inc. |
| R3-244604 | Discussion on MRO enhancements for LTM | CMCC |
| R3-244615 | (TP for TS 38.300 TS37.340)Discussion on MRO | ZTE Corporation |
| R3-244727 | SoD of MRO for LTM | CMCC |
| R3-244728 | SoD of MRO for others | Samsung |
| R3-244764 | (TP for TS37.340) on MRO for S-CPAC | Samsung |
| R3-244782 | (TP for 38.300) MRO enhancement for LTM | ZTE Corporation |
| R3-244826 | (TP for SON BL CR for TS 38.300) MRO enhancement for LTM | ZTE Corporation, Samsung, Nokia, Lenovo |
| R3-244827 | (TP for TS37.340) on MRO for S-CPAC | Samsung, Nokia |
| R3-244853 | (BL CR to 38.300 for SON) Addition of SON enhancements | ZTE Corporation, Samsung, Nokia, Lenovo |
| TDoc | Title | Source |
|---|---|---|
| R3-244066 | [TP to TS 38.423 BL CR, SON] Solution to avoid restarting MRO in NTN deployments | Nokia |
| R3-244260 | Discussion on SON enhancements for NTN | Samsung |
| R3-244265 | Discussion on intra-NTN mobility for SONMDT | CATT |
| R3-244308 | Discussion on MRO for intra-NTN mobility | Lenovo |
| R3-244431 | SON MDT for NTN | Qualcomm Incorporated |
| R3-244434 | SON/MDT enhancements for NTN | Ericsson |
| R3-244460 | (TP to BL CR for TS 38.300) Further discussion on SONMDT enhancements for NTN | ZTE Corporation |
| R3-244481 | SON for Intra-NTN mobility | Huawei |
| R3-244534 | Discussion on SONMDT enhancements for NTN mobility | China Unicom |
| R3-244575 | (TP to 38.300) Discussion on SONMDT enhancement for NTN | CMCC |
| R3-244729 | SoD of SONMDT NTN related | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R3-244067 | [TP to TS 38.300 BL CR, SON] MDT solution for slice support and slice-related mobility enhancements | Nokia |
| R3-244257 | Discussion on SON enhancements for network slicing | China Telecom |
| R3-244266 | Discussion on network slicing for SONMDT | CATT |
| R3-244279 | SON for Network Slicing | Huawei |
| R3-244432 | SON MDT for network slicing | Qualcomm Incorporated |
| R3-244435 | On slice specific MDT measurements and SON enhancements | Ericsson |
| R3-244436 | (TP for SON BL CR for TS 38.413) MDT Area Scope for Network Slicing | Ericsson, InterDigital, Deutsche Telekom, Telecom Italia, T-Mobile USA |
| R3-244535 | Discussion on SONMDT enhancements for network slicing | China Unicom |
| R3-244573 | Discussion on SONMDT for network slicing | CMCC |
| R3-244616 | Further consideration on SON/MDT for Slicing | ZTE Corporation |
| R3-244730 | SoD of SONMDT slicing related | Nokia |
| R3-244815 | (TP for SON BL CR for TS 38.423) MDT Area Scope for Network Slicing | ZTE corporation |
| R3-244816 | (TP for SON BL CR for TS 38.413) MDT Area Scope for Network Slicing | Ericsson, InterDigital, Deutsche Telekom, Telecom Italia, T-Mobile USA |
| R3-244819 | [TP to TS 38.300 BL CR, SON] MDT solution for slice support and slice-related mobility enhancements | Nokia |
| R3-244820 | LS on SON for Network Slicing and enhanced area scope | RAN3(Nokia) |
| R3-244822 | SoD of SONMDT slicing related | Nokia |
| R3-244823 | LS on SON for Network Slicing and enhanced area scope | RAN3(Nokia) |
| R3-244854 | (BL CR to 38.413 for MDT) Addition of MDT enhancements | Ericsson, InterDigital, Deutsche Telekom, Telecom Italia, T-Mobile USA |
| TDoc | Title | Source |
|---|---|---|
| R3-244011 | Reply LS on support of MRO for MR-DC SCG failure | RAN2(ZTE) |
| R3-244225 | Discussion on the support of the leftovers in Rel-18 SON/MDT | Samsung |
| R3-244267 | Discussion on SON enhancement for MR-DC SCG failure | CATT |
| R3-244280 | (TP for SON BLCR for 36.300, 36.423) Rel-18 SON and MDT leftovers | Huawei |
| R3-244309 | (TP for SON BLCR for 36.300) Discussion on MRO for MR-DC SCG failure | Lenovo |
| R3-244437 | Further discussion on RACH optimization for SDT | Ericsson |
| R3-244461 | (TP to BL CR for TS 36.300) Rel-18 leftovers | ZTE Corporation |
| R3-244731 | SoD of SONMDT leftovers | Lenovo |
| R3-244766 | (TP for TS36.423) on MRO for SCG failure | Samsung |
| R3-244777 | (TP to BL CR for TS 36.300) MRO for EN-DC SCG Failure | ZTE Corporation, Nokia, Samsung, Lenovo, Ericsson, Huawei |
| R3-244825 | (TP for TS36.423) on MRO for SCG failure | Samsung, Lenovo, Huawei, Ericsson, CATT, ZTE, CMCC, Nokia |
| R3-244851 | (BL CR to 36.300 for SON) Addition of SON enhancements | Lenovo (Beijing) Ltd |
| R3-244852 | (BL CR to 36.423) on MRO for SCG failure | CATT, Samsung, Lenovo, Huawei, Ericsson, ZTE, CMCC, Nokia |
| TDoc | Title | Source |
|---|---|---|
| R3-244028 | Skeleton for TR38.743 | ZTE, NEC |
| R3-244515 | (TP to 38.743) Conclusion on AI/ML NG-RAN Enhancements | ZTE Corporation, NEC, Samsung, Lenovo, CATT, Qualcomm, Nokia, Huawei, CMCC, China Telecom, China Unicom |
| R3-244625 | Work plan for Study on enhancements for Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN | ZTE Corporation, NEC |
| R3-244694 | Skeleton for TR38.743 | ZTE, NEC |
| R3-244747 | (TP to 38.743) Conclusion on AI/ML NG-RAN Enhancements | ZTE Corporation, NEC, Samsung, Lenovo, CATT, Qualcomm, Nokia, Huawei, CMCC, China Telecom, China Unicom, Telecom Italia |
| R3-244810 | (TP for TR38.743) Conclusion on AI/ML NG-RAN Enhancements | ZTE Corporation, NEC, Samsung, Lenovo, CATT, Qualcomm, Nokia, Huawei, CMCC, China Telecom, China Unicom, Telecom Italia, InterDigital, Ericsson, LG Electronics, Deutsche Telekom, Jio |
| R3-244848 | Study on enhancements for Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN | ZTE, NEC |
| TDoc | Title | Source |
|---|---|---|
| R3-244039 | Discussion on NG-RAN AI/ML for Network Slicing | Tejas Networks Limited |
| R3-244084 | (TP to 38.743) AIML assisted Network Slicing | ZTE Corporation |
| R3-244138 | (TP for TR 38.743) TP on General Corrections for CCO and Slicing | InterDigital Communications |
| R3-244162 | (TP to TR38.743) AI/ML enabled Slicing | NEC |
| R3-244208 | (TP to TR 38.743) AI/ML enabled slicing | Samsung |
| R3-244292 | Discussion on NG-RAN AI/ML for Network Slicing | Qualcomm Incorporated |
| R3-244294 | (TP to TR 38.743) Discussion on the AI/ML-enabled Network Slicing | Huawei |
| R3-244303 | AIML for Network Slicing | Ericsson, InterDigital, T-Mobile USA, Lenovo, Telecom Italia, Qualcomm, Deutsche Telekom |
| R3-244304 | TP for TR 38.743 on AIML for Network Slicing | Ericsson, InterDigital, T-Mobile USA, Lenovo, Telecom Italia, Qualcomm, Deutsche Telekom |
| R3-244311 | Discussion on AIML based network slicing | Lenovo |
| R3-244312 | TP to 38.743 for AIML based network slicing | Lenovo |
| R3-244442 | AI/ML Network Slicing Discussion | Nokia, Jio |
| R3-244472 | (TP to TR 38.743) AI/ML Network Slicing | Nokia, Jio |
| R3-244507 | Support of AI/ML enabled slicing | CATT |
| R3-244508 | (TP for TR38.743) Support of AI/ML enabled slicing | CATT |
| R3-244571 | Discussion on AI-based network slice | CMCC |
| R3-244581 | TP to 38.743 AI/ML based CCO | CMCC |
| R3-244636 | Discussion on AIML based Network Slicing | Rakuten Mobile, Inc |
| R3-244638 | TP for TR 38.743 on AIML for Network Slicing | Rakuten Mobile, Inc |
| R3-244696 | CB:# AIRAN1_Slicing | Nokia |
| R3-244734 | (TP to TR 38.743) AI/ML Network Slicing | Nokia, Jio |
| R3-244804 | (TP to TR 38.743) AI/ML Network Slicing | Nokia, Jio, Huawei, ZTE Corporation, Ericsson, Telecom Italia, InterDigital, NEC,CATT, Lenovo, Samsung, CMCC, Deutsche Telekom |
| TDoc | Title | Source |
|---|---|---|
| R3-244034 | Further Enhancements on AIML CCO as SON use case | Jio |
| R3-244035 | AIML CCO as SON use case | Jio |
| R3-244036 | Discussion on Enhancements for AIML based CCO | Jio |
| R3-244037 | Enhancements for AI ML NG-RAN CCO | Jio |
| R3-244038 | Discussion on AIML based CCO | Jio |
| R3-244062 | Discussion on Centralized beam prediction for AI/ML based CCO | Jio |
| R3-244063 | Discussion on AIML based CCO De-Centralized beam prediction | Jio |
| R3-244071 | Discussion on beam prediction for AIML based CCO | Jio |
| R3-244072 | (TP to TR 38.743) Further Enhancements for AI ML NG-RAN mobility | Jio |
| R3-244073 | (TP for TR 38.744) Enhancements in AI ML NG-RAN mobility | Jio |
| R3-244085 | (TP to 38.743) AIML assisted CCO | ZTE Corporation |
| R3-244163 | (TP to TR38.743) AI/ML enabled CCO | NEC |
| R3-244209 | Discussion on AI/ML enabled CCO | Samsung |
| R3-244210 | (TP to TR 38.743) AI/ML enabled CCO | Samsung |
| R3-244249 | Discussion on AI/ML based Coverage and Capacity Optimization | China Telecom |
| R3-244250 | (TP to 38.743) Support of AI/ML based Coverage and Capacity Optimization | China Telecom |
| R3-244290 | Discussion on AI/ML enabled CCO | Qualcomm Incorporated |
| R3-244291 | (TP for TR 38.743) AI/ML enabled CCO | Qualcomm Incorporated, ZTE, CATT, SS, CMCC |
| R3-244295 | (TP to TR 38.743) AI/ML-based Coverage and Capacity Optimization | Huawei |
| R3-244302 | Discussinos on timing aspects of AI/ML based CCO | Ericsson, InterDigital, Telecom Italia, Deutsche Telekom, Vodafone |
| R3-244310 | Discussion on AI/ML based CCO | Lenovo |
| R3-244313 | TP to 38.743 for AIML based CCO | Lenovo |
| R3-244377 | Discussion on how to determine the future CCO state | Nokia, Telecom Italia, Jio, Vodafone |
| R3-244378 | Discussion on solution for AI/ML-based CCO | Nokia |
| R3-244379 | (TP for TR 38.743) Solution for AI/ML-based CCO | Nokia |
| R3-244438 | TP on AIML support for CCO | Ericsson, InterDigital |
| R3-244451 | TP on AIML support for CCO | Ericsson, InterDigital |
| R3-244452 | Further discussion on AIML support for CCO | Ericsson, InterDigital |
| R3-244509 | (TP for TR38.743) Open issues on the CCO use case | CATT |
| R3-244537 | Remaining issues of AIML-based CCO | LG Electronics Inc. |
| R3-244538 | (TP to TR 38.743) Remaining issues of AIML-based CCO | LG Electronics Inc. |
| R3-244572 | Discussion on AI/ML-based CCO | CMCC |
| R3-244644 | Response to R3-244085 | Jio |
| R3-244697 | (TP for TR 38.743) AI/ML enabled CCO | Qualcomm Incorporated, ZTE, CATT, Samsung, CMCC |
| R3-244698 | CB:#AIRAN2_CCO | Lenovo |
| R3-244807 | (TP for TR 38.743) AI/ML enabled CCO | Qualcomm Incorporated, ZTE, CATT, Samsung, CMCC, LGE, DT, Lenovo |
| R3-244821 | (TP for TR 38.743) AI/ML enabled CCO | Qualcomm Incorporated, ZTE, CATT, Samsung, CMCC, LGE, DT, Lenovo |
| R3-244843 | (TP for TR 38.743) AI/ML enabled CCO | Qualcomm Incorporated, ZTE, CATT, Samsung, CMCC, Telecom Italia, Huawei, NEC, InterDigital, Nokia, Ericsson, LG Electronics, Deutsche Telekom, Lenovo, Reliance JIO |
| TDoc | Title | Source |
|---|---|---|
| R3-244040 | Enhancements on AI-ML Network Energy Saving | Jio |
| R3-244041 | Enhancements for AI ML Energy Savings | Jio |
| R3-244046 | (TP for TR 38.744) AI/ML NG-RAN mobility | Jio |
| R3-244047 | (TP to TR 38.743) Enhancements for AI ML NG-RAN mobility | Jio |
| R3-244086 | (TP to 38.743) Continuous MDT collection enhancements | ZTE Corporation |
| R3-244087 | (TP to 38.743) Mobility Optimization for NR-DC | ZTE Corporation |
| R3-244088 | (TP to 38.743) Support of AI/ML NG-RAN in split architecture | ZTE Corporation |
| R3-244089 | Discussion on Finer granularity of Energy Cost | ZTE Corporation |
| R3-244164 | Energy Saving Enhancements | NEC |
| R3-244165 | Continuous MDT collection for AI/ML | NEC |
| R3-244166 | Split architecture and NR-DC mobility optimization | NEC |
| R3-244197 | Discussion on AIML for energy saving | NTT DOCOMO INC.. |
| R3-244211 | (TP to TR 38.743) AI/ML for mobility in NR-DC | Samsung |
| R3-244212 | (TP to TR 38.743) AI/ML for NG-RAN in split architecture | Samsung |
| R3-244213 | (TP to TR 38.743) Continuous MDT collection targeting the same UE across RRC states | Samsung |
| R3-244251 | Discussion on Continuous MDT measurement | China Telecom |
| R3-244252 | (TP to 38.743) Support of Continuous MDT measurement | China Telecom |
| R3-244293 | Discussion on Continuous MDT | Qualcomm Incorporated |
| R3-244296 | (TP to TR 38.743) AI/ML-based Mobility Enhancements in NR-DC | Huawei |
| R3-244297 | (TP to TR 38.743) Split architecture support for Rel-18 “AI/ML for NG-RAN” use cases | Huawei |
| R3-244298 | Rel-18 AI/ML for NG-RAN leftovers: Energy Saving Enhancements | Huawei |
| R3-244299 | On Continuous MDT for AI/ML | Huawei |
| R3-244314 | Discussion on other leftover issues | Lenovo |
| R3-244315 | TP to 38.743 for other leftover issues | Lenovo |
| R3-244350 | (TP for TR 38.743) TP on Continuous MDT feasibility | Ericsson, InterDigital, Deutsche Telekom |
| R3-244351 | Continuous MDT feasibility | Ericsson, InterDigital, Deutsche Telekom |
| R3-244352 | Network Energy Saving for EC in mobility | Jio |
| R3-244417 | Further discussion on AI/ML for split architecture use cases | Ericsson |
| R3-244418 | TP on Split architecture support for Rel-18 use cases | Ericsson |
| R3-244439 | TP on Mobility Optimization for NR-DC | Ericsson, InterDigital |
| R3-244440 | Improved granularity for Energy Cost | Ericsson |
| R3-244441 | TP on Improved granularity for Energy Cost | Ericsson |
| R3-244443 | Discussion on AI/ML Mobility Optimization for NR-DC | Nokia |
| R3-244444 | (TP to TR 38.743) Mobility Optimization for NR-DC | Nokia |
| R3-244445 | On the Support of Split Architecture for the Rel-18 AI/ML Use Cases | Nokia, Telecom Italia, Huawei |
| R3-244446 | (TP to TR 38.743) Split Architecture Support for the Rel-18 AI/ML Use Cases | Nokia, Telecom Italia, Huawei |
| R3-244447 | Finer Granularity Energy Cost Discussion | Nokia, Telecom Italia, T-Mobile USA, BT |
| R3-244448 | (TP to TR 38.743) Finer Granularity Energy Cost | Nokia, Telecom Italia, T-Mobile USA, BT |
| R3-244449 | Continuous Management-based MDT | Nokia, Telecom Italia, Qualcomm |
| R3-244450 | (TP to TR 38.743) Towards a Continuous Management-based MDT solution | Nokia, Telecom Italia, Qualcomm |
| R3-244453 | Further discussion on Mobility Optimization for NR-DC | Ericsson, InterDigital, AT&T |
| R3-244454 | TP on Mobility Optimization for NR-DC | Ericsson, InterDigital, AT&T |
| R3-244510 | (TP for TR 38.743) Discussion on left over issues on DC and split architecture | CATT |
| R3-244511 | (TP for TR 38.743)Enhancement of UE performance metrics | CATT |
| R3-244512 | (TP for TR 38.743Finer granularity of Energy Cost | CATT |
| R3-244539 | Remaining issues of mobility optimization for NR-DC | LG Electronics Inc. |
| R3-244540 | (TP to TR 38.743) Remaining issues of mobility optimization for NR-DC | LG Electronics Inc. |
| R3-244565 | TP to TR38.743 on Finer granularity of Energy Cost | CMCC,Samsung |
| R3-244566 | TP to TR38.743 Discussion on AIML for split architecure use cases | CMCC,ZTE,Lenovo,Qualcomm |
| R3-244567 | TP to TR38.743 on continuous MDT | CMCC |
| R3-244574 | (TP to 38.743) Discussion on AIML based Mobility Optimization for NR-DC | CMCC |
| R3-244699 | CB:#AIRAN3_EC | Ericsson |
| R3-244700 | CB:#AIRAN4_Others | ZTE |
| R3-244742 | (TP to TR 38.743) AI/ML for NG-RAN Rel-18 Leftovers | ZTE Corporation |
| R3-244749 | (TP for 38.743) on Improved granularity for Energy Cost | Ericsson |
| R3-244808 | (TP for 38.743) on Improved granularity for Energy Cost | Ericsson, Nokia, Lenovo, Telecom Italia |
| R3-244809 | (TP to TR 38.743) AI/ML for NG-RAN Rel-18 Leftovers | ZTE Corporation, Telecom Italia, DT, Samsung, LGE, CMCC |
| R3-244841 | (TP for 38.743) on Improved granularity for Energy Cost | Ericsson, Telecom Italia, Lenovo, Nokia, Jio |
| R3-244842 | (TP to TR 38.743) AI/ML for NG-RAN Rel-18 Leftovers | ZTE Corporation, Huawei, Ericsson, InterDigital, Nokia,CATT, NEC, Lenovo, Telecom Italia, LG Electronics, Deutsche Telekom, Samsung, CMCC, Jio |
| R3-244862 | (TP to TR 38.743) AI/ML for NG-RAN Rel-18 Leftovers | ZTE Corporation, Huawei, Ericsson, InterDigital, Nokia,CATT, NEC, Lenovo, Telecom Italia, LG Electronics, Deutsche Telekom, Samsung, CMCC, Jio |
| TDoc | Title | Source |
|---|---|---|
| R3-244029 | TR skeleton for additional topological enhancements for NR | NTT DOCOMO INC., AT&T |
| R3-244849 | Study on additional topological enhancements for NR | NTT DOCOMO INC., AT&T |
| TDoc | Title | Source |
|---|---|---|
| R3-244019 | LS on questions regarding FS_VMR_Ph2 | SA2(Samsung) |
| R3-244118 | (TP to TR 38.799) Discussion on supporting WAB and the reply LS to SA2 | ZTE Corporation |
| R3-244119 | (TP to TR 38.799) Discussion on WAB mobility | ZTE Corporation |
| R3-244120 | (TP to TR 38.799) Discussion on other aspects in WAB | ZTE Corporation |
| R3-244121 | Discussion on Network Selection for WAB | Fraunhofer IIS, Fraunhofer HHI |
| R3-244140 | (draft Reply LS) Discussion on reply LS to SA2 on questions regaring VS_VMR_Ph2 | Qualcomm Inc. |
| R3-244141 | (TP to TR 38.799) Remaining issues for WAB | Qualcomm Inc. |
| R3-244142 | (TP to TR 38.799) Conclusion of study on WAB | Qualcomm Inc. |
| R3-244154 | Discussion on the architecture and mobility for WAB | NEC |
| R3-244231 | (TP to TR 38.799 & draft reply LS) On WAB architecture and authorization | CATT |
| R3-244232 | (TP to TR 38.799) Discussion on WAB mobility | CATT |
| R3-244233 | (TP to TR 38.799) Discusson on resource multiplexing for WAB | CATT |
| R3-244269 | (pCR for TR 38.799): Functional Aspects of WAB-Nodes | Ericsson |
| R3-244270 | (pCR for TR 38.799): Handling of Reliability and Latency for WAB | Ericsson |
| R3-244271 | Reply to SA2 Questions Regarding UE Access Control and Additional ULI | Ericsson |
| R3-244316 | Discussion on architecture and QoS mapping for WAB | Lenovo |
| R3-244317 | (TP to TR 38.799) Discussion on WAB-gNB migration | Lenovo |
| R3-244318 | (TP to TR 38.799) Discussion on resource multiplexing for WAB node | Lenovo |
| R3-244334 | Discussion on enhancements for WAB | CANON Research Centre France |
| R3-244337 | (TP to TR 38.799) Discussion on Xn support for WAB-gNB and Traffic Mapping | Nokia, Nokia Shanghai Bell |
| R3-244338 | (TP to TR 38.799) Discussion on WAB mobility | Nokia, Nokia Shanghai Bell |
| R3-244339 | Discussion on SA2 LS | Nokia, Nokia Shanghai Bell |
| R3-244392 | (TP for TR 38.799) Remaining open issues in WAB | LG Electronics |
| R3-244394 | (TP for TR 38.799) Access control and location information in WAB | LG Electronics |
| R3-244395 | Reply LS on questions regarding FS_VMR_Ph2 | LG Electronics |
| R3-244526 | Discussion on the Architecture, access control and QoS mappingsupport of WAB | Huawei |
| R3-244527 | Discussion on WAB mobility and other some remaining issues | Huawei |
| R3-244528 | Discussion on SA2's LS (S2-2407345) on questions regarding FS_VMR_Ph2 | Huawei |
| R3-244541 | (TP to TR 38.799) Discussion on support WAB | Samsung |
| R3-244542 | Discussion on WAB mobility | Samsung |
| R3-244543 | (draft Reply LS) Discussion on LS for VMR from SA2 | Samsung |
| R3-244562 | On WAB Awareness and Authorization | China Telecom |
| R3-244563 | On Xn Connection Management | China Telecom |
| R3-244631 | Discussion on Wireless Access Backhaul | NTT DOCOMO INC. |
| R3-244701 | Summary of Offline Discussion on additional topological enhancement | NTTDOCOMO, INC. |
| R3-244737 | Summary of offline discussion for AI 12.2 | Ericsson |
| R3-244743 | CB:#WAB, Summary of offline discussion | Ericsson |
| R3-244744 | Reply LS on questions regarding FS_VMR_Ph2 | RAN3(ZTE) |
| R3-244745 | (TP for TR 38.799): Agreements and SI conclusions for WAB | Ericsson |
| R3-244746 | (TP for TR 38.799): WAB mobility | Huawei |
| R3-244828 | (TP for TR 38.799): Agreements and SI conclusions for WAB | Ericsson |
| R3-244829 | (TP for TR 38.799): WAB mobility | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R3-244012 | Reply LS on Support of UE move between CAG cell of 5G Femto and CSG cell | RAN2(LGE) |
| R3-244101 | (TP for TR 38.799) Access to local services from the 5G Femto via distributed UPF | Huawei |
| R3-244143 | (draft Reply LS) Discussion on reply LS to SA2 on Support of UE move between CAG cell of 5G Femto and CSG cell | Qualcomm Inc. |
| R3-244144 | Support of local services with UPF at NR Femto | Qualcomm Inc. |
| R3-244145 | Conclusion of study on NR Femto | Qualcomm Inc. |
| R3-244167 | (Draft reply LS) Mobility between CAG cell and CSG cell | NEC |
| R3-244168 | NR femto | NEC |
| R3-244171 | (TP to TR 38.799)Discussion on architecture and access control of NR Femto | ZTE Corporation |
| R3-244172 | (TP to TR 38.799)Discussion on support of local services | ZTE Corporation |
| R3-244173 | (TP for TR 38.799)Evaluation of NR Femto Architecture Options | ZTE Corporation |
| R3-244202 | (TP to TR 38.799) Proposals on NR Femto Architecture | Baicells |
| R3-244234 | (TP to TR 38.799) Discussion on 5G Femto architecture | CATT |
| R3-244235 | (TP to TR 38.799) On 5G Femto local service access | CATT |
| R3-244236 | (TP to TR 38.799) On 5G Femto access control mechanism | CATT |
| R3-244258 | (TP to TR 38.799) On Access Control and Mobility for NR Femto | China Telecom |
| R3-244259 | (TP to TR 38.799) On local service access for NR Femto | China Telecom |
| R3-244319 | Discussion on interworking between CAG and CSG cells | Lenovo |
| R3-244320 | (TP to TR 38.799) Access control and handover for NR Femto with CAG | Lenovo |
| R3-244321 | Local services for NR Femto via collocated local UPF | Lenovo |
| R3-244369 | (Non-Opinionated) Analysis of CAG-CSG Mobility Support | Ericsson, NTT Docomo, Huawei, ZTE, LG Electronics Inc., Deutsche Telekom |
| R3-244370 | Discussion and Potential Conclusions for NR Femto | Ericsson |
| R3-244371 | NR Femto Node Access Control with CAG | Ericsson |
| R3-244372 | Access to Local Services via Local UPF | Ericsson |
| R3-244396 | (TP for TR 38.799) Remaining open issues in 5G Femto | LG Electronics |
| R3-244414 | [TP for TR 38.799] Conclusion on NR Femto Architecture Options | Nokia, TMO US, AT&T, Verizon Wireless, British Telekom, NTT Docomo, KDDI, Charter |
| R3-244415 | Answer to SA2 LS on UE Move between CAG cell and CSG cell | Nokia |
| R3-244416 | [TP for TR 38.799] Temporary Access Control for NR Femtos and Mobility | Nokia |
| R3-244419 | [TP for TR 38.799] Access to Local Services | Nokia |
| R3-244529 | Discussion on the architecture for NR Femto | Huawei |
| R3-244530 | Discussion on the access control for NR Femto | Huawei |
| R3-244544 | (TP to TR 38.799) Discussion on Femto architecture | Samsung |
| R3-244545 | (TP to TR 38.799) Discussion on access control and handover for NR Femto | Samsung |
| R3-244589 | Discussion on 5G Femto architecture | CMCC |
| R3-244590 | Discussion on access control for 5G Femto with CAG | CMCC |
| R3-244591 | Draft Reply LS to request clarification on the potential baseline system architecture of 5G NR Femto | CMCC |
| R3-244632 | Discussion on 5G Femto | NTT DOCOMO INC. |
| R3-244710 | (TP for TR 38.799) Conclusion and Recommendation of NR Femto Study | Nokia |
| R3-244712 | (TP for TR 38.799) Access to Local Services – Text Proposal | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-244720 | (TP for TR 38.799) Conclusion and Recommendation of NR Femto Study | Nokia, Ericsson |
| R3-244721 | (TP for TR 38.799) TP for Xn IF evaluation | ZTE, Huawei |
| R3-244722 | (TP for TR 38.799) Access control for NR femto | Huawei |
| R3-244726 | (TP for TR 38.799) Access to Local Services – Text Proposal | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-244732 | (TP for TR 38.799) General | ZTE, Huawei |
| R3-244733 | Reply LS on Support of UE move between CAG cell of 5G Femto and CSG cell | RAN3(Ericsson) |
| R3-244738 | Summary of offline discussion for AI 12.3 | Ericsson |
| R3-244814 | Response LS to SA3 on architecture of NR Femto | Huawei |
| R3-244824 | (TP for TR 38.799) Access to Local Services – Text Proposal | Ericsson, Nokia, Huawei |
| R3-244830 | Reply LS on Support of UE move between CAG cell of 5G Femto and CSG cell | RAN3(Ericsson) |
| R3-244831 | Response LS to SA3 on architecture of NR Femto | RAN3(Huawei) |
| R3-244832 | (TP for TR 38.799) General | ZTE, Huawei |
| R3-244833 | (TP for TR 38.799) Access to Local Services – Text Proposal | Ericsson, Nokia, Huawei |
| R3-244834 | (TP for TR 38.799) TP for Xn IF evaluation | ZTE, Huawei |
| R3-244835 | (TP for TR 38.799) Access control for NR femto | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R3-244022 | Reply LS to RAN2 on security handling for inter-CU LTM in non-DC cases | SA3(Apple) |
| R3-244042 | Discussion on Inter-gNB-CU LTM Procedure | Nokia |
| R3-244043 | Discussion on RRC Implications to RAN3 Signaling for Inter-gNB-CU LTM | Nokia |
| R3-244044 | TP (BL CR TS 38.401) L1/2 Triggered Mobility (LTM) Procedures | Nokia |
| R3-244055 | Discussion on inter-CU LTM | ZTE Corporation |
| R3-244056 | TP to 38.300 for inter-CU LTM | ZTE Corporation |
| R3-244057 | TP to 38.423 for inter-CU LTM | ZTE Corporation |
| R3-244152 | inter-CU LTM issues | NEC |
| R3-244180 | Discussion on Early Sync and CFRA resource configurations in inter-CU LTM | |
| R3-244198 | Discussion on inter-CU LTM non-DC case | NTT DOCOMO INC.. |
| R3-244203 | Resource management Inter-CU LTM | Rakuten Mobile, Inc |
| R3-244204 | Data forwarding and transmission in Inter-CU LTM | Rakuten Mobile, Inc |
| R3-244228 | Inter-gNB LTM with no change of RRC/PDCP anchor | Qualcomm Incorporated, NTT DOCOMO, Vodafone, Bharti AirTel (India), Sony |
| R3-244229 | Signalling enhancements for inter-CU LTM HO | Qualcomm Incorporated |
| R3-244253 | Discussion on signaling enhancement for inter-CU LTM | China Telecom |
| R3-244254 | (TP for TS38.420) On support of inter-CU LTM | China Telecom |
| R3-244255 | (TP for TS38.423) On support of inter-CU LTM | China Telecom |
| R3-244272 | Discussion for Inter-CU LTM | CATT |
| R3-244273 | Common impact in RAN3 for security key update | CATT |
| R3-244274 | TP for LTM BLCR for TS38.300 | CATT |
| R3-244322 | General aspects of inter-CU LTM | Lenovo |
| R3-244323 | [TP for TS 38.423] Inter-CU LTM | Lenovo |
| R3-244324 | [TP for TS 38.300] Inter-CU LTM | Lenovo |
| R3-244355 | Further discussion on XnAP signaling for inter-CU LTM | Ericsson |
| R3-244356 | (TP for TS 38.423) Xn support for inter-CU LTM | Ericsson |
| R3-244357 | (TP for TS 38.300) Stage-2 signalings for inter-CU LTM | Ericsson |
| R3-244476 | Further discussion on Inter-CU LTM signaling design | LG Electronics Inc. |
| R3-244477 | Baseline CR for introducing Rel-19 Mobility enhancement in E1AP | LG Electronics Inc. |
| R3-244478 | (TP for NR_Mob_Ph4 TS 38.423) | LG Electronics Inc. |
| R3-244482 | Discussion on the PDCP anchor based solution | Huawei, Ericsson, CATT, China Telecom, CMCC, Samsung |
| R3-244483 | Discussion on Inter-CU LTM procedure | Huawei |
| R3-244484 | (TP for LTM BLCR for TS38.300): Inter-CU LTM basic procedure | Huawei |
| R3-244485 | (TP for LTM BLCR for TS 38.473): F1 impact for Inter-CU LTM | Huawei |
| R3-244559 | Discussion on Inter-gNB-CU LTM | Samsung |
| R3-244560 | Additional discussion on Inter-gNB-CU LTM | Samsung |
| R3-244561 | (TP to BLCR for TS 38.401/38.300) Procedure for Inter-CU/gNB LTM | Samsung |
| R3-244584 | Discussion on inter-CU LTM | CMCC |
| R3-244646 | Response to R3-244482 | Qualcomm Incorporated |
| R3-244718 | CB:#LTM_stage2procedure | China Telecom |
| R3-244719 | CB:#LTM_PDCPanchor | Lenovo |
| R3-244790 | (TP for LTM BLCR for TS38.300): Inter-CU LTM basic procedure | Huawei, Google, Nokia, China Telecom, NEC, Ericsson, LGE, ZTE, CATT |
| R3-244836 | (TP for LTM BLCR for TS38.300): Inter-CU LTM basic procedure | Huawei, Google, Nokia, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung |
| R3-244855 | (BL CR to 38.300) Inter-CU LTM basic procedure | Huawei, Google, Nokia, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R3-244031 | (BL CR to 38.300) Support for Regenerative Payload in NR NTN | Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei, Dish Networks, Echostar, Eutelsat Group, Xiaomi, Samsung, CMCC, LG Electronics |
| R3-244739 | (BL CR to 38.300) Support for Regenerative Payload in NR NTN | Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei, Dish Networks, Echostar, Eutelsat Group, Xiaomi, Samsung, CMCC, LG Electronics, NEC, Lenovo |
| R3-244856 | (BL CR to 38.300) Support for Regenerative Payload in NR NTN | Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei, Dish Networks, Echostar, Eutelsat Group, Xiaomi, Samsung, CMCC, LG Electronics, NEC, Lenovo |
| TDoc | Title | Source |
|---|---|---|
| R3-244123 | Way forward for MBS Broadcast intended service area discussion | THALES |
| R3-244155 | Discussion on NR NTN supporting MBS broadcast service | NEC |
| R3-244181 | (TP to NTN BL CRs) Support of MBS broadcast service for NR NTN | CATT |
| R3-244194 | Support of Broadcast service | Xiaomi |
| R3-244246 | Further discussion on support MBS broadcast service for NTN | China Telecom |
| R3-244288 | (TP for TS38.300) Discussion on Support for NR NTN MBS Broadcast Service | Qualcomm Incorporated |
| R3-244325 | Support of broadcast service in NTN | Lenovo |
| R3-244342 | (TP to BL CR for TS 38.300) Discussion on the support of MBS Broadcast Service | Nokia, Nokia Shanghai Bell |
| R3-244363 | (TP for TS 38.413 and TS 38.300) Support MBS broadcast service | Huawei |
| R3-244373 | Broadcast Service Area for NR NTN | Ericsson, SES, ESA |
| R3-244374 | Broadcast Service Area for NR NTN - NGAP Impacts | Ericsson, SES, ESA |
| R3-244468 | Discussion on NTN broadcast service supporting with TP to TS 38.300 and 38413 | ZTE Corporation |
| R3-244552 | Discussion on support MBS broadcast service for NR NTN | Samsung |
| R3-244568 | Discussion on Supporting MBS broadcast service for NR NTN | CMCC |
| R3-244635 | Discussion on Support of MBS Broadcasting over NTN access | TCL |
| R3-244813 | (TP to BL CR for TS 38.300) Support of MBS broadcast service | CATT, Xiaomi, Nokia, Nokia Shanghai Bell, ZTE, NEC, China Telecom |
| TDoc | Title | Source |
|---|---|---|
| R3-244051 | Regenerative payload considerations | Eutelsat Group |
| R3-244108 | (TP for TS 38.413) Introduce NG Removal procedure | Nokia, Nokia Shanghai Bell, Huawei, CATT, CMCC, Ericsson, Qualcomm |
| R3-244156 | Discussion on NR NTN supporting regenerative NTN | NEC |
| R3-244182 | (TP to NTN BL CRs) Support of regenerative payload | CATT |
| R3-244195 | (TP for TS 38.300) Support of regenerative payload | Xiaomi |
| R3-244200 | Discussion on Xn impact for NR NTN regenerative payload | NTT DOCOMO INC.. |
| R3-244201 | Discussion on support of regenerative payload | ETRI |
| R3-244247 | Further discussion on support of regenerative payload | China Telecom |
| R3-244289 | (TP for TS 38.300) Discussion on NG Signaling impacts for NR NTN Regenerative Payload | Qualcomm Incorporated |
| R3-244326 | Mobility issues for regenerative payload in NTN | Lenovo |
| R3-244343 | (TP to BL CR for TS 38.300) Discussion on the support of Regenerative payload | Nokia, Nokia Shanghai Bell |
| R3-244364 | (TP for BLCR for TS 38.300) Support of regenerative payload | Huawei |
| R3-244365 | (TP for TS 38.410) Support for Regenerative Payload in NR NTN | Huawei, Nokia, Nokia Shanghai Bell, CATT, CMCC, Ericsson |
| R3-244375 | Further Discussion on NTN Regenerative Payload Issues in Rel-19 | Ericsson, Thales, SES, ESA, Sateliot |
| R3-244426 | NG Removal - Stage 2 Description | Ericsson, Huawei |
| R3-244462 | Further discussion on support of regenerative payload | ZTE Corporation |
| R3-244479 | Discussion on N2/S1 connection management | LG Electronics Inc. |
| R3-244480 | (TP for NR_NTN_Ph3 TS 38.413) | LG Electronics Inc. |
| R3-244547 | (TP for TS 38.410) Support for Regenerative Payload in NR NTN | Huawei, Nokia, Nokia Shanghai Bell, CATT, CMCC, Ericsson, Qualcomm Incorporated |
| R3-244548 | (TP for BLCR for TS 38.300) Support of regenerative payload | Huawei |
| R3-244553 | Discussion on support of regenerative payload for NR NTN | Samsung |
| R3-244569 | Discussion on support of regenerative payload for NR NTN | CMCC |
| R3-244634 | Discussion on NTN regenerative architecture | TCL |
| R3-244639 | NG Removal – Stage 2 Description | Ericsson, Huawei, Nokia |
| R3-244748 | CB:#NRNTN2_RegenerativePayload | Thales |
| TDoc | Title | Source |
|---|---|---|
| R3-244463 | Work Plan for Rel-19 IoT NTN | ZTE Corporation, CATT, MediaTek Inc. |
| TDoc | Title | Source |
|---|---|---|
| R3-244124 | Discussion on Support of Store and Forward in NTN | THALES |
| R3-244196 | Support of Store and Forward in IoT NTN | Xiaomi |
| R3-244245 | Support for Store and Forward operation in IoT NTN | China Telecom |
| R3-244277 | Discussion about UE attachment in Store & Forward | CATT |
| R3-244287 | Discussion on Support for IoT NTN for Regenerative Payload | Qualcomm Incorporated |
| R3-244344 | Discussion on the support of Store&Forward | Nokia, Nokia Shanghai Bell |
| R3-244366 | Support store and forward for IoT NTN | Huawei |
| R3-244383 | Support for Regenerative Payload in IoT NTN | Ericsson, Sateliot |
| R3-244464 | Initial considerations on support of store and forward satellite operation for IoT NTN | ZTE Corporation |
| R3-244516 | Discussion on Support of Store and Forward in NTN | THALES, Novamint, Sateliot |
| R3-244554 | Discussion on support of regenerative payload for IoT NTN | Samsung |
| R3-244570 | Discussion on support of IoT NTN | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-244014 | LS on RAN2 agreements and assumptions for Ambient IoT | RAN2(OPPO) |
| R3-244018 | LS on Clarification of requirements for Ambient IoT | SA2(Ericsson) |
| R3-244030 | (BL pCR to TR 38.769) Study on solutions for Ambient IoT in NR | Huawei, CMCC |
| R3-244592 | Work Plan for Ambient IoT SI | CMCC, Huawei, T-Mobile USA |
| R3-244850 | (pCR to TR 38.769) Study on solutions for Ambient IoT in NR | Huawei, CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-244058 | (TP for TR38.769) RAN architecture for Ambient-IoT | ZTE Corporation |
| R3-244102 | (TP for TR 38.769) RAN architecture aspects | Huawei |
| R3-244139 | [TP for TR 38.769] RAN Architecture for AIoT | InterDigital Communications |
| R3-244148 | A-IoT Architecture | MediaTek Inc. |
| R3-244157 | RAN architecture discussion on ambient IoT | NEC |
| R3-244183 | (TP to TR 38.769) A-IoT architecture aspects | CATT |
| R3-244191 | (TP for TR 38.769) AIoT RAN architecture | Xiaomi |
| R3-244248 | (TP for TR 38.769) RAN architecture for Ambient-IoT | China Telecom |
| R3-244327 | RAN architecture considerations of ambient IoT | Lenovo |
| R3-244387 | On AIoT RAN functional and logical architecture | Ericsson |
| R3-244388 | [TP for TR 38.769] on AIoT Architecture aspects | Ericsson |
| R3-244420 | [TP for TR 38.769] AIoT Architecture for Topology 1 and 2 | Nokia |
| R3-244427 | Architecture, interfaces and transport for Ambient IoT | Qualcomm Incorporated |
| R3-244555 | Discussion on RAN architecture for Ambient IoT | Samsung |
| R3-244593 | Discussion on RAN Architecture for Ambient IoT | CMCC |
| R3-244702 | CB:#AIoT1_ArchitectureProtocol | Huawei |
| R3-244716 | (TP for TR 38.769) RAN architecture aspects | Huawei |
| R3-244837 | (TP for TR 38.769) RAN architecture aspects | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R3-244059 | (TP for TR38.769) NG interface impact for Ambient-IoT | ZTE Corporation |
| R3-244060 | Discussion on unified procedure for AIoT topology 1 and 2 | ZTE Corporation |
| R3-244104 | (TP for TR 38.769) Signalling and Procedures for Topology 1 | Huawei |
| R3-244105 | (TP for TR 38.769) Signalling and Procedures for Topology 2 | Huawei |
| R3-244158 | RAN-CN interface impact on ambient IoT | NEC |
| R3-244184 | (TP to TR 38.769) Network signalling aspects for Topology 1 | CATT |
| R3-244185 | (TP to TR 38.769) Network signalling aspects for Topology 2 | CATT |
| R3-244192 | (TP for TR 38.769) AIoT interface impacts between RAN and CN | Xiaomi |
| R3-244328 | Inventory procedure of ambient IoT | Lenovo |
| R3-244329 | Context Management and Data Transport of Ambient IOT | Lenovo |
| R3-244389 | [TP for TR 38.769] Elements for AIoT RAN – AIoT CN communication and overall signalling | Ericsson |
| R3-244421 | Inventory Signalling Reusing Paging procedures for AIoT Topology 2 | Nokia |
| R3-244422 | [TP for TR 38.769] Inventory Signalling reusing Paging procedures for AIoT Topology 2 | Nokia |
| R3-244423 | [TP for TR 38.769] Data Transport and Context Management for AIoT | Nokia |
| R3-244428 | Inventory, Command and device context management for Ambient IoT | Qualcomm Incorporated |
| R3-244556 | Discussion on RAN-CN interface impact for Ambient IoT | Samsung |
| R3-244564 | Discussion on RAN-CN interface for Ambient IoT | China Telecom |
| R3-244594 | Discussion on paging for Ambient IoT | CMCC |
| R3-244595 | Discussion on Device Context Management and Data Transfer | CMCC |
| R3-244607 | Discussion on NG impact for Ambient IoT | LG Electronics |
| R3-244703 | CB:#AIoT2_CNRANSignalling | ZTE |
| R3-244792 | (TP for TR38.769) NG interface impact for Ambient-IoT | ZTE Corporation |
| R3-244812 | (TP for TR38.769) NG interface impact for Ambient-IoT | ZTE Corporation |
| R3-244838 | (TP for TR38.769) NG interface impact for Ambient-IoT | ZTE Corporation, Xiaomi |
| TDoc | Title | Source |
|---|---|---|
| R3-244061 | (TP for TR38.769) Locating an AIoT device | ZTE Corporation |
| R3-244103 | (TP for TR 38.769) Ambient IoT device locating | Huawei |
| R3-244159 | Further discussion on ambient IoT locating | NEC |
| R3-244186 | (TP to TR 38.879) Locating of A-IoT device | CATT |
| R3-244193 | (TP for TR 38.769) Locating AIoT device | Xiaomi |
| R3-244390 | [TP for TR 38.769] On locating AIoT devices | Ericsson |
| R3-244429 | Methods for locating Ambient IoT devices | Qualcomm Incorporated |
| R3-244596 | Discussion on locating Ambient IoT device | CMCC |
| R3-244705 | CB:#AIoT_Location | CMCC |
| R3-244811 | (TP for TR38.769) Locating Ambient-IoT device | CMCC |
| R3-244840 | (TP for TR 38.769) Locating Ambient-IoT device | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-244347 | WI Work plan for R19 Network Energy Savings | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-244106 | (TP for TS 38.473) Discussion on on-demand SSB SCell operation | Huawei |
| R3-244169 | Support on-demand SSB operation | NEC |
| R3-244214 | Discussion on on-demand SSB SCell operation in low-carbon green network | Samsung |
| R3-244237 | On support on-demand SSB SCell operation | CATT |
| R3-244330 | Discussion on On-demand SSB for SCell | Lenovo |
| R3-244348 | On-demand SSB SCell operation | Ericsson |
| R3-244380 | On-Demand SSB SCell operation for UEs in connected mode | Nokia |
| R3-244465 | Further discussion on on-demand SSB Scell operation | ZTE Corporation |
| R3-244576 | (TP for TS 38.473) Discussion on On-Demand SSB SCell Operation | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-244107 | Discussion on on-demand SIB1 for UEs in idle or inactive mode | Huawei |
| R3-244146 | Aspects of on-demand SIB1 for NES enhancements | Qualcomm Inc. |
| R3-244170 | Support on-demand SIB1 | NEC |
| R3-244215 | Discussion on on-demand SIB1 in low-carbon green network | Samsung |
| R3-244238 | On support on-demand SIB1 for idle UE | CATT |
| R3-244331 | Discussion on On-demand SIB1 for Idle/Inactive UE | Lenovo |
| R3-244349 | On-demand SIB1 transmission | Ericsson |
| R3-244381 | Open Issues in support of On-Demand SIB1 | Nokia |
| R3-244466 | Further discussion on on-demand SIB1 | ZTE Corporation |
| R3-244577 | Support On-Demand SIB1 for UEs | CMCC |
| R3-244633 | Discussion on OD-SIB1 | Rakuten Mobile, Inc |
| R3-244645 | Response to R3-244107 | Jio |
| R3-244708 | CB:#NES_OnDemandSIB1 | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-244069 | Work plan for Rel-19 WI on LP-WUSWUR | vivo |
| TDoc | Title | Source |
|---|---|---|
| R3-244070 | Discussion on signaling design for LP-WUS subgrouping | vivo, NTT DOCOMO INC. |
| R3-244076 | (TP for TS 38.413 and TS 38.423) Discussion on Low-power wake-up signal and receiver for NR | Huawei |
| R3-244077 | Introduction of low-power wake-up signal and receiver for NR | Huawei |
| R3-244095 | (TP to TS 38.413, 38.473, 38.423) Discussion on LP-WUS subgrouping | ZTE Corporation |
| R3-244096 | [draft] LS on LP-WUS subgrouping | ZTE Corporation |
| R3-244147 | Support LP-WUS subgrouping | Qualcomm Inc. |
| R3-244199 | Initial discussion on LP-WUS subgrouping | NTT DOCOMO INC.. |
| R3-244409 | Discussion of LPWUS impacts on NG-RAN architecture | Ericsson |
| R3-244410 | Introduction of LP-WUS paging monitoring | Ericsson |
| R3-244424 | Overview of RAN3 impacts of LP-WUS | Nokia |
| R3-244425 | Support of LP-WUS | Nokia |
| R3-244513 | Discussion on potential RAN3 impacts of LP-WUS | CATT |
| R3-244514 | (TP on BLCR for TS 38.300)Support of LP-WUS | CATT |
| R3-244605 | Discussion on LP-WUS subgrouping | Samsung |
| R3-244606 | (TP to BLCR for TS 38.413, 38.423, 38.473) LP-WUS Assistance Information to support subgrouping | Samsung |
| R3-244611 | Discussion on support LP-WUS indicating paging monitoring | CMCC |
| R3-244626 | BLCR for TS 38.300 on support of LP-WUS | vivo |
| TDoc | Title | Source |
|---|---|---|
| R3-244008 | Reply LS to SA2 on FS_XRM PH2 | RAN2(Vivo) |
| R3-244009 | Reply LS on Application-Layer FEC Awareness at RAN | RAN2(Qualcomm) |
| R3-244010 | LS on multi-modality awareness at RAN | RAN2(Nokia) |
| R3-244020 | LS on FS_XRM Ph2 | SA2(Vivo) |
| R3-244024 | LS Reply to SA2 LS on Application-Layer FEC Awareness at RAN | SA4(Qualcomm) |
| R3-244025 | LS Reply on FS_XRM Ph2 | SA4(Huawei) |
| R3-244032 | (BL CR to 37.340) Support of XR enhancements | ZTE Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Inc, Lenovo, Huawei, Ericsson, CATT, CMCC, Samsung, Xiaomi, NEC |
| R3-244033 | Support of XR enhancements | CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC, NEC |
| R3-244045 | LS on FS_XRM Ph2 | SA2(Vivo) |
| R3-244068 | Discussion on LS from SA2 on LS on FS_XRM Ph2 | vivo |
| R3-244153 | proposed reply to SA2 LS | NEC |
| R3-244332 | Discussion on LS on FS_XRM Ph2 | Lenovo |
| R3-244340 | Work Plan for Rel-19 on XR Enhancements for NR | Nokia, Qualcomm (Rapporteurs) |
| R3-244411 | Discussion on SA2 LS questions to RAN3 | Ericsson |
| R3-244469 | Discussion on SA2 LS with draft reply LS | ZTE Corporation, China Telecom |
| R3-244580 | Discussion on SA2’s LS (S2-2407351) on FS_XRM Ph2 | CMCC |
| R3-244715 | Reply LS on FS_XRM Ph2 | RAN3(ZTE) |
| R3-244839 | Response LS to SA2 on FS_XRM Ph2 | RAN3(ZTE) |
| R3-244844 | Response LS to SA2 on FS_XRM Ph2 | RAN3(ZTE) |
| R3-244857 | (BL CR to 37.340) Support of XR enhancements | ZTE Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Inc, Lenovo, Huawei, Ericsson, CATT, CMCC, Samsung, Xiaomi, NEC |
| R3-244858 | (BL CR to 38.423) Support of XR enhancements | CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC, NEC |
| TDoc | Title | Source |
|---|---|---|
| R3-244082 | R19 XR DC Remaining Signaling Enhancements | Qualcomm Incorporated |
| R3-244109 | Support of XR enhancements | Nokia, Nokia Shanghai Bell, Lenovo, Qualcomm, Xiaomi, CATT, Ericsson, CMCC, Samsung |
| R3-244268 | Discussion on XR in DC | CATT |
| R3-244301 | Support for L4S in NR-NR DC | Ericsson, AT&T, BT, T-Mobile USA, Charter Communications, Qualcomm |
| R3-244333 | (TP for 38.340 BLR) Corrections on XR in NR-DC | Lenovo |
| R3-244341 | (TP to BL CR for TS 37.340) Discussion on the support of XR in NR-NR DC | Nokia, Nokia Shanghai Bell |
| R3-244470 | Further discussion on XR supporting | ZTE Corporation, China Telecom, China Unicom |
| R3-244471 | TP to BLCR for 37.340 and 38.423 on XR supporting | ZTE Corporation, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-244531 | (TP for NR_XR_Ph3 BL CR) Discussion on NR-DC support of XR and SA2's LS | Huawei |
| R3-244546 | (TP to TS 38.423) Support XR in DC | Samsung |
| R3-244578 | (TP to TS 38.423 and 37.340) PDU Set Based Handling Support in DC | CMCC, Lenovo, Qualcomm, Xiaomi, China Unicom |
| R3-244579 | Further Discussion on XR Support in DC | CMCC, Lenovo, Xiaomi |
| R3-244706 | CB:#XR2_NRDC | Nokia |
| R3-244750 | XR enhancements for NR-NR DC | Ericsson, AT&T, BT, T-Mobile USA, Charter Communications, Qualcomm, Huawei, Nokia, Nokia Shanghai Bell,China Telecom, CMCC |
| R3-244760 | (TP for 38.423 BLCR) PDU Set Based Handling Support in NR-DC | Lenovo, Nokia, Nokia Shanghai Bell, CMCC, Huawei |
| R3-244762 | (TP to BL CR for TS 38.423) PSI Based SDU Discard DL | CMCC, Huawei, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, China Telecom, Xiaomi |
| R3-244767 | (BL CR to 38.473) Support for DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi, Nokia, Nokia Shanghai Bell,China Telecom |
| R3-244768 | (TP for TS 38.425) Support for DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi, Nokia, Nokia Shanghai Bell, China Telecom |
| R3-244769 | Support of XR enhancements | Nokia, Nokia Shanghai Bell, Lenovo, Qualcomm, Xiaomi, CATT, Ericsson, CMCC, Samsung |
| R3-244770 | (TP to BL CR for TS 37.340) Update on XR in DC | ZTE Corporation, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-244771 | (TP to BL CR for TS 38.423) Update on ECN marking in DC | CATT, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CMCC |
| R3-244845 | (BL CR to 38.300) Support of XR enhancements | Nokia, Nokia Shanghai Bell, Lenovo, Qualcomm, Xiaomi, CATT, Ericsson, CMCC, Samsung, Huawei |
| R3-244846 | (TP to BL CR for TS 37.340) Update on XR in DC | ZTE Corporation, China Telecom, Nokia, Nokia Shanghai Bell, Huawei, CATT, Ericsson, Samsung, Lenovo, CMCC |
| R3-244847 | (BL CR to 38.425) XR enhancements for NR-NR DC | Ericsson, AT&T, BT, T-Mobile USA, Charter Communications, Qualcomm, Huawei, Nokia, Nokia Shanghai Bell,China Telecom, CMCC, ZTE, CATT |
| R3-244859 | (BL CR to 38.425) XR enhancements for NR-NR DC | Ericsson, AT&T, BT, T-Mobile USA, Charter Communications, Qualcomm, Huawei, Nokia, Nokia Shanghai Bell,China Telecom, CMCC, ZTE, CATT |
| TDoc | Title | Source |
|---|---|---|
| R3-244161 | Input to 3GPP AI/ML Consistency Alignment SI | NEC |
| R3-244861 | RAN3 Social Event | Chair |