Tdoc List
2025-10-13 16:42
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‑256501 | RAN3#129-bis Meeting Agenda | RAN3 Chair | agenda | Approval | Yes |
Yes
| approved | No | ||
4 | Approval of the minutes from previous meetings | R3‑256502 | RAN3#129 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‑256503 | TR 30.531 v1.60.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC | draft TR | Endorsement | Yes |
Yes
| endorsed | No | ||
R3‑256532 | LS on Study on Modernization of Specification Format and Procedures for 6G | TSG SA(Nokia) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
8 | Incoming LSs |   | ||||||||||
8.1 | New Incoming LSs | R3‑256515 | LS on Average Window for Alternative QoS | SA2(CICT mobile) | LS in | Discussion | Yes |
Yes
| noted | No | ||
R3‑256645 | Discussion on LS on Average Window for Alternative QoS | CATT | discussion | Decision | Yes |
Yes
| noted | No | ||||
R3‑256646 | Correction on Average Window for Alternative QoS for NGAP | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256647 | Correction on Average Window for Alternative QoS for XnAP | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256648 | Correction on Average Window for Alternative QoS for F1AP | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256649 | Correction on Average Window for Alternative QoS for E1AP | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256701 | Discussion on Average Window for Alternative QoS | Huawei | discussion | Yes |
Yes
| noted | No | |||||
R3‑256702 | [draft] Reply to R3-256515 on Average Window for Alternative QoS | Huawei | LS out | Approval | Yes |
No
| available | No | ||||
R3‑256849 | Discussion on Average Window for Alternative QoS | CMCC | discussion | Discussion | Yes |
Yes
| noted | No | ||||
R3‑256848 | [Draft] Reply LS to SA2 on Average Window for Alternative QoS | CMCC | LS out | Approval | Yes |
No
| available | No | ||||
R3‑257002 | Discussion on Average Window for Alternative QoS | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
R3‑257003 | Correction on Alternative QoS parameter | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | R3‑257204 | |||
R3‑257204 | Correction on Alternative QoS parameter | Ericsson, CATT, Qualcomm Inc., Jio Platforms | CR | Agreement | No |
No
| reserved | No | R3‑257003 | |||
R3‑257004 | Correction on Alternative QoS parameter | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | R3‑257205 | |||
R3‑257205 | Correction on Alternative QoS parameter | Ericsson, CATT, Qualcomm Inc., Jio Platforms | CR | Agreement | No |
No
| reserved | No | R3‑257004 | |||
R3‑257005 | Correction on Alternative QoS parameter | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | R3‑257206 | |||
R3‑257206 | Correction on Alternative QoS parameter | Ericsson, CATT, Qualcomm Inc., Jio Platforms | CR | Agreement | No |
No
| reserved | No | R3‑257005 | |||
R3‑257006 | Correction on Alternative QoS parameter | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | R3‑257207 | |||
R3‑257207 | Correction on Alternative QoS parameter | Ericsson, CATT, Qualcomm Inc., Jio Platforms | CR | Agreement | No |
No
| reserved | No | R3‑257006 | |||
R3‑257007 | Correction on Alternative QoS parameter | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | R3‑257208 | |||
R3‑257208 | Correction on Alternative QoS parameter | Ericsson, CATT, Qualcomm Inc., Jio Platforms | CR | Agreement | No |
No
| reserved | No | R3‑257007 | |||
R3‑257008 | Correction on Alternative QoS parameter | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | R3‑257209 | |||
R3‑257209 | Correction on Alternative QoS parameter | Ericsson, CATT, Qualcomm Inc., Jio Platforms | CR | Agreement | No |
No
| reserved | No | R3‑257008 | |||
R3‑257009 | Correction on Alternative QoS parameter | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | R3‑257210 | |||
R3‑257210 | Correction on Alternative QoS parameter | Ericsson, CATT, Qualcomm Inc., Jio Platforms | CR | Agreement | No |
No
| reserved | No | R3‑257009 | |||
R3‑257010 | Correction on Alternative QoS parameter | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | R3‑257211 | |||
R3‑257211 | Correction on Alternative QoS parameter | Ericsson, CATT, Qualcomm Inc., Jio Platforms | CR | Agreement | No |
No
| reserved | No | R3‑257010 | |||
R3‑257011 | Correction on Alternative QoS parameter | Ericsson | draftCR | Endorsement | Yes |
Yes
| revised | No | R3‑257212 | |||
R3‑257212 | Correction on Alternative QoS parameter | Ericsson, CATT, Qualcomm Inc., Jio Platforms | draftCR | Endorsement | No |
No
| reserved | No | R3‑257011 | |||
R3‑257012 | Correction on Alternative QoS parameter | Ericsson | draftCR | Endorsement | Yes |
Yes
| revised | No | R3‑257213 | |||
R3‑257213 | Correction on Alternative QoS parameter | Ericsson, CATT, Qualcomm Inc., Jio Platforms | draftCR | Endorsement | No |
No
| reserved | No | R3‑257012 | |||
R3‑257083 | Handling of Average window for alternative QoS | Nokia | discussion | Yes |
Yes
| noted | No | |||||
R3‑257084 | Correction of Average QoS Window for AQP | Nokia | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257085 | Correction of Average QoS Window for AQP | Nokia | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257086 | Response LS on Average window for alternative QoS | Nokia | LS out | Approval | Yes |
No
| available | No | ||||
R3‑257168 | Discussion on average window for alternative QoS | ZTE Corporation | discussion | Approval | Yes |
Yes
| noted | No | ||||
R3‑256518 | Reply LS on per-UE UE performance metrics | SA5(HuaWei) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑256973 | Further discussion on per-UE UE performance in AI/ML for NG-RAN | Huawei, FiberCop, BT, Jio Platforms | discussion | Agreement | Yes |
Yes
| noted | No | ||||
R3‑256974 | Correction on Average Packet Delay and Average Packet Loss DL - Option 1 | Huawei, FiberCop, BT, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256975 | Correction on Average Packet Delay and Average Packet Loss DL - Option 2 | Huawei, FiberCop, BT, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256976 | Correction on Average Packet Delay and Average Packet Loss DL - Option 1 | Huawei, FiberCop, BT, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256977 | Correction on Average Packet Delay and Average Packet Loss DL - Option 2 | Huawei, FiberCop, BT, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256979 | Addition of the Average Packet Loss UL measurement as UE Performance | Huawei, FiberCop, BT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256980 | Addition of the Average Packet Loss UL measurement as UE Performance | Huawei, FiberCop, BT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257112 | [DRAFT] Reply LS on per-UE UE performance metrics | Huawei | LS out | Approval | Yes |
No
| available | No | ||||
R3‑256560 | Discussion on per-UE UE performance metrics | ZTE Corporation | discussion | Yes |
No
| available | No | |||||
R3‑256561 | Correction to per-UE UE performance metrics | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256562 | Correction to per-UE UE performance metrics | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256799 | Correction on UE performance for AI/ML | NEC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256837 | Discussion on supporting UL Packet Loss in AIML UE Performance feedback | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256838 | Correction on R18 UE performance feedback for UL packet loss | CMCC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256839 | Correction on R19 UE performance feedback for UL packet loss | CMCC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256868 | Discussion on UE level performance | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256869 | Correction to XnAP on UL Packet Loss Rate metrics | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256870 | Correction to XnAP on UL Packet Loss Rate metrics | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256931 | On LS discussions with SA5 on Packet loss measurements in context of Release-19 | Ericsson, InterDigital, Jio Platforms, Verizon | discussion | Approval | Yes |
No
| available | No | ||||
R3‑256932 | Corrections to Release-18 Packet Loss measurements in UE Performance | Ericsson, InterDigital, Jio Platforms, Verizon | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256933 | Corrections to Release-19 Packet Loss measurements in UE Performance | Ericsson, InterDigital, Jio Platforms, Verizon | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256943 | Reply to R3-256518 on per-UE UE performance metrics | Ericsson, InterDigital, Jio Platforms | LS out | Approval | Yes |
No
| available | No | ||||
R3‑257093 | UE Performance Metrics in Rel-18 | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑257094 | Removal of Average Packet Loss DL IE from Rel-18 specifications | Nokia | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257095 | [Draft] Reply LS on per-UE UE performance metrics | Nokia | LS out | Approval | Yes |
No
| available | No | ||||
R3‑256519 | LS on temporary suspension of trace production | SA5(Ericsson) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑257070 | Discussion on Trace Suspension feasibility | Ericsson | discussion | Approval | Yes |
Yes
| noted | No | ||||
R3‑257195 | Response to R3-256747, R3-257070 | Nokia | response | Discussion | No |
Yes
| noted | No | ||||
R3‑256724 | Discussion on Average Window for Alternative QoS | Huawei | discussion | No |
Yes
| withdrawn | Yes | |||||
R3‑256725 | [draft] Reply LS on Average Window for Alternative QoS | Huawei | LS out | Approval | No |
Yes
| withdrawn | Yes | ||||
R3‑257071 | Reply to R3-256519 on temporary suspension of trace production | Ericsson | LS out | Approval | Yes |
Yes
| revised | No | R3‑257198 | |||
R3‑257198 | Reply to R3-256519 on temporary suspension of trace production | Ericsson | LS out | Approval | No |
No
| reserved | No | R3‑257071 | |||
R3‑256747 | Temporary suspension of trace production | ZTE Corporation | discussion | Yes |
Yes
| noted | No | |||||
R3‑256748 | Reply LS on temporary suspension of trace production | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
R3‑256505 | Reply LS on non-RedCap UE UL SRS frequency hopping for positioning | RAN1(ZTE) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑256506 | LS on Rel-19 higher layers parameters list Post RAN1#122 | RAN1(Ericsson) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑256521 | Reply to RAN2 LS on Number of UEs in RRC_INACTIVE state with data transmission | SA5(Chinatelecom) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑256524 | LS on UE data collection and data transfer | SA2(Nokia) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑256526 | LS on “IETF Network Slice Application in 3GPP 5G End-to-End Network Slice” | IETF teas(HuaWei) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑257184 | Discussion on the IETF Network Slice Application | Huawei | discussion | Yes |
No
| available | No | |||||
R3‑257185 | [draft] Reply LS on “IETF Network Slice Application in 3GPP 5G End-to-End Network Slice” | Huawei | LS out | Approval | Yes |
No
| available | No | ||||
R3‑256749 | IETF Network Slice | ZTE Corporation | discussion | Yes |
No
| available | No | |||||
R3‑256750 | Reply LS on IETF Network Slice | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
R3‑256917 | IETF Network Slice Application and 3GPP Slicing | Ericsson | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256918 | [DRAFT] Reply LS on IETF Network Slice Application in 3GPP 5G End-to-End Network Slice | Ericsson | LS out | Approval | Yes |
No
| available | No | ||||
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 |   | ||||||||||
9.1.1 | R19 IoT NTN enhancements | R3‑256683 | Clarification on S1 Removal for IoT NTN | ZTE Corporation, LG Electronics, Ericsson, CMCC, Nokia, Nokia Shanghai Bell, CATT, Samsung | draftCR | Endorsement | Yes |
Yes
| revised | No | R3‑257199 | |
R3‑257199 | Clarification on S1 Removal for IoT NTN | ZTE Corporation, LG Electronics, Ericsson, CMCC, Nokia, Nokia Shanghai Bell, CATT, Samsung, Huawei, Deutsche Telekom, Jio Platforms | draftCR | Endorsement | No |
Yes
| endorsed | No | R3‑256683 | |||
R3‑256737 | Correction of TNL address change and S1 removal | Huawei, Deutsche Telekom, Jio Platforms | draftCR | Endorsement | Yes |
Yes
| noted | No | ||||
R3‑256733 | Correction on the Presence of the MME Name IE in the S1 REMOVAL RESPONSE message | Nokia, Nokia Shanghai Bell, Xiaomi, Qualcomm, Ericsson, CATT, Airbus, Jio Platforms, ZTE, LG Electronics | CR | Agreement | Yes |
Yes
| revised | No | R3‑257200 | |||
R3‑257200 | Correction on the MME Name IE in the S1 REMOVAL RESPONSE message | Nokia, Nokia Shanghai Bell, Xiaomi, Qualcomm, Ericsson, CATT, Airbus, Jio Platforms, ZTE, LG Electronics | CR | Agreement | No |
Yes
| endorsed | No | R3‑256733 | |||
R3‑256740 | Correction of MME name for S1 Removal | Huawei | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑256738 | Provision of S&F Mode Indication Information | Huawei, Deutsche Telekom, Jio Platforms, Ericsson | draftCR | Endorsement | Yes |
Yes
| revised | No | R3‑257201 | |||
R3‑257201 | Provision of S&F Mode Indication Information | Huawei, Deutsche Telekom, Jio Platforms, Ericsson, Nokia, Nokia Shanghai Bell, Xiaomi, CATT, ZTE, CMCC, NEC | draftCR | Endorsement | No |
Yes
| endorsed | No | R3‑256738 | |||
R3‑256739 | Clarify MME unchange for store and forward mode change | Huawei, Deutsche Telekom, Jio Platforms, Ericsson | draftCR | Endorsement | Yes |
Yes
| noted | No | ||||
R3‑256843 | Discussion on introducing S1 suspend resume during hard FLSO | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256614 | Suspend/resume S1 during hard FLSO | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE, CATT, China Telecom, CMCC, LG Electronics, Xiaomi, Samsung | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256732 | Suspend/resume S1 during hard FLSO | Nokia, Nokia Shanghai Bell, ZTE Corporation, CATT, Qualcomm, CMCC, Samsung, China Telecom, LG Electronics, Xiaomi | CR | Agreement | Yes |
No
| available | No | ||||
9.1.2 | R19 LTE-based 5G Broadcast | R3‑256751 | Correction of Time Interleaving parameters | ZTE Corporation,Pengcheng Laboratory,China Unicom,China Telecom | CR | Agreement | Yes |
Yes
| revised | No | R3‑257202 | |
R3‑257202 | Correction of Time Interleaving parameters | ZTE Corporation,Pengcheng Laboratory,China Unicom,China Telecom | CR | Agreement | No |
Yes
| endorsed | No | R3‑256751 | |||
9.1.3 | Other | R3‑256741 | Correction of time-based handover for IoT NTN | Huawei, Deutsche Telekom, Jio Platforms, CATT, Ericsson | draftCR | Endorsement | Yes |
Yes
| revised | No | R3‑257214 | |
R3‑257214 | Correction of time-based handover for IoT NTN | Huawei, Deutsche Telekom, Jio Platforms, CATT, Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics | draftCR | Endorsement | No |
Yes
| endorsed | No | R3‑256741 | |||
R3‑257197 | Response to R3-256741, R3-256742, R3-256745, R3-256746 | ZTE Corporation | response | Discussion | No |
No
| available | No | ||||
R3‑256742 | Correction of time-based handover for IoT NTN | Huawei, Deutsche Telekom, Jio Platforms, CATT, Ericsson | draftCR | Endorsement | Yes |
Yes
| revised | No | R3‑257215 | |||
R3‑257215 | Correction of time-based handover for IoT NTN | Huawei, Deutsche Telekom, Jio Platforms, CATT, Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics | draftCR | Endorsement | No |
Yes
| endorsed | No | R3‑256742 | |||
9.2 | NR |   | ||||||||||
9.2.1 | R19 SON/MDT | R3‑256628 | Correction of the description of the geographical area scope | Nokia, ZTE, Huawei, CATT, Samsung, Ericsson | CR | Agreement | Yes |
Yes
| endorsed | No | ||
R3‑256658 | Correction on the description of the geographical area scope | ZTE Corporation, Nokia, Huawei, Samsung, CATT, Ericsson | CR | Agreement | Yes |
Yes
| endorsed | No | ||||
R3‑256674 | Correction of the description of the geographical area scope | Huawei, Nokia, Samsung, CATT, ZTE, Ericsson | draftCR | Endorsement | Yes |
Yes
| endorsed | No | ||||
R3‑256959 | Correcting SCG activation time after CHO | Huawei, CMCC, Deutsche Telekom | discussion | Yes |
Yes
| noted | No | |||||
R3‑256960 | Correcting SCG activation time after CHO | Huawei, CMCC, Deutsche Telekom, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256961 | Correcting SCG activation time after CHO | Huawei, CMCC, Deutsche Telekom | draftCR | Endorsement | Yes |
Yes
| revised | No | R3‑257216 | |||
R3‑257216 | Correcting SCG activation time after CHO | Huawei, CMCC, Deutsche Telekom | draftCR | Endorsement | No |
No
| reserved | No | R3‑256961 | |||
R3‑256599 | Correction in the Target Cell CGI IE of the HO Report for too late CHO with Candidate SCG(s) | Nokia | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑256629 | Problem with location-based selection of UEs for immediate MDT | Nokia | discussion | Discussion | Yes |
Yes
| noted | No | ||||
R3‑256650 | Correction on MRO for CHO with candidate SCG for 38.423 | CATT | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑256651 | Correction on MRO for CHO with candidate SCG and S-CPAC for 37.340 | CATT | draftCR | Endorsement | Yes |
Yes
| noted | No | ||||
R3‑256659 | Correction on beam information | Samsung | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑256660 | Correction on beam information | Samsung | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑256856 | Correction of missing elementary procedure table | ZTE Corporation | CR | Agreement | Yes |
YesMerged in XnAP rapporteur CR
| merged | No | ||||
R3‑257113 | Clarifying the MRO for LTM use-case | Ericsson | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑257114 | BFR in CSI-RS beam | Ericsson | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑256962 | Failure report without RLF report | Huawei, CMCC, Deutsche Telekom | discussion | Yes |
Yes
| noted | No | |||||
R3‑256963 | Failure report without RLF report | Huawei, CMCC, Deutsche Telekom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256964 | Failure report without RLF report | Huawei, CMCC, Deutsche Telekom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256781 | Correction on MRO for LTM failure without RLF report | NEC | discussion | Agreement | Yes |
Yes
| noted | No | ||||
R3‑256752 | Correction of missing stage 2 description of LTM MRO without RLF Report | ZTE Corporation,Google,Pengcheng Laboratory,China Unicom,China Telecom | CR | Agreement | Yes |
Yes
| noted | No | ||||
9.2.2 | R19 AI/ML for NG-RAN | R3‑256523 | Reply to LS on Continuous MDT | SA5(Ericsson) | LS in | Discussion | Yes |
Yes
| noted | No | ||
R3‑256603 | Introduction of predicted PSCell for Mobility Optimization in NR-DC | ZTE Corporation, Qualcomm, Samsung, CATT, CMCC, China Telecom, China Unicom, Ofinno | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256923 | Abnormal conditions for gNB-CU Configuration Update | Ericsson, InterDigital, Jio Platforms, FiberCop | discussion | Approval | Yes |
Yes
| noted | No | ||||
R3‑256924 | Abnormal conditions for gNB-CU Configuration Update | Ericsson, InterDigital, Jio Platforms, FiberCop | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257079 | Corrections of AI/ML-based CCO | Nokia, Ofinno, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256828 | Miscellaneous correction to XnAP - AI/ML for NG-RAN | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256829 | Miscellaneous correction to F1AP - AI/ML for NG-RAN | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256840 | Correction on R19 AIML F1-U stage2 | CMCC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256866 | Correction on AI/ML for NG-RAN | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256867 | Correction to E1AP on AI/ML for NG-RAN | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256925 | Correction for gNB-DU Configuration Update | Ericsson, InterDigital, Jio Platforms, FiberCop | discussion | Approval | Yes |
No
| available | No | ||||
R3‑256926 | Correction for gNB-DU Configuration Update | Ericsson, InterDigital, Jio Platforms, FiberCop | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256927 | Stage 2 corrections for AI/ML based CCO | Ericsson, InterDigital, Jio Platforms, FiberCop | discussion | Approval | Yes |
No
| available | No | ||||
R3‑256928 | Stage 2 corrections for AI/ML based CCO | Ericsson, InterDigital, Jio Platforms, FiberCop | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256929 | Corrections to Performance Delay Monitoring IEs | Ericsson, InterDigital, Jio Platforms, Verizon | discussion | Approval | Yes |
No
| available | No | ||||
R3‑256930 | Semantic description of Performance Delay Monitoring IEs | Ericsson, InterDigital, Jio Platforms, Verizon | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256986 | Correction on AI/ML-based CCO use case | Huawei | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑256987 | Correction on AI/ML-based CCO use case | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257078 | (CR to TS 38.423, TS 37.483, TS 38.300, TS 38.401) Corrections of UE performance and CCO | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑257096 | Alignment on UE Performance Terminology | Nokia, Deutsche Telekom, Verizon Wireless | discussion | Yes |
No
| available | No | |||||
R3‑257097 | UE Performance Delay Monitoring naming alignment | Nokia, Deutsche Telekom, Verizon Wireless | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256935 | Support for Continuous MDT in RAN3 specifications | Ericsson, Deutsche Telekom, FiberCop, Jio Platforms, InterDigital, BT, Orange, Verizon | discussion | Approval | Yes |
No
| available | No | ||||
R3‑256936 | Continuous MDT support | Ericsson, Deutsche Telekom, FiberCop, Jio Platforms, InterDigital, BT, Orange, Verizon | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256937 | Continuous MDT support | Ericsson, Deutsche Telekom, FiberCop, Jio Platforms, InterDigital, BT, Orange, Verizon | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256938 | Continuous MDT support | Ericsson, Deutsche Telekom, FiberCop, Jio Platforms, InterDigital, BT, Orange, Verizon | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256944 | Reply to R3-256523 on Continuous MDT | Ericsson, Deutsche Telekom, FiberCop, Jio Platforms, InterDigital, BT, Orange | LS out | Approval | Yes |
No
| available | No | ||||
R3‑256865 | Completion of Continuous management-based MDT in RAN3 | CATT, ZTE, Samsung,China Telecom, CMCC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256864 | Support for continuous management-based MDT | CATT, ZTE, Samsung,China Telecom, CMCC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256606 | CR to 38.300 to support Continuous MDT collection | ZTE Corporation, CATT, Samsung, China Unicom, China Telecom | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256607 | CR to 37.320 to support Continuous MDT collection | ZTE Corporation, CATT, Samsung, China Unicom, China Telecom | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256690 | Continuous MDT for split architecture | Samsung, CATT, ZTE, CMCC, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257189 | Discussion on the Reply LS from SA5 on Continuous MDT (C-MDT) | Huawei, Jio Platforms, Ofinno | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256982 | Discussion on the Reply LS from SA5 on Continuous MDT (C-MDT) | Huawei, Jio Platforms, Ofinno | discussion | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
R3‑256983 | Introducing support for Continuous management-based MDT (C-MDT) | Huawei, Jio Platforms, Ofinno | draftCR | Endorsement | Yes |
Yes
| withdrawn | Yes | ||||
R3‑256985 | Introducing support for Continuous management-based MDT (C-MDT) | Huawei, Jio Platforms, Ofinno | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
R3‑256984 | Correction on support for Continuous management-based MDT (C-MDT) | Huawei, Jio Platforms, Ofinno | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257187 | Support for Continuous management-based MDT (C-MDT) | Huawei, Jio Platforms, Ofinno | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257188 | Support for Continuous management-based MDT (C-MDT) | Huawei, Jio Platforms, Ofinno | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256800 | Correction on continuous MDT | NEC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257098 | Continuous MDT Discussion | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑256604 | CR to 38.423 to Slice UE performance metrics | ZTE Corporation, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256605 | CR to 37.483 to UE performance per DRB | ZTE Corporation, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256688 | Correction on the reference of Slice Average Packet Loss | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256689 | Correction on the reference of Average Packet Loss | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256798 | Correction on UE performance for AI/ML | NEC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256934 | Corrections to Release-19 Packet Loss measurements in UE Performance for Slicing | Ericsson, InterDigital, Jio Platforms, Verizon | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256978 | Correction on Slice UE Performance | Huawei, FiberCop, BT, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256981 | Correction on UE Performance | Huawei, FiberCop, BT, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
9.2.3 | R19 WAB | R3‑256806 | Correction on WAB NG management | Huawei, CANON Research Centre France, Lenovo | CR | Agreement | Yes |
No
| available | No | ||
R3‑256890 | Correction on handover a WAB-MT to a target WAB-gNB | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256728 | Correction on WAB Xn management | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256761 | Correction on the description of WAB-MT Identifier | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256951 | Corrections for WAB | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257191 | Corrections of WAB | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257190 | (CR TS 38.423): Correction of WAB | Ericsson | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
R3‑256715 | Correction of WAB | Ericsson, Jio Platforms, Qualcomm, CATT | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256714 | Corrections of WAB | Ericsson, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256727 | Correction on WAB | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256760 | Corrections to WAB stage-2 | CATT, Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256889 | Correction on AULI | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256950 | Corrections for WAB | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257138 | Correction to TS 38.401 for WAB | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
9.2.4 | R19 NR Femto | R3‑256516 | LS on security verification related to NR Femto nodes | SA3(HuaWei) | LS in | Discussion | Yes |
No
| available | No | ||
R3‑256729 | Correction on NR femto procedures | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256763 | Correction on GW Context Release Indication | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256879 | Correction of Paging NR Femtos | Nokia, NTT Docomo, BT | discussion | Yes |
No
| available | No | |||||
R3‑256881 | Correction of Paging NR Femtos | Nokia, NTT Docomo, BT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256953 | Corrections for Femto | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257139 | Correction to TS 38.413 for NR Femto | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256762 | Corrections on NR Femto Architecture | CATT | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256807 | Correction on NR Femto functions | Huawei | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256952 | Corrections for Femto | ZTE Corporation | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257092 | Correction of NR Femtos functions | Nokia | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257105 | Correction of NR Femtos Security | Nokia | draftCR | Endorsement | Yes |
No
| available | No | ||||
9.2.5 | R19 Mobility enhancements | R3‑257127 | CSI-RS Resource Set and CSI IM Resource Transfer for inter-CU LTM | Huawei, Jio Platforms, CATT, China Telecom, Lenovo, Nokia | discussion | Yes |
No
| available | No | |||
R3‑257128 | Correction on CSI-RS Resource Set and CSI IM Resource Transfer for inter-CU LTM | Huawei, Jio Platforms, CATT, China Telecom, Lenovo, Nokia | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257129 | Correction on CSI-RS Resource Set and CSI IM Resource Transfer for inter-CU LTM | Huawei, Jio Platforms, CATT, China Telecom, Lenovo, Nokia | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256530 | Discussion on remaining LTM Issues | Nokia | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256825 | Semi-Persistent CSI-RS activation/deactivation with TCI state | Nokia, CATT, China Telecom, | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256872 | Semi-Persistent CSI-RS activation/deactivation with TCI state | CATT, Nokia, ZTE, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256531 | Remaining Conditional LTM Issues | Nokia | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256699 | Discussion on shared CFRA resource for inter-CU LTM | vivo | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256705 | LTM CFRA Resource Information transfer | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256706 | LTM UE Association Information Transfer | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256802 | Early Data Forwarding for subsequent inter-CU LTM | NEC, Huawei, Google, Jio Platforms, Qualcomm Inc, Nokia, Samsung, Lenovo, CATT, LG Electronics, Ericsson | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256803 | Early Data Forwarding for subsequent MCG LTM | NEC, Huawei, Google, Jio Platforms, Qualcomm Inc, Nokia, Samsung, Lenovo, CATT, LG Electronics, Ericsson | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256830 | [Draft TP for TS 38.473, TS 38.423] Remaining issues in Inter-CU LTM | Qualcomm Incorporated | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256831 | [Draft TP for TS 38.473, TS 38.401] Remaining issues in Intra-CU Conditional LTM | Qualcomm Incorporated | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256857 | Essential Corrections for Inter-CU (SCG) LTM | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256858 | (CR to 38.473) Essential correction for Inter-CU SCG LTM | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256871 | Essential correction for inter-CU LTM on F1AP | CATT,Huawei, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256873 | Essential correction on inter-CU LTM in DC | CATT,Huawei, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256874 | Discussion on LTM candidate PSCell cancel procedure in DC | CATT,Huawei | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256875 | Correction on LTM candidate PSCell cancel procedure in DC | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257033 | Correction on SN initiated inter-SN SCG LTM procedure | Ofinno, LLC | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257042 | PRACH resources for RACH-less LTM | Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO | discussion | Yes |
No
| available | No | |||||
R3‑257043 | PRACH resources for Inter-CU LTM | Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257044 | PRACH resources for RACH-less LTM | Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257045 | PRACH resource for RACH-less LTM | Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257046 | PRACH resources for RACH-less LTM | Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257047 | Fast LTM recovery for Inter-CU LTM | Ericsson, Jio Platforms, Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑257048 | Fast LTM Recovery for Inter-CU LTM | Ericsson, Jio Platforms, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257050 | CSI-RS Coordination for inter-gNB LTM | Ericsson | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257058 | Corrections for LTM in NR-DC | Ericsson | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257125 | Correction on LTM Cell Switch Notification | LG Electronics Inc. | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257126 | Correction related to LTM Security Information | LG Electronics Inc. | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257130 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM | Huawei, Jio Platforms, CMCC, China Telecom, NEC, Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑257131 | Correction on CSI report configuration for CSI acquisition for inter-CU LTM | Huawei, Jio Platforms, CMCC, China Telecom, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257132 | Correction on CSI report configuration for CSI acquisition for inter-CU LTM | Huawei, Jio Platforms, CMCC, China Telecom, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257146 | Essential corrections to XnAP for inter-CU LTM | Huawei, Jio Platforms, CMCC, Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑257147 | Essential corrections to XnAP for inter-CU LTM | Huawei, Jio Platforms, CMCC, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257148 | Exchange of early RACH Resources Requester ID for inter-CU LTM | Huawei, Jio Platforms, CATT, CMCC, China Telecom, Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑257149 | Exchange of early RACH Resources Requester ID for inter-CU LTM | Huawei, Jio Platforms, CATT, CMCC, China Telecom, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257150 | Correction on the Rel-19 set ID assignment in inter-CU LTM | Huawei, Jio Platforms, CATT, China Telecom | discussion | Yes |
No
| available | No | |||||
R3‑257151 | Correction on the Rel-19 set ID assignment in inter-CU LTM | Huawei, Jio Platforms, CATT, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257152 | Correction on inter-CU LTM and conditional intra-CU LTM | Huawei, Jio Platforms, CATT, China Telecom, Lenovo | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257153 | Correction on inter-CU LTM | Huawei, Jio Platforms, CATT, China Telecom, Lenovo | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257154 | Corrections on inter-CU MCG LTM without SN change | Huawei, Jio Platforms, Lenovo, Google | discussion | Yes |
No
| available | No | |||||
R3‑257155 | Correction on security key update for inter-CU MCG LTM | Huawei, Jio Platforms, China Telecom, Lenovo, ,Google | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257156 | Stage 2 corrections to inter-CU MCG LTM | Huawei, Jio Platforms, Lenovo, Google | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257157 | Discussion on supporting inter-CU SCG LTM and the L2 reset function in inter-CU LTM | discussion | Decision | Yes |
No
| available | No | |||||
R3‑257158 | Correction to L2 reset in inter-CU LTM | CR | Agreement | Yes |
No
| available | No | |||||
R3‑257172 | Remaining issues for CSI-RS coordination | Ericsson, Jio Platforms, Verizon Wireless, LG Electronics | discussion | Yes |
No
| available | No | |||||
R3‑257173 | Corrections on CSI-RS coordination for LTM | Ericsson, Jio Platforms, Verizon Wireless, LG Electronics | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257174 | Corrections on CSI-RS coordination for LTM | Ericsson, Jio Platforms, Verizon Wireless, LG Electronics | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257175 | Corrections on Inter-CU LTM | Ericsson, Lenovo, LG Electronics | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256552 | LTM CFRA Resource Information transfer | ZTE Corporation | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
R3‑256553 | LTM UE Association Information Transfer | ZTE Corporation | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
R3‑257038 | Correction on ETA resource release in DU | Ofinno, LLC | CR | Agreement | Yes |
Yes
| withdrawn | Yes | R3‑257117 | |||
9.2.6 | R19 NR NTN enhancements | R3‑257196 | Response to R3-256631, R3-256734, R3-256842, R3-256614 | Ericsson, Thales, Deutsche Telekom, ESA, Airbus | response | Discussion | No |
No
| available | No | ||
R3‑256919 | Adding Extended AMF Name to NG REMOVAL RESPONSE message | Ericsson, Thales, LG Electronics, Xiaomi, CATT, ZTE, Nokia, Nokia Shanghai Bell, Eutelsat Group, Deutsche Telekom, Qualcomm Incorporated, Airbus, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256743 | Correction of TNL address change and O&M requirements | Huawei, Deutsche Telekom, Jio Platforms | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256744 | Correction of NG Removal Response and Broadcast Session Modification messages | Huawei, Deutsche Telekom, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256631 | Further discussion on NG Suspend/Resume | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256632 | Support of NG Suspend and Resume | CATT, Nokia, Nokia Shanghai Bell, ZTE Corporation, Qualcomm, CMCC, Samsung, China Telecom, LG Electronics, Xiaomi | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256633 | [DRAFT] LS on Support of NG/S1 Suspend and Resume | CATT | LS out | Approval | Yes |
No
| available | No | ||||
R3‑256675 | NG Suspend and Resume during Hard FLSO | ZTE Corporation, Nokia, Nokia Shanghai Bell, CATT, Qualcomm, CMCC, Samsung, China Telecom, LG Electronics, Xiaomi | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256920 | Short Feeder Link Interruption and UE Retention | Ericsson, Jio Platforms, Thales | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256921 | UE Context Retention at SCTP Recovery | Ericsson, Jio Platforms, Thales | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256734 | Discussion on UE Retention at hard FLSO | Nokia, Nokia Shanghai Bell, ZTE Corporation, CATT, Qualcomm, CMCC, Samsung, China Telecom, LG Electronics, Xiaomi | discussion | Yes |
No
| available | No | |||||
R3‑256787 | NG interface suspend and resume indication for hard feeder link switchover | NEC | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256788 | NG interface suspend and resume indication | NEC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256842 | Discussion on introducing NG suspend resume during hard FLSO | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
9.2.7 | R19 Ambient IoT | R3‑256512 | Reply LS to Reply LS on the removal of service type information | SA2(LGE) | LS in | Discussion | Yes |
No
| available | No | ||
R3‑256522 | Reply LS on Ambient IoT progress of RAN3 on OAM requirements | SA5(HuaWei) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑256525 | LS on Structure updates of AIoT Identifiers | CT4(CICT mobile) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑256504 | LS on the maximum supported AIoT NAS container length | CT1(Lenovo) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑256517 | Reply LS on paging ID length | SA3(CATT) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑256634 | Corrections to A-IoT context definition | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256641 | Consideration on A-IoT leftovers on IE details | Huawei, CMCC, China Unicom, China Telecom | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256642 | Correction on A-IoT leftovers on IE details | Huawei, CMCC, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256643 | Consideration on Interface Management procedures for A-IoT | Huawei, CMCC, Lenovo, China Unicom, China Telecom | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256644 | Correction on Interface Management procedures for A-IoT | Huawei, CMCC, Lenovo, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256661 | Correction on AIoT IE encoding | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256708 | Correction on AIoT | ZTE Corporation, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256882 | Open issues of Ambient IOT Release 19 | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑256883 | Correction of Ambient IOT | Nokia | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257061 | On further open issue for Rel-19 AIoT | Ericsson | discussion | Yes |
No
| available | No | |||||
R3‑256554 | Clarification on AIoT | ZTE Corporation, China Telecom | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
R3‑256555 | Correction on AIoT | ZTE Corporation, China Telecom | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
R3‑256639 | Consideration on A-IoT dedicated Cause values | Huawei, CMCC, Futurewei, Lenovo, China Unicom, China Telecom | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256640 | Correction on A-IoT dedicated Cause values | Huawei, CMCC, Futurewei, Lenovo, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256635 | Corrections to A-IoT procedure texts | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256707 | Clarification on AIoT | ZTE Corporation, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256758 | Correction on sercurity support in A-IoT | Xiaomi | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256759 | Correction on sercurity support in A-IoT | Xiaomi | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257060 | On security related open topics for Rel-19 AIoT | Ericsson | discussion | Yes |
No
| available | No | |||||
R3‑256789 | Cyphering indication for A-IoT NAS Command Request PDU | NEC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256790 | A-IoT device identifier privacy protection impact on RAN3 | NEC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256844 | Correction on A-IoT security aspects | CMCC, Huawei | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256845 | Correction on A-IoT security aspects | CMCC, Huawei | CR | Agreement | Yes |
No
| available | No | ||||
9.2.8 | R19 Network Energy Saving | R3‑256513 | Reply LS on energy saving indication from CN to RAN | SA2(LGE) | LS in | Discussion | Yes |
No
| available | No | ||
R3‑256703 | Correction on OD-SIB1 | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256704 | Correction on OD-SIB1 | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256791 | Correction on allowed cell list for OD-SSB | NEC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256792 | Correction on inter-gNB OD-SIB1 capability transfer | NEC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257088 | Corrections to Xn support for on-demand SIB1 coordination | Ericsson, Qualcomm, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257089 | Corrections to F1 support of Network Energy Saving Enhancement | Ericsson, Qualcomm, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256764 | Corrections on OD-SIB1 Configuration Provision | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256899 | Correction of OD-SIB1 procedure for network energy saving | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256900 | Correction of OD-SIB1 procedure for network energy saving | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257080 | Discussion on ANR for OD-SIB1 | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑257081 | Correction on ANR for OD-SIB1 | Nokia | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257091 | Corrections to OD-SIB1 Configuration Provision Status Update | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257140 | Correction to TS 38.423 for NES | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257141 | Correction to TS 38.473 for NES | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257087 | Corrections to stage-2 specification for support for on-demand SIB1 | Ericsson, Qualcomm, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256765 | Corrections on OD-SIB1 Stage-2 | CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257090 | Corrections to TS 38.420 on support of Network Energy Saving Enhancement | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
9.2.9 | R19 Low Power WUS/WUR | R3‑256507 | LS on enabling/disabling LP-WUS per UE with NAS signalling | RAN2(HuaWei) | LS in | Discussion | Yes |
No
| available | No | ||
R3‑256766 | On introducing LP-WUS disabling indication | CATT, Nokia, Huawei, Ericsson, ZTE, Qualcomm | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256956 | Introducing of LP-WUS disabling | ZTE Corporation, Ericsson, Nokia, Huawei, Qualcomm, CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257019 | Introducing LP-WUS disabling indication | Ericsson, ZTE, Huawei, CATT, Nokia, Qualcomm Inc. | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256901 | [draft] Reply LS on enabling/disabling LP-WUS per UE with NAS signalling | Huawei | LS out | Approval | Yes |
No
| available | No | ||||
R3‑256697 | Discussion on RAN2 LS on per-UE enable disable LP-WUS by NAS | vivo | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256698 | (TP for 38.413 38.423 38.473) Support per-UE enable disable LP-WUS by NAS | vivo | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256884 | Correction of LP-WUS Assistance Information | Nokia | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256885 | Correction of LP-WUS Assistance Information | Nokia | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256902 | Correction of Further Extended UE Identity Index Value | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256903 | Correction of RAN Paging for low-power wake-up signal and receiver | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257020 | LP-WUS correction | Ericsson | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257021 | LS on LP-WUS usage over Xn | Ericsson | LS out | Approval | Yes |
No
| available | No | ||||
9.2.10 | R19 Evolution of Duplex Operation | R3‑256508 | Reply LS on simultaneous configuration of SBFD and DC | RAN2(ZTE) | LS in | Discussion | Yes |
No
| available | No | ||
R3‑256653 | Correction on SBFD RACH configuration for XnAP | CATT, Qualcomm, CMCC, Charter | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256654 | Correction on SBFD RACH configuration for F1AP | CATT, Qualcomm, CMCC, Charter | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256692 | Correction on the indication of L1 UE-to-UE CLI | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257068 | Corrections of semantic descriptions for SBFD IEs | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257069 | Corrections to the procedures supporting for SBFD | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257162 | Correction to XnAP on CLI Indication | ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257163 | Correction to F1AP on CLI Indication | ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257164 | Correction to F1AP on SBFD RACH configuration | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257178 | Corrections to SBFD operation | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257176 | Clarification to UE-to-UE CLI mitigation in SBFD operation | Huawei, CATT, China Unicom | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256691 | Correction on the introduction of SBFD | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257177 | Clarification to CLI mitigation in SBFD operation | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256652 | Correction on Evolution of NR duplex operation for 38.470 | CATT | CR | Agreement | Yes |
No
| available | No | ||||
9.2.11 | R19 AI/ML for air interface | R3‑256511 | LS to RAN1 and RAN3 on NW side data collection | RAN2(ZTE) | LS in | Discussion | Yes |
No
| available | No | ||
R3‑256509 | LS on User consent for Data collection at the UE for NW-side model training | RAN2(NTT DoCoMo) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑256510 | Reply LS on OAM-centric solution for NW-side data collection | RAN2(HuaWei) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑256514 | Reply LS on signalling feasibility of dataset and parameter sharing | SA2(Samsung) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑256520 | Reply LS on signalling feasibility of dataset and parameter sharing | SA5(HuaWei) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑256693 | Correction on the ASN.1 of Positioning Data Information for data collection | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256757 | Correction on positioning data collection for case 3a | Xiaomi | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256780 | Remaining Issue on AI/ML based Positioning Accuracy Enhancement | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256989 | (NRPPa CR & draftCR to TS 38.305) Miscellaneous corrections for supporting AI/ML-based positioning | Huawei | other | Agreement | Yes |
No
| available | No | ||||
R3‑257022 | Correction on Positioning Data Collection Needed | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257099 | Discussion on terminology related to AI/ML for PHY | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑257100 | Corrections on support of AI/ML assisted positioning with gNB-side AI/ML model | Nokia | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257171 | Correction to NRPPa on AI/ML assisted positioning | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257170 | Discussion on reply LS on NW side data collection | ZTE Corporation | discussion | Yes |
No
| available | No | |||||
R3‑256851 | Discussion on NW side data collection | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256850 | [Draft] Reply LS on NW side data collection | CMCC | LS out | Approval | Yes |
No
| available | No | ||||
R3‑256988 | (Draft Reply LS to RAN2) Discussion on the Reply LS from RAN2 on NW side data collection | Huawei | other | Agreement | Yes |
No
| available | No | ||||
R3‑257075 | Discussion on incoming LSes to RAN3 on AIML for PHY | Ericsson | discussion | Approval | Yes |
No
| available | No | ||||
R3‑256735 | [Draft LS] Reply LS to RAN2 about NW-side data colleciton | ZTE Corporation | LS out | Approval | Yes |
No
| available | No | ||||
9.2.12 | R19 NR XR Enhancements | R3‑256655 | Correction on PDU Set based QoS handling | CATT, Nokia, Nokia Shanghai Bell, Huawei, Offinno, ZTE, Ericsson | draftCR | Endorsement | Yes |
No
| available | No | ||
R3‑256808 | Correction on PDU Set handling during Handover | Huawei, Nokia, Nokia Shanghai Bell, Ericsson, CATT, Offinno, ZTE | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256891 | Add the missing behavior text for DL PDU Set Information Marking Support Indication | Nokia, Nokia Shanghai Bell, CATT, Qualcomm, ZTE, Ericsson, Ofinno | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257166 | Correction on stage 3 description on Indication of Bitrate Adaptation IE in NGAP | ZTE Corporation, Nokia, Nokia Shanghai Bell,CATT, Qualcomm, Huawei, Ericsson, | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257034 | Add procedure texts on XR uplink rate control in NGAP | Ofinno | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257143 | Correction to TS 38.413 for XR | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256730 | Discussion on RLC enhancement for XR | Huawei | discussion | Yes |
No
| available | No | |||||
R3‑256731 | Correction on RLC enhancement for XR | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257023 | RAN status indication of Available Bitrate reporting | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257142 | Correction to TS 37.483 for XR | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257165 | Correction on semantic description for Notification Cause IE in NGAP | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257167 | Discussion on UL Rate Control on XR with the correction and draft LS | ZTE Corporation | discussion | Approval | Yes |
No
| available | No | ||||
9.2.13 | R19 NR Sidelink Multi-hop Relay | R3‑257186 | Corrections on Multi-hop relay | LG Electronics Inc. | CR | Agreement | Yes |
No
| available | No | ||
R3‑256955 | Corrections for Multi-hop relay | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256968 | Correction for Multihop relay | Huawei | discussion | Yes |
No
| available | No | |||||
R3‑256969 | Correction for Multihop relay | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257030 | Corrections on SL Multi-hop | Ericsson | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256954 | Corrections for multi-hop relay | ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256662 | Correction on multihop initial access | Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257031 | Corrections on SL Multi-hop | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
9.2.14 | Other | R3‑256636 | Correction to Positioning activation and deactivation procedure | CATT, Samsung, ZTE, Huawei | draftCR | Endorsement | Yes |
No
| available | No | ||
R3‑256637 | Correction to Positioning activation and deactivation procedure | CATT, Samsung, ZTE, Huawei | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256663 | Discussion on positioning activation and deactivation procedure | Samsung, CATT, ZTE, Huawei | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256664 | Correction to positioning activation and deactivation procedure | Samsung, CATT, ZTE Corporation, Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256665 | Correction to positioning activation and deactivation procedure | Samsung, CATT, ZTE Corporation, Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256678 | Correction to positioning activation and deactivation procedure | Huawei, Samsung, CATT, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256679 | Correction to positioning activation and deactivation procedure | Huawei, Samsung, CATT, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256680 | Correction to positioning activation and deactivation procedure | ZTE Corporation, Samsung, CATT, Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256681 | Correction to positioning activation and deactivation procedure | ZTE Corporation, Samsung, CATT, Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256815 | Further discussion on paging capability loss issue | Huawei, China Unicom, China Telecom | discussion | Yes |
No
| available | No | |||||
R3‑256816 | Avoiding paging capability loss for CN paging | Huawei, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256817 | Avoiding paging capability loss for CN paging | Huawei, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256818 | Avoiding paging capability loss for CN paging | Huawei, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256819 | Avoiding paging capability loss for CN paging | Huawei, China Unicom, China Telecom | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256820 | Avoiding paging capability loss for CN paging | Huawei, China Unicom, China Telecom | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256821 | Avoiding paging capability loss for CN paging | Huawei, China Unicom, China Telecom | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257015 | Correction on Paging Loss issue | Ericsson, Nokia, Jio Platforms | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257016 | Correction on Paging Loss issue | Ericsson, Nokia, Jio Platforms | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257017 | Correction on Paging Loss issue | Ericsson, Nokia, Jio Platforms | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257018 | [DRAFT] Reply LS on Response to Reply LS on paging capability loss issue | Ericsson | LS out | Approval | Yes |
No
| available | No | ||||
R3‑257106 | Correction of UE Radio Capability for Paging | Nokia, Ericsson, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257107 | Correction of UE Radio Capability for Paging | Nokia, Ericsson, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257108 | Correction of UE Radio Capability for Paging | Nokia, Ericsson, Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257110 | Response LS on Paging Capability Loss Issue | Nokia | LS out | Approval | Yes |
No
| available | No | ||||
R3‑257053 | Missing UE radio paging capabilities | Vodafone GmbH | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑257054 | Paging capability loss in RAN | Vodafone | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257055 | Paging capability loss in RAN | Vodafone | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257056 | Paging capability loss in RAN | Vodafone GmbH | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256767 | Discussion on Paging capability missing issue | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256822 | Avoiding UE paging loss | CATT | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256823 | Avoiding UE paging loss | CATT | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256824 | Avoiding UE paging loss | CATT | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256957 | Remaining issues for paging capability loss | ZTE Corporation | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256958 | [draft] Reply LS on paging capability loss issue | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
R3‑256527 | Clarification for propagation of MDT Configuration in stage2 | ZTE Corporation,China Unicom,China Telecom,CMCC,Huawei | other | Agreement | Yes |
No
| available | No | R3‑255737 | |||
R3‑256598 | Clarification for propagation of roaming and access restrictions | Samsung | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256682 | Specifying procedure texts for the Core Network Assistance Information for RRC INACTIVE IE | Huawei, Ericsson, Nokia | CR | Agreement | Yes |
No
| available | No | R3‑255232 | |||
R3‑256995 | Extensions for enumerated type definitions over several Releases - and what can go wrong | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | discussion | Discussion | Yes |
No
| available | No | R3‑255560 | |||
R3‑256996 | Correcting the extension of FR1-bandwidth type definition | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement | Yes |
No
| available | No | R3‑255561 | |||
R3‑256997 | Correcting the extension of FR1-bandwidth type definition | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement | Yes |
No
| available | No | R3‑255562 | |||
R3‑256998 | Correcting the IE extension definition for bandwidth SRS | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement | Yes |
No
| available | No | R3‑255563 | |||
R3‑256999 | Correcting the IE extension definition for bandwidth SRS | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement | Yes |
No
| available | No | R3‑255564 | |||
R3‑257000 | Correcting the IE extension definition for SRS Pos SIB Type | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement | Yes |
No
| available | No | R3‑255565 | |||
R3‑257037 | Addition of PDCP discard timer for scheduling with DSR | Ericsson, Qualcomm Inc., Jio Platforms | CR | Agreement | Yes |
No
| available | No | R3‑255566 | |||
R3‑257039 | Addition of PDCP discard timer for scheduling with DSR | Ericsson, Qualcomm Inc., Jio Platforms | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256563 | Additional procedure text for Data Collection Update | ZTE Corporation, Ercisson, Samsung, NEC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256564 | Correction on the description of UE Context Information - Retrieve UE Context Response | ZTE Corporation, Nokia, Huawei, CATT, Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256566 | Correction of Transmission Bandwidth Asymmetric | Nokia, Huawei, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256567 | Correction of Transmission Bandwidth Asymmetric | Nokia, Huawei, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256568 | Correction of Transmission Bandwidth Asymmetric | Nokia, Huawei, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256569 | Correction of Transmission Bandwidth Asymmetric | Nokia, Huawei, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256570 | Correction of Transmission Bandwidth Asymmetric | Nokia, Huawei, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256669 | Correction of Transmission Bandwidth Asymmetric | Huawei, Nokia, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256670 | Correction of Transmission Bandwidth Asymmetric | Huawei, Nokia, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256671 | Correction of Transmission Bandwidth Asymmetric | Huawei, Nokia, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256672 | Correction of Transmission Bandwidth Asymmetric | Huawei, Nokia, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256673 | Correction of Transmission Bandwidth Asymmetric | Huawei, Nokia, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256621 | Discussion on UL data forwarding | CATT,Huawei | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256745 | Correction of time-based handover for NR NTN | Huawei, Deutsche Telekom, Jio Platforms, CATT, Ericsson | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256746 | Correction of time-based handover for NR NTN | Huawei, Deutsche Telekom, Jio Platforms, CATT, Ericsson | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256753 | Correction on UHI | ZTE Corporation,China Telecom, Pengcheng Laboratory | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256754 | Correction on UHI | ZTE Corporation,China Telecom, Pengcheng Laboratory | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256804 | Correction on QNC | Huawei, Nokia, Nokia Shanghai Bell, China Telecom, CMCC | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256805 | Correction on QNC | Huawei, Nokia, Nokia Shanghai Bell, China Telecom, CMCC | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑256859 | R18 correction on the CU-DU Mobility Initiation Request message | Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256860 | R19 correction on the CU-DU Mobility Initiation Request message | Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256892 | Correction on Notification Control Indication | Nokia, Nokia Shanghai Bell, Huawei, CMCC, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256893 | Correction on Notification Control Indication | Nokia, Nokia Shanghai Bell, Huawei, CMCC, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256898 | Correction on Configured TAC | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257001 | LTM Resource consumption for the target cells | SONY, Ericsson, vivo, Jio Platforms, LG Electronics | discussion | Yes |
No
| available | No | |||||
R3‑257013 | Addition of 2Rx XR UE Capability | Ericsson, Qualcomm inc. Nokia, Nokia Shanghai Bell, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257014 | Addition of 2Rx XR UE Capability | Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257026 | Correction for Cell Switch execution | SONY, Ericsson, vivo, Jio Platforms, LG Electronics | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑257028 | Correction for Cell Switch execution | Ericsson, Sony, Jio Platforms, LG Electronics, vivo | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257029 | Correction for Cell Switch execution | Ericsson, Sony, Jio Platforms, LG Electronics, vivo | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257036 | Correction on ETA resource release in DU | Ofinno | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257117 | Correction on ETA resource release in DU | Ofinno | CR | Agreement | Yes |
No
| available | No | R3‑257038 | |||
R3‑257101 | Alignment of DATA COLLECTION UPDATE messages between Rel-18 and Rel-19 | Nokia, Deutsche Telekom, FiberCop, Orange | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257133 | Discussion on TNLA handling during Xn handover | DOCOMO Communications Lab. | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑257134 | Clarification on TNLA handling during Xn handover | NTT DOCOMO | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257135 | Clarification on TNLA handling during Xn handover | NTT DOCOMO | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257136 | Clarification on TNLA handling during Xn handover | NTT DOCOMO | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257137 | Clarification on TNLA handling during Xn handover | NTT DOCOMO | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257182 | Connection of Secondary RAT Data Usage Report for NG based handover | Huawei, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257183 | Connection of Secondary RAT Data Usage Report for Xn based handover | Huawei, China Unicom, China Telecom | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256768 | withdraw | CATT | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
R3‑256769 | withdraw | CATT | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
R3‑256770 | withdraw | CATT | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
R3‑256876 | Correction on Reference Signal for Positioning | China Telecom, China Unicom, CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256877 | Correction on Reference Signal for Positioning | China Telecom, China Unicom, CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256878 | Correction on Reference Signal for Positioning | China Telecom, China Unicom, CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑256880 | Correction on Reference Signal for Positioning | China Telecom, China Unicom, CATT | CR | Agreement | Yes |
No
| available | No | ||||
9.3 | R19 Rapporteur Corrections | R3‑256894 | Correction on the reference to TS 36.331 IEs | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
No
| available | No | ||
R3‑256965 | Rapporteur Corrections | Huawei | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257024 | NRPPa Rapporteur Corrections | Ericsson, Nokia | CR | Agreement | Yes |
No
| available | No | ||||
R3‑257062 | [Draft] Rapporteur Rel-19 Corrections | Ericsson | draftCR | Agreement | Yes |
No
| available | No | ||||
R3‑257120 | Rapporteur's editorial corrections for E1AP | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
10 | Study on 6G Radio |   | ||||||||||
10.1 | General | R3‑256533 | LS on Guidance on 6G data related work tasks | TSG SA(China mobile) | LS in | Discussion | Yes |
No
| available | No | ||
R3‑256534 | Reply to LS on Early Alignment on Access Stratum security aspects | TSG SA(Vodafone) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑256535 | LS on Early Alignment on Access Stratum security aspects | TSG RAN(Vodafone) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑256536 | LS on 6G fronthaul | TSG RAN(Nokia) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑256939 | Workplan for Rel-20 Study of 6GR | Vodafone GmbH | Work Plan | Decision | Yes |
No
| available | No | ||||
R3‑257035 | Skeleton for 38.760-3 | Vodafone GmbH | draft TR | Endorsement | Yes |
No
| available | No | ||||
10.2 | Overall RAN architecture |   | ||||||||||
10.2.1 | General principles and requirements | R3‑256539 | RAN architecture general principles and requirements | ZTE Corporation | discussion | Yes |
No
| available | No | |||
R3‑256544 | Discussion on Feasibility of RAN Service Based Architecture | FiberCop, Jio Platforms, KT Corp., Qualcomm Inc., Telstra | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256556 | Initial discussion on 6G study in RAN3 and 6G RAN general principles and requirements | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑256571 | 6G RAN general principles and requirements | Qualcomm Inc, Charter Communications, T-Mobile USA, Verizon Wireless, KT Corp , Tejas Networks, Fujitsu, Rakuten, NTT DOCOMO, JIO Platforms, Reliance JIO, FiberCop, CEWiT, Telstra | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256592 | Discussion on RAN architecture principle and requirement | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256615 | Discussion on general principles and requirements for 6G RAN | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256622 | General principles and requirements on RAN architecture | Xiaomi | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256638 | Discussion on the general principles and requirements of 6G NTN | CSCN | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256687 | High-level principles and requirements for 6G Architecture | Tejas Network Limited | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256716 | 6G Service Aware RAN Architecture Option | T-Mobile USA Inc. | discussion | Yes |
No
| available | No | |||||
R3‑256718 | E911 Voice Support for 6G | T-Mobile USA Inc. | discussion | Yes |
No
| available | No | |||||
R3‑256777 | 6G overall RAN architecture principle and requirements | NEC | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256846 | Considerations on RAN data collection function for 6G RAN | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256904 | General Principles and Requirements of 6G RAN Architecture | Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑256945 | (TP to 6G TR) General Principles and Requirements for the 6G RAN architecture | Ericsson | other | Agreement | Yes |
No
| available | No | ||||
R3‑256970 | Considerations on 6G General principles and requirements | China Unicom | discussion | Approval | Yes |
No
| available | No | ||||
R3‑257040 | RAN3 naming | InterDigital, Inc. | discussion | Decision | Yes |
No
| available | No | ||||
R3‑257041 | 6G Data Management Framework Considerations | AT&T | discussion | Decision | Yes |
No
| available | No | ||||
R3‑257057 | 6G RAN Sharing for Multiple Operator Core Networks | Boost Mobile Network | discussion | Decision | Yes |
No
| available | No | ||||
R3‑257067 | Discussion on 6G General Principles and Requirements | Jio Platforms | discussion | Yes |
No
| available | No | |||||
R3‑257121 | Design principles for 6G RAN architecture | LG Electronics Inc. | discussion | Decision | Yes |
No
| available | No | ||||
R3‑257159 | Requirements and deployment scenarios toward 6G RAN | DOCOMO Communications Lab. | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑257179 | Consideration on General requirement and priniciples for RAN architecture | Huawei | other | Agreement | Yes |
No
| available | No | ||||
R3‑257192 | 6G RAN overall architecture for NTN | THALES, Echostar | discussion | Decision | Yes |
No
| available | No | ||||
10.2.2 | RAN functions and logical architecture | R3‑256543 | Discussion on RAN logical architecture and functions | ZTE Corporation | discussion | Decision | Yes |
No
| available | No | ||
R3‑256545 | Discussion on possible RAN internal architecture evolution towards Service Based Architecture | FiberCop, Jio Platforms, KT Corp., Qualcomm Inc., Telstra | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256557 | Resilient 6G RAN Architecture | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑256574 | Discussion on 6G RAN logical architecture | Qualcomm Incorporated | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256593 | Discussion on 6G RAN logical architecture and 6G RAN function | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256616 | Discussion on 6G RAN Logical Architecture | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256623 | Initial views on RAN logical architecture | Xiaomi | other | Agreement | Yes |
No
| available | No | ||||
R3‑256709 | Discussion on 6G overall RAN architecture | OPPO | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256778 | 6G RAN function and logical architecture | NEC | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256812 | RAN Architecture | InterDigital, Inc. | other | Agreement | Yes |
No
| available | No | ||||
R3‑256847 | Initial consideration on RAN functions and logical architecture | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256905 | 6G RAN Logical Architecture | Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑256946 | (TP to 6G TR) Functions and Architecture for the 6G RAN | Ericsson | other | Agreement | Yes |
No
| available | No | ||||
R3‑257066 | Discussion on 6G RAN Functions and Architecture | Jio Platforms | discussion | Yes |
No
| available | No | |||||
R3‑257180 | Consideration on RAN logical architecture | Huawei | other | Agreement | Yes |
No
| available | No | ||||
10.3 | RAN-CN interface | R3‑256994 | Discussion on RAN-CN interface | Rakuten Mobile, Inc | discussion | No |
Yes
| withdrawn | Yes | |||
10.3.1 | General principles and requirements | R3‑256540 | Discussion on Principles of RAN-CN Interface | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||
R3‑256575 | 6G RAN-CN interface: General principles and requirements | Qualcomm Inc, NTT Docomo Inc, Fibercop, Tejas Network Limited, KT Corp, Charter Communications Inc | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256590 | [TP to BL pCR] General principles and functions on RAN-CN interface | Huawei, Jio Platforms | other | Agreement | Yes |
No
| available | No | ||||
R3‑256594 | Discussion on general principles of RAN-CN interface | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256617 | Discussion on general principles and requirements on RAN-CN interface | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256624 | General principles and requirements on RAN-CN interface | Xiaomi | other | Agreement | Yes |
No
| available | No | ||||
R3‑256717 | AI Native Architecture for 6G | T-Mobile USA Inc. | discussion | Yes |
No
| available | No | |||||
R3‑256779 | On RAN-CN interface principle and requirement | NEC | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256811 | RAN-CN General Principles | InterDigital, Inc. | other | Agreement | Yes |
No
| available | No | ||||
R3‑256852 | Discussion on general principles and requirements for RAN-CN interface | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256886 | 6G RAN-CN Interface Requirements and Principles | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑256906 | General Principles and Requirements of 6G RAN-CN Functional Split and Interface | Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑256940 | SBI and Point2Point Definitions | Vodafone GmbH | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256949 | General Principles and Requirements for RAN-CN interface | China Telecom | discussion | Yes |
No
| available | No | |||||
R3‑257051 | General principles and requirements for 6G RAN-CN interface | LG Electronics | other | Agreement | Yes |
No
| available | No | ||||
R3‑257063 | On General Principles and Requirements for the 6G RAN-CN interface | Ericsson | discussion | Yes |
No
| available | No | |||||
R3‑257064 | [potentialTP for TR 38.xxx] On Principles and Requirements for the 6G RAN-CN interface | Ericsson | discussion | Yes |
No
| available | No | |||||
R3‑257109 | General Principles and Requirements for RAN-CN interface | CEWiT, Tejas Networks | discussion | Yes |
No
| available | No | |||||
R3‑257160 | Requirements toward 6G RAN-CN functional split | DOCOMO Communications Lab. | discussion | Discussion | Yes |
No
| available | No | ||||
10.3.2 | RAN-CN interface options | R3‑256542 | Consideration on 6G RAN-CN interface options | ZTE Corporation | discussion | Approval | Yes |
No
| available | No | ||
R3‑256576 | Discussion on 6G RAN-CN Interface options | Qualcomm Inc, NTT Docomo Inc, Fibercop, Tejas Network Limited, KT Corp, Charter Communications Inc | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256581 | RAN-CN interface considerations | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256591 | [TP to BL pCR] Consideration on RAN-CN interface options | Huawei, Jio Platforms | other | Agreement | Yes |
No
| available | No | ||||
R3‑256595 | Discussion on RAN-CN interface design | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256618 | Considerations on 6G RAN-CN interface options | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256625 | RAN-CN interface and protocol option | Xiaomi | other | Agreement | Yes |
No
| available | No | ||||
R3‑256710 | Discussion on 6G RAN-CN interfaces | OPPO | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256719 | Discussion on possible RAN-CN interface evolution towards Service Based Architecture | FiberCop, Jio Platforms, KT Corp., Qualcomm Inc., Telstra | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256796 | Considerations on RAN-CN interface | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256809 | Service Based Core Network | InterDigital, Inc. | other | Agreement | Yes |
No
| available | No | ||||
R3‑256853 | Discussion on RAN-CN interface options | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256887 | 6G RAN-CN Enhanced P2P Solution | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑256907 | 6G RAN-CN Interface Options | Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑257052 | Consideration on RAN-CN interface options | LG Electronics | other | Agreement | Yes |
No
| available | No | ||||
R3‑257059 | Discussion on RAN-CN interface Principal Interface Options | Jio Platforms, FiberCop | discussion | Yes |
No
| available | No | |||||
R3‑257161 | Candidate options for 6G RAN-CN interface | DOCOMO Communications Lab. | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑257181 | Discussion on RAN-CN interface | Rakuten Mobile, Inc | discussion | Yes |
No
| available | No | |||||
10.4 | RAN internal functional split and interfaces | R3‑256541 | Discussion on internal functional split and interfaces | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||
R3‑256577 | 6G RAN internal functional split and interfaces | Qualcomm Incorporated | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256583 | Views on 6G RAN internal functional split and interfaces | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256596 | Discussion on RAN internal architecture | Samsung, Verizon, NTT DoCoMo, Rakuten | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256620 | Consideration on internal split of 6G RAN node | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256626 | RAN internal functional split and interfaces | Xiaomi | other | Agreement | Yes |
No
| available | No | ||||
R3‑256630 | 6G RAN internal functional split and interfaces | Nokia | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256700 | Consideration on RAN internal function split and interfaces | Huawei | other | Agreement | Yes |
No
| available | No | ||||
R3‑256711 | Discussion on 6G RAN internal interfaces | OPPO | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256736 | Initial views on 6G RAN internal functions split | Fujitsu Limited | discussion | Yes |
No
| available | No | |||||
R3‑256801 | Discussion on RAN internal functional split and interfaces | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256810 | 6G Xn General Principles | InterDigital, Inc. | other | Agreement | Yes |
No
| available | No | ||||
R3‑256832 | Views on 6G RAN internal functionality split and interfaces | NTT DOCOMO INC.. | discussion | Yes |
No
| available | No | |||||
R3‑256897 | Discussion on RAN internal functional split and interfaces | Rakuten Mobile, Samsung | discussion | Yes |
No
| available | No | |||||
R3‑256908 | 6G RAN Internal Functional Split and Interfaces | Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑256971 | Considerations on 6G RAN internal functional split and interfaces | China Unicom | discussion | Approval | Yes |
No
| available | No | ||||
R3‑257049 | On the Discussion of 6G RAN Internal Functional Spit | Jio Platforms | discussion | Yes |
No
| available | No | |||||
R3‑257082 | About 6G RAN-internal architecture topics | Ericsson | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑257122 | Considerations on 6G RAN internal functional split | LG Electronics Inc. | discussion | Decision | Yes |
No
| available | No | ||||
R3‑257169 | Discussion on supporting a F1-like interface in 6G RAN | discussion | Discussion | Yes |
No
| available | No | |||||
R3‑257193 | 6G RAN internal functional split and interfaces for NTN | THALES, Echostar | discussion | Decision | Yes |
No
| available | No | ||||
10.5 | AI/ML for RAN |   | ||||||||||
10.5.1 | AI/ML use cases | R3‑256538 | Initial discussion on AIRAN for 6G Network | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||
R3‑256580 | Discussion on high priority use cases for 6G | China Telecom | other | Agreement | Yes |
No
| available | No | ||||
R3‑256597 | Discussion on AI use cases for 6G | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256613 | Discussion on 6G AI/ML Use Cases | Qualcomm Incorporated | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256619 | Consideration on AI/ML use cases | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256627 | AI/ML for Network in 6G – Use Cases | Xiaomi | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256713 | 6G Data Collection | Ericsson, Jio Platforms | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256797 | AI/ML use cases for 6G | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256813 | 6G AI/ML Use Cases | InterDigital, Inc. | other | Agreement | Yes |
No
| available | No | ||||
R3‑256835 | Discussion on 6G AIML use cases | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256909 | Consideration on 6G AI use cases | Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑256948 | Initial Considerations for AI-native Radio Access Network | Hanbat National University | discussion | Yes |
No
| available | No | |||||
R3‑256972 | Considerations on Use Cases of 6G AI/ML for RAN | China Unicom | discussion | Approval | Yes |
No
| available | No | ||||
R3‑256990 | (TP for 6G TR) Considerations on AI/ML use cases for 6G RAN | Huawei | other | Agreement | Yes |
No
| available | No | ||||
R3‑257076 | Discussion on AI/ML use cases to be considered in 6GR | LG Electronics Inc. | discussion | Yes |
No
| available | No | |||||
R3‑257102 | AI/ML Use Cases for 6G | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑257194 | Use cases of AI/ML for NG-RAN in 6G | DOCOMO Communications Lab. | discussion | Discussion | Yes |
No
| available | No | ||||
10.5.2 | AI/ML framework | R3‑256602 | Federated Learning Framework for AI/ML for RAN | Tejas Network Limited | discussion | Decision | Yes |
No
| available | No | ||
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‑256774 | Workplan for Rel-20 SON_MDT Enhancement | China Unicom | Work Plan | Decision | Yes |
Yes
| revised | No | R3‑257203 | |
R3‑257203 | Workplan for Rel-20 SON_MDT Enhancement | China Unicom | Work Plan | Decision | No |
No
| reserved | No | R3‑256774 | |||
11.2 | MRO Enhancements |   | ||||||||||
11.2.1 | Inter-CU LTM | R3‑256601 | MRO Enhancements for Inter-CU LTM | Nokia | discussion | Discussion | Yes |
No
| available | No | ||
R3‑256608 | MRO enhancements for Inter-CU LTM | Qualcomm Korea | discussion | Yes |
No
| available | No | |||||
R3‑256656 | Discussion on SON enhancement for inter-CU LTM | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256666 | Discussion on MRO enhancement on inter-CU LTM | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256755 | Initial consideration on MRO for inter CU LTM | ZTE Corporation | discussion | Yes |
No
| available | No | |||||
R3‑256775 | Discussion on MRO Enhancements for inter-CU LTM | China Unicom | discussion | Yes |
No
| available | No | |||||
R3‑256782 | MRO for inter-CU LTM | NEC | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256910 | Discussion on MRO for inter-CU LTM | Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑256966 | (TP for BLCR for 38.413) Inter-CU LTM | Huawei | other | Agreement | Yes |
No
| available | No | ||||
R3‑257115 | MRO for inter-gNB LTM | Ericsson | discussion | Yes |
No
| available | No | |||||
11.2.2 | Intra-CU conditional LTM | R3‑256600 | (TP for SON BL CR for TS 38.300) MRO Enhancements for Conditional Intra-CU LTM | Nokia | other | Agreement | Yes |
No
| available | No | ||
R3‑256611 | MRO enhancements for Intra-CU conditional LTM | Qualcomm Korea | discussion | Yes |
No
| available | No | |||||
R3‑256657 | Discussion on SON enhancement for conditional intra-CU LTM | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256667 | (TP for SON BLCR to TS 38.401 and TS 38.300) Discussion on MRO enhancement on intra-CU conditional LTM | Samsung | other | Agreement | Yes |
No
| available | No | ||||
R3‑256756 | Initial consideration on MRO for CLTM | ZTE Corporation | discussion | Yes |
No
| available | No | |||||
R3‑256776 | Discussion on MRO Enhancements for C-LTM | China Unicom | discussion | Yes |
No
| available | No | |||||
R3‑256783 | MRO for Intra-CU conditional LTM | NEC | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256911 | (TP for TS38.300) Discussion on MRO for intra-CU CLTM | Lenovo | other | Agreement | Yes |
No
| available | No | ||||
R3‑256967 | Intra-CU conditional LTM | Huawei | discussion | Yes |
No
| available | No | |||||
R3‑257116 | MRO for Conditional LTM | Ericsson | discussion | Yes |
No
| available | No | |||||
12 | Study on AI/ML for NG-RAN Phase 3 (RAN3-led) |   | ||||||||||
12.1 | General | R3‑256546 | Skeleton for TR38.745 | ZTE Corporation, NEC | draft TR | Endorsement | Yes |
No
| available | No | ||
R3‑256547 | Work plan for Study on AI/ML for NG-RAN Phase 3 | ZTE Corporation, NEC | Work Plan | Decision | Yes |
No
| available | No | ||||
12.2 | AI/ML-based mobility |   | ||||||||||
12.2.1 | Multi-hop UE trajectory across gNBs | R3‑256548 | (TP to TR 38.745) Consideration on Mulltiple-hop UE trajectory | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||
R3‑256565 | Discussion on Multiple-hop UE trajectory | Lekha Wireless Solutions | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256579 | Discussion on multi-hop UE trajectory prediction | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256609 | Discussion on Multi-hop UE Trajectory Prediction and Feedback | Qualcomm Incorporated | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256694 | (TP to TR 38.745) Multi-hop UE trajectory across gNBs | Samsung | other | Agreement | Yes |
No
| available | No | ||||
R3‑256720 | Study on Multi-hop UE Trajectory Across gNBs | Xiaomi Technology | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256793 | (pCR for TR38.745) Multi-hop UE trajectory across gNBs | NEC | other | Agreement | Yes |
No
| available | No | ||||
R3‑256814 | Multi-Hop UE Trajectory Options | InterDigital, Inc. | other | Agreement | Yes |
No
| available | No | ||||
R3‑256833 | (TP to TR 38.745) Discussion on AI/ML based Multi-hop UE trajectory across gNBs | CMCC | other | Agreement | Yes |
No
| available | No | ||||
R3‑256861 | Support of multi-hop UE trajectory prediction/feedback | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256912 | (TP to TR38.745) Discussion on multi-hop UE trajectory | Lenovo | other | Agreement | Yes |
No
| available | No | ||||
R3‑256991 | (TP for TR 38.745) Considerations on multi-hop UE trajectory in AI/ML-based mobility | Huawei | other | Agreement | Yes |
No
| available | No | ||||
R3‑257072 | (TP to TR 38.745) Support for multi-hop UE trajectory | Ericsson | other | Agreement | Yes |
No
| available | No | ||||
R3‑257103 | (TP to TR 38.745) Multi-hop UE trajectory across gNBs | Nokia | other | Agreement | Yes |
No
| available | No | ||||
12.2.2 | Intra-CU LTM | R3‑256537 | Discussion on AI/ML for Intra-CU LTM | Nokia | discussion | Decision | Yes |
No
| available | No | ||
R3‑256549 | (TP to TR 38.745) Consideration on AIML assisted intra-CU LTM | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
R3‑256578 | Discussion on support of AIML based intra-CU LTM | China Telecom | other | Agreement | Yes |
No
| available | No | ||||
R3‑256610 | Discussion on Intra-CU LTM | Qualcomm Incorporated | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256684 | AI/ML Enhancements for Intra-CU LTM | Tejas Network Limited | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256695 | Discussion on AI/ML-based intra-CU LTM | Samsung | other | Agreement | Yes |
No
| available | No | ||||
R3‑256721 | Study on Intra-CU AI/ML-assisted LTM Mobility Support | Xiaomi Technology | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256794 | (pCR for TR38.745) AI/ML based intra-CU LTM | NEC | other | Agreement | Yes |
No
| available | No | ||||
R3‑256841 | Discussion on AIML based intra CU LTM use cases | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256862 | Discussion on support of AI/ML enabled intra-CU LTM | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256913 | AI/ML for Intra-CU LTM | Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑256992 | (TP to TR 38.745) Discussion for AI/ML assisted intra-CU LTM | Huawei | other | Agreement | Yes |
No
| available | No | ||||
R3‑257073 | (TP to TR 38.745) AI/ML based mobility – Intra-CU LTM | Ericsson | other | Agreement | Yes |
No
| available | No | ||||
R3‑257077 | Discussion on considerations in intra-CU LTM use case | LG Electronics Inc. | discussion | Yes |
No
| available | No | |||||
12.2.3 | Handover enhancements | R3‑256550 | (TP to TR 38.745) Consideration on Mulltiple-hop UE trajectory | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||
R3‑256612 | Discussion on Inter-CU LTM | Qualcomm Incorporated | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256696 | Discussion on other handover enhancements | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256722 | Study on Inter-CU AI/ML-assisted LTM in NG-RAN | Xiaomi Technology | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256795 | (pCR for TR38.745) Other AI/ML based handover enhancements | NEC | other | Agreement | Yes |
No
| available | No | ||||
R3‑256834 | (TP to TR 38.745) Discussion on AI/ML based handover enhancement | CMCC | other | Agreement | Yes |
No
| available | No | ||||
R3‑256863 | Discussion on support of AI/ML enabled inter-CU LTM | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256993 | (TP for TR 38.745) Discussion for Handover Enhancements | Huawei | other | Agreement | Yes |
No
| available | No | ||||
R3‑257074 | (TP to TR 38.745) Considerations for Handover Enhancements in Release-20 | Ericsson | other | Agreement | Yes |
No
| available | No | ||||
R3‑257104 | (TP to TR 38.745) Handover Enhancements | Nokia | other | Agreement | Yes |
No
| available | No | ||||
13 | Study on Integrated Sensing And Communication (ISAC) for NR |   | ||||||||||
13.1 | General | R3‑256588 | Work plan for study on Integrated Sensing And Communication (ISAC) for NR | China Telecom, Xiaomi | Work Plan | Decision | Yes |
No
| available | No | ||
R3‑256589 | TR skeleton for study on Integrated Sensing And Communication (ISAC) for NR | China Telecom, Xiaomi | discussion | Approval | Yes |
No
| available | No | ||||
R3‑256584 | Work plan for study on Integrated Sensing And Communication (ISAC) for NR | China Telecom | Work Plan | Decision | No |
Yes
| withdrawn | Yes | ||||
R3‑256585 | TR skeleton for study on Integrated Sensing And Communication (ISAC) for NR | China Telecom | discussion | Approval | No |
Yes
| withdrawn | Yes | ||||
13.2 | Network architecture | R3‑256528 | Discussion on ISAC Architecture and General Aspects | Xiaomi | other | Agreement | Yes |
No
| available | No | ||
R3‑256558 | Discussion on Network Architecture for ISAC | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
R3‑256586 | (TP for 38.765) Network architecture solution for gNB-based mono-static sensing | China Telecom | other | Agreement | Yes |
No
| available | No | ||||
R3‑256676 | (TP for ISAC TR) Network architecture for ISAC | Huawei | other | Agreement | Yes |
No
| available | No | ||||
R3‑256685 | Discussion on Network Architecture for NR ISAC | Tejas Network Limited | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256771 | Discussion on network architecture for ISAC | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256784 | The discussion on ISAC network architecture | NEC | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256826 | Network Architecture and Protocol Aspects for NR Sensing Support | Qualcomm Incorporated | discussion | Yes |
No
| available | No | |||||
R3‑256854 | Discussion on Network Architecture for Sensing | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256895 | Discussion on architecture for ISAC | Nokia, Nokia Shanghai Bell | discussion | Yes |
No
| available | No | |||||
R3‑256914 | Discussion on ISAC network architecture | Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑256922 | Discussion on Network Architecture for ISAC | Ericsson, Jio Platforms | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256941 | Discussions on the framework of ISAC | China Unicom | discussion | Yes |
No
| available | No | |||||
R3‑256947 | Network architecture enhancements for NR ISAC | Hanbat National University | discussion | Yes |
No
| available | No | |||||
R3‑257111 | Discussion paper on ISAC network architecuture | CEWiT | discussion | Yes |
No
| available | No | |||||
R3‑257118 | NR ISAC Network Architecture | InterDigital, Inc. | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑257123 | Discussions for ISAC network architecture in RAN3 | LG Electronics Inc. | discussion | Decision | Yes |
No
| available | No | ||||
R3‑257144 | Discussion on network architecture for ISAC | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
13.3 | RAN-CN procedures and signaling | R3‑256529 | Discussion on Sensing procedures and singalling | Xiaomi | other | Agreement | Yes |
No
| available | No | ||
R3‑256559 | Discussion on RAN-CN Procedures and Signalling for ISAC | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
R3‑256587 | On RAN-CN procedures and signalling for supporting sensing | China Telecom, BUPT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256677 | (TP for ISAC TR) RAN-CN procedures and signaling for ISAC | Huawei | other | Agreement | Yes |
No
| available | No | ||||
R3‑256686 | Discussion on RAN-CN procedures and signaling for ISAC | Tejas Network Limited | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256712 | Discussion on RAN3 impact of gNB-based mono-static sensing | OPPO | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256772 | RAN-CN procedures and signaling on ISAC | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256785 | The discussion on ISAC RAN-CN procedure and signaling | NEC | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256827 | Signalling and Procedures for NR Sensing Support | Qualcomm Incorporated | discussion | Yes |
No
| available | No | |||||
R3‑256855 | Discussion on RAN-CN Procedures Supporting ISAC | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256896 | Discussion on RAN-CN procedures and signaling for ISAC | Nokia, Nokia Shanghai Bell | discussion | Yes |
No
| available | No | |||||
R3‑256915 | Discussion on general procedures for gNB-based sensing | Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑256942 | RAN-CN procedures and signaling of ISAC | China Unicom | discussion | Yes |
No
| available | No | |||||
R3‑257025 | Discussion on RAN-CN procedures and signaling to support ISAC | Ericsson, Jio Platforms | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑257119 | NR ISAC RAN-CN Procedures and Signaling | InterDigital, Inc. | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑257124 | Discussions on ISAC RAN-CN procedures and signalling | LG Electronics Inc. | discussion | Decision | Yes |
No
| available | No | ||||
R3‑257145 | 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‑256572 | Work Plan for Solutions for Ambient IoT (Internet of Things) in NR Phase 2 | Huawei, T-Mobile USA | Work Plan | Decision | Yes |
No
| available | No | ||
14.2 | Topology 2 | R3‑256551 | Discussion on R20 A-IoT for Topology 2 | ZTE Corporation, China Telecom | discussion | Yes |
No
| available | No | |||
R3‑256573 | [TPs to BL CRs] Consideration on Ambient IoT Topology 2 | Huawei, China Unicom, China Telecom | other | Agreement | Yes |
No
| available | No | ||||
R3‑256582 | Support of Ambient IoT Topology 2 | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256668 | Discussion on Topology 2 for AIoT | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256723 | Initial Considerations on Solutions for Ambient IoT in NR | Xiaomi Technology | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256726 | Architecture, functionalities and signaling to support Topology 2 | Qualcomm Incorporated | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256773 | Discussion on Topology-2 for Ambient IoT | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑256786 | Discussion on Topology 2 of Ambient IoT | NEC | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑256836 | Discussion on Topology 2 for A-IoT | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑256888 | Inventory Procedure for AIoT Topology 2 UEs | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑256916 | On A-IOT Topology 2 | Lenovo | discussion | Yes |
No
| available | No | |||||
R3‑257027 | Discussion on support of Topology 2 | LG Electronics | discussion | Yes |
No
| available | No | |||||
R3‑257032 | Consideration on the Impacts of A-IoT Topology 2 | Ofinno, LLC | discussion | Yes |
No
| available | No | |||||
R3‑257065 | Topology 2 - Starting points for discussions | Ericsson | discussion | 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 |   | ||||||||||
20.2 | Coordination between gNB and CN on N3 delay measurement |   | ||||||||||
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 |   |