Tdoc List
2026-02-09 10:35
| Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Opening of the meeting |   | ||||||||||
| 2 | Reminders |   | ||||||||||
| 2.1 | IPR Declaration |   | ||||||||||
| 2.2 | Statement of Antitrust Compliance |   | ||||||||||
| 2.3 | Consensus Principles |   | ||||||||||
| 2.4 | Responsible IT Behavior |   | ||||||||||
| 2.5 | Additional reminders |   | ||||||||||
| 3 | Approval of the Agenda | R3‑260001 | RAN3#131 Meeting Agenda | RAN3 Chair | agenda | Approval | Yes |
Yes
| approved | No | ||
| 4 | Approval of the minutes from previous meetings | R3‑260002 | RAN3#130 Meeting Report | ETSI-MCC | report | Approval | Yes |
Yes
| approved | No | ||
| 5 | Documents for immediate consideration |   | ||||||||||
| 6 | Organizational topics |   | ||||||||||
| 7 | General, protocol principles and issues | R3‑260115 | TR 30.531 v1.62.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC | draft TR | Endorsement | Yes |
Yes
| revised | No | R3‑260642 | R3‑260003 |
| R3‑260642 | TR 30.531 v1.62.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC | draft TR | Endorsement | No |
Yes
| endorsed | No | R3‑260115 | |||
| R3‑260003 | TR 30.531 v1.62.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC | draft TR | Endorsement | No |
Yes
| withdrawn | Yes | R3‑260115 | |||
| 8 | Incoming LSs |   | ||||||||||
| 8.1 | New Incoming LSs | R3‑260012 | LS on support for Alternative QoS Profile for network energy saving | SA2(VIVO) | LS in | Discussion | Yes |
Yes
| noted | No | ||
| R3‑260073 | Discussion on support for Alternative QoS Profile for network energy saving | Huawei | discussion | Yes |
Yes
| noted | No | |||||
| R3‑260074 | [draft] Reply LS on support for Alternative QoS Profile for network energy saving | Huawei | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260146 | Discussion on support for Alternative QoS Profile for network energy saving | ZTE Corporation | discussion | Discussion | Yes |
Yes
| noted | No | ||||
| R3‑260147 | [Draft] Reply LS on support for Alternative QoS Profile for network energy saving | ZTE Corporation | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260496 | Discussion on LS on support for Alternative QoS Profile for network energy saving | Nokia | discussion | Yes |
Yes
| noted | No | |||||
| R3‑260497 | [Draft] Reply LS on support for Alternative QoS Profile for network energy saving | Nokia | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260571 | Discussion on support for Alternative QoS Profile for network energy saving | Ericsson | discussion | Yes |
Yes
| noted | No | |||||
| R3‑260572 | [Draft] Reply LS on support for Alternative QoS Profile for network energy saving | Ericsson | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260583 | Alternative QoS Profile for network energy saving | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260597 | Discussion on AQP for network energy saving | Samsung | discussion | Agreement | Yes |
Yes
| noted | No | ||||
| R3‑260598 | [Draft] Reply LS on AQP for network energy saving | Samsung | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260015 | LS on NR to LTE mobility restriction | SA2(DOCOMO) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
| R3‑260165 | Enhancement of NR to LTE mobility restriction | NTT DOCOMO INC., Nokia | discussion | Yes |
Yes
| noted | No | |||||
| R3‑260166 | Enhancement of NR to LTE mobility restriction [Enhanced Mobility] | NTTDOCOMO, INC., Nokia, ZTE | CR | Agreement | Yes |
Yes
| revised | No | R3‑260643 | |||
| R3‑260643 | Enhancement of NR to LTE mobility restriction [Enhanced Mobility] | NTTDOCOMO, INC., Nokia, ZTE | CR | Agreement | No |
No
| reserved | No | R3‑260166 | |||
| R3‑260213 | Enhancement of NR to LTE mobility restriction [Enhanced Mobility] | Nokia, NTTDOCOMO, INC. | CR | Agreement | Yes |
Yes
| revised | No | R3‑260644 | |||
| R3‑260644 | Enhancement of NR to LTE mobility restriction [Enhanced Mobility] | Nokia, NTTDOCOMO, INC. | CR | Agreement | No |
No
| reserved | No | R3‑260213 | |||
| R3‑260231 | Discussion on NR to LTE mobility restriction | Huawei | discussion | Yes |
Yes
| noted | No | |||||
| R3‑260232 | Inclusion of Forbidden EPS Areas in mobility restriction for NR to LTE mobility [NR_To_LTE_Mobility] | Huawei | CR | Agreement | Yes |
Yes
| noted | No | ||||
| R3‑260233 | Inclusion of Forbidden EPS Areas in mobility restriction for NR to LTE mobility [NR_To_LTE_Mobility] | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260304 | Enhancement of NR to LTE mobility restriction | ZTE Corporation, NTT DOCOMO | draftCR | Endorsement | Yes |
Yes
| noted | No | ||||
| R3‑260305 | [draft] Reply LS on NR to LTE mobility restriction | ZTE Corporation | other | Approval | Yes |
No
| available | No | ||||
| R3‑260414 | Forbidden EPS Areas for NR to LTE mobility | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260415 | [DRAFT] Reply LS on NR to LTE mobility restriction | Ericsson | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260488 | Consequence of the NR to LTE mobility restriction | Nokia | discussion | Yes |
No
| available | No | |||||
| R3‑260489 | Enhancement of LTE to NR mobility restriction | Nokia | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260540 | Correction on Forbiden Area for EPS | CMCC | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260019 | Reply to LS on temporary suspension of trace production | SA5(Ericsson) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
| R3‑260423 | Discussion on the temporary suspension of Trace | Ericsson | discussion | Approval | Yes |
Yes
| noted | No | ||||
| R3‑260424 | Reply LS on temporary suspension of trace production | Ericsson | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260056 | Discussion on temporary suspension of trace production | ZTE Corporation | discussion | Yes |
Yes
| noted | No | |||||
| R3‑260639 | Response to R3-260056 | Huawei | response | Discussion | Yes |
Yes
| noted | No | ||||
| R3‑260286 | Temporary Suspension Trace-Opt1-37320 | ZTE Corporation | other | Agreement | Yes |
Yes
| noted | No | ||||
| R3‑260287 | Temporary Suspension Trace-Opt2-38413 | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260288 | Temporary Suspension Trace-Opt2-38423 | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260289 | Temporary Suspension Trace-Opt2-38473 | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260290 | Temporary Suspension Trace-Opt2-37483 | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260499 | Discussion on temporary suspension of trace production | Nokia | discussion | Yes |
Yes
| noted | No | |||||
| R3‑260022 | LS on MWAB-gNB Configurations | SA5(ZTE) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260023 | LS on MWAB-gNB configuration to support Xn connection management | SA5(Huawei) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260271 | Discussion on WAB configuration for Xn management | Huawei | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260272 | [Draft] Reply LS on WAB-gNB configuration of Xn connection management | Huawei | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260273 | Correction on Xn management configuration for WAB-gNB | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260476 | Discussion of the SA5 LS on MWAB-gNB configuration to support Xn connection management | Ericsson | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260594 | [Draft] Reply LS on MWAB-gNB configuration to support Xn connection management | Samsung | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260301 | Discussion on the two LS for WAB from SA5 | ZTE Corporation | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260302 | [draft] Reply LS on MWAB-gNB Configurations | ZTE Corporation | other | Approval | Yes |
No
| available | No | ||||
| R3‑260303 | Corrections on BH PDU ssession for WAB | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260274 | Discussion on WAB-gNB configurations regarding R3-260022 | Huawei | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260275 | [Draft] Reply LS on WAB-gNB configurations | Huawei | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260477 | Discussion of the SA5 LS on LS on MWAB-gNB Configurations | Ericsson | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260595 | Discussion on MWAB-gNB configurations | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260596 | [Draft] Reply LS on MWAB-gNB configurations | Samsung | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260279 | Discussion on the WAB configuration | Nokia | discussion | Yes |
No
| available | No | |||||
| R3‑260362 | Discussion on WAB-gNB configurations | CATT | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260363 | [Draft]Reply LS on MWAB-gNB configurations | CATT | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260364 | [Draft]Reply LS on MWAB-gNB configurations to support Xn connection management | CATT | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260582 | Corrections on Xn connection management for WAB | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260025 | LS on completion of Study on AI/ML consistency alignment | TSG SA(Magenta) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260350 | Discussion on AI/ML consistency alignment | ZTE Corporation | discussion | Yes |
No
| available | No | |||||
| R3‑260351 | Consistency and Alignment of AI/ML Terminology | ZTE Corporation | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260352 | Consistency and Alignment of AI/ML Terminology | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260353 | [Draft] Reply LS on completion of Study on AI/ML consistency alignment | ZTE Corporation | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260396 | Discussion on the LS on completion of Study on AI/ML consistency alignment from SA | Huawei | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260397 | [DRAFT] Reply LS on completion of Study on AI/ML consistency alignment from SA | Huawei | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260422 | Discussion on new definitions from the study on AI/ML consistency alignment | Ericsson | discussion | Approval | Yes |
No
| available | No | ||||
| R3‑260438 | Discussion on LS on completion of study on AI/ML consistency alignment | Nokia | discussion | Yes |
No
| available | No | |||||
| R3‑260008 | Reply LS on Rel-19 higher layers parameters list Post RAN1#122bis | RAN2(Ericsson) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260013 | LS Response on IETF Network Slice Application in 3GPP 5G End-to-End Network Slice | SA2(ZTE) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260020 | LS reply to IETF Network Slice Application in 3GPP 5G End-to-End Network Slice | SA5(Ericsson) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260285 | Discussion on temporary suspension of trace production | ZTE Corporation | discussion | No |
Yes
| withdrawn | Yes | |||||
| 8.2 | LSin received during the meeting |   | ||||||||||
| 8.3 | Left over LSs / pending actions |   | ||||||||||
| 9 | Corrections to Rel-19 or earlier releases |   | ||||||||||
| 9.1 | LTE | R3‑260150 | Correction on Coarse UE Location Reporting for NB-IoT UEs | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||
| R3‑260151 | Correction on Coarse UE Location Reporting for NB-IoT UEs | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
| 9.2 | NR |   | ||||||||||
| 9.2.1 | Rel-18 or earlier releases | R3‑260005 | Reply LS on removal of support of PWS over satellite NG-RAN in Rel-17 and 18 | TSG CT(Qualcomm) | LS in | Discussion | Yes |
No
| available | No | ||
| R3‑260055 | Discussion on R17 and R18 PWS for NTN feature removal alignment among RAN, CT and SA | ZTE Corporation, China Telecom, Pengcheng Laboratory | discussion | Yes |
No
| available | No | |||||
| R3‑260080 | Discussion on PWS Support for IoT NTN | Qualcomm Incorporated | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260240 | Discussion on support of PWS in NTN | CATT | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260509 | Discussion on removal of PWS support for NR NTN and IoT NTN in Rel-17 and 18 | Huawei, Thales, China Unicom | discussion | Yes |
No
| available | No | |||||
| R3‑260510 | [draft] Reply LS on removal of PWS support for NR NTN and IoT NTN in Rel-17 and 18 | Huawei | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260148 | Correction on support of PWS over IoT NTN | ZTE Corporation, China Telecom, Pengcheng Laboratory | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260149 | Correction on support of PWS over IoT NTN | ZTE Corporation, China Telecom, Pengcheng Laboratory | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260511 | Correction of mapped cell for PWS over IoT NTN | Huawei, Thales, China Unicom | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260512 | Correction of mapped cell for PWS over IoT NTN | Huawei, Thales, China Unicom | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260051 | Correction of time-based handover for NR NTN | Huawei, Jio Platforms, CATT, Ericsson, Nokia, LG Electronics, Deutsche Telekom, Samsung, Thales | draftCR | Endorsement | Yes |
No
| available | No | R3‑258220 | |||
| R3‑260052 | Correction of time-based handover for NR NTN | Huawei, Jio Platforms, CATT, Ericsson, Nokia, LG Electronics, Deutsche Telekom, Samsung, Thales | draftCR | Endorsement | Yes |
No
| available | No | R3‑258221 | |||
| R3‑260262 | Correction on prioritized alternative QoS profile | Huawei, ZTE, Ericsson, Nokia, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258276 | |||
| R3‑260263 | Correction on prioritized alternative QoS profile | Huawei, ZTE, Ericsson, Nokia, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258277 | |||
| R3‑260264 | Correction on prioritized alternative QoS profile | Huawei, ZTE, Ericsson, Nokia, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258278 | |||
| R3‑260265 | Correction on prioritized alternative QoS profile | Huawei, ZTE, Ericsson, Nokia, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258279 | |||
| R3‑260266 | Correction on QoS parameters for QoS Notification Control | Huawei, Nokia, China Telecom, CMCC, Ericsson, Qualcomm, CATT, Samsung, ZTE, Ofinno | draftCR | Endorsement | Yes |
No
| available | No | R3‑258333 | |||
| R3‑260267 | Correction on QoS parameters for QoS Notification Control | Huawei, Nokia, China Telecom, CMCC, Ericsson, Qualcomm, CATT, Samsung, ZTE, Ofinno | draftCR | Endorsement | Yes |
No
| available | No | R3‑258334 | |||
| R3‑260280 | Correction on Notification Control Indication | Nokia, Huawei, CMCC, China Telecom, Ericsson, Qualcomm, CATT, Samsung, ZTE, Ofinno | CR | Agreement | Yes |
No
| available | No | R3‑258202 | |||
| R3‑260281 | Correction on Notification Control Indication | Nokia, Huawei, CMCC, China Telecom, Ericsson, Qualcomm, CATT, Samsung, ZTE, Ofinno | CR | Agreement | Yes |
No
| available | No | R3‑258203 | |||
| R3‑260344 | UE Context Retention in NG-RAN | Ericsson, Huawei, Jio Platforms, Thales, Nokia, Airbus, Verizon, Deutsche Telekom, AT&T, Samsung, China Unicom, Telecom Italia | discussion | Discussion | Yes |
No
| available | No | R3‑258464 | |||
| R3‑260345 | UE Context Retention for NG - Stage 2 | Ericsson, Huawei, Jio Platforms, Thales, Nokia, Airbus, Verizon, Deutsche Telekom, AT&T, Samsung, China Unicom, Telecom Italia | draftCR | Endorsement | Yes |
No
| available | No | R3‑258465 | |||
| R3‑260346 | UE Context Retention for NG - Stage 2 | Ericsson, Huawei, Jio Platforms, Thales, Nokia, Airbus, Verizon, Deutsche Telekom, AT&T, Samsung, China Unicom, Telecom Italia | draftCR | Endorsement | Yes |
No
| available | No | R3‑258470 | |||
| R3‑260441 | Addition of 2Rx XR UE Capability | Ericsson, Qualcomm inc. Nokia, Nokia Shanghai Bell, ZTE | CR | Agreement | Yes |
No
| available | No | R3‑258530 | |||
| R3‑260442 | Addition of 2Rx XR UE Capability | Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, ZTE | CR | Agreement | Yes |
No
| available | No | R3‑258531 | |||
| R3‑260561 | Discussion on prioritized alternative QoS profile list | ZTE Corporation, Nokia, Ericsson, Huawei, Samsung | discussion | Information | Yes |
No
| available | No | ||||
| R3‑260557 | Correction on prioritized alternative QoS profile | ZTE Corporation, Nokia, Ericsson, Huawei, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258163 | |||
| R3‑260558 | Correction on prioritized alternative QoS profile | ZTE Corporation, Nokia, Ericsson, Huawei, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258164 | |||
| R3‑260559 | Correction on prioritized alternative QoS profile | ZTE Corporation, Nokia, Ericsson, Huawei, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258165 | |||
| R3‑260560 | Correction on prioritized alternative QoS profile | ZTE Corporation, Nokia, Ericsson, Huawei, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258166 | |||
| R3‑260443 | Correction on prioritized alternative QoS profile | Ericsson, ZTE Corporation, Huawei, Nokia, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258222 | |||
| R3‑260444 | Correction on prioritized alternative QoS profile | Ericsson, ZTE Corporation, Huawei, Nokia, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258223 | |||
| R3‑260445 | Correction on prioritized alternative QoS profile | Ericsson, ZTE Corporation, Huawei, Nokia, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258224 | |||
| R3‑260446 | Correction on prioritized alternative QoS profile | Ericsson, ZTE Corporation, Huawei, Nokia, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258225 | |||
| R3‑260209 | Correction on prioritized alternative QoS profile | Nokia, Ericsson, ZTE Corporation, Huawei, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258227 | |||
| R3‑260210 | Correction on prioritized alternative QoS profile | Nokia, Ericsson, ZTE Corporation, Huawei, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258228 | |||
| R3‑260211 | Correction on prioritized alternative QoS profile | Nokia, Ericsson, ZTE Corporation, Huawei, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258230 | |||
| R3‑260212 | Correction on prioritized alternative QoS profile | Nokia, Ericsson, ZTE Corporation, Huawei, Samsung | CR | Agreement | Yes |
No
| available | No | R3‑258231 | |||
| R3‑260085 | Beam measurement report quantity | Huawei, Ericsson, Nokia, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260086 | Beam measurement report quantity | Huawei, Ericsson, Nokia, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260087 | Beam measurement report quantity | Huawei, Ericsson, Nokia, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260202 | Beam measurement report quantity | Ericsson, Jio Platforms, Huawei, Nokia, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260204 | Beam measurement report quantity | Ericsson, Jio Platforms, Huawei, Nokia, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260205 | Beam measurement report quantity | Ericsson, Jio Platforms, Huawei, Nokia, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260214 | Correction of QMC Coordination Request | Ericsson, Qualcomm, Jio Platforms, Samsung, ZTE, Huawei, Nokia, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260215 | Correction of QMC Coordination Request | Ericsson, Qualcomm, Jio Platforms, Samsung, ZTE, Huawei, Nokia, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260081 | Correction on UHI | ZTE Corporation,China Telecom, Pengcheng Laboratory | CR | Agreement | Yes |
No
| available | No | R3‑258676 | |||
| R3‑260082 | Correction on UHI | ZTE Corporation,China Telecom, Pengcheng Laboratory | CR | Agreement | Yes |
No
| available | No | R3‑258677 | |||
| R3‑260167 | Discussion on TNLA handling during Xn handover | NTT DOCOMO INC.. | discussion | Yes |
No
| available | No | |||||
| R3‑260168 | Clarification on TNLA handling during Xn handover | NTT DOCOMO | CR | Agreement | Yes |
No
| available | No | R3‑258408 | |||
| R3‑260169 | Clarification on TNLA handling during Xn handover | NTT DOCOMO | CR | Agreement | Yes |
No
| available | No | R3‑258411 | |||
| R3‑260170 | Clarification on TNLA handling during Xn handover | NTT DOCOMO | CR | Agreement | Yes |
No
| available | No | R3‑258413 | |||
| R3‑260171 | Clarification on TNLA handling during Xn handover | NTT DOCOMO | CR | Agreement | Yes |
No
| available | No | R3‑258414 | |||
| R3‑260365 | Correction on the Extended UE Identity Index Value | CATT, ZTE, China Telecomm | draftCR | Endorsement | Yes |
No
| available | No | R3‑258308 | |||
| R3‑260366 | Correction on the Extended UE Identity Index Value | CATT, ZTE, China Telecomm | draftCR | Endorsement | Yes |
No
| available | No | R3‑258307 | |||
| R3‑260432 | LTM Resource consumption for the target cells | Sony, Ericsson, vivo, Jio Platforms, LG Electronics, Qualcomm | discussion | Yes |
No
| available | No | |||||
| R3‑260433 | Correction for Cell Switch execution | Sony, Ericsson, vivo, Jio Platforms, LG Electronics, Qualcomm | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260498 | Correction for Cell Switch execution | Ericsson, Sony, Jio Platforms, LG Electronics, vivo, Qualcomm | CR | Agreement | Yes |
No
| available | No | R3‑258562 | |||
| R3‑260450 | Correction for Cell Switch execution | Ericsson, Sony, Jio Platforms, LG Electronics, vivo, Qualcomm | CR | Agreement | Yes |
No
| available | No | R3‑258563 | |||
| R3‑260059 | Corrections on Ephemeris orbital parameters and epoch time provided by O&M for NR NTN | Thales, Apple, Iridium, CATT, Airbus, ESA | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260060 | Corrections on Ephemeris orbital parameters and epoch time provided by O&M for NR NTN | Thales, Apple, Iridium, CATT, Airbus, ESA | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260061 | Corrections on Ephemeris orbital parameters and epoch time provided by O&M for NR TN | Thales, Apple, Iridium, CATT, Airbus, ESA | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260095 | Correction on procedural text for Coverage and Capacity Optimization | ZTE Corporation, Jio Platforms, CMCC, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260096 | Correction on procedural text for Coverage and Capacity Optimization | ZTE Corporation, Jio Platforms, CMCC, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260097 | Correction on procedural text for Coverage and Capacity Optimization | ZTE Corporation, Jio Platforms, CMCC, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260098 | Correction on load measurement function | ZTE Corporation, Jio Platforms, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260099 | Correction on load measurement function | ZTE Corporation, Jio Platforms, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260100 | Correction on load measurement function | ZTE Corporation, Jio Platforms, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260196 | Discussion on SRS Tx Frequency Hopping Configuration | ZTE Corporation, Samsung, CATT | discussion | Yes |
No
| available | No | |||||
| R3‑260197 | Correction to BWP configuration for SRS frequency hopping (Option-1) | ZTE Corporation, Samsung, CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260198 | Correction to BWP configuration for SRS frequency hopping (Option-1) | ZTE Corporation, Samsung, CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260199 | Correction to BWP configuration for SRS frequency hopping (Option-2) | ZTE Corporation, Samsung, CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260200 | Correction to BWP configuration for SRS frequency hopping (Option-2) | ZTE Corporation, Samsung, CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260238 | Correction to BWP configuration for SRS frequency hopping | CATT, Samsung, ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260239 | Correction to BWP configuration for SRS frequency hopping | CATT, Samsung, ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260255 | Correction to BWP configuration for SRS frequency hopping | Samsung, ZTE Corporation, CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260256 | Correction to BWP configuration for SRS frequency hopping | Samsung, ZTE Corporation, CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260379 | Corrections on Source M-NG-RAN node UE XnAP ID IE transfer for CHO in DC | CATT,Huawei, China Telecom, ZTE Corporation,CMCC | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260408 | SRB ID correction | Ericsson, Jio Platforms, Nokia | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260409 | SRB ID correction | Ericsson, Jio Platforms, Nokia | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260429 | Correction on CCO Assistance Information over F1 | ZTE Corporation, China Telecom, China Unicom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260430 | Correction on CCO Assistance Information over F1 | ZTE Corporation, China Telecom, China Unicom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260431 | Correction on CCO Assistance Information over F1 | ZTE Corporation, China Telecom, China Unicom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260492 | Introduction of IAB-related Definitions | Ericsson, Qualcomm, CATT, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260493 | Introduction of IAB-related Definitions | Ericsson, Qualcomm, CATT, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260578 | Correction on the Extended UE Identity Index Value | ZTE Corporation, CATT, China Telecom | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260579 | Correction on the Extended UE Identity Index Value | ZTE Corporation, CATT, China Telecom | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260580 | Corrections on L2 reset for inter-DU LTM | ZTE Corporation, Pengcheng Laboratory | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260581 | Corrections on L2 reset for inter-DU LTM | ZTE Corporation, Pengcheng Laboratory | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260603 | Correction on SSB Time and Frequency Configuration for Positioning | China Telecom, China Unicom,CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260604 | Correction on SSB Time and Frequency Configuration for Positioning | China Telecom, China Unicom,CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260605 | Correction on SSB Time and Frequency Configuration for Positioning | China Telecom, China Unicom,CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260607 | Correction on SSB Time and Frequency Configuration for Positioning | China Telecom, China Unicom,CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260608 | Correction on SSB Time and Frequency Configuration for Positioning | China Telecom, China Unicom,CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260610 | Correction on SSB Time and Frequency Configuration for Positioning | China Telecom, China Unicom,CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260614 | Correction on SSB Time and Frequency Configuration for Positioning | China Telecom, China Unicom,CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260615 | Correction on SSB Time and Frequency Configuration for Positioning | China Telecom, China Unicom,CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260616 | Correction on SSB configuration in UL-TDOA positioning | China Telecom,CATT, China Unicom | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260617 | Correction on SSB configuration in UL-TDOA positioning | China Telecom,CATT, China Unicom | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260622 | Correction on SSB configuration in UL-TDOA positioning | China Telecom, CATT, China Unicom | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260623 | Correction on SSB configuration in UL-TDOA positioning | China Telecom, CATT, China Unicom | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260241 | Reply LS on removal of support of PWS for NR NTN and IoT NTN in Rel-17 and 18 | CATT | LS out | Approval | Yes |
Yes
| withdrawn | Yes | ||||
| R3‑260449 | Correction for Cell Switch execution | Ericsson, Sony, Jio Platforms, LG Electronics, vivo, Qualcomm | CR | Agreement | No |
Yes
| withdrawn | Yes | R3‑257028 | |||
| R3‑260478 | Introduction of IAB-related Definitions | Ericsson, Qualcomm, CATT | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
| R3‑260479 | Introduction of IAB-related Definitions | Ericsson, Qualcomm, CATT | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
| 9.2.2 | Rel-19 Mobility enhancements | R3‑260009 | LS on support of LTM modification | RAN2(Ericsson) | LS in | Discussion | Yes |
No
| available | No | ||
| R3‑260455 | Support for modification of LTM configurations | Ericsson, Ofinno, Jio Platforms | discussion | Yes |
No
| available | No | |||||
| R3‑260456 | [DRAFT] Reply LS on support of LTM modification | Ericsson | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260457 | Support for modification of LTM configurations for Option 2 | Ericsson, Ofinno, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260458 | Support for modification of LTM configurations for Option 2 | Ericsson, Jio Platforms, Ofinno | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260459 | Support for modification of LTM configurations for Option 2 | Ericsson, Ofinno, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260460 | Support for modification of LTM configurations for Option 2 | Ericsson, Jio Platforms, Ofinno | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260618 | Support for modification of LTM configurations for Option 3 | Ericsson, Ofinno, Jio Platforms, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260619 | Support for modification of LTM configurations for Option 3 | Ericsson, Ofinno, Jio Platforms, Lenovo | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260620 | Support for modification of LTM configurations for Option 3 | Ericsson, Ofinno, Jio Platforms, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260621 | Support for modification of LTM configurations for Option 3 | Ericsson, Jio Platforms, Ofinno, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260520 | Discussion on candidate gNB initiated LTM modification | Huawei, Nokia, NEC, Lenovo, ZTE, CATT, China Telecom | discussion | Yes |
No
| available | No | |||||
| R3‑260521 | Candidate gNB initiated LTM modification | Huawei, Nokia, NEC, Lenovo, ZTE, CATT, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260377 | Candidate gNB-DU initiated LTM modification | CATT, Nokia, NEC, Lenovo, ZTE, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260576 | Support of LTM modification | ZTE Corporation, Huawei, Nokia, NEC, Lenovo, CATT | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260306 | Discussion on the LSin R3-258766 on the signaling design of SCG LTM related parameters | ZTE Corporation | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260307 | [draft]Reply LS on the signalling design of SCG LTM related parameters | ZTE Corporation | other | Approval | Yes |
No
| available | No | ||||
| R3‑260627 | Correction on TA Information Transfer inter-SN SCG LTM | Samsung, Huawei, Ericsson, Nokia, Google, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260628 | Correction on UE Based TA Measurement ID assignment for inter-CU (SCG) LTM | Samsung, ZTE, LG Electronics, Huawei, Nokia, Lenovo, Google, Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260383 | Discussion on handling UE based TA | CATT | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260116 | Exchange of early RACH Resources Requester ID for inter-CU LTM | Huawei, Nokia Samsung, Jio Platforms, CATT, CMCC, China Telecom, Lenovo | discussion | Yes |
No
| available | No | |||||
| R3‑260117 | Exchange of early RACH Resources Requester ID for inter-CU LTM | Huawei, Nokia, Samsung, Jio Platforms, CATT, CMCC, China Telecom, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260309 | Discussion on the early RACH resource requester ID transfer | ZTE Corporation, Qualcomm, Ericsson, Pengcheng Laboratory | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260310 | Early RACH Resource Requester ID | ZTE Corporation, Qualcomm, Ericsson, Pengcheng Laboratory | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260503 | Correction on IE presence for LTM L2 Reset Configuration List | LG Electronics, Nokia, Qualcomm, Google, Samsung, NEC, Ericsson, Ofinno, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260041 | LTM Cell Switch Type Indication | Nokia, LGE, Huawei | CR | Agreement | Yes |
No
| available | No | R3‑258471 | |||
| R3‑260042 | LTM Cell Switch Type Indication | Nokia, LGE, Huawei | CR | Agreement | Yes |
No
| available | No | R3‑258473 | |||
| R3‑260118 | Correction on Reference Configuration in LTM Configuration Update for inter-CU LTM | Huawei, Ofinno, Jio Platforms, CMCC, Lenovo, CATT, NEC, Samsung | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260119 | Interaction between Handover Success and Cell Switch Notification | Huawei, Nokia, LG Electronics, ZTE, Ofinno, Jio Platforms, CMCC | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260120 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM | Huawei, NEC,Jio Platforms, CMCC, China Telecom, Lenovo | discussion | Yes |
No
| available | No | |||||
| R3‑260121 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 1) | Huawei, NEC, Jio Platforms, CMCC, China Telecom, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260122 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 1) | Huawei, NEC, Jio Platforms, CMCC, China Telecom, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260123 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 2) | Huawei, NEC, Jio Platforms, CMCC, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260124 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 2) | Huawei, NEC, Jio Platforms, CMCC, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260125 | Correction on NG-RAN node UE XnAP IDs transfer after LTM failure | Huawei, Nokia, Offinno, Jio Platforms, CMCC. NEC | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260126 | UE context retrieval in the candidate gNB during subsequent LTM | Huawei, Nokia, Offinno, Jio Platforms, CMCC, Lenovo, NEC, Samsung | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260127 | Corrections on inter-CU MCG LTM without SN change | Huawei, Jio Platforms, Lenovo, Google, NEC | discussion | Yes |
No
| available | No | |||||
| R3‑260128 | Stage 2 corrections to inter-CU MCG LTM | Huawei, Jio Platforms, Lenovo, Google, NEC | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260129 | Correction on security key update for inter-CU MCG LTM | Huawei, Jio Platforms, China Telecom, Lenovo, Google, NEC | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260230 | [Draft TP for TS 38.473, TS 38.423] Remaining key open issues in Inter-CU LTM | Qualcomm Incorporated, Rakuten | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260297 | Correction to LTM MCG configuration management for inter-CU SCG LTM | Google, Huawei | CR | Agreement | Yes |
No
| available | No | R3‑258319 | |||
| R3‑260298 | Correction to timer issue for inter-SN LTM | Google, Huawei, Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260308 | Corrections on last target NG-RAN node UE XnAP ID transfer | ZTE Corporation, CATT, Huawei | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260378 | Corrections on Source M-NG-RAN node UE XnAP ID IE transfer for LTM and CHO in DC | CATT,Huawei, China Telecom, ZTE Corporation, CMCC | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260380 | Clarification on Ambiguity of SN Addition Request for CHO and Inter-CU LTM | CATT, Huawei, China Telecom, ZTE Corporation,CMCC | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260381 | Correction on CSI-RS Coordination procedure | CATT, Ericsson, China Telecom, CMCC | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260417 | Correction on ETA resource release in DU | Ofinno, Ericsson | CR | Agreement | Yes |
No
| available | No | R3‑258493 | |||
| R3‑260418 | Correction on ETA resource release in DU | Ofinno, Ericsson | CR | Agreement | Yes |
No
| available | No | R3‑258494 | |||
| R3‑260461 | Support for Handover Cancel from the source gNB for LTM | Ericsson, Ofinno, Jio Platforms, Lenovo | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260462 | Support for Handover Cancel from the source gNB for LTM | Ericsson, LG Electronics, Ofinno, Lenovo, CATT, Google, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260463 | Fast LTM recovery for Inter-CU LTM | Ericsson, Jio Platforms, Lenovo, Ofinno | discussion | Yes |
No
| available | No | |||||
| R3‑260464 | Fast LTM Recovery for Inter-CU LTM | Ericsson, Jio Platforms, Lenovo, Ofinno | CR | Agreement | Yes |
No
| available | No | R3‑258557 | |||
| R3‑260465 | Corrections on CSI-RS report configuration | Ericsson, Jio Platforms, Lenovo | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260466 | Corrections on CSI-RS report configuration | Ericsson, Jio Platforms, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260502 | Correction on ID assignment behaviors for LTM no security change and L2 reset | LG Electronics | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260573 | Correction on Handover Preparation for LTM | ZTE Corporation, Huawei, CATT, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260574 | Discussion on early sync resource modification | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260575 | Clarification on Early RACH Resource Requester ID and gNB-DU ID | ZTE Corporation, Pengcheng Laboratory | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260629 | Discussion on remaining issues on inter-CU LTM | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260630 | Xn CR_L3 HO enhancement with LTM configuration kept | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260631 | Stage2 CR_L3 HO enhancement with LTM configuration kept | Samsung | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260515 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM | Huawei, NEC,Jio Platforms, CMCC, China Telecom, Lenovo | discussion | No |
Yes
| withdrawn | Yes | |||||
| R3‑260516 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 1) | Huawei, NEC, Jio Platforms, CMCC, China Telecom, Lenovo | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R3‑260517 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 1) | Huawei, NEC, Jio Platforms, CMCC, China Telecom, Lenovo | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R3‑260518 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 2) | Huawei, NEC, Jio Platforms, CMCC, China Telecom | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R3‑260519 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 2) | Huawei, NEC, Jio Platforms, CMCC, China Telecom | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R3‑260533 | Discussion on UAV aerial UE report configuration | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260534 | Reply LS on multiple aerial UE reporting configurations | CMCC | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260535 | Correction on Aerial UE Flight Information Reporting Control IE | CMCC | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260536 | Correction on Aerial UE location reporting stage2 | CMCC | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260546 | Correction on the description of NG Control Plane | CMCC, CATT, Huawei, Xiaomi, Samsung, ZTE | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260547 | Correction on the description of NGAP Services | CMCC | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260552 | Discussion on AIoT security parameter information status | ZTE Corporation | discussion | Approval | Yes |
Yes
| withdrawn | Yes | ||||
| R3‑260553 | [Draft] LS on AIOT Security parameter | ZTE Corporation | LS out | Approval | Yes |
Yes
| withdrawn | Yes | ||||
| R3‑260554 | Correction on AIoT security parameter information | ZTE Corporation | draftCR | Endorsement | Yes |
Yes
| withdrawn | Yes | ||||
| R3‑260555 | Correction on AIoT security parameter information | ZTE Corporation | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
| 9.2.3 | Rel-19 Other | R3‑260593 | [Draft] LS on prioritized AQP list | Samsung | LS out | Approval | Yes |
No
| available | No | ||
| R3‑260006 | Reply LS on CN assigned subgroup ID for LP-WUS | RAN2(Ericsson) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260007 | Reply LS on geographical area scope MDT | RAN2(CICT) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260010 | Reply LS on the paging in Store and Forward | SA2(CICT) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260016 | Reply LS on enabling/disabling LP-WUS per UE with NAS signalling | SA2(Huawei) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260021 | Reply LS on OAM-centric solution for NW-side data collection | SA5(Nokia) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260014 | Reply LS on clarification of UAV regulation from SA2 | SA2(Ericsson) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260566 | Support Aerial UE Flight Information Reporting for different UAV NF/NEF | Ericsson | discussion | Yes |
No
| available | No | |||||
| R3‑260567 | [Draft] Reply LS on Reply LS on clarification of UAV regulation from SA2 | Ericsson | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260568 | Support Aerial UE Flight Information Reporting for different UAV NF/NEF | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260569 | Support Aerial UE Flight Information Reporting for different UAV NF/NEF | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260398 | Further discussion on UAV altitude information reporting | Huawei, Nokia, China Telecom | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260399 | Correction on aerial UE flight information reporting | Huawei, Nokia, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260400 | [DRAFT] Reply LS on clarification of UAV regulation from SA2 | Huawei, Nokia, China Telecom | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260562 | [TP to TS 38.413, TS38.423, and TS 38.300] Consideration on aerial UE altitude reporting based on SA2 progress with draft LS | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260004 | Reply LS on Structure updates of AIoT Identifiers | CT4(CICT) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260024 | Reply LS on Security parameter in A-IoT paging | TSG SA(CMCC) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260018 | Reply LS on integrity failure | SA3(Xiaomi) | LS in | Discussion | Yes |
No
| available | No | ||||
| R3‑260111 | Correction on command failure in A-IoT | Xiaomi, Huawei, CATT, Samsung, CMCC, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260112 | Correction on command failure in A-IoT | Xiaomi, Huawei, CATT, Samsung, CMCC, ZTE | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260152 | Consideration on A-IoT Device Identification Requested | Huawei, China Telecom, China Unicom, CATT, CMCC, Nokia, Ericsson, Lenovo | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260153 | Correction on A-IoT Device Identification Requested | Huawei, China Telecom, China Unicom, CATT, CMCC, Nokia, Ericsson, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260154 | Consideration on A-IoT Supported PLMN by the gNB | Huawei, China Telecom, China Unicom, Xiaomi, CMCC, Lenovo | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260155 | Correction on the supported PLMN for AIoT by the gNB | Huawei, China Telecom, China Unicom, Xiaomi, CMCC, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260156 | Correction on the inclusion of security parameter for A-IoT | Huawei, China Telecom, China Unicom, CATT, CMCC | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260157 | Correction on AIOTF Name | Huawei, CMCC, China Unicom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260237 | Correction to the texts of NG interface management function | CATT, CMCC, Xiaomi, ZTE Corporation, Samsung | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260369 | Correction on A-IoT related NGAP procedures | CATT, Huawei, Samsung, CMCC | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260625 | Correction on maximum length of Group Device Identity in Inventory Request | China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260419 | Abnormal conditions for F1: gNB-CU Configuration Update | Ericsson, Jio Platforms, InterDigital, Fibercop, AT&T, Deutsche Telekom , Telecom Italia | discussion | Approval | Yes |
No
| available | No | ||||
| R3‑260480 | Abnormal conditions for F1AP gNB-CU Configuration Update | Ericsson, Jio Platforms, InterDigital, Fibercop, AT&T, Deutsche Telekom , Telecom Italia | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260343 | CCO corrections | Nokia, Ofinno, Deutsche Telekom, ZTE Corporation | discussion | Yes |
No
| available | No | |||||
| R3‑260342 | Corrections of AI/ML-based CCO | Nokia, Ofinno, Deutsche Telekom, ZTE Corporation | CR | Agreement | Yes |
No
| available | No | R3‑258271 | |||
| R3‑260354 | Correction on Predicted CCO Assistance Information | ZTE Corporation, Lenovo, China Unicom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260564 | Corrections on IEs consolidation for AI/ML-based CCO | CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260420 | Correction for gNB-DU Configuration Update | Ericsson, Jio Platforms, InterDigital, Fibercop, AT&T, Deutsche Telekom , Telecom Italia | discussion | Approval | Yes |
No
| available | No | ||||
| R3‑260481 | Correction for gNB-DU Configuration Update | Ericsson, Jio Platforms, InterDigital, Fibercop, AT&T, Deutsche Telekom , Telecom Italia | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260101 | Correction on the criticality of gNB-CU-UP Measurement ID | ZTE Corporation, Nokia, Samsung, CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260357 | Miscellaneous corrections on AI/ML for NG-RAN enhancements | Nokia | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260356 | Discussion on Exit Conditions | Nokia, Deutsche Telekom, InterDigital, BT | discussion | Yes |
No
| available | No | |||||
| R3‑260361 | Correction of Exit Conditions | Nokia, Deutsche Telekom, InterDigital, BT | CR | Agreement | Yes |
No
| available | No | R3‑258172 | |||
| R3‑260382 | Corrections of AI/ML-based CCO for XnAP | CATT,CMCC, ZTE Corporation, Samsung | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260402 | Stage2 correction on procedures used for AI/ML for NG-RAN | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260421 | Stage 2 corrections for AI/ML based CCO | Ericsson, Jio Platforms, InterDigital, Fibercop, AT&T, Deutsche Telekom , Telecom Italia | discussion | Approval | Yes |
No
| available | No | ||||
| R3‑260437 | Stage 2 corrections for AI/ML based CCO | Ericsson, Jio Platforms, InterDigital, Fibercop, AT&T, Deutsche Telekom , Telecom Italia | CR | Agreement | Yes |
No
| available | No | R3‑258439 | |||
| R3‑260401 | Correction of SRB ID for network-side data collection | Huawei, Xiaomi, CATT, Ericsson, Nokia, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260043 | Correction of Transmission Bandwidth Asymmetric | Nokia, Huawei, Qualcomm, China Telecom | CR | Agreement | Yes |
No
| available | No | R3‑258098 | |||
| R3‑260044 | Correction of Transmission Bandwidth Asymmetric | Huawei, Nokia, Qualcomm, China Telecom | CR | Agreement | Yes |
No
| available | No | R3‑258103 | |||
| R3‑260513 | Connection of Secondary RAT Data Usage Report for NG based handover | Huawei, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | R3‑258692 | |||
| R3‑260514 | Connection of Secondary RAT Data Usage Report for Xn based handover | Huawei, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | R3‑258693 | |||
| R3‑260599 | Corrections on SBFD CLI and SBFD RACH | Samsung, Qualcomm, Charter, ZTE, CATT | CR | Agreement | Yes |
No
| available | No | R3‑258686 | |||
| R3‑260158 | Correction on using RRCResumeRequest1 during SDT procedures | Huawei, Nokia, China Telecom | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260159 | Correction on missing RRCResumeRequest1 | Huawei, Nokia, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260160 | Correction on Configured TAC | Huawei, China Unicom, China Telecom, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260172 | ApplicabilityReportList for AI/ML air interface | NEC | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260176 | Remianing Issue on AI/ML Positioning | NEC | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260177 | Correction on positioning data collection for assisting in the pairing with the TRP's measurement | NEC | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260178 | Correction on positioning data collection for assisting in the pairing with the TRP's measurement | NEC | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260216 | Correction of MBS | Nokia | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260235 | Correction of paging capability for LP-WUS | Huawei, CATT, Qualcomm, ZTE, Vivo, Nokia | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260236 | Correction of Positioning System Information Delivery | Huawei, Samsung, CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260276 | Discussion on NR Femto awareness at CN | Huawei, CATT | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260277 | Correction on NR Femto awareness at CN | Huawei, CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260278 | Correction on NR Femto awareness at CN | Huawei, CATT | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260311 | Correction on the LP-WUS disable indication | ZTE Corporation, CATT, Huawei | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260312 | Correction on SON description for CHO with candidate SCG(s) in stage-2 | CATT, Lenovo, Nokia | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260313 | Correction on Evolution of NR duplex operation for 38.470 | CATT | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260367 | Correction on LP-WUS for UEs in RRC_INACTIVE mode | CATT, Huawei, ZTE | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260368 | Correction on PO-to-LO association configuration | CATT | draftCR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260370 | Correction on WAB-gNB configurations | CATT, Nokia, China Telecomm, Ericsson, Huawei | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260484 | Correction of NR Femto | Nokia | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260491 | Correction of WAB Xn Connection Management | Ericsson, CATT, Qualcomm, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260577 | Corrections on additional ULI for WAB | ZTE Corporation, China Telecom, Pengcheng Laboratory, Samsung, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
| R3‑260434 | Abnormal conditions for gNB-CU Configuration Update with updated Presence IE | Ericsson, Jio Platforms, InterDigital, Fibercop, AT&T, Deutsche Telekom , Telecom Italia | CR | Agreement | No |
Yes
| withdrawn | Yes | R3‑258435 | |||
| R3‑260436 | Correction for gNB-DU Configuration Update | Ericsson, Jio Platforms, InterDigital, Fibercop, AT&T, Deutsche Telekom , Telecom Italia | CR | Agreement | No |
Yes
| withdrawn | Yes | R3‑258437 | |||
| 10 | Study on 6G Radio |   | ||||||||||
| 10.1 | General | R3‑260017 | Reply LS on Early Alignment on Access Stratum security aspects | SA3(Lenovo) | LS in | Discussion | Yes |
No
| available | No | ||
| R3‑260392 | 38.760-3 | VODAFONE Group Plc | draft TR | Endorsement | Yes |
No
| available | No | ||||
| R3‑260394 | Workplan for Rel-20 Study of 6GR | VODAFONE Group Plc | Work Plan | Information | Yes |
No
| available | No | ||||
| R3‑260026 | TR38.760-3 v0.3.0 for Study on 6G Radio RAN3 aspects | Vodafone GmbH | draft TR | Endorsement | No |
Yes
| withdrawn | Yes | R3‑258877 | |||
| 10.2 | Overall RAN architecture | R3‑260317 | 6G RAN Principles and Functions | Lenovo | pCR | Yes |
No
| available | No | |||
| R3‑260173 | [pCR to TR38.760-3] Overall 6G RAN Architecture | NEC | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260548 | Discussion on 6G RAN architecture and function | Samsung | pCR | Yes |
No
| available | No | |||||
| R3‑260541 | (pCR to TR 38.760-3) Discussion on the requirements and principles for 6G RAN architecture | CMCC | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260045 | Further discussion on 6G RAN Architecture | Nokia | pCR | Yes |
No
| available | No | |||||
| R3‑260062 | 6G RAT overall architecture for NTN | THALES, ESA, Airbus, Novamint, Iridium | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260070 | RAN architecture general aspects and functions | Xiaomi | pCR | Yes |
No
| available | No | |||||
| R3‑260089 | (pCR to TR 38.760-3) Discussion on 6G RAN functionalities | OPPO | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260113 | Definitions related to 6G RAN architecture design | FiberCop, Qualcomm Inc., T-Mobile USA, LG Electronics, Verizon Wireless, Jio Platforms, Boost Mobile Network, Telecom Italia | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260640 | Response to R3-260113: Definitions related to 6G RAN architecture design | VODAFONE Group Plc | response | Discussion | Yes |
No
| available | No | ||||
| R3‑260201 | TP on 5.2.2 Shared RAN deployment for TR 38.760-3 | Boost Mobile Network | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260218 | 6G RAN functions | Qualcomm Incorporated | pCR | Discussion | Yes |
No
| available | No | ||||
| R3‑260219 | Removing FFS on general principles and deployment scenarios | CATT | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260224 | Service Aware RAN Data Collection | T-Mobile USA Inc. | pCR | Yes |
No
| available | No | |||||
| R3‑260294 | (pCR to TS 38.760-3) Furhter discussion on the overall RAN architecture | ZTE Corporation | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260425 | General Principles and Requirements for the 6G RAN Architecture | Ericsson, InterDigital, Jio Platforms | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260428 | Overall RAN architecture | InterDigital Inc. | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260439 | Architectural Considerations for Service-Aware and AI-Native 6G RAN | Seoul National University | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260470 | Discussion on RAN-CN Function Split and RAN Functions | AT&T | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260494 | (pCR to 38.760) 6G RAN Architecture Requirements | Jio Platforms | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260565 | Further discussions on general requirement, principles and RAN functions for RAN architecture | Huawei | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260609 | Requirements and deployment scenarios toward 6G RAN | NTT DOCOMO INC.. | discussion | Yes |
No
| available | No | |||||
| R3‑260038 | (pCR for TR 38.760-3): 6G Data Collection | Ericsson, Jio Platforms | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260542 | (pCR to TR 38.760-3) Considerations on RAN data collection and data management for 6G RAN | CMCC, FiberCop, T-Mobile, USA, Verizon, China Unicom, PML | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260182 | (pCR to TR38.760-3) Discussion on 6G data collection | NEC | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260046 | Framework for network-side data collection | Nokia | pCR | Yes |
No
| available | No | |||||
| R3‑260071 | Further discussion on Data Collection Principles | Xiaomi | pCR | Yes |
No
| available | No | |||||
| R3‑260075 | (pCR to TR 38.760-3) Discussion on 6G Data Collection | Qualcomm Incorporated, JIO Platforms | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260088 | Discussion on 6G data collection | OPPO | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260132 | Further consideration on overall RAN architecture | Tejas Network Limited | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260194 | (pCR to TR38.760-3) Data Collection Principles and Functional Framework for 6G AI | ZTE Corporation | pCR | Yes |
No
| available | No | |||||
| R3‑260220 | Discussion on data collection | CATT | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260225 | AI-Native RAN Data Collection | T-Mobile USA Inc. | discussion | Yes |
No
| available | No | |||||
| R3‑260296 | Proposals on 6G RAN Architecture and Data Plane | PML, CMCC | discussion | Yes |
No
| available | No | |||||
| R3‑260323 | Consideration on 6G data collection framework | Lenovo | pCR | Yes |
No
| available | No | |||||
| R3‑260413 | 6G Data Collection | Huawei | discussion | Yes |
No
| available | No | |||||
| R3‑260451 | (pCR to 38.760) On 6G RAN Data Collection Triggering | Jio Platforms, FiberCop | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260471 | Discussion on 6G data collection | AT&T | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260523 | Discussion on data collection in 6G RAN architecture | LG Electronics Inc. | pCR | Yes |
No
| available | No | |||||
| R3‑260570 | Discussion on 6G RAN architecture of data collection | CSCN | pCR | Discussion | Yes |
No
| available | No | ||||
| R3‑260586 | Discussion on 6G RAN architecture of data collection | Samsung | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260634 | 6G Data Collection | Rakuten Mobile, Inc | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260452 | (pCR to 38.760) 6G RAN Architecture Requirements | Jio Platforms | discussion | Decision | Yes |
Yes
| withdrawn | Yes | ||||
| 10.3 | RAN-CN interface |   | ||||||||||
| 10.3.1 | General principles and functions | R3‑260162 | Further consideration on RAN-CN interface principles and functions | Huawei | pCR | Agreement | Yes |
No
| available | No | ||
| R3‑260485 | Handling work on Data Transfer Protocols | Nokia | pCR | Yes |
No
| available | No | |||||
| R3‑260139 | Discussion on General Principles and Functions for RAN-CN interface | Seoul National University | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260206 | RAN-CN General Principles | InterDigital Inc. | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260226 | General principles and requirements for 6G RAN-CN interface | LG Electronics | pCR | Yes |
No
| available | No | |||||
| R3‑260242 | Considerations on 6G RAN-CN interface principles and functions | CATT | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260249 | Further consideration on RAN-CN interface principles and functions | Tejas Network Limited | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260252 | Discussion on general principles of RAN-CN interface | Samsung | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260268 | Discussion on General principles and functions of RAN-CN interface | Pengcheng Laboratory | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260318 | Principles and Functions of 6G RAN-CN Interface | Lenovo | pCR | Yes |
No
| available | No | |||||
| R3‑260472 | General Principles and Functions of 6G RAN-CN Interface | AT&T | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260543 | (pCR to TR 38.760-3) Discussion on general principles and functions for RAN-CN interface | CMCC | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260584 | General principles and functions on RAN-CN interface | Xiaomi | pCR | Yes |
No
| available | No | |||||
| R3‑260613 | Proposals on 6G RAN-CN Interface | PML | discussion | Yes |
No
| available | No | |||||
| 10.3.2 | RAN-CN control plane | R3‑260454 | Discussion on the reported advantages of QUIC | Orange | discussion | Yes |
No
| available | No | |||
| R3‑260473 | Discussion on RAN-CN Control Plane Options | AT&T | discussion | Discussion | Yes |
No
| available | No | ||||
| 10.3.2.1 | Point to Point Interface (P2P) | R3‑260063 | (pCR to TR 38.760-3) On 6G RAN-CN P2P interface | Qualcomm Incorporated, T-mobile USA, Verizon, NTT Docomo, Boost Mobile Networks, JIO Platforms, FiberCop, Charter Communications, Telstra, Google | pCR | Discussion | Yes |
No
| available | No | ||
| R3‑260319 | On RAN-CN Point to Point Interface | Lenovo | pCR | Yes |
No
| available | No | |||||
| R3‑260067 | P2P Interface Core Network | InterDigital Inc. | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260107 | RAN-CN P2P Interface and Protocol Stack | Xiaomi | pCR | Yes |
No
| available | No | |||||
| R3‑260163 | Consideration on RAN-CN interface options | Huawei | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260187 | (pCR to TR38.760-3) Consideration of Point-to-Point Interface for 6G RAN-CN | NEC | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260227 | Consideration on 6G RAN-CN P2P interface | LG Electronics | pCR | Yes |
No
| available | No | |||||
| R3‑260250 | Consideration on 6G RAN-CN CP Point-to-Point (P2P) Interface | Tejas Network Limited | pCR | Discussion | Yes |
No
| available | No | ||||
| R3‑260269 | (pCR to TR 38.760-3) On 6G RAN-CN P2P interface | Pengcheng Laboratory | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260467 | P2P Interface for 6G | Ericsson | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260486 | Text Proposals for P2P Solution and for P2P Solution based on QUIC | Nokia | pCR | Yes |
No
| available | No | |||||
| R3‑260544 | Discussion on P2P interface for RAN-CN interface design | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260549 | Consideration on 6G RAN-CN P2P interface options | ZTE Corporation | pCR | Approval | Yes |
No
| available | No | ||||
| R3‑260587 | Discussion on RAN-CN control plane interface options | Samsung | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260632 | Discussion on P2P interface for RAN-CN Control Plane | China Telecom | discussion | Yes |
No
| available | No | |||||
| 10.3.2.2 | Service Based Interface (SBI) | R3‑260114 | RAN-CN interface evolution towards Service Based Interface (SBI) | FiberCop, Qualcomm Inc., Deutsche Telekom, T-Mobile USA, Jio Platforms, Teja Networks | pCR | Agreement | Yes |
No
| available | No | ||
| R3‑260550 | Consideration on 6G RAN-CN SBI interface options | ZTE Corporation | pCR | Approval | Yes |
No
| available | No | ||||
| R3‑260490 | Considerations on SBI for RAN-CN interface | Ericsson, Nokia | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260641 | Response to R3-260490 | Qualcomm Inc | response | Discussion | Yes |
No
| available | No | ||||
| R3‑260064 | (pCR to TR 38.760-3) On 6G RAN-CN service-based interface | Qualcomm Incorporated, T-mobile USA, Verizon, NTT Docomo, Boost Mobile Networks, JIO Platforms, FiberCop, Charter Communications, Telstra, Google | pCR | Discussion | Yes |
No
| available | No | ||||
| R3‑260066 | Service Based Interface Core Network | InterDigital Inc. | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260090 | (pCR to TR 38.760-3) Discussion on 6G RAN-CN SBI | OPPO | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260108 | RAN-CN SBI Interface and Protocol Stack | Xiaomi | pCR | Yes |
No
| available | No | |||||
| R3‑260136 | Discussion on Service Based Interface (SBI) | Seoul National University | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260188 | (pCR to TR38.760-3) Consideration of Service-Based Interface for 6G RAN-CN | NEC | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260228 | Consideration on 6G RAN-CN SBI | LG Electronics | pCR | Yes |
No
| available | No | |||||
| R3‑260243 | Considerations on 6G RAN-CN interface options | CATT | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260251 | Consideration on RAN-CN CP Service-based Interface (SBI) | Tejas Network Limited | pCR | Discussion | Yes |
No
| available | No | ||||
| R3‑260270 | Discussion on Service Based Interface (SBI) of RAN-CN control plane | Pengcheng Laboratory | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260320 | On Service Based RAN-CN Interface | Lenovo | pCR | Yes |
No
| available | No | |||||
| R3‑260624 | Discussion on SBI for RAN-CN interface design | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260635 | Discussion on SBI for RAN-CN interface | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
| 10.3.2.3 | Evaluation criteria | R3‑260588 | Discussion on the evaluation criteria for RAN-CN interface design | Samsung | pCR | Agreement | Yes |
No
| available | No | ||
| R3‑260341 | Evaluation for RAN-CN interface options | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260440 | Proposal on Evaluation Criteria for RAN-CN CP interface options | Deutsche Telekom, FiberCop | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260065 | (pCR to TR 38.760-3) Evaluation criteria for 6G RAN-CN IF solutions | Qualcomm Incorporated, T-mobile USA, Verizon, NTT Docomo, Boost Mobile Networks, JIO Platforms, Sony, FiberCop, Charter Communications, Telstra, Google | pCR | Discussion | Yes |
No
| available | No | ||||
| R3‑260164 | Evaluation criteria for RAN-CN control plane interface options | Huawei | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260189 | (pCR to TR38.760-3) Evaluation Criteria for 6G RAN-CN Interface Options | NEC | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260244 | Evaluation Criteria of RAN-CN Interface Options | CATT | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260355 | Evaluation Criteria for RAN-CN Interface Options | Tejas Network Limited | pCR | Discussion | Yes |
No
| available | No | ||||
| R3‑260407 | Template for comparison of different protocol options for control plane in 6G between 6GR and CN | VODAFONE Group Plc | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260468 | On how to achieve interim study results on "P2P vs SBI" | Ericsson, Vodafone, Jio Platforms | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260487 | Evaluation Criteria for comparing P2P versus SBI | Nokia, Ericsson | pCR | Yes |
No
| available | No | |||||
| R3‑260495 | (pCR to 38.760) Evaluation Criteria for 6G RAN–CN CP Interface | Jio Platforms | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260551 | Discussion on evaluation criteria for 6G RAN-CN control plane interface | ZTE Corporation | pCR | Approval | Yes |
No
| available | No | ||||
| R3‑260611 | Necessary considerations for 6G RAN-CN interface options | NTT DOCOMO INC.. | discussion | Yes |
No
| available | No | |||||
| R3‑260636 | Discussion on RAN-CN interface evaluation criteria | Rakuten Mobile, Inc | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260453 | (pCR to 38.760) Evaluation Criteria for 6G RAN–CN CP Interface | Jio Platforms | discussion | Decision | Yes |
Yes
| withdrawn | Yes | ||||
| 10.3.3 | RAN-CN user plane |   | ||||||||||
| 10.4 | RAN internal functional split and interfaces |   | ||||||||||
| 10.4.1 | Higher Layer Split (HLS) | R3‑260633 | (pCR to TR 38.760-3) Benefits of the disaggregated RAN architecture | Rakuten Mobile, Inc, Qualcomm, Samsung, NTT DOCOMO, Verizon, KDDI, Mavenir, Fujitsu, Jio Platforms | pCR | Yes |
No
| available | No | |||
| R3‑260482 | Challenges and benefits of Higher Layer Split (HLS) | Ericsson | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260109 | Higher Layer Split | Xiaomi | pCR | Yes |
No
| available | No | |||||
| R3‑260321 | Higher Layer Split in 6G RAN | Lenovo | pCR | Yes |
No
| available | No | |||||
| R3‑260091 | Discussion on 6G HLS | OPPO | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260130 | Consideration on RAN internal higher layer split | Huawei, Orange | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260143 | (pCR to TR38.760-3) Further discussion on higher layer split | ZTE Corporation | pCR | Approval | Yes |
No
| available | No | ||||
| R3‑260185 | (pCR to TR38.760-3) Discussion on Higher Layer Split (HLS) | NEC | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260203 | Study on the UE context handling with 5G-like HLS | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
| R3‑260222 | Consideration on high layer split of 6G RAN node | CATT | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260234 | Discussion on Benefits and Study Areas of 6G RAN Higher Layer Split | Seoul National University | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260246 | Consolidation of HLS benefits and principal areas of study under RAN internal functional split | Tejas Network Limited | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260291 | Discussion on 6G RAN internal split | Fujitsu Limited | discussion | Yes |
No
| available | No | |||||
| R3‑260292 | Discussion on 6G RAN Higher Layer Split for NTN | ETRI | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260299 | Justification for continuing an open F1-like Interface for 6G | discussion | Decision | Yes |
No
| available | No | |||||
| R3‑260300 | Considerations on 6G Higher Layer Split | KDDI Corporation (TTC) | discussion | Yes |
No
| available | No | |||||
| R3‑260335 | Discussion on 6G RAN internal functional split | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260410 | Benefits and challenges of disaggregated RAN Architecture | VODAFONE Group Plc | discussion | Approval | Yes |
No
| available | No | ||||
| R3‑260585 | (pCR to TR 38.760-3) 6G RAN Higher Layer Split (HLS) benefits | Qualcomm Incorporated, Rakuten, Samsung | pCR | Yes |
No
| available | No | |||||
| R3‑260589 | Discussion on 6G RAN functional split | Samsung, Verizon, NTT DoCoMo, Rakuten, Qualcomm, FiberCop, T-Mobile USA, China Unicom, Jio Platforms, NEC, Google, Fujitsu, Thales, Mavenir, CATT, Boost Mobile, Tejas Networks, Charter, Sony, Lenovo | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260034 | (pCR to TR 38.760-3) 6G-RAN Higher Layer Split (HLS) benefits | Qualcomm Korea | pCR | Yes |
Yes
| withdrawn | Yes | |||||
| R3‑260193 | Discussion on Benefits and Study Areas of 6G RAN Higher Layer Split | Seoul National University | discussion | Decision | Yes |
Yes
| withdrawn | Yes | ||||
| 10.4.2 | Interface between 6G RAN nodes | R3‑260223 | Consideration on interface between 6G RAN nodes | CATT | pCR | Decision | Yes |
No
| available | No | ||
| R3‑260506 | (pCR to TR38.760-3) General Principles and Functions for Interface between 6G RAN nodes | Ofinno | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260131 | Consideration on interface between 6G RAN nodes | Huawei, Orange | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260035 | (pCR to TR 38.760-3) 6G RAN node - 6G RAN node interface | Qualcomm Korea | pCR | Yes |
No
| available | No | |||||
| R3‑260068 | 6G RAN Node - 6GRAN Node Interface General Principles | InterDigital Inc. | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260110 | Interface between 6G RAN nodes | Xiaomi | pCR | Yes |
No
| available | No | |||||
| R3‑260140 | Discussion on Interface between 6G RAN Nodes | Seoul National University | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260174 | [pCR to TR38.760-3] Description for Interface between 6G RAN nodes | NEC | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260248 | Baseline architectural principles and study scope for the interface between 6G RAN nodes | Tejas Network Limited | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260253 | Discussion on interface between 6G RAN nodes | Samsung, Nokia, Verizon, Jio Platforms | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260295 | (pCR to TR38.760-3) Further discussion on interface between 6G RAN nodes | ZTE Corporation | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260322 | On Interface between RAN nodes | Lenovo | pCR | Yes |
No
| available | No | |||||
| R3‑260336 | Consideration on Interface between 6G RAN nodes | China Telecom | pCR | Approval | Yes |
No
| available | No | ||||
| R3‑260483 | Defining the interface between 6G RAN nodes | Ericsson | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260537 | Discussion on general principles and requirements for interface between 6G RAN node | CMCC | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260612 | Requirements for the interface between RAN nodes | NTT DOCOMO INC.. | discussion | Yes |
No
| available | No | |||||
| R3‑260638 | Baseline considerations for interface between 6G RAN nodes | Nokia | pCR | Approval | Yes |
No
| available | No | ||||
| 10.5 | AI/ML for RAN |   | ||||||||||
| 10.5.1 | AI/ML use cases | R3‑260076 | (pCR to TR 38.760-3) Discussion on 6G AI/ML Use Cases | Qualcomm Incorporated, JIO Platforms | pCR | Agreement | Yes |
No
| available | No | ||
| R3‑260141 | Discussion on 6G AI/ML use cases | Seoul National University | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260324 | Consideration on 6G AI use cases | Lenovo | pCR | Yes |
No
| available | No | |||||
| R3‑260358 | AI/ML Use Cases in 6G | Nokia | pCR | Yes |
No
| available | No | |||||
| R3‑260529 | (pCR to TR 38.760-3) Discussion on 6G AIML use cases | CMCC | pCR | Approval | Yes |
No
| available | No | ||||
| R3‑260039 | (pCR for TR 38.760-3): High-level principles and Use Cases for AIML in 6G RAN | Ericsson, AT&T, Jio Platforms | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260195 | (pCR to TR38.760-3) Consideration on AIRAN for 6G Network | ZTE Corporation | pCR | Yes |
No
| available | No | |||||
| R3‑260221 | Consideration on AI/ML use cases | CATT | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260069 | 6G AI/ML Use Cases | InterDigital Inc. | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260133 | Considerations on AIML data flow in AI-native Radio Access Network | Hanbat National University | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260183 | (pCR to TR38.760-3) AI/ML use cases for 6G | NEC | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260245 | AI/ML Use Cases for 6G RAN | Tejas Network Limited | pCR | Decision | Yes |
No
| available | No | ||||
| R3‑260293 | Discussion on 6G AI/ML Network Energy Savngs use case | Fujitsu Limited | discussion | Yes |
No
| available | No | |||||
| R3‑260337 | Discussion on high priority use cases for 6G | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260393 | 6G AI/ML Use Case | Ofinno | discussion | Yes |
No
| available | No | |||||
| R3‑260403 | Further discussion on AI/ML for 6G RAN use cases | Huawei | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260525 | Discussion on other AI/ML use cases to be considered | LG Electronics Inc. | discussion | Yes |
No
| available | No | |||||
| R3‑260606 | Discussion on 6G AI/ML use cases | CEWiT | discussion | Yes |
No
| available | No | |||||
| R3‑260637 | 6G AI/ML Use Cases: Network Slicing | Rakuten Mobile, Inc | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260254 | Discussion on AI/ML use cases for 6G | Samsung | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260142 | Discussion on 6G AI/ML use cases | Seoul National University | discussion | Decision | No |
Yes
| withdrawn | Yes | ||||
| 10.5.2 | AI/ML framework |   | ||||||||||
| 10.6 | Mobility for 6GR |   | ||||||||||
| 10.7 | Interworking between 6GR and NR |   | ||||||||||
| 11 | Data Collection for SON/MDT in NR Phase 5 (RAN3-led) |   | ||||||||||
| 11.1 | General | R3‑260029 | (BLCR for 38.413) Inter-CU LTM | Ericsson | CR | Endorsement | Yes |
No
| available | No | R3‑258880 | |
| R3‑260030 | (BLCR for 38.300) Introduction of SON enhancements | China Unicom | draftCR | Endorsement | Yes |
No
| available | No | R3‑258881 | |||
| R3‑260388 | Workplan for Rel-20 SON_MDT Enhancement | China Unicom | Work Plan | Information | Yes |
No
| available | No | ||||
| 11.2 | MRO Enhancements |   | ||||||||||
| 11.2.1 | Inter-CU LTM | R3‑260036 | MRO enhancements for Inter-CU LTM | Qualcomm Korea | discussion | Yes |
No
| available | No | |||
| R3‑260053 | MRO Enhancements for Inter-CU LTM | Nokia | discussion | Yes |
No
| available | No | |||||
| R3‑260072 | Considerations on MRO applicability for Inter-CU LTM | ETRI | discussion | Yes |
No
| available | No | |||||
| R3‑260083 | (TP for TS 38.423)MRO for inter CU LTM | ZTE Corporation | discussion | Yes |
No
| available | No | |||||
| R3‑260186 | MRO for Inter-CU LTM | NEC | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260257 | (TP for SON BLCR to TS 38.473 and TS 38.401) Discussion on MRO enhancement on inter-CU LTM | Samsung | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260314 | (TP for 38.401, 38.413 and 38.423) Discussion on SON enhancement for inter-CU LTM | CATT | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260325 | Discussion on MRO for inter-CU LTM | Lenovo | discussion | Yes |
No
| available | No | |||||
| R3‑260389 | Discussion on MRO Enhancements for inter-CU LTM | China Unicom | discussion | Yes |
No
| available | No | |||||
| R3‑260411 | (TP for BLCR for 38.473, 38.423, 38.401, 38.300) Inter-CU LTM | Huawei | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260501 | MRO for inter-gNB LTM | Ericsson | discussion | Yes |
No
| available | No | |||||
| R3‑260530 | Discussion on MRO enhancements for inter-CU LTM | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
| 11.2.2 | Intra-CU conditional LTM | R3‑260037 | MRO enhancements for Intra-CU CLTM | Qualcomm Korea | discussion | Yes |
No
| available | No | |||
| R3‑260054 | MRO Enhancements for Conditional Intra-CU LTM | Nokia | discussion | Yes |
No
| available | No | |||||
| R3‑260084 | (TP for TS38.300 and TS38.401)MRO for CLTM | ZTE Corporation | discussion | Yes |
No
| available | No | |||||
| R3‑260184 | MRO for Intra-CU Conditional LTM | NEC | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260258 | (TP for SON BLCR to TS 38.401) Discussion on MRO enhancement on intra-CU conditional LTM | Samsung | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260315 | (TP for 38.473) Discussion on SON enhancement for conditional intra-CU LTM | CATT | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260326 | Discussion on MRO for intra-CU CLTM | Lenovo | discussion | Yes |
No
| available | No | |||||
| R3‑260391 | Discussion on MRO Enhancements for C-LTM | China Unicom | discussion | Yes |
No
| available | No | |||||
| R3‑260412 | (TP for BLCR for 38.473) Intra-CU conditional LTM | Huawei | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260500 | MRO for Conditional LTM | Ericsson | discussion | Yes |
No
| available | No | |||||
| R3‑260531 | Discussion on MRO enhancements for intra-CU CLTM | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
| 12 | Study on AI/ML for NG-RAN Phase 3 (RAN3-led) |   | ||||||||||
| 12.1 | General | R3‑260027 | TR38.745 v1.1.0 for Study on Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN Phase 3 | ZTE Corporation, NEC | draft TR | Endorsement | Yes |
No
| available | No | R3‑258878 | |
| R3‑260102 | Work plan for Study on AI/ML for NG-RAN Phase 3 | ZTE Corporation, NEC | Work Plan | Information | Yes |
No
| available | No | ||||
| R3‑260103 | (TP to TR 38.745) Conclusion on Study on AI/ML for NG-RAN Phase 3 | ZTE Corporation (Rapporteur), NEC, Nokia | other | Agreement | Yes |
No
| available | No | ||||
| 12.2 | AI/ML-based mobility |   | ||||||||||
| 12.2.1 | Multi-hop UE trajectory across gNBs | R3‑260104 | (pCR to TR 38.745) Consideration on Multi-hop UE trajectory | ZTE Corporation, Lenovo, LG Electronics | pCR | Yes |
No
| available | No | |||
| R3‑260385 | (pCR to TR 38.745) AIML based mobility – Multi-hop UE Trajectory | Ericsson, Jio Platform | pCR | Yes |
No
| available | No | |||||
| R3‑260077 | Discussion on Multi-hop UE Trajectory Prediction and Feedback | Qualcomm Incorporated | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260179 | (pCR for TR38.745) Multi-hop UE trajectory across gNBs | NEC | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260338 | Discussion on multi-hop UE trajectory prediction | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260359 | Multi-hop UE trajectory across gNBs | Nokia | pCR | Yes |
No
| available | No | |||||
| R3‑260374 | Support of multi-hop UE trajectory prediction/feedback | CATT | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260404 | Further considerations on multi-hop UE trajectory in AI/ML-based mobility | Huawei | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260527 | Discussion on AIML based Multi-hop UE trajectory across gNBs | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260600 | (pCR to 38.745) Multi-hop UE trajectory across gNBs | Samsung | other | Agreement | Yes |
No
| available | No | ||||
| 12.2.2 | Intra-CU LTM | R3‑260348 | Discussion on AI/ML for Intra CU LTM | Tejas Network Limited | discussion | Discussion | Yes |
No
| available | No | ||
| R3‑260405 | Further discussion on AI/ML assisted intra-CU LTM | Huawei | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260040 | AI/ML for Intra-CU LTM | Nokia | pCR | Yes |
No
| available | No | |||||
| R3‑260078 | (pCR To TR 38.745) Discussion on AI/ML based Intra-CU LTM | Qualcomm Incorporated | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260105 | (pCR to TR 38.745) Consideration on AI/ML assisted intra-CU LTM | ZTE Corporation | pCR | Yes |
No
| available | No | |||||
| R3‑260180 | (pCR for TR38.745) AI/ML based intra-CU LTM | NEC | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260327 | AI/ML for Intra-CU LTM | Lenovo | discussion | Yes |
No
| available | No | |||||
| R3‑260339 | Discussion on support of AIML based intra-CU LTM | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260375 | Discussion on support of AI/ML enabled intra-CU LTM | CATT | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260386 | (pCR to TR 38.745) AI/ML based mobility – Intra-CU LTM | Ericsson | pCR | Yes |
No
| available | No | |||||
| R3‑260526 | Discussion on remaining issues for intra-CU LTM use case | LG Electronics Inc. | discussion | Yes |
No
| available | No | |||||
| R3‑260539 | (pCR to TR 38.745) AIML based intra CU LTM use cases | CMCC | pCR | Approval | Yes |
No
| available | No | ||||
| R3‑260601 | (pCR to 38.745) AI-based intra-CU LTM | Samsung | other | Agreement | Yes |
No
| available | No | ||||
| 12.2.3 | Handover enhancements | R3‑260360 | AI/ML-based Handover Enhancements | Nokia | pCR | Yes |
No
| available | No | |||
| R3‑260387 | (pCR to TR 38.745) AI/ML based mobility – Handover Enhancements | Ericsson | pCR | Yes |
No
| available | No | |||||
| R3‑260384 | Discussion on AI/ML based inter-CU LTM | Ofinno, LLC | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260079 | (pCR To TR 38.745) Discussion on Inter-CU LTM | Qualcomm Incorporated | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260106 | (pCR to TR 38.745) Consideration on other handover enhancements | ZTE Corporation | pCR | Yes |
No
| available | No | |||||
| R3‑260181 | (pCR for TR38.745) Other AI/ML based handover enhancements | NEC | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260340 | Discussion on support of AIML based inter-CU LTM | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260376 | Discussion on support of AI/ML enabled inter-CU LTM | CATT | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260390 | (pCR for TR 38.745) AI/ML based inter-CU LTM | Ofinno | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260406 | Further discussion for Handover Enhancements | Huawei | pCR | Agreement | Yes |
No
| available | No | ||||
| R3‑260528 | Discussion on AI/ML based handover enhancement | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260602 | (pCR to 38.745) AI-based inter-CU LTM | Samsung | other | Agreement | Yes |
No
| available | No | ||||
| 13 | Study on Integrated Sensing And Communication (ISAC) for NR |   | ||||||||||
| 13.1 | General | R3‑260028 | (BL pCR to TR 38.765) Study on Integrated Sensing and Communication (ISAC) for NR | China Telecom, Xiaomi | pCR | Endorsement | Yes |
No
| available | No | R3‑258879 | |
| R3‑260331 | Work plan for study on Integrated Sensing And Communication (ISAC) for NR | China Telecom, Xiaomi | Work Plan | Information | Yes |
No
| available | No | ||||
| 13.2 | Network architecture | R3‑260011 | LS on Sensing aspects related to RAN coordination | SA2(OPPO) | LS in | Discussion | Yes |
No
| available | No | ||
| R3‑260190 | (TP to BL pCR of TR38.765) The discussion on ISAC network architecture | NEC | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260047 | (TP to pCR 38.765) ISAC architecture and protocol | Xiaomi | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260049 | (TP to BL pCR) Network architecture for ISAC | Huawei | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260057 | (TP to pCR 38.765) Network Architecture and Protocol Aspects for NR Sensing Support | Qualcomm Incorporated | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260092 | [DRAFT] Reply LS on Sensing aspects related to RAN coordination | OPPO | LS out | Approval | Yes |
No
| available | No | ||||
| R3‑260093 | (TP to BL pCR) Discussion on RAN architecture for sensing | OPPO | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260134 | Network architecture enhancements for NR ISAC | Hanbat National University | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260137 | (TP to pCR 38.765) Network Architecture and Protocol stack for NR ISAC | Tejas Network Limited | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260144 | (TP to pCR 38.765) Further discussion on Network Architecture for ISAC | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260207 | NR ISAC Network Architecture | InterDigital Inc. | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260282 | (TP to pCR for TR 38.765) Discussion on architecture for ISAC | Nokia | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260328 | (TP to TR 38.765) Discussion on ISAC network architecture | Lenovo | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260332 | (TP to 38.473) On potocal stack for ISAC | China Telecom | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260371 | (TP to pCR 38.765) Network architecture for ISAC and draft Reply LS | CATT | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260416 | ISAC Logical Architecture and Data Transmission | Ericsson, Jio Platforms | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260426 | Discussion on the reply for LSin from SA2 | KPN N.V. | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260474 | Discussion on Network Architecture for ISAC | AT&T | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260507 | Discussions on the network architecture design of ISAC | China Unicom | discussion | Yes |
No
| available | No | |||||
| R3‑260545 | Discussion on Network Architecture for ISAC | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260590 | Discussion on network architecture for ISAC | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
| 13.3 | RAN-CN procedures and signaling | R3‑260048 | (TP to pCR 38.765) RAN-CN procedure and signalling for ISAC | Xiaomi | other | Agreement | Yes |
No
| available | No | ||
| R3‑260145 | (TP to pCR 38.765) Further discussion on RAN-CN Procedures and Signalling for ISAC | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260372 | (TP to pCR 38.765) RAN-CN procedures and signaling for ISAC | CATT | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260435 | (TP to pCR) RAN-CN procedures and signaling for ISAC | KPN N.V., TNO | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260447 | Discussion on RAN-CN ISAC procedures and signalling content with reply LS and TP | Ericsson, Jio Platforms, China Unicom | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260504 | Discussions for ISAC RAN-CN aspects | LG Electronics Inc. | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260050 | (TP to BL pCR) RAN-CN procedures and signaling for ISAC and reply LS to SA2 | Huawei, Deutsche Telekom | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260058 | (TP to pCR 38.765) Signalling and Procedures for NR Sensing Support | Qualcomm Incorporated | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260094 | Discussion on RAN-CN procedures and signalling for sensing | OPPO | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260135 | RAN-CN procedures and signaling for ISAC | Hanbat National University | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260138 | (TP to pCR 38.765) RAN-CN procedures and signaling for NR ISAC | Tejas Network Limited | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260191 | (TP to BL pCR of TR38.765)The discussion on ISAC RAN-CN procedure and signaling | NEC | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260208 | NR ISAC RAN-CN Procedures and Signaling | InterDigital Inc. | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260283 | (TP to pCR for TR 38.765) Discussion on RAN-CN procedures and signaling for ISAC | Nokia | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260329 | (TP to TR 38.765) Discussion on general procedures for gNB-based sensing | Lenovo | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260333 | On RAN-CN procedures for supporting ISAC | China Telecom, BUPT | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260347 | Discussion for the support of ISAC | CANON Research Centre France | discussion | Yes |
No
| available | No | |||||
| R3‑260349 | Discussion on sensing aspects related to RAN coordination | Sony | discussion | Yes |
No
| available | No | |||||
| R3‑260427 | Discussion on RAN-CN procedures and signaling for ISAC | TNO, KPN N.V., ITRI | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260475 | Discussion on RAN-CN Procedures and Signaling for ISAC | AT&T | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260505 | (TP to BL pCR to TR 38.765) ISAC RAN-CN aspects | LG Electronics Inc. | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260508 | Standard impacts of RAN-CN procedures for ISAC | China Unicom | discussion | Yes |
No
| available | No | |||||
| R3‑260522 | Discussion on RAN-CN procedures and signaling for ISAC | discussion | Decision | Yes |
No
| available | No | |||||
| R3‑260538 | Discussion on RAN-CN Procedures Supporting ISAC | CMCC | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260591 | Discussion on RAN-CN procedures and signaling | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
| 14 | Solutions for Ambient IoT in NR Phase 2 |   | ||||||||||
| 14.1 | General | R3‑260031 | (BLCR for 38.300) Introduction of Ambient IoT Ph2 | CMCC | draftCR | Endorsement | Yes |
No
| available | No | R3‑258882 | |
| R3‑260032 | (BLCR for 38.413) Introduction of Ambient IoT Ph2 | Huawei | CR | Endorsement | Yes |
No
| available | No | R3‑258883 | |||
| R3‑260033 | (BLCR for 38.423) Introduction of Ambient IoT Ph2 | Samsung | CR | Endorsement | Yes |
No
| available | No | R3‑258884 | |||
| 14.2 | Topology 2 | R3‑260161 | [TPs to BL CRs] Further consideration on A-IoT Topology 2 | Huawei, China Unicom | other | Agreement | Yes |
No
| available | No | ||
| R3‑260192 | Discussion on Topology 2 of Ambient IoT | NEC | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260217 | (TP for 38.413 AIoT BL CR) Inventory procedure for UEs in AIoT topology 2 | Nokia | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260247 | Functionalities and signaling to support Topology 2 | Qualcomm Incorporated | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260259 | Discussion on Topology 2 for AIoT | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260330 | Discussion on UE Reader Authorization and Selection in Topology 2 | Lenovo | discussion | Yes |
No
| available | No | |||||
| R3‑260334 | Discussion on Topology 2 for Ambient IoT | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260373 | (TP to BLCR 38.473) Discussion on Topology-2 for Ambient-IoT | CATT, CBN, China Broadnet | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260395 | Discussion on Open Issues of Topology 2 for A-IoT | Ofinno | discussion | Decision | Yes |
No
| available | No | ||||
| R3‑260469 | On A-IoT Topology 2 | Ericsson | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260524 | (TPs to BL CRs) Support of Topology 2 | LG Electronics | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260532 | (TP for TS 38.300 BL CR) Discussion on Topology 2 for A-IoT | CMCC | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260556 | [TP to BLCR for 38473 and 38423]Consideration on Rel-20 AIOT | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
| 14.3 | Topology 1 |   | ||||||||||
| 15 | NR mobility enhancements Phase 5 |   | ||||||||||
| 15.1 | General |   | ||||||||||
| 15.2 | LTM SCell activation enhancements |   | ||||||||||
| 20 | XR for NR Phase 4 |   | ||||||||||
| 20.1 | General | R3‑260260 | Work Plan for XR for NR Phase 4 | Meta | Work Plan | Information | Yes |
No
| available | No | ||
| 20.2 | Coordination between gNB and CN on N3 delay measurement | R3‑260175 | Coordination on N3 delay measurement in XR for NR Ph 4 | NEC | discussion | Decision | Yes |
No
| available | No | ||
| R3‑260229 | R20 XR Signaling Enhancements | Qualcomm Incorporated | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260261 | Discussion on Coordination for N3 delay Measurement | Huawei | discussion | Discussion | Yes |
No
| available | No | ||||
| R3‑260284 | Discussion on the enhancement for XR | Nokia | discussion | Yes |
No
| available | No | |||||
| R3‑260316 | Discussion on N3 delay measurement for XR | CATT | discussion | Approval | Yes |
No
| available | No | ||||
| R3‑260448 | Discussion on Rel-20 XR objectives | Ericsson | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260563 | [TP to 38.413, 38.423, 37.483, and 38.415]Consideration on enhanced N3 delay measurement with draft LS | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
| R3‑260592 | Discussion on N3 interface delay measurement for XR | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
| R3‑260626 | Discussion on N3 Interface Measurement for Mobile AI | China Telecom | discussion | Yes |
No
| available | No | |||||
| 21 | AI/ML for NR air interface Phase 2 |   | ||||||||||
| 21.1 | General |   | ||||||||||
| 21.2 | Two-sided AI/ML model |   | ||||||||||
| 31 | Corrections and Enhancements to Rel-20 |   | ||||||||||
| 31.1 | Corrections |   | ||||||||||
| 31.2 | Enhancements |   | ||||||||||
| 32 | Any other business |   | ||||||||||
| 33 | Closing of the meeting |   |