Tdoc List
2025-08-25 19:24
| TDoc | Title | Source | Type | For | Agenda | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
|---|---|---|---|---|---|---|---|---|---|---|---|
| R3‑255001 | RAN3#129 Meeting Agenda | RAN3 Chair | agenda | Approval |
3Approval of the Agenda
| Yes |
Yes
| approved | No | ||
| R3‑255002 | RAN3#128 Meeting Report | ETSI-MCC | report | Approval |
4Approval of the minutes from previous meetings
| Yes |
Yes
| approved | No | ||
| R3‑255003 | Guidelines for RAN3 Meetings | RAN3 Chair, RAN3 Vice-Chairs | discussion | Endorsement |
5Documents for immediate consideration
| Yes |
Yes
| endorsed | No | ||
| R3‑255004 | TR 30.531 v1.59.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC | draft TR | Endorsement |
7General, protocol principles and issues
| Yes |
Yes
| endorsed | No | ||
| R3‑255005 | Reply LS on AIoT device identifier length | CT4(Huawei) | LS in | Discussion |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255006 | Reply LS on paging ID length | CT4(CICT Mobile) | LS in | Discussion |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255007 | LS on Rel-19 higher layers parameters list Post RAN1#121 | RAN1(Ericsson) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑255008 | Reply LS on simultaneous configuration of SBFD and DC | RAN1(Xiaomi) | LS in | Discussion |
19.2Support CLI Handling
| Yes |
Yes
| noted | No | ||
| R3‑255009 | LS on Rel-19 AI/ML positioning higher layer parameters list Post RAN1#121 | RAN1(Ericsson) | LS in | Discussion |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255010 | LS on TP for TS38.300 on Rel-19 SBFD | RAN1(Huawei) | LS in | Discussion |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255011 | LS on RAN2 agreements for SP CSI-RS activation/deactivation | RAN2(CATT) | LS in | Discussion |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255012 | Reply LS on Number of UEs in RRC_INACTIVE state with data transmission | RAN2(chinatelecom) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑255013 | Reply to LS on Indicating Time to the Next Data Burst (TTNB) | RAN2(Qualcomm) | LS in | Discussion |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255014 | Reply LS to SA2 on XR rate control | RAN2(vivo) | LS in | Discussion |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255015 | LS on parallel service request | RAN2(Xiaomi) | LS in | Discussion |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255016 | Logged Data Handling During Handover | RAN2(Nokia) | LS in | Discussion |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255017 | Reply LS to RAN2 on Signalling for 7 MHz Channel Bandwidth | RAN4(T-Mobile) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑255018 | Reply LS from RAN on removal of support of PWS over satellite NG-RAN in Rel-17 and 18 | TSG RAN(AALYRIA) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑255019 | Reply LS on stage 1 requirements for the support for PWS over satellite NGRAN in Rel-17 | SA2(Samsung) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑255020 | Reply LS on paging ID length | SA2(CATT) | LS in | Discussion |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255021 | Reply LS on D2R message size for inventory response | SA2(Interdigital) | LS in | Discussion |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255022 | Reply LS on emergency call back and paging | SA2(Qualcomm) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255023 | Reply LS on AI/ML Positioning Case 3a | SA2(Nokia) | LS in | Discussion |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255024 | Reply LS on OAM requirements to support regenerative payload transport links | SA2(CATT) | LS in | Discussion |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255025 | Reply LS on Handling of UE Radio Capability for Paging | SA2(Ericsson) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑255026 | Response to Reply LS on paging capability loss issue | SA2(Vodafone) | LS in | Discussion |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255027 | Reply LS on security handling for inter-CU LTM in non-DC cases | SA3(Huawei) | LS in | Discussion |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255028 | Draft LS to RAN3 on MBS Communication Service Type | SA4(Nokia) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑255029 | Reply LS on OAM-centric solution for NW-side data collection | SA5(Huawei) | LS in | Discussion |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255030 | (BL CR to 36.300 for SON) Addition of SON enhancements | Lenovo | draftCR | Endorsement |
10.1General
| Yes |
No
| available | No | R3‑253063 | |
| R3‑255031 | (BL CR to 38.413 for MDT) Addition of MDT enhancements | Nokia | CR | Agreement |
10.1General
| Yes |
No
| available | No | R3‑253068 | |
| R3‑255032 | (BL CR to 38.423 for MDT) Addition of MDT enhancements | CATT | CR | Agreement |
10.1General
| Yes |
No
| available | No | R3‑253069 | |
| R3‑255033 | (BL CR to 38.420 for SON) Addition of SON enhancements | Samsung, ZTE, CATT, Lenovo, Cybecore | CR | Agreement |
10.1General
| Yes |
No
| available | No | R3‑253627 | |
| R3‑255034 | (BL CR to 36.423 for SON) Addition of SON enhancements | CATT, Samsung, Lenovo, Huawei, Ericsson, ZTE, CMCC, Nokia, Jio Platforms | CR | Agreement |
10.1General
| Yes |
No
| available | No | R3‑253845 | |
| R3‑255035 | (BL CR to 37.340 for SON) Addition of SON enhancements | CMCC | draftCR | Endorsement |
10.1General
| Yes |
No
| available | No | R3‑253995 | |
| R3‑255036 | (BL CR to 38.300 for SON) Addition of SON enhancements | China Unicom | draftCR | Endorsement |
10.1General
| Yes |
No
| available | No | R3‑253996 | |
| R3‑255037 | (BL CR to 38.401 for SON) Addition of SON enhancements | ZTE Corporation, Nokia, Huawei, Lenovo, CATT, Ericsson, Samsung, Jio Platforms | CR | Agreement |
10.1General
| Yes |
No
| available | No | R3‑253997 | |
| R3‑255038 | (BL CR to 38.413 for SON) Addition of SON enhancements | Ericsson, Jio Platforms | CR | Agreement |
10.1General
| Yes |
No
| available | No | R3‑253998 | |
| R3‑255039 | (BL CR to 38.423 for SON) Addition of SON enhancements | ZTE Corporation, Samsung, Nokia, Lenovo, Jio | CR | Agreement |
10.1General
| Yes |
No
| available | No | R3‑253999 | |
| R3‑255040 | (BL CR to 38.473 for SON) Addition of SON enhancements | Huawei, Nokia, Jio | CR | Agreement |
10.1General
| Yes |
No
| available | No | R3‑254000 | |
| R3‑255041 | (BL CR to 37.480) Support of enhancements on AI/ML for NG-RAN | CATT, ZTE Corporation | CR | Agreement |
11.1General
| Yes |
No
| available | No | R3‑253072 | |
| R3‑255042 | (BL CR to 37.483) Support of enhancements on AI/ML for NG-RAN | Samsung, ZTE Corporation, Nokia | CR | Agreement |
11.1General
| Yes |
No
| available | No | R3‑253983 | |
| R3‑255043 | (BL CR to 38.401) Enhancement of AI/ML Energy Saving for NGRAN split architecture | CMCC, Samsung, Huawei, NEC, CATT, ZTE, Nokia, Ericsson, Deutsche Telekom, FiberCop, Jio Platforms | CR | Agreement |
11.1General
| Yes |
No
| available | No | R3‑253985 | |
| R3‑255044 | (BL CR to 38.423) Support of enhancements on AI/ML for NG-RAN | ZTE Corporation, Qualcomm, China Unicom, Ericsson, Samsung, Nokia, Lenovo, CATT, Huawei, NEC, CMCC, China Telecom, Telecom Italia, Deutsche Telekom, Verizon Wireless, LGE, Jio Platforms (JPL), Rakuten, Orange, FiberCop, InterDigital, Ofinno | CR | Agreement |
11.1General
| Yes |
No
| available | No | R3‑253986 | |
| R3‑255045 | (BL CR to 38.425) UE performance enhancement for split architecture | Nokia, Samsung, Ericsson, Huawei, ZTE, Deutsche Telekom, FiberCop, Jio Platforms | CR | Agreement |
11.1General
| Yes |
No
| available | No | R3‑253987 | |
| R3‑255046 | (BL CR to TS 38.473) Support of enhancements on AI/ML for NG-RAN | Ericsson (Rapporteur), ZTE, NEC, Nokia, Huawei, Ofinno | CR | Agreement |
11.1General
| Yes |
No
| available | No | R3‑253988 | |
| R3‑255047 | (BL CR to 37.340) AIML for NR-DC | Huawei, Lenovo, CATT, ZTE Corporation, Samsung, Ericsson, Nokia, Huawei, Ofinno, FiberCop, LG Electronics, Jio Platforms | draftCR | Endorsement |
11.1General
| Yes |
No
| available | No | R3‑254028 | |
| R3‑255048 | (BL CR to 38.300) Support of enhancements on AI/ML for NG-RAN | NEC, ZTE, Qualcomm, Samsung, CMCC, Ericsson, CATT, Ofinno, Huawei, Nokia, Jio Platforms | draftCR | Endorsement |
11.1General
| Yes |
No
| available | No | R3‑254029 | |
| R3‑255049 | (BL CR to 38.305 for WAB) Support of Location Service Involving WAB-Nodes | ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, Lenovo, CATT, Samsung, Huawei, China Telecom | draftCR | Endorsement |
12.1General
| Yes |
No
| available | No | R3‑253077 | |
| R3‑255050 | (BL CR to 38.401 for WAB) Support for Wireless Access Backhaul | Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung, Lenovo, Qualcomm, Jio Platforms | CR | Agreement |
12.1General
| Yes |
No
| available | No | R3‑253078 | |
| R3‑255051 | (BL CR to 38.410 for Femto) Introduction of NR Femto in NGAP list of functions | ZTE Corporation, Nokia, Baicells | CR | Agreement |
12.1General
| Yes |
No
| available | No | R3‑253079 | |
| R3‑255052 | (BL CR to 38.413 for WAB) Support for Wireless Access Backhaul | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, China Telecom, ZTE, Qualcomm, Samsung, CATT, Jio Platforms (JPL), Lenovo | CR | Agreement |
12.1General
| Yes |
No
| available | No | R3‑253081 | |
| R3‑255053 | (BL CR to 38.423 for WAB) Support for Wireless Access Backhaul | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, LG Electronics, Qualcomm, Huawei, China Telecom, Samsung, Lenovo | CR | Agreement |
12.1General
| Yes |
No
| available | No | R3‑253082 | |
| R3‑255054 | (BL CR to 38.455 for WAB) Support of Location Service Involving WAB-Nodes | Lenovo, ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, CATT, Samsung, Huawei, China Telecom, Jio Platforms (JPL) | CR | Agreement |
12.1General
| Yes |
No
| available | No | R3‑253083 | |
| R3‑255055 | (BL CR to 38.300 for Femto) Introduction of NR Femto Architecture and Protocol Aspects | Ericsson, Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, Huawei, LG Electronics, Samsung, Lenovo, Baicells, ZTE, NEC, CATT, Qualcomm | draftCR | Endorsement |
12.1General
| Yes |
No
| available | No | R3‑254017 | |
| R3‑255056 | (BL CR to TS 38.413 for Femto) Support of NR Femto architecture with NR Femto Gateway | Nokia, Huawei | CR | Agreement |
12.1General
| Yes |
No
| available | No | R3‑254018 | |
| R3‑255057 | (BL CR to 37.483) Introducing Rel-19 Mobility enhancement | LG Electronics Inc., Nokia, China Telecom, Google, Ericsson, CATT, Qualcomm, Samsung, CMCC, ZTE, Huawei, NTT Docomo, Lenovo, NEC, Ofinno, Jio Platforms (JPL) | CR | Agreement |
13.1General
| Yes |
No
| available | No | R3‑253085 | |
| R3‑255058 | (BL CR to 38.420) Support for Inter-CU LTM | ZTE Corporation, China Telecom, Samsung, Nokia, CATT, NEC, LG Electronics, Ericsson, Huawei, Lenovo | CR | Agreement |
13.1General
| Yes |
No
| available | No | R3‑253088 | |
| R3‑255059 | (BL CR to 38.470) Support for Inter-CU LTM procedure | Samsung, Huawei, LG Electronics, Ericsson, China Telecom, Nokia, ZTE Corporation, CATT | CR | Agreement |
13.1General
| Yes |
No
| available | No | R3‑253091 | |
| R3‑255060 | (BL CR to 37.340) stage 2 for inter-CU LTM in NR-DC | CATT, China Telecom, Huawei, Nokia, LG Electronics, Google, Samsung, Ofinno, Ericsson, Lenovo, NEC, ZTE, Qualcomm | draftCR | Endorsement |
13.1General
| Yes |
No
| available | No | R3‑254006 | |
| R3‑255061 | (BL CR to 38.300) Support for Inter-CU LTM | Nokia, Huawei, Google, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung, Ofinno | draftCR | Endorsement |
13.1General
| Yes |
No
| available | No | R3‑254007 | |
| R3‑255062 | (BL CR to 38.401) on conditional intra-CU LTM and intra-CU LTM | China Telecom, ZTE Corporation, NEC, Samsung, Nokia, Google, Huawei, Ericsson, LG Electronics, Qualcomm, Jio Platforms | CR | Agreement |
13.1General
| Yes |
No
| available | No | R3‑254008 | |
| R3‑255063 | (BL CR to 38.423) Xn support for inter-CU LTM | Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC, ZTE, LG Electronics, Ofinno, Qualcomm | CR | Agreement |
13.1General
| Yes |
Yes
| withdrawn | Yes | R3‑255715 | R3‑254009 |
| R3‑255064 | (BL CR to 38.423 for DC) Xn support for inter-CU LTM in DC | Lenovo, Ericsson, CATT, Huawei, Ofinno, Nokia, NEC, LGE, China Telecom, Google, ZTE, Samsung | CR | Agreement |
13.1General
| Yes |
No
| available | No | R3‑254010 | |
| R3‑255065 | (BL CR to 38.473) Inter-CU LTM and intra-CU conditional LTM | Huawei, Nokia, Samsung, Google, NEC, China Telecom, Ericsson, LG Electronics, CATT, Ofinno, ZTE, Lenovo, Qualcomm Incorporated, Jio Platforms | CR | Agreement |
13.1General
| Yes |
No
| available | No | R3‑254011 | |
| R3‑255066 | (BL CR to 38.410) Introduce NG Removal procedure | CMCC, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Qualcomm, Xiaomi, LG Electronics, China Telecom, Samsung, ZTE, NEC, ETRI | CR | Agreement |
14.1General
| Yes |
No
| available | No | R3‑253094 | |
| R3‑255067 | (BL CR to 38.300) Support for Regenerative Payload and MBS broadcast in NR NTN | Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei, Dish Networks, Echostar, Eutelsat Group, Xiaomi, Samsung, CMCC, LG Electronics, NEC, Lenovo, ETRI, Jio Platforms | draftCR | Endorsement |
14.1General
| Yes |
No
| available | No | R3‑254012 | |
| R3‑255068 | Support for Regenerative Payload and MBS broadcast in NR NTN | CATT, Thales, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Qualcomm, Samsung, Xiaomi, CMCC, China Telecom, Jio Platforms, LG Electronics, NEC, ETRI, SES, ESA | CR | Agreement |
14.1General
| Yes |
No
| available | No | R3‑254013 | |
| R3‑255069 | (BL CR to 36.410) Support of Full eNB as Regenerative payload | Samsung, Ericsson, Sateliot, Thales, ESA, Deutsche Telekom, Jio Platforms Limited, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei | CR | Agreement |
15.1General
| Yes |
No
| available | No | R3‑253134 | |
| R3‑255070 | (BL CR to 36.413) Support of Full eNB as Regenerative Payload | Huawei, Ericsson, Thales, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, Xaomi, CATT, Samsung, Jio Platforms | CR | Agreement |
15.1General
| Yes |
No
| available | No | R3‑253135 | |
| R3‑255071 | (BL CR to 36.300) Support of full eNB as regnerative payload and store&forward operation | ZTE Corporation, Samsung, CMCC, CATT, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Xiaomi, Qualcomm, Jio Platforms | draftCR | Endorsement |
15.1General
| Yes |
No
| available | No | R3‑253973 | |
| R3‑255072 | (BL CR to 38.300) Introduction of Ambient IoT | CMCC, Huawei, Nokia | draftCR | Endorsement |
16.1General
| Yes |
No
| available | No | R3‑253968 | |
| R3‑255073 | (BL CR to 38.401) Introduction of Ambient IoT | Ericsson, Huawei, Nokia | CR | Agreement |
16.1General
| Yes |
No
| available | No | R3‑253969 | |
| R3‑255074 | (BL CR to 38.410) Introduction of Ambient IoT | ZTE Corporation, China Telecom, Huawei, Samsung, CMCC, Nokia, Xiaomi | CR | Agreement |
16.1General
| Yes |
No
| available | No | R3‑253970 | |
| R3‑255075 | (BL CR to 38.412) Introduction of Ambient IoT | Xiaomi, Huawei, Nokia | CR | Agreement |
16.1General
| Yes |
No
| available | No | R3‑253971 | |
| R3‑255076 | (BL CR to 38.413) Introduction of Ambient IoT | Huawei, Nokia | CR | Agreement |
16.1General
| Yes |
No
| available | No | R3‑253972 | |
| R3‑255077 | (BL CR to 38.300) Introduction of Network Energy Saving Enhancement | CATT, Ericsson, Huawei, Samsung, China Telecomm, Rakuten, ZTE, CMCC, Lenovo, Deutsche Telekom, Nokia | draftCR | Endorsement |
17.1General
| Yes |
No
| available | No | R3‑253101 | |
| R3‑255078 | (BL CR to 38.470) Introduction of Network Energy Saving Enhancement | Samsung, Huawei, NEC, CATT, ZTE, Ericsson | CR | Agreement |
17.1General
| Yes |
No
| available | No | R3‑253103 | |
| R3‑255079 | (BL CR to 38.420) Introduction of Network Energy Saving Enhancement | ZTE Corporation, Samsung, Lenovo, Huawei, Qualcomm, Ericsson, CATT, Nokia, Rakuten, NEC | CR | Agreement |
17.1General
| Yes |
No
| available | No | R3‑253917 | |
| R3‑255080 | Introduction of Network Energy Saving Enhancement | Ericsson, Huawei, CMCC, Samsung, Qualcomm, Nokia, ZTE, Lenovo, Deutsche Telekom, NEC, CATT, China Unicom, Jio Platforms, Rakuten | CR | Agreement |
17.1General
| Yes |
No
| available | No | R3‑253974 | |
| R3‑255081 | (BL CR to 38.473) Introduction of Network Energy Saving Enhancement | Huawei, Ericsson, CMCC, Samsung, ZTE, Nokia, Deutsche Telekom, Lenovo, NEC, Jio Platforms, CATT, Qualcomm | CR | Agreement |
17.1General
| Yes |
No
| available | No | R3‑253975 | |
| R3‑255082 | (BL CR to 38.300) Introduction of low-power wake-up signal and receiver for NR | vivo, NTT DOCOMO INC., Nokia, Samsung, Ericsson, ZTE, CATT, Huawei | draftCR | Endorsement |
18.1General
| Yes |
No
| available | No | R3‑253105 | |
| R3‑255083 | (BL CR to 38.470) Introduction of low-power wake-up signal and receiver for NR | Nokia, Samsung, ZTE, Ericsson, Huawei, CATT | CR | Agreement |
18.1General
| Yes |
No
| available | No | R3‑253108 | |
| R3‑255084 | (BL CR to 38.410) Introduction of LP-WUS | CATT, Nokia, Ericsson, Huawei, Vivo, ZTE, Qualcomm, NTT Docomo | CR | Agreement |
18.1General
| Yes |
No
| available | No | R3‑254001 | |
| R3‑255085 | (BL CR to 38.413) Introduction of low-power wake-up signal and receiver for NR | ZTE Corporation, Nokia, Samsung, Ericsson, Huawei, CATT, NTT DOCOMO | CR | Agreement |
18.1General
| Yes |
No
| available | No | R3‑254002 | |
| R3‑255086 | (BL CR to 38.420) Introduction of LP-WUS | Qualcomm, ZTE Corporation, Nokia, Ericsson, CATT, Huawei, Samsung | CR | Agreement |
18.1General
| Yes |
No
| available | No | R3‑254003 | |
| R3‑255087 | Introduction of low-power wake-up signal and receiver for NR | Ericsson, Vivo, NTT Docomo, Huawei, ZTE, Nokia, Samsung, CATT | CR | Agreement |
18.1General
| Yes |
No
| available | No | R3‑254004 | |
| R3‑255088 | (BL CR to 38.473) Introduction of low-power wake-up signal and receiver for NR | Huawei, Nokia, Samsung, Ericsson, CATT, ZTE, Vivo, NTT DOCOMO INC. | CR | Agreement |
18.1General
| Yes |
No
| available | No | R3‑254005 | |
| R3‑255089 | (BL CR to 38.300) introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD) | Ericsson, Nokia | draftCR | Endorsement |
19.1General
| Yes |
Yes
| endorsed | No | R3‑253989 | |
| R3‑255090 | (BL CR to 38.401) introduction of Evolution of NR duplex operation | ZTE Corporation, Ericsson, Samsung, Qualcomm, Huawei, CATT, Nokia, CMCC, LGE | CR | Agreement |
19.1General
| Yes |
Yes
| endorsed | No | R3‑253990 | |
| R3‑255091 | (BL CR to 38.420) introduction of Evolution of NR duplex operation | CMCC, Ericsson, Huawei, Samsung, ZTE, Nokia, Jio Platforms | CR | Agreement |
19.1General
| Yes |
Yes
| endorsed | No | R3‑253991 | |
| R3‑255092 | (BL CR to 38.423) introduction of Evolution of NR duplex operation | Huawei, China Telecom, China Unicom, China Mobile, Ericsson, Qualcomm, Samsung, ZTE Corporation, LG Electronics, Nokia, Jio Platforms (JPL), CATT | CR | Agreement |
19.1General
| Yes |
Yes
| endorsed | No | R3‑253992 | |
| R3‑255093 | (BL CR to 38.470) introduction of Evolution of NR duplex operation | CATT, Ericsson, CMCC, Nokia, ZTE, Qualcomm, Samsung, Jio Platforms | CR | Agreement |
19.1General
| Yes |
Yes
| endorsed | No | R3‑253993 | |
| R3‑255094 | (BL CR to 38.473) introduction of Evolution of NR duplex operation | Samsung, Huawei, Ericsson, ZTE, LG Electronics Inc., Nokia, Qualcomm, Jio Platforms | CR | Agreement |
19.1General
| Yes |
Yes
| endorsed | No | R3‑253994 | |
| R3‑255095 | (BL CR to 38.305) Introduction of AI/ML air | CATT, Ericsson, Nokia, Huawei, Xiaomi, ZTE, CMCC, Samsung, CEWiT, Jio Platforms | draftCR | Endorsement |
20.1General
| Yes |
No
| available | No | R3‑253977 | |
| R3‑255096 | (BL CR to 38.401) Support of AI/ML assisted positioning | ZTE Corporation, Xiaomi, CATT, Ericsson, Huawei, NEC, Nokia, Jio Platforms | CR | Agreement |
20.1General
| Yes |
No
| available | No | R3‑253978 | |
| R3‑255097 | (BL CR to 38.413) Support of Case 3a | Huawei, ZTE, Lenovo, Nokia, Ericsson, Jio Platforms | CR | Agreement |
20.1General
| Yes |
No
| available | No | R3‑253979 | |
| R3‑255098 | (BL CR to 38.455) Introduction of AI/ML air | Ericsson, Nokia | CR | Agreement |
20.1General
| Yes |
No
| available | No | R3‑253980 | |
| R3‑255099 | (BL CR to 38.473) Support of Sample-based measurement (case 3b) | Xiaomi, Ericsson, ZTE, CATT, Samsung, Nokia, Jio Platforms | CR | Agreement |
20.1General
| Yes |
No
| available | No | R3‑253981 | |
| R3‑255100 | (BL CR to 38.300) Stage 2 for case 3a | Nokia, CATT, Xiaomi, Ericsson, CMCC, Huawei, ZTE, Lenovo, Jio Platforms | draftCR | Endorsement |
20.1General
| Yes |
No
| available | No | R3‑254027 | |
| R3‑255101 | (BL CR to 37.340) Support of XR enhancements | ZTE Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Inc, Lenovo, Huawei, Ericsson, CATT, CMCC, Samsung, Xiaomi, NEC, China Telecom, Ofinno | draftCR | Endorsement |
21.1General
| Yes |
No
| available | No | R3‑254019 | |
| R3‑255102 | (BL CR to 37.483) Support of XR enhancements | CMCC, Nokia, Nokia Shanghai Bell, Huawei, CATT, Xiaomi, Ofinno, China Telecom, ZTE, Ericsson, Qualcomm, Samsung, NEC | CR | Agreement |
21.1General
| Yes |
No
| available | No | R3‑254020 | |
| R3‑255103 | (BL CR to 38.300) Support of XR enhancements | Nokia, Nokia Shanghai Bell, Lenovo, Qualcomm, Xiaomi, CATT, Ericsson, CMCC, Samsung, Huawei, China Telecom | draftCR | Endorsement |
21.1General
| Yes |
No
| available | No | R3‑254021 | |
| R3‑255104 | (BL CR to 38.413) Support of XR enhancements | Lenovo, Nokia, Nokia Shanghai Bell, CMCC, China Telecom, Huawei, ZTE, Ericsson, Samsung, Qualcomm, Ofinno | CR | Agreement |
21.1General
| Yes |
No
| available | No | R3‑254022 | |
| R3‑255105 | (BL CR to 38.415) Support of XR enhancements | China Telecom, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CMCC, Ericsson, Samsung, Lenovo | CR | Agreement |
21.1General
| Yes |
No
| available | No | R3‑254023 | |
| R3‑255106 | (BL CR to 38.423) Support of XR enhancements | CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC, NEC, Ofinno | CR | Agreement |
21.1General
| Yes |
No
| available | No | R3‑254024 | |
| R3‑255107 | (BL CR to 38.425) Support of XR enhancements | Ericsson, AT&T, BT, T-Mobile USA, Charter Communications, Qualcomm, Huawei, Nokia, Nokia Shanghai Bell, China Telecom, CMCC, ZTE, CATT, Ofinno | CR | Agreement |
21.1General
| Yes |
No
| available | No | R3‑254025 | |
| R3‑255108 | (BL CR to 38.473) Support of XR enhancements | Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi, Nokia, Nokia Shanghai Bell, China Telecom, Ofinno | CR | Agreement |
21.1General
| Yes |
No
| available | No | R3‑254026 | |
| R3‑255109 | (BL CR to 38.413) Support of Multi-hop relay | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, LG Electronics, NEC, CATT, InterDigital, Samsung, ZTE, FirstNet, NIST | CR | Agreement |
22.1General
| Yes |
No
| available | No | R3‑253127 | |
| R3‑255110 | (BL CR to 38.423) Support of Multi-hop relay | Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, Huawei, NEC, CATT, InterDigital, Samsung, ZTE, FirstNet, NIST | CR | Agreement |
22.1General
| Yes |
No
| available | No | R3‑253128 | |
| R3‑255111 | (BL CR to 38.401) Support of Multi-hop relay | LG Electronics Inc., ZTE, Nokia, Nokia Shanghai Bell, Ericsson, FirstNet, Huawei | CR | Agreement |
22.1General
| Yes |
No
| available | No | R3‑254014 | |
| R3‑255112 | (BL CR to 38.470) Support of Multi-hop relay | ZTE Corporation, Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell | CR | Agreement |
22.1General
| Yes |
No
| available | No | R3‑254015 | |
| R3‑255113 | (BL CR to 38.473) Support of Multi-hop relay | Huawei, LG Electronics, Nokia, Nokia Shanghai Bell, NEC, CATT, Ericsson, Samsung, ZTE, Interdigital, FirstNet | CR | Agreement |
22.1General
| Yes |
No
| available | No | R3‑254016 | |
| R3‑255114 | Correction of message level criticality of E1AP procedures | Huawei | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑245712 | |
| R3‑255115 | Time Reference Distribution Information in S1AP | Qualcomm, Vodafone Group Plc, Vodafone Telekomnikasyon A.S. | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑245771 | |
| R3‑255116 | Support of Multicast MBS session restoration procedure for N3mb path failure | Huawei, CMCC, CBN, China Broadnet, Qualcomm Incorporated, Nokia | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑247876 | |
| R3‑255117 | Recovery of N3mb path failure for unicast transport of multicast session | Nokia, Ericsson, Huawei | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑247877 | |
| R3‑255118 | Recovery of N3mb path failure for unicast transport of multicast session | ZTE Corporation, Nokia, Huawei, CATT | draftCR | Endorsement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑247878 | |
| R3‑255119 | Inactivity Timer for Fixed Wireless Access [Inactivity_Timer_FWA] | Nokia, Ericsson, Huawei, ZTE | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑250782 | |
| R3‑255120 | Inactivity Timer for Fixed Wireless Access [Inactivity_Timer_FWA] | Huawei, Nokia, ZTE, Ericsson | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑250783 | |
| R3‑255121 | Correction on UE Radio Capability Retrieval | ZTE Corporation, CMCC, Nokia, Huawei, Ericsson, CATT | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑252278 | |
| R3‑255122 | Correction on UE Radio Capability Retrieval | Huawei, Ericsson, Nokia, ZTE, CATT, CMCC | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑252279 | |
| R3‑255123 | E-CID measurement enhancement [ECID_enh1] | Ericsson, NTT Docomo, Nokia, Polaris Wireless, ZTE, CATT, Huawei, Samsung, China Telecom | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑252283 | |
| R3‑255124 | E-CID measurement enhancement [ECID_enh1] | Ericsson, NTT Docomo, Nokia, Polaris Wireless, ZTE, CATT, Huawei, Samsung, China Telecom | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑252284 | |
| R3‑255125 | Trace Depth for Vendor Specific Trace Record | Nokia, Ericsson, Huawei, ZTE Corporation | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑252393 | |
| R3‑255126 | Trace Depth for Vendor Specific Trace Record | Ericsson, Huawei, ZTE Corporation, Nokia | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑252394 | |
| R3‑255127 | Trace Depth for Vendor Specific Trace Record | ZTE Corporation, Ericsson, Nokia, Huawei | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑252396 | |
| R3‑255128 | Trace Depth for Vendor Specific Trace Record | Huawei, Ericsson, ZTE Corporation, Nokia | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑252403 | |
| R3‑255129 | Correction of the interaction with other procedures related to the User Plane Failure | Ericsson, Nokia, Huawei | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑252425 | |
| R3‑255130 | X2 TNL address exchange | Vodafone, Ericsson, Huawei, Nokia, ZTE Corporation | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑252429 | |
| R3‑255131 | Xn TNL address exchange | Vodafone, Ericsson, Huawei, ZTE Corporation, Nokia, Jio Platforms | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑252460 | |
| R3‑255132 | E-CID measurement enhancement [ECID_enh1] | Ericsson, ZTE | draftCR | Endorsement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑253872 | |
| R3‑255133 | Support Aerial UE Flight Information Reporting | CATT, ZTE, Ericsson, CMCC, Nokia, China Telecom, Huawei | draftCR | Endorsement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑253900 | |
| R3‑255134 | Support Aerial UE Flight Information Reporting [UAS_Ph3] | ZTE Corporation, Ericsson, CATT, CMCC, Nokia, China Telecom, Huawei | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑253901 | |
| R3‑255135 | Support Aerial UE Flight Information Reporting to CN | Ericsson, CMCC, ZTE, CATT, Nokia, Huawei | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
Yes
| revised | No | R3‑255757 | R3‑253902 |
| R3‑255136 | Support Aerial UE Flight Information Reporting | Huawei, Nokia, ZTE, CATT, Ericsson | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑253903 | |
| R3‑255137 | Correction for PDCP SN gap report during UE's handover - Alt 1 | Huawei, LG Electronics, Qualcomm, China Telecom, Xiaomi, CMCC, Samsung | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| Yes |
No
| available | No | R3‑253905 | |
| R3‑255138 | TP (BL CR TS 38.300, TS 38.473, TS 38.423) Remaining issues on Inter-CU LTM procedure | Nokia | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255139 | Discussion on Inter-CU LTM with Dual Connectivity | Nokia | discussion | Decision |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255140 | Discussion on Conditional LTM in split architecture | Nokia | discussion | Decision |
13.3Support for Conditional LTM
| Yes |
No
| available | No | ||
| R3‑255141 | TDoc Quota Rules | RAN3 Chair | discussion | Decision |
6Organizational topics
| Yes |
Yes
| noted | No | ||
| R3‑255142 | Pre-release Feature Removal | ZTE Corporation | discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | |||
| R3‑255143 | pCR on Pre-release feature removal process | ZTE Corporation | pCR | Endorsement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255144 | Introduction of 7MHz channel bandwidth | ZTE Corporation | CR | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255145 | Introduction of 7MHz channel bandwidth | ZTE Corporation | CR | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255146 | [Draft] Reply LS on Signalling for 7 MHz Channel Bandwidth | ZTE Corporation | LS out | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255147 | Discussion on the configuration in case of CHO with CPAC | ZTE Corporation, CATT, China Telecom, China Unicom | discussion |
9.2NR
| Yes |
Yes
| noted | No | |||
| R3‑255148 | Clarification on the configuration in case of CHO with CPAC | ZTE Corporation, CATT, China Telecom, China Unicom | draftCR | Endorsement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255149 | (TP to 38.423, 38.473) Inter-CU LTM | ZTE Corporation | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255150 | (TP to BL CR for TS 38.300, 38.473, 38.423) Rel-19 Set ID assignment | ZTE Corporation | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255151 | (TP to BL CR for TS 38.401, 38.473) TAT transfer for Conditional LTM | ZTE Corporation | other | Agreement |
13.3Support for Conditional LTM
| Yes |
No
| available | No | ||
| R3‑255152 | (TP for 38.300) Leftover issues on AIoT | ZTE Corporation, China Telecom | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255153 | (TP for 38.413) Leftover issues on AIoT | ZTE Corporation, China Telecom | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255154 | (TP for 38.300) Session Release procedure | ZTE Corporation, China Telecom | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255155 | (TP for 38.413) Session Release procedure | ZTE Corporation, China Telecom | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255156 | Functional Aspects of WAB-Nodes | Ericsson, Jio Platforms | discussion | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255157 | (TP for WAB BL CR for TS 38.401) Functional Aspects of WAB-Nodes | Ericsson, Jio Platforms | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255158 | (TP for TS 38.401 and 38.473) Support of Multi-hop relay | LG Electronics, FirstNet | other | Agreement |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255159 | Discussion on remaining issues in service continuity | LG Electronics, FirstNet | discussion |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | |||
| R3‑255160 | Views on the Open Issues for AI/ML Positioning Accuracy Enhancements | Qualcomm Incorporated | discussion |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | |||
| R3‑255161 | TP to BL CR for TS 38.305 | Qualcomm Incorporated | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255162 | [TP for BL CR NR Femto TS 38.413] Completion of open points of NR Femto | Nokia | other | Agreement |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255163 | [TP for BL CR NR Femto TS 38.413] Paging issue with NR Femtos | Nokia | other | Agreement |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255164 | (TP for SON BL CR for TS 38.401) MRO Enhancements for LTM | Nokia | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255165 | MRO Enhancements for CHO with Candidate SCG(s) | Nokia | discussion | Discussion |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255166 | Discussion and Draft Reply LS on MBS Communication Service Type for QMC | Ericsson | discussion | Agreement |
8.1New Incoming LSs
| Yes |
Yes
| revised | No | R3‑255756 | |
| R3‑255167 | MBS Communication Service Type for QMC | Ericsson | CR | Agreement |
8.1New Incoming LSs
| Yes |
Yes
| revised | No | R3‑255755 | |
| R3‑255168 | MBS Communication Service Type for QMC | Ericsson | CR | Agreement |
8.1New Incoming LSs
| Yes |
Yes
| revised | No | R3‑255754 | |
| R3‑255169 | Remaining aspects for the support of WAB | CANON Research Centre France | discussion |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | |||
| R3‑255170 | Remaining issues in AI/ML assisted Network Slicing | ZTE Corporation | discussion | Discussion |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255171 | (TP to BL CR to 38.423) Support of AI/ML assisted Network Slicing | ZTE Corporation, Qualcomm, China Unicom | other | Agreement |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255172 | (TP to BL CR to 38.300) Support of AI/ML assisted CCO | ZTE Corporation, Lenovo, China Unicom | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255173 | (TP to BL CR to 38.401) Support of AI/ML assisted CCO | ZTE Corporation, Lenovo, China Unicom, China Telecom | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255174 | Way forward on Continuous MDT collection | ZTE Corporation | discussion | Discussion |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255175 | (TP to BL CR to 38.423) Addition of predicted PSCell ID within DC procedure | ZTE Corporation, Samsung, Qualcomm, China Unicom, CMCC, CATT, Ofinno | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255176 | (TP to BL CR to 38.473) Remaining issues in F1AP for AI/ML for NG-RAN | ZTE Corporation | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255177 | (TP to BL CR to 37.483) Remaining issues in E1AP for AI/ML for NG-RAN | ZTE Corporation | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255178 | Work plan for enhancements for Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN | ZTE Corporation, NEC | Work Plan | Information |
11.1General
| Yes |
No
| available | No | ||
| R3‑255179 | (TP to BL CR for TS38.300) Support of NG Suspend Resume | CATT, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm, CMCC, Samsung, China Telecom, LG Electronics, Xiaomi | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255180 | (TP to BL CR for TS38.300) OAM configuration for supported TAI list | CATT, Nokia, Nokia Shanghai Bell, ZTE, Samsung, China Telecom, CSCN, CMCC, LG Electronics, NEC, Xiaomi | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255181 | Discussion on A-IoT leftover issues | CATT | discussion | Decision |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255182 | (TP to BL CR for TS38.300) Support of A-IoT | CATT | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255183 | (TP to BL CR for TS38.413) on A-IoT leftover issues | CATT | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255184 | (TP to BL CR for TS38.305) Support of AI Positioning | CATT | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255185 | (TP to BL CR for TS38.455) Support of AI Positioning for Case 3a | CATT | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255186 | Correction to Positioning activation and deactivation procedure | CATT, Samsung, ZTE | draftCR | Endorsement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255187 | Discussion on positioning activation and deactivation procedure | Samsung, CATT, ZTE | discussion | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255188 | Correction to positioning activation and deactivation procedure | Samsung, CATT, ZTE Corporation | CR | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255189 | Correction to positioning activation and deactivation procedure | Samsung, CATT, ZTE Corporation | CR | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255190 | Correction to positioning activation and deactivation procedure | ZTE Corporation, Samsung, CATT | CR | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255191 | [DRAFT] Reply LS on clarification of UAV regulation from SA2 | Nokia, Huawei | LS out | Approval |
8.3Left over LSs / pending actions
| Yes |
No
| available | No | ||
| R3‑255192 | Withdrawn | Nokia | CR | Agreement |
9.2NR
| No |
Yes
| withdrawn | Yes | ||
| R3‑255193 | (SON TPs to BL CR to TS 38.423 and to TS 37.340) Completion of the signalling for providing UHI to the SN in case of S-CPAC release | Nokia, Huawei, Ericsson | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255194 | (SON TP to BL CR to TS 38.423 and MDT TP to BL CR TS 38.413) Solution to avoid restarting MRO in NTN deployments and a proposal for the MDT area definition | Nokia | other | Agreement |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | R3‑253186 | |
| R3‑255195 | Discussion on the possibility of requesting a non-registered slice | Nokia | discussion | Discussion |
10.3.2Network Slicing
| Yes |
No
| available | No | ||
| R3‑255196 | Open issues related to Rel 19 AIoT Procedures | Tejas Network Limited | discussion | Decision |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255197 | (TP to BL CR for TS 38.423 and 38.473 on Inter-CU LTM) Remaining Rel-19 inter-CU LTM issues | NEC | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255198 | (TP to BL CR for TS 38.423 and 37.340 on Inter-CU LTM with DC) Remaining issues of Rel-19 inter-CU LTM in DC scenario | NEC | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255199 | (TP to BL CR for 38.473 on conditional intra-CU LTM) Remaining issues of Rel-19 intra-CU Conditional LTM | NEC | other | Agreement |
13.3Support for Conditional LTM
| Yes |
No
| available | No | ||
| R3‑255200 | [TP for BL CR to TS 38.305 & TP for BL CR to TS 38.455] Discussion on AI/ML for positioning Case 3a | NEC | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255201 | [TP for BL CR to TS 38.455] Discussion on AI/ML for positioning Case 3b | NEC | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255202 | (TP to BL CR of 38.423 on WAB) Discussion on access and reliability for WAB | NEC | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255203 | (TP to BLCR TS38.423) Clean-up for AI/ML-based slicing | NEC | other | Agreement |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255204 | Clean-up for AI/ML-based CCO | NEC | discussion | Decision |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255205 | (TP to BLCR TS38.423 and TS38.473) AI/ML-based CCO | NEC | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255206 | (TP to BLCR for TS38.300) AI/ML-based CCO | NEC | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255207 | Clean-up for NR-DC mobility optimization | NEC | discussion | Decision |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255208 | Clean-up for Split architecture support | NEC | discussion | Decision |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255209 | (TP to BLCR TS38.473) Support on-demand SSB | NEC | other | Agreement |
17.2Support on-demand SSB SCell operation
| Yes |
No
| available | No | ||
| R3‑255210 | (TP to BLCR TS38.473) Support on-demand SIB1 | NEC | other | Agreement |
17.3Support on-demand SIB1 for UEs
| Yes |
No
| available | No | ||
| R3‑255211 | TP to BLCR TS38.423 on support on-demand SIB1 | NEC | other | Agreement |
17.3Support on-demand SIB1 for UEs
| Yes |
No
| available | No | ||
| R3‑255212 | (TP to BL CR for TS 38.300 on NR_NTN_Ph3) Discussion on NTN leftover issue | NEC | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255213 | Discussion on A-IoT leftover issues | NEC | discussion | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255214 | (TP for SON BLCR of 38.473) Discussion on MRO for LTM | NEC | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255215 | Discussion on RLC enhancement | NEC | discussion | Decision |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255216 | [TP for AIoT BL CR 38.300] Resolution of open points and signalling for AIoT | Nokia | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255217 | [TP for AIoT BL CR TS 38.413] Resolution of open points and signalling for AIoT | Nokia | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255218 | [TP for A-IoT BL CR TS 38.300] AIoT Release procedures for Inventory and Command | Nokia | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255219 | [TP for AIoT BL CR TS 38.413] AIoT Release procedures for Inventory and Command | Nokia | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255220 | [TP for LP-WUS BL CR TS 38.423] Conclusions for LP-WUS open points | Nokia | other | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255221 | [TP for LP-WUS BL CR TS 38.300] Conclusion of Paging Loss | Nokia | other | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255222 | Handling of Emergency call back and Paging | Nokia | discussion |
8.1New Incoming LSs
| Yes |
No
| available | No | |||
| R3‑255223 | Response LS on Emergency call back and paging | Nokia | LS out | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255224 | (TP to 38.423, 38.473) Supporting resource coordination in WAB | ZTE Corporation | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255225 | (TP to 38.401, 38.413) Remaining issues for WAB | ZTE Corporation | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255226 | Discussion on IP version selection at Femto GW | ZTE Corporation, China Telecom, Samsung, Baicells, Pengcheng Laboratory | discussion | Discussion |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255227 | (TP to TS 38.300) on support of Femto | ZTE Corporation | other | Agreement |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255228 | Remaining issues on multi-hop relay | ZTE Corporation | discussion | Discussion |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255229 | (TP to TS 38.401, 38.473) on support of multi-hop relay | ZTE Corporation | other | Agreement |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255230 | Remaining issues on LP-WUS | ZTE Corporation | discussion | Discussion |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255231 | (TP to TS 38.413) on support of LP-WUS | ZTE Corporation | other | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255232 | Specifying procedure texts for the Core Network Assistance Information for RRC INACTIVE IE | Huawei, Ericsson, Nokia | CR | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255233 | Correction of PEI and emergency PDU session | Huawei, Qualcomm, Ericsson, China Telecom, Nokia, CATT | draftCR | Endorsement |
9.2NR
| Yes |
No
| available | No | R3‑253408 | |
| R3‑255234 | Correction of PEI and emergency PDU session | Huawei, Qualcomm, Ericsson, China Telecom, Nokia, CATT | draftCR | Endorsement |
9.2NR
| Yes |
No
| available | No | R3‑253409 | |
| R3‑255235 | Emergency call back and paging | Huawei | discussion |
8.1New Incoming LSs
| Yes |
No
| available | No | |||
| R3‑255236 | [draft] Reply LS on emergency call back and paging | Huawei | LS out | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255237 | (TP to BLCR for TS 38.413, TS 38.423 and TS 38.300) Discussion on Low-power wake-up signal and receiver for NR | Huawei | other | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255238 | (TP to BLCR for TS 38.473) Discussion on Low-power wake-up signal and receiver for NR | Huawei | other | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255239 | (TP to BLCR for TS 38.473 and TS 38.470) Discussion on on-demand SSB SCell operation | Huawei | other | Agreement |
17.2Support on-demand SSB SCell operation
| Yes |
No
| available | No | R3‑253258 | |
| R3‑255240 | (TP to BLCR for TS 38.473, TS 38.423 and TS 38.420) Discussion on on-demand SIB1 for UEs in idle or inactive mode | Huawei | other | Agreement |
17.3Support on-demand SIB1 for UEs
| Yes |
No
| available | No | R3‑253259 | |
| R3‑255241 | (TP to BLCR for TS 38.473) Finalizing common signal adaptation | Huawei | other | Agreement |
17.4Others
| Yes |
No
| available | No | R3‑253407 | |
| R3‑255242 | Discussion on L3-report based SCell activation | CATT, China Telecom, CMCC, NTT Docomo, Huawei | discussion | Decision |
9.2NR
| Yes |
No
| available | No | R3‑253300 | |
| R3‑255243 | (TP for to BLCR for TSto 38.401) On remaining issues of WAB | CATT | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255244 | On resource coordination for WAB | CATT | discussion | Decision |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255245 | Discussion on remain issue of NR Femto | CATT | discussion | Decision |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255246 | (TP to BLCR for TS 38.300) Miscellaneous corrections for NR Femto | CATT | other | Agreement |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255247 | (TP to BLCRs for TS 38.473) On remaining issues of OD-SSB | CATT | other | Agreement |
17.2Support on-demand SSB SCell operation
| Yes |
No
| available | No | ||
| R3‑255248 | (TP to BLCR for TS 38.300) On remaining issues of OD-SIB1 | CATT | other | Agreement |
17.3Support on-demand SIB1 for UEs
| Yes |
No
| available | No | ||
| R3‑255249 | (TP to BLCR for TS 38.473) Adaptation of paging | CATT, ZTE, China Telecom, Samsung | other | Agreement |
17.4Others
| Yes |
No
| available | No | ||
| R3‑255250 | (TP to BLCR of TS 38.300) On remaining issues of LP-WUS | CATT | other | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255251 | (TP to BLCR for TS 38.413, 38.423, 38.473) On CN Subgroup ID range for LP-WUS | CATT | other | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255252 | Remaining issues of WAB | Qualcomm Inc. | discussion | Discussion |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255253 | (TP to TS 38.401) WAB resource coordination | Qualcomm Inc. | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255254 | BL draft CR to TS 38.300 on Support of WAB | Qualcomm, Ericsson, CATT, ZTE, Nokia, Nokia Shanghai Bell | draftCR | Endorsement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255255 | (TP to BL CR 38.401) Stage-2 procedures for OD SIB1 | Qualcomm Inc. | other | Agreement |
17.3Support on-demand SIB1 for UEs
| Yes |
No
| available | No | ||
| R3‑255256 | Support LP-WUS subgrouping in RRC_IDLE/RRC_INACTIVE | Qualcomm Inc. | discussion | Discussion |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255257 | (TP to BL CR for TS 38.401) Stage-2 Updates for SL Multi-hop | Ericsson | other | Agreement |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255258 | (TP to BL CR for TS 38.473) Support of SL Multi-hop in F1AP | Ericsson | other | Agreement |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255259 | Further discussion on emergency call back and paging | ZTE Corporation | discussion | Discussion |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255260 | [Draft] Reply LS on emergency call back and paging | ZTE Corporation | LS out | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255261 | (TPs to BL CR for 38.300, 38.413 and 38.423) Further discussion on SONMDT enhancements for NTN | ZTE Corporation | other | Agreement |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | ||
| R3‑255262 | Remaing issues for NR NTN | ZTE Corporation | discussion | Discussion |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255263 | (TP to BL CR for 38.413) Support of NG Suspend and Resume Indication | ZTE Corporation, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, CMCC, Samsung, China Telecom, LG Electronics, Xiaomi | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255264 | (TP to BL CR for 38.413) Support of MBS Broadcast | ZTE Corporation | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255265 | Updated Work Plan for IoT NTN | ZTE Corporation, CATT, MediaTek.Inc | Work Plan | Information |
15.1General
| Yes |
No
| available | No | ||
| R3‑255266 | Remaing issues for IoT NTN | ZTE Corporation | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255267 | UE-to-UE CLI mitigation support | Charter Communications, Inc | other | Agreement |
19.2Support CLI Handling
| Yes |
Yes
| noted | No | ||
| R3‑255268 | Completion of Inter-CU LTM | Ericsson | discussion |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑255269 | (TP for LTM BL CR for TS 38.423, TS 38.473, TS 38.300, TS 38.401) – Support for inter-CU LTM | Ericsson | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255270 | (TP to CLTM BL CR for TS 38.473, TS 38.401) – Completion of Intra-CU Conditional LTM | Ericsson | other | Agreement |
13.3Support for Conditional LTM
| Yes |
No
| available | No | ||
| R3‑255271 | AI/ML enabled Coverage and Capacity Optimization: Cause value in the Neighbour Future Coverage Modification Notification | Ofinno, LLC | discussion |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | |||
| R3‑255272 | (TP for BLCR to 38.473) AI/ML enabled Coverage and Capacity Optimization: Cause value in the Neighbour Future Coverage Modification Notification | Ofinno, LLC | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255273 | AI/ML enabled Coverage and Capacity Optimization | Ofinno, LLC | discussion |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | |||
| R3‑255274 | Mobility Optimization for NR-DC | Ofinno, LLC | discussion |
11.4R18 leftovers
| Yes |
No
| available | No | |||
| R3‑255275 | (TP for BLCR to 38.423) Mobility Optimization for NR-DC | Ofinno, LLC | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255276 | [TP for BL CR TS 38.300] Introduction of SRS resource configurations for Evolution of NR duplex operation Sub-Band Full Duplex | Charter Communications, Inc | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255277 | [TP for BL CR 38.423] Introduction of UE-to-UE CLI mitigation support signaling | Charter Communications, Inc | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255278 | [TP for BL CR 38.473] Introduction of UE-to-UE CLI mitigation support signaling | Charter Communications, Inc | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255279 | Remaining issues on XR uplink rate control | Ofinno, LLC | discussion |
21.3Others
| Yes |
No
| available | No | |||
| R3‑255280 | (TPs for TS 38.423, TS 37.340) Support of UL rate control | Ofinno, LLC | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255281 | Remaining Issues on Data Forwarding for SN initiated Inter-SN LTM | Ofinno, LLC | discussion | Decision |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255282 | (TP for TS 38.423) Cell Switch Notification for LTM DC Scenario | Ofinno, LLC | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255283 | Open Issues on Access Success for Inter-SN SCG LTM | Ofinno, LLC | discussion |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑255284 | Discussion on remaining issues for AI/ML-based CCO | LG Electronics Inc. | discussion |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | |||
| R3‑255285 | (TP for NR_AIML_NGRAN_enh-Core for TS 38.423) Discussion on remaining issues for AIML-based CCO | LG Electronics Inc. | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255286 | (TP for NR_AIML_NGRAN_enh-Core for TS 38.473) Discussion on remaining issues for AIML-based CCO | LG Electronics Inc. | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255287 | Remaining Issues on Support of NTN Regenerative Architecture | TCL | discussion | Discussion |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255288 | Remaining Issues for AI/ML based positioning case 3a and TP to NRPPa | CEWiT, IITM, Tejas Networks | other | Decision |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255289 | Correction on the description of UE Context Information - Retrieve UE Context Response | ZTE Corporation | CR | Agreement |
31.1Corrections
| Yes |
No
| available | No | ||
| R3‑255290 | (TP for TS 38.401) Discussion on NG management and Xn management for WAB | Nokia, Nokia Shanghai Bell | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255291 | (TP to BL CR for TS 38.413 and TS 38.423) Enhancement for WAB | Nokia, Nokia Shanghai Bell | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255292 | (TP to BL CR for TS 38.300) Clarification on the OAM requirements | Nokia, Nokia Shanghai Bell | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255293 | Discussion on the support of S&F | Nokia, Nokia Shanghai Bell | discussion |
15.2Support Full eNB as Regenerative Payload
| No |
Yes
| withdrawn | Yes | |||
| R3‑255294 | (TP to BL CR for TS 36.300) Correction on S1 Removal | Nokia, Nokia Shanghai Bell, Huawei, Ericsson, LG Electronics, Samsung | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255295 | (TP to BL CR for TS 36.413) Support of regenerative payload | Nokia, Nokia Shanghai Bell, ZTE Corporation, CATT, Qualcomm, CMCC, Samsung, China Telecom, LG Electronics, Xiaomi | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255296 | Rapporteur Inputs on workplan | Nokia, Qualcomm (Rapporteurs) | Work Plan | Information |
21.1General
| Yes |
No
| available | No | ||
| R3‑255297 | (TP to BL CR for TS 37.340) Discussion on the remaining issues for Rel-19 XR | Nokia, Nokia Shanghai Bell | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255298 | (TP for BL CR for TS 38.300) enhancements to Stage-2 | Nokia, Nokia Shanghai Bell, ZTE Corporation, Ericsson | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255299 | (TP to BL CR for TS 38.473) Discussion on the support of multi-hop Layer-2 UE-to-Network relay | Nokia, Nokia Shanghai Bell | other | Agreement |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255300 | (TP to BL CR for TS 38.401) update for service continuity | Nokia, Nokia Shanghai Bell | other | Agreement |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255301 | Signalling enhancements for Inter-CU LTM handover | Qualcomm India Pvt Ltd | discussion | Agreement |
13.3Support for Conditional LTM
| Yes |
No
| available | No | ||
| R3‑255302 | Signalling enhancements for Intra-CU Conditional LTM | Qualcomm India Pvt Ltd | discussion | Agreement |
13.3Support for Conditional LTM
| Yes |
No
| available | No | ||
| R3‑255303 | Discussion on 7MHz channel bandwidth | Nokia | discussion |
8.1New Incoming LSs
| Yes |
No
| available | No | |||
| R3‑255304 | TP (BL CR TS38.473) Support for 7MHz transmission bandwidth | Nokia, T-Mobile USA | other | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255305 | (TPs to BL CR for 38.470 and 38.473) Support of on-demand SSB Scell operation | ZTE Corporation | other | Agreement |
17.2Support on-demand SSB SCell operation
| Yes |
No
| available | No | ||
| R3‑255306 | (TPs to BL CR for TS38.420, TS38.470 and TS38.473) Support of on-demand SIB1 | ZTE Corporation | other | Agreement |
17.3Support on-demand SIB1 for UEs
| Yes |
No
| available | No | ||
| R3‑255307 | (TP to BL CR for 38.470) Support of Paging Adaptation | ZTE Corporation | other | Agreement |
17.4Others
| Yes |
No
| available | No | ||
| R3‑255308 | TP (BL CR TS38.423) Support for 7MHz transmission bandwidth | Nokia, T-Mobile USA | other | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255309 | [Draft] Reply LS on emergency call back and paging | Qualcomm India Pvt Ltd | LS out | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255310 | nodelevel indication of temporary NTN feeder-link outage via RAN CONFIGURATION UPDATE | Jio Platforms | CR | Agreement |
14.3Support of Regenerative payload
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑255311 | (TP for TS 36.300) Support for Regenerative Payload for IoT NTN | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE, CATT, China Telecom, CMCC, LG Electronics, Xiaomi | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255312 | Discussion on Support for IoT NTN for Regenerative Payload | Qualcomm Incorporated | discussion | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255313 | Interface management procedures and Reader selection | Qualcomm Incorporated | discussion | Discussion |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255314 | Open issues on Inventory and Command procedures | Qualcomm Incorporated | discussion | Discussion |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255315 | MRO enhancements for LTM | Qualcomm Incorporated | discussion | Discussion |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255316 | MDT enhancements for NTN | Qualcomm Incorporated | discussion | Discussion |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | ||
| R3‑255317 | Discussion on remaining issues in AI/ML enabled CCO | Qualcomm Incorporated | discussion | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255318 | Discussion on UE Performance Reporting for Split Architecture | Qualcomm Incorporated | discussion | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255319 | Support Cell Level Measurements signaling from CU to DU for L3 measurement based R18 LTM | Qualcomm Inc, Apple Inc, NTT DOCOMO, AT&T, Boost Mobile Networks, JIO Platforms, Charter Communications, Rakuten, CEWiT, Vivo, Tejas Networks, Xiaomi. | discussion | Agreement |
9.2NR
| Yes |
Yes
| noted | No | ||
| R3‑255320 | Workplan for Rel-19 SON_MDT Enhancement | China Unicom, CMCC | Work Plan | Information |
10.1General
| Yes |
No
| available | No | ||
| R3‑255321 | Discussion on MRO Enhancements | China Unicom | discussion |
10.2MRO Enhancements
| Yes |
No
| available | No | |||
| R3‑255322 | Cell level measurements in F1-AP signalling for L3 measurements-based LTM | Qualcomm Inc, Apple Inc, NTT DOCOMO, AT&T, Boost Mobile Networks, JIO Platforms, Charter Communications, Rakuten, CEWiT, Vivo, Tejas Networks, Xiaomi. | CR | Agreement |
9.2NR
| Yes |
Yes
| noted | No | ||
| R3‑255323 | R19 XR Signaling Enhancements | Qualcomm Incorporated | discussion | Agreement |
21.3Others
| Yes |
No
| available | No | R3‑253564 | |
| R3‑255324 | Signaling design to enable NR SBFD operation | Qualcomm Incorporated | discussion | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | R3‑253563 | |
| R3‑255325 | Correction on RRC establishment Cause for CIoT | Huawei, ZTE, Nokia, Qualcomm Incorporated | CR | Agreement |
9.1LTE
| Yes |
Yes
| revised | No | R3‑255751 | |
| R3‑255326 | [TPs to TS 38.300 38.413 BL CRs] A-IoT Security Aspects | Huawei, China Telecom, China Unicom | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255327 | [TPs to TS 38.300 38.413 BL CRs] Leftovers for Inventory and Command procedures | Huawei, China Telecom, China Unicom, Lenovo | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255328 | [TPs to TS 38.300, 38.413 BL CRs] A-IoT Session Release and Inventory Complete Indication | Huawei, China Telecom, China Unicom, Lenovo | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255329 | [TPs to TS 38.300 38.413 BL CRs] Leftovers for Interface Management and Reader Selection | Huawei, China Telecom, China Unicom, Lenovo | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255330 | Discussion on open issues of A-IoT | Xiaomi | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255331 | (TP to BL CR TS 38.300) Support of A-IoT | Xiaomi | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255332 | (TP to BL CR TS 38.413) Support of A-IoT | Xiaomi | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255333 | (Draft reply LS) LS on parallel service request | Xiaomi | LS out | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255334 | (TP to BL CR TS 38.300) Support of NG suspend/resume | Xiaomi | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255335 | (Draft LS out) Support of NG suspend resume | Xiaomi | LS out | Approval |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255336 | (TPs for TS 38.305 and TS 38.455) Support of gNB-side model (case 3a) | Xiaomi | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255337 | (TP to BL CR TS 38.473) addition of UL SRS time domain channel measurement | Xiaomi, Ericsson, CATT, Nokia, Samsung | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255338 | (Draft LS out) Logged data handling during handover | Xiaomi | LS out | Approval |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255339 | Signalling for 7 MHz Channel Bandwidth | Huawei | discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | |||
| R3‑255340 | Introduction of 7 MHz Channel Bandwidth | Huawei | CR | Agreement |
8.1New Incoming LSs
| Yes |
Yes
| revised | No | R3‑255752 | |
| R3‑255341 | Introduction of 7 MHz Channel Bandwidth | Huawei | CR | Agreement |
8.1New Incoming LSs
| Yes |
YesTechnically Endorsed
| revised | No | R3‑255753 | |
| R3‑255342 | [draft] Reply LS on Signalling for 7 MHz Channel Bandwidth | Huawei | LS out | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255343 | Remaining issues on support of regenerative payload for NR NTN | Samsung | discussion | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255344 | (TP for TS 38.410) NG Removal completion | Samsung, Huawei, Nokia, Nokia Shanghai Bell, Ericsson | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255345 | Remaining issue on support of regenerative payload for IoT NTN | Samsung | discussion | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255346 | (TP to BL CR for 38.413 and 38.401) Discussion on general issues for AIoT | Samsung | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255347 | (TP to BL CR for 38.300 and 38.413) Discussion on inventory complete and session release | Samsung | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255348 | Remaining issues on multi-hop for SL relay | Samsung | discussion | Agreement |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255349 | (TP to BL CR for 38.473) Support of multi-hop relay | Samsung | other | Agreement |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255350 | (TP for MDT BLCRs for TS38.413, TS38.423) SON/MDT enhancements for NTN | Samsung | other | Agreement |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | ||
| R3‑255351 | Clarification for propagation of roaming and access restrictions | Samsung | draftCR | Endorsement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255352 | Further discussion on UAV altitude information reporting | Huawei, Nokia | discussion | Agreement |
8.3Left over LSs / pending actions
| Yes |
Yes
| noted | No | ||
| R3‑255353 | Support Aerial UE Flight Information Reporting to CN | Huawei, Nokia | CR | Agreement |
8.3Left over LSs / pending actions
| Yes |
No
| available | No | ||
| R3‑255354 | (TP for AI/ML BLCR to TS 38.300) Capturing agreements in Stage 2 RAN specifications | Huawei, Jio Platforms, Deutsche Telekom, Ofinno, FiberCop, Qualcomm, InterDigital, Orange | other | Agreement |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255355 | (TP for AI/ML BLCR to TS 38.401) Capturing agreements in Stage 2 RAN specifications | Huawei, Jio Platforms, Deutsche Telekom, FiberCop, InterDigital, CATT | other | Agreement |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255356 | (TP for AI/ML BLCR to TS 37.340) Capturing agreements in Stage 2 RAN specifications | Huawei, Jio Platforms, Ofinno, Qualcomm, InterDigital, Deutsche Telekom | other | Agreement |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255357 | Further discussion on per-UE per-slice UE performance in AI/ML-based Network Slicing | Huawei, Jio Platforms, FiberCop, BT | discussion | Agreement |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255358 | (TP for AI/ML BLCR to TS 38.423) Per-UE per-slice UE performance in AI/ML-based Network Slicing | Huawei, Ofinno, Jio Platforms, FiberCop, BT | other | Agreement |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255359 | Discussion on timing aspects for AI/ML-based Coverage and Capacity Optimization | Huawei, Jio Platforms, Deutsche Telekom, Orange, BT, Vodafone | discussion | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255360 | (TP for AI/ML BLCR to TS 38.423) Timing information for predicted CCO issue over Xn | Huawei, Jio Platforms, Deutsche Telekom, Orange, BT, Vodafone | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255361 | Discussion on feedback information for AI/ML-based Coverage and Capacity Optimization | Huawei, Jio Platforms, Deutsche Telekom, Orange, Vodafone | discussion | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255362 | (TP for AIML BLCR to TS 38.423) Additional feedback information for AI/ML-based Coverage and Capacity Optimization | Huawei, Jio Platforms, Deutsche Telekom, Orange, Vodafone | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255363 | Discussion on prediction update/cancel for AI/ML-based Coverage and Capacity Optimization | Huawei, Jio Platforms, Vodafone, Deutsche Telekom, Orange | discussion | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255364 | (TP for AI/ML BLCR to TS 38.473) Replacing a predicted CCO assistance information previously signalled | Huawei, Jio Platforms, Vodafone, Deutsche Telekom, Orange | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255365 | (TP for AI/ML BLCR to TS 38.423) Replacing a predicted CCO assistance information previously signalled | Huawei, Jio Platforms, Vodafone, Deutsche Telekom, Orange | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255366 | Discussion on assistance information for SN configuration in AI/ML-based Mobility Optimization in NR-DC | Huawei, Nokia | discussion | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255367 | (TP for AI/ML BLCR to TS 38.423) Discussion on UE performance feedback for AI/ML-based Mobility Optimization in NR-DC | Huawei | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255368 | Remaining open issues on split architecture support for Rel-18 “AI/ML for NG-RAN” use cases | Huawei | discussion | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255369 | [Draft] LS reply to LS on energy saving for split gNB | Huawei | LS out | Approval |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255370 | (TP for AI/ML BLCR to TS 38.473) F1AP enhancements for split architecture support for Rel-18 “AI/ML for NG-RAN” use cases | Huawei | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255371 | (TP for AI/ML BLCR to TS 37.483) E1AP enhancements for split architecture support for Rel-18 “AI/ML for NG-RAN” use cases | Huawei | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255372 | (TPs for AI/ML BLCR to TS 38.300/305/401/455/473) Remaining open issues for AI/ML-based positioning Case 3a and Case 3b | Huawei | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255373 | (Draft Reply LS to RAN2) Discussion on R3-255016 (R2-2504950) LS Logged Data Handling During Handover | Huawei | LS out | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255374 | (TP for TS38.401) On support of inter-CU LTM | China Telecom | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255375 | Discussion on inter-CU LTM in DC scenario | China Telecom | discussion | Decision |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255376 | (TP to TS38.401) On support of intra-CU Conditional LTM | China Telecom | other | Agreement |
13.3Support for Conditional LTM
| Yes |
No
| available | No | ||
| R3‑255377 | Discussion on support of AI/ML assisted positioning (Case 3a) | China Telecom | discussion | Decision |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255378 | (TP to TS38.305) On support of AIML assisted positioning | China Telecom | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255379 | (TP to 38.473) On support on-demand SSB SCell operation | China Telecom | other | Decision |
17.2Support on-demand SSB SCell operation
| Yes |
No
| available | No | ||
| R3‑255380 | On remaining issues for NR Femto | China Telecom | discussion | Decision |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255381 | Discussion on remaining issues for IoT NTN | China Telecom | discussion | Decision |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255382 | NG transmission suspend resume procedure | China Telecom | discussion | Decision |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255383 | Remaining issues for AIoT | China Telecom | discussion | Decision |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255384 | Further discussion on multi-hop relay | China Telecom | discussion | Decision |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255385 | Discussion on AI/ML based Coverage and Capacity Optimization | China Telecom | discussion | Decision |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255386 | Clarification on E-RAB management procedures | CR | Agreement |
9.1LTE
| Yes |
Yes
| noted | No | |||
| R3‑255387 | Clarification on E-RAB management procedures | CR | Agreement |
9.1LTE
| Yes |
No
| available | No | |||
| R3‑255388 | Clarification on E-RAB management procedures | CR | Agreement |
9.1LTE
| Yes |
No
| available | No | |||
| R3‑255389 | Discussion on XR rate control | vivo | discussion | Discussion |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255390 | Correction of system information management function | Huawei | CR | Agreement |
31.1Corrections
| Yes |
No
| available | No | ||
| R3‑255391 | Clarification on PDU session management procedures | CR | Agreement |
9.2NR
| Yes |
No
| available | No | |||
| R3‑255392 | Clarification on PDU session management procedures | CR | Agreement |
9.2NR
| Yes |
No
| available | No | |||
| R3‑255393 | (TP for SON BLCR for 38.473) Discussion on MRO for LTM | Lenovo | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255394 | (TP for SON BLCR for 38.423) Discussion on MRO for CHO with candidate SCG(s) and subsequent CPAC | Lenovo | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255395 | Discussion on SON/MDT for NTN | Lenovo | discussion |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | |||
| R3‑255396 | Discussion on AI/ML based CCO | Lenovo | discussion |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | |||
| R3‑255397 | (TP to BLCR 37.483) UE performance collection via E1 interface after intra-CU-UP HO | Lenovo | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255398 | (TP to BLCR 37.340) Discussion on UE performance collection in AIML for NR-DC | Lenovo | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255399 | (TP to BLCR 38.401) AIML for RAN in split architecture | Lenovo, CATT, ZTE Corporation | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255400 | (TP to BLCR 38.423) Xn management for WAB-node | Lenovo | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255401 | (TP to BLCR 38.413) Discussion on remaining issues for WAB-node | Lenovo | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255402 | Discussion on remaining issues for NR Femto | Lenovo | discussion |
12.35G Femto
| Yes |
No
| available | No | |||
| R3‑255403 | [TP to BLCR for TS 38.401] Inter-CU LTM | Lenovo | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255404 | [TP to BLCR for TS 38.423] Inter-CU LTM in DC | Lenovo | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255405 | [TP to BLCR for TS 38.423] Inter-CU LTM in DC - text update | Lenovo | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255406 | Discussion on NW side data collection | Lenovo | discussion |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | |||
| R3‑255407 | (TP to BLCR 38.455) Provision of associated ID in Case 1 | Lenovo | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255408 | (TP to XR BLCR for 38.473) On Timely RLC Retransmission | Lenovo | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255409 | (TP to XR BLCR for 38.425) On Unnecessary RLC Retransmission Avoidance | Lenovo | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255410 | Clarification on PDU session management procedures | CR | Agreement |
9.2NR
| Yes |
No
| available | No | |||
| R3‑255411 | (TPs for WAB BL CRs) Architecture, Access Control and Additional ULI for WAB | Huawei | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255412 | (TP for WAB BL CRs) Radio Resource Multiplexing Coordination for WAB-node | Huawei | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255413 | (TP for Femto BL CR for TS 38.300/38.413) Discussion on NG mobility impact for NR Femto | Huawei, Ericsson, Qualcomm | other | Agreement |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255414 | (TP for Femto BL CR for TS38.300) Discussion on NR Femto awareness at CN | Huawei | other | Agreement |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255415 | (TP for Femto BL CRs for TS 38.413) NR Femto awareness at CN | Huawei | other | Agreement |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255416 | Discussion on UL rate control | Huawei | discussion |
21.3Others
| Yes |
No
| available | No | |||
| R3‑255417 | (TP for XR BL CRs) Discussion on RLC enhancements for XR | Huawei | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255418 | (TP to BL CR 38.423) Clarification on inter-CU LTM and LTM with SCG in NR-DC | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑255419 | (TP to BL CR 37.340 and 38.473) Clarification on inter-CU LTM and LTM with SCG in NR-DCs | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑255420 | Further discussion on LP-WUS | NTT DOCOMO INC.. | discussion |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | |||
| R3‑255421 | Discussion on inter-CU LTM | NTT DOCOMO INC.. | discussion |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑255422 | (TP for BL CR for TS 38.473) enhancements to support timely RLC retransmissions | Nokia, Nokia Shanghai Bell | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255423 | SON MDT for Intra-NTN Mobility | Jio Platforms | discussion | Decision |
10.3.1Intra-NTN Mobility
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑255424 | (TP for LTM BLCR for TS38.300): Inter-CU LTM | Huawei | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255425 | (TP for LTM BLCR for TS38.473):Inter-CU LTM | Huawei | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255426 | [DRAFT] Reply LS on security handling for inter-CU LTM in non-DC cases | Huawei | LS out | Approval |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255427 | (TP for LTM BLCR for TS38.473, TS38.401): Intra-CU conditional LTM | Huawei | other | Agreement |
13.3Support for Conditional LTM
| Yes |
No
| available | No | ||
| R3‑255428 | Discussion on SONMDT for Intra-NTN mobility | Huawei, CMCC, Jio Platforms, China Unicom | discussion |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | |||
| R3‑255429 | (TP for MDT BLCR for TS38.413): MDT enhancement for NTN | Huawei, CMCC, Jio Platforms, China Unicom | other | Agreement |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | ||
| R3‑255430 | (TP for MDT BLCR for TS38.423): MDT enhancement for NTN | Huawei, CMCC, Jio Platforms, China Unicom | other | Agreement |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | ||
| R3‑255431 | (TP for MDT BLCR for TS37.320): MDT enhancement for NTN | Huawei, CMCC, Jio Platforms, China Unicom | other | Agreement |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | ||
| R3‑255432 | Ping-Pong Mitigation in CU-DU Coordination for LTM Mobility | Jio Platforms | discussion | Decision |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255433 | SON MDT for Intra-NTN Mobility | Jio Platforms | discussion | Decision |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | ||
| R3‑255434 | (TP for BLCR to TS 38.300, 38.401, 38.423, 38.473) Remaining issues for AI/ML-based CCO | Nokia | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255435 | (TP for BLCR to TS 38.473) On assistance information for OD-SSB over F1 | Nokia | other | Agreement |
17.2Support on-demand SSB SCell operation
| Yes |
No
| available | No | ||
| R3‑255436 | (TP for BLCR to TS 38.423, TS 38.473) Stage 3 Proposals for On-Demand SIB1 | Nokia | other | Agreement |
17.3Support on-demand SIB1 for UEs
| Yes |
No
| available | No | ||
| R3‑255437 | Discussion on adaptation of common signals/channels | Nokia | discussion |
17.4Others
| Yes |
No
| available | No | |||
| R3‑255438 | (TP for BLCRs to TS 38.420, 38.470) Finalizing stage 2 for Sub-band Full Duplex operation | Nokia | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255439 | (TP for BLCRs to TS 38.423, 38.473) Finalizing stage 3 for Sub-band Full Duplex operation | Nokia | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255440 | (TP for LTM CR for TS38.423): LTM Resource Lifecycle Management in inter-CU LTM | Jio Platforms | other |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑255441 | (TP for AI/ML BLCR to TS 38.423) AI/ML-Based CCO with Timing Aspects over Xn | Jio Platforms | other | Decision |
11.3AI/ML enabled Coverage and Capacity Optimization
| No |
Yes
| withdrawn | Yes | ||
| R3‑255442 | (TP for TS 38.413) Introduce gNB-initiated AMF switch signaling to support UE context transfer for regenerative NTN gNB mobility | Jio Platforms | other | Agreement |
14.3Support of Regenerative payload
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑255443 | (TP for TS 36.300) IoT-NTN Switchover (FLSO) & Store-and-Forward Principles | Jio Platforms | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255444 | Inventory completion indication (via Inventory Report Transfer) | Jio Platforms | CR | Agreement |
16Ambient IoT WI
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑255445 | Define AIoT-FunctionIdentifier and AIoT-CorrelationIdentifier IEs (encoding closure) | Jio Platforms | CR | Agreement |
16Ambient IoT WI
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑255446 | Collection of rejected slice information for slice coverage optimisation | Ericsson, BT, Deutsche Telekom, Jio Platforms (JPL), FiberCop, InterDigital | discussion | Agreement |
10.3.2Network Slicing
| Yes |
No
| available | No | ||
| R3‑255447 | (TP for BL CR to 38.413 for SON) Collection of rejected slice information for slice coverage optimisation | Ericsson, BT, Deutsche Telekom, Jio Platforms (JPL), FiberCop, InterDigital | other | Agreement |
10.3.2Network Slicing
| Yes |
No
| available | No | ||
| R3‑255448 | Correction of the granularity of the Average Packet Loss DL IE | Nokia | CR | Agreement |
9.2NR
| Yes |
Yes
| noted | No | ||
| R3‑255449 | (TP to TS 38.423) AI/ML Slicing Remaining Aspects | Nokia | other | Agreement |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255450 | [Draft] Reply LS on clarification on UE performance measurement at PDCP level | Nokia | LS out | Approval |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255451 | (TP to TS 38.401) Stage 2 updates for split architecture support | Nokia, Deutsche Telekom, Orange | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255452 | (TP to TS 38.425) Stage 2 NR User Plane Updates | Nokia, FiberCop, Deutsche Telekom | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255453 | (TP to TS 38.423) Remaining issues for AI/ML Mobility Optimization in NR-DC | Nokia | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255454 | Open points on UE Performance in Split Architecture | Nokia | discussion |
11.4R18 leftovers
| Yes |
No
| available | No | |||
| R3‑255455 | (TP to TS 38.473, TP to TS 37.483) UE Performance in Split Architecture | Nokia | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255456 | (TP to TS 38.300) AI/ML Training in OAM for case 3a | Nokia, Ericsson, Xiaomi, Samsung, CATT, ZTE | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255457 | (TP to TS 38.305) Addressing remaining aspects in case 3a and case 3b | Nokia | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255458 | Logged Data Handling after a Handover Event | Nokia | discussion |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | |||
| R3‑255459 | [Draft] Reply LS on Logged Data Handling During Handover | Nokia | LS out | Approval |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255460 | On packet loss metric in UE performance | Ericsson, Deutsche Telekom, Jio Platforms | discussion | Approval |
9.2NR
| Yes |
Yes
| noted | No | ||
| R3‑255461 | Correction to exclude Packet Loss as a UE Performance metric | Ericsson, Deutsche Telekom, Jio Platforms | CR | Agreement |
9.2NR
| Yes |
Yes
| noted | No | R3‑253475 | |
| R3‑255462 | (TP to TS 38.300) AI/ML support | Ericsson, Deutsche Telekom, Jio Platforms, BT | other | Agreement |
11.1General
| Yes |
No
| available | No | ||
| R3‑255463 | (TP to TS 38.401) AI/ML support | Ericsson, Deutsche Telekom, Jio Platforms, BT | other | Agreement |
11.1General
| Yes |
No
| available | No | ||
| R3‑255464 | AI/ML enabled Network Slicing | Ericsson, Jio Platforms | discussion | Approval |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255465 | (TP for BLCR to 38.423) Support of AI/ML assisted Network Slicing | Ericsson, Jio Platforms | other | Agreement |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255466 | Prediction time for CCO issue | Ericsson, Jio Platforms, Orange, InterDigital, BT, Deutsche Telekom, FiberCop | discussion | Approval |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255467 | (TP for TS 38.423) - Prediction time for CCO issue | Ericsson, Jio Platforms, Orange, InterDigital, BT, Deutsche Telekom, FiberCop | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255468 | Cancel or update a predicted CCO issue | Ericsson, Jio Platforms, Orange, InterDigital, Deutsche Telekom, FiberCop | discussion | Approval |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255469 | (TP for TS 38.423) - Cancel or update a predicted CCO issue | Ericsson, Jio Platforms, Orange, InterDigital, Deutsche Telekom, FiberCop | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255470 | (TP for TS 38.473) - Cancel or update a predicted CCO issue | Ericsson, Jio Platforms, Orange, InterDigital, Deutsche Telekom, FiberCop | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255471 | UE radio measurements for CCO | Ericsson, Jio Platforms, Orange, Deutsche Telekom | discussion | Approval |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255472 | (TP for TS 38.423) – UE radio measurements for CCO | Ericsson, Jio Platforms, Orange, Deutsche Telekom | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255473 | AI/ML support for NR-DC | Ericsson, Jio Platforms | discussion | Approval |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255474 | (TP to TS 38.423) AI/ML support for NR-DC | Ericsson, Jio Platforms | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255475 | On LS discussions with SA5 on Packet loss measurements | Ericsson, Deutsche Telekom, Jio Platforms | discussion | Approval |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255476 | Introduction of new packet loss metric in UE performance | Ericsson, Deutsche Telekom, Jio Platforms | discussion | Approval |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255477 | (TP to 38.423) On packet loss metric in UE performance | Ericsson, Deutsche Telekom, Jio Platforms | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255478 | (TP to 37.320) - Continuous MDT collection targeting the same UE across RRC states | Ericsson, ZTE Corporation, BT, Deutsche Telekom, InterDigital, Jio Platforms | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255479 | (TP for AI/ML BLCR to TS38.423) Continuous MDT collection targeting the same UE across RRC states | Ericsson, ZTE Corporation, BT, Deutsche Telekom, InterDigital, Jio Platform | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255480 | (TP to BLCR to TS38.423 for SBFD) Discussion on SBFD WI completion | Ericsson | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255481 | (TP to BLCR to TS38.300 for SBFD) Introduction of SBFD | Ericsson | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255482 | Discussion on remaining open issues in A-IoT | LG Electronics | discussion |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | |||
| R3‑255483 | Usage of root cause in MRO | Huawei, Vodafone, Nokia, Qualcomm, BT, Jio Platforms | discussion |
9.2NR
| Yes |
No
| available | No | |||
| R3‑255484 | Usage of root cause in SON/MRO | Huawei, Vodafone, Nokia, Qualcomm, BT, Jio Platforms | draftCR | Endorsement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255485 | Usage of root cause in SON/MRO | Huawei, Vodafone, Nokia, Qualcomm, BT, Jio Platforms | draftCR | Endorsement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255486 | Usage of root cause in MRO | Huawei, Vodafone, Qualcomm, BT, Jio Platforms | discussion |
10.2MRO Enhancements
| Yes |
No
| available | No | |||
| R3‑255487 | (TP for BLCR for SON for 38.401) Usage of root cause in MRO | Huawei, Vodafone, Qualcomm, BT, Jio Platforms | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255488 | LTM ping pong | Huawei, Qualcomm, CMCC, Jio Platforms | discussion |
10.2MRO Enhancements
| Yes |
No
| available | No | |||
| R3‑255489 | (TP for BLCR for SON for 38.473) LTM ping pong | Huawei, Qualcomm, CMCC, Jio Platforms | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255490 | (TP for BLCR for SON for 38.413) LTM ping pong | Huawei, Qualcomm, CMCC, Jio Platforms | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255491 | LTM Near failure TA | Huawei, Ericsson, Jio Platforms | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255492 | SON/MDT Leftovers | Huawei | other | Agreement |
10.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255493 | (TP for 38.401) Multi-hop relay | Huawei | other | Agreement |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255494 | (TP for 38.473) Multi-hop relay | Huawei | other | Agreement |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255495 | MRO for NTN | Huawei | other | Agreement |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | ||
| R3‑255496 | (TP to TS 38.300 and 38.413) TP for A-IoT support | LG Electronics | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255497 | (TP on 38.423)Discussion on slice level UE performance | CATT | other | Agreement |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255498 | Open issues on CCO issue | CATT | discussion | Decision |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255499 | (TP for 38.423 and 38.473)Open issues on CCO issue | CATT | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255500 | (TP on 37.340) Discussion on AI/ML in DC scenario | CATT | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255501 | (TP for 38.423) AI/ML in DC scenario | CATT | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255502 | (TP on 37.483 and 38.473)AI/ML for split scenario | CATT | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255503 | (TP to BL CR to 38.401) AI/ML assisted Positioning | ZTE Corporation, Ericsson, Xiaomi, Nokia, Samsung, CATT | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255504 | (TP to BL CR to 38.455) Support of AI/ML assisted Positioning (case 3a) | ZTE Corporation | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255505 | [Draft LS] Reply LS on logged Data Handling During Handover | ZTE Corporation | LS out | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255506 | (TP for TS 38.413) NG Removal completion | Huawei, LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson, Thales, Jio Platforms, CATT, Qualcomm Incorporated, Deutsche Telekom,Samsung | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255507 | (TP for TS 36.413) S1 Removal completion | Huawei, LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson, Thales, Jio Platforms, CATT, Qualcomm Incorporated, Deutsche Telekom,Samsung | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255508 | (TP to BL CR for TS 38.300) Hard FLSO and AMF management | Huawei, Ericsson, Thales, Jio Platforms, Deutsche Telekom | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255509 | (TP to BL CR for TS 36.300) Hard FLSO and MME management | Huawei, Ericsson, Thales, Jio Platforms, Deutsche Telekom | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255510 | (TP to BLCR for TS 38.300) Further discussion on TAI configuration | Huawei, Jio Platforms, Ericsson | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255511 | (TP to BL CR for TS 36.300) Removal of the Suspend/Resume part of TS 36.300 | Huawei | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑255512 | (TP for TS 36.300) Full eNB as Regenerative Payload - TNL aspetcs | Huawei, Jio Platforms | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255513 | (TP for TS 36.300) Discussion on S&F mode transition | Huawei, Jio Platforms, Ericsson | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255514 | (TP for TS 36.300) Provision of S&F Mode Indication of neighbour cell list | Huawei, Ericsson, Jio Platforms | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255515 | Discussion on Reply LS to SA2 on support of Full eNB as Regenerative Payload | Huawei, Jio Platforms, Ericsson | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255516 | [DRAFT] Reply LS on Support of Regenerative-based Satellite Access | Huawei, Jio Platforms, Ericsson | LS out | Approval |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255517 | Draft skeleton of the RAN3 Technical Report (TR) for 6G | VODAFONE Group Plc | discussion | Information |
32Any other business
| Yes |
No
| available | No | ||
| R3‑255518 | PNI NPN with limited CAG validity | Nokia | discussion |
31.1Corrections
| Yes |
No
| available | No | |||
| R3‑255519 | Enhancement of Split Bearers | Nokia | discussion |
31.2Enhancements
| Yes |
No
| available | No | |||
| R3‑255520 | Support Aerial UE Flight Information Failure Reporting in FAILURE INDICATION message | Ericsson, CMCC, CATT | CR | Agreement |
8.3Left over LSs / pending actions
| Yes |
No
| available | No | ||
| R3‑255521 | Handling of Radio Capability for Paging | Nokia | discussion |
8.1New Incoming LSs
| Yes |
No
| available | No | |||
| R3‑255522 | Response LS on handling of UE radio capability for paging | Nokia | LS out | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255523 | Way Forward On Multi-hop Prevention for WAB | China Telecom, CATT, Huawei, DoCoMo, Lenovo, Samsung, NEC | discussion |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | |||
| R3‑255524 | Correction of handling UE radio capability for paging | Nokia | CR | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255525 | Correction of handling UE radio capability for paging | Nokia | CR | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255526 | Correction of handling UE radio capability for paging | Nokia | CR | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255527 | Missing UE radio paging capabilities | VODAFONE Group Plc | discussion | Decision |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255528 | [Draft] Reply LS on paging capability loss issue | VODAFONE Group Plc | LS out | Approval |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255529 | Paging capability loss in RAN | VODAFONE Group Plc | CR | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255530 | Paging capability loss in RAN | VODAFONE Group Plc | CR | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255531 | Paging capability loss in RAN | VODAFONE Group Plc | CR | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255532 | PRACH resources for RACH-less LTM | Ericsson, Jio Platforms, Lenovo, NTT DoCoMo | discussion |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑255533 | (TP to BL CR for TS 38.423) – PRACH Resources for RACH-less LTM | Ericsson, Jio Platforms, Lenovo, NTT DoCoMo | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255534 | (TP to BL CR for TS 38.473) – PRACH Resources for RACH-less LTM | Ericsson, Jio Platforms, Lenovo, NTT DoCoMo | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255535 | Rel-18 LTM Correction for L2 reset | Ericsson, CATT, Jio Platforms | discussion |
9.2NR
| Yes |
Yes
| noted | No | |||
| R3‑255536 | F1AP correction for Layer 2 reset at inter-gNB-DU LTM | Ericsson, CATT, Jio Platforms | CR | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255537 | Stage 2 correction for Layer 2 reset at inter-gNB-DU LTM | Ericsson, CATT, Jio Platforms | draftCR | Endorsement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255538 | PWS Support in NTN | Ericsson, Thales, Huawei | discussion | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑255539 | Partial Data Collection Reporting | Ericsson, Jio Platforms, BT, LG Electronics | discussion | Decision |
31.2Enhancements
| Yes |
No
| available | No | ||
| R3‑255540 | NR Femto Indication in NGAP | Ericsson, Qualcomm Incorporated | discussion | Discussion |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255541 | Open topics for Rel-19 work on A-IoT | Ericsson | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255542 | [TP for BL CR 38.300 and 38.413] Correcting references to AS related protocol elements | Ericsson | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255543 | [TP for BL CR 38.300 and 38.413] Applicability of A-IoT procedures for multiple devices | Ericsson | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255544 | [TP for BL CR 38.413] Reconsideingr WA on A-IoT support indication | Ericsson | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255545 | TAI Coordination and OAM | Ericsson, Huawei | discussion | Discussion |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255546 | Downlink NG Transmission Suspend/Resume | Ericsson, Thales, Huawei, Jio Platforms, Airbus, ESA, Sateliot, Deutsche Telekom | discussion | Discussion |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255547 | Downlink NG Transmission Suspend/Resume – Stage 2 TP | Ericsson, Thales, Huawei, Jio Platforms, Airbus, ESA, Sateliot, Deutsche Telekom | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255548 | Downlink NG Transmission Suspend/Resume – NGAP TP | Ericsson, Thales, Huawei, Jio Platforms, Airbus, ESA, Sateliot, Deutsche Telekom | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255549 | Downlink Transmission Suspend/Resume – Stage 2 TP | Ericsson, Thales, Huawei, Jio Platforms, Airbus, ESA, Sateliot, Deutsche Telekom | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| Yes |
Yes
| revised | No | R3‑255750 | |
| R3‑255550 | gNB-DU initiated LTM resource reconfiguration | Rakuten Mobile Inc, Qualcomm Inc, NTT DOCOMO INC | discussion | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255551 | (TP for TS 38.455) Enhancements for AI/ML-assisted Positioning – Feedback, Model Identification, and Training-Inference Consistency | Jio Platforms | other | Discussion |
20.2Support Positioning Accuracy Enhancements
| No |
Yes
| withdrawn | Yes | ||
| R3‑255552 | Discussion on the LS from SA2 on emergency call back and paging | Ericsson | discussion | Discussion |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255553 | Clarification on emergency call back and UE RRC state | Ericsson | draftCR | Endorsement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255554 | Clarification on emergency call back and UE RRC state | Ericsson | draftCR | Endorsement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255555 | [DRAFT] Reply LS on emergency call back and paging | Ericsson | LS out | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255556 | Clarification on BL CE UE in RRC_INACTIVE | Ericsson | draftCR | Endorsement |
9.1LTE
| Yes |
Yes
| noted | No | ||
| R3‑255557 | Clarification on BL CE UE in RRC_INACTIVE | Ericsson | draftCR | Endorsement |
9.1LTE
| Yes |
Yes
| noted | No | ||
| R3‑255558 | Clarification on BL CE UE in RRC_INACTIVE | Ericsson | draftCR | Endorsement |
9.1LTE
| Yes |
No
| available | No | ||
| R3‑255559 | Discussion on emergency call back and paging with PEIPS | Ericsson | discussion | Discussion |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255560 | Extensions for enumerated type definitions over several Releases - and what can go wrong | Ericsson, Jio Platforms, China Telecom, CMCC | discussion | Discussion |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255561 | Correcting the extension of FR1-bandwidth type definition | Ericsson, Jio Platforms, China Telecom, CMCC | CR | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255562 | Correcting the extension of FR1-bandwidth type definition | Ericsson, Jio Platforms, China Telecom, CMCC | CR | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255563 | Correcting the IE extension definition for bandwidth SRS | Ericsson, Jio Platforms, China Telecom, CMCC | CR | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255564 | Correcting the IE extension definition for bandwidth SRS | Ericsson, Jio Platforms, China Telecom, CMCC | CR | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255565 | Correcting the IE extension definition for SRS Pos SIB Type | Ericsson, Jio Platforms, China Telecom, CMCC | CR | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255566 | Addition of PDCP discard timer for scheduling with DSR | Ericsson, Qualcomm Inc., Jio Platforms | CR | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255567 | Discussion on forwarding of paging capabilities | Ericsson | other | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255568 | (TP for LP-WUS BL CR for TS38.423) Removal of FFS | Ericsson | other | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255569 | Work Plan for Rel-19 on AI/ML for PHY (Positioning) | Ericsson (Rapporteur) | Work Plan | Information |
20.1General
| Yes |
No
| available | No | ||
| R3‑255570 | (TP to NRPPa/TS 38.305 BL CR): Addressing remaining issues of NW-assisted AI/ML positioning with gNB-sided model | Ericsson, Nokia | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255571 | Way forward for Proactive (NGAP-based solution) for AI/ML NG-RAN assisted positioning | Ericsson | discussion | Approval |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255572 | (TP to NRPPa BL CR): addition of UL SRS time domain channel measurement | Ericsson, Xiaomi, CATT, CEWIT, Nokia, Samsung | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255573 | [TP for BL CR TS 37.483] Support of DL PDU Set Information Marking Support Indication | Ericsson, ZTE Corporation, Nokia, Nokia Shanghai Bell | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255574 | [TP to XR BL CR for 38.413] RAN status indication of Available data rate reporting | Ericsson | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255575 | Support of UE RRC state indication for faster UE context setup | Ericsson | CR | Agreement |
31.2Enhancements
| Yes |
No
| available | No | ||
| R3‑255576 | WI Work plan for R19 Network Energy Savings | Ericsson | Work Plan | Information |
17.1General
| Yes |
No
| available | No | ||
| R3‑255577 | On-demand SSB SCell operation | Ericsson | discussion |
17.2Support on-demand SSB SCell operation
| Yes |
No
| available | No | |||
| R3‑255578 | Xn impact of On-demand SIB1 for UEs in idle/inactive mode | Ericsson, Deutsche Telekom, China Unicom, Jio Platforms | other | Agreement |
17.3Support on-demand SIB1 for UEs
| Yes |
No
| available | No | ||
| R3‑255579 | F1 impact of On-demand SIB1 for UEs in idle/inactive mode | Ericsson, Deutsche Telekom, China Unicom, Jio Platforms | other | Agreement |
17.3Support on-demand SIB1 for UEs
| Yes |
No
| available | No | ||
| R3‑255580 | Stage 2 Specifications TPs for On-demand SIB1 for UEs in idle/inactive mode | Ericsson | other | Agreement |
17.3Support on-demand SIB1 for UEs
| Yes |
No
| available | No | ||
| R3‑255581 | Adaptation of common signal/channel transmissions | Ericsson | discussion |
17.4Others
| Yes |
No
| available | No | |||
| R3‑255582 | Support Aerial UE Flight Information Reporting to CN | Ericsson, CATT | discussion |
8.3Left over LSs / pending actions
| Yes |
Yes
| noted | No | |||
| R3‑255583 | [Draft] Reply LS on AI/ML Positioning Case 3a | Nokia | LS out | Approval |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255584 | Discussion on MBS Communication Service Type for QMC | Nokia | discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | |||
| R3‑255585 | [Draft] Reply LS on MBS Communication Service Type for QMC | Nokia | LS out | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255586 | AI_ML-Based CCO with Timing Aspects over Xn | Jio Platforms | discussion | Decision |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑255587 | (TP for AIML BLCR to TS 38.423) AI_ML-Based CCO with timing aspects over XN | Jio Platforms | other |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
Yes
| withdrawn | Yes | |||
| R3‑255588 | AI/ML-Based CCO with Timing Aspects over Xn | Jio Platforms, Ericsson | discussion |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | |||
| R3‑255589 | (TP for AIML BLCR to TS 38.423) AI_ML-Based CCO with timing aspects over XN | Jio Platforms, Ericsson | other |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | |||
| R3‑255590 | Discussion on update/cancel procedures for Predicted CCO issue vs. Detected CCO issue | Jio Platforms | discussion |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | |||
| R3‑255591 | Discussion on remaining issues for WAB | LG Electronics | discussion |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | |||
| R3‑255592 | Signaling of MRO for LTM between target DU and source DU | Ericsson, Huawei, Jio Platforms | discussion |
10.2MRO Enhancements
| Yes |
No
| available | No | |||
| R3‑255593 | (TP for BL CR to 38.401 for SON) Signaling of MRO for LTM between target DU and source DU | Ericsson, Huawei, Jio Platforms | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255594 | (TP for BL CR to 38.473 for SON) Signaling of MRO for LTM between target DU and source DU | Ericsson, Huawei, Jio Platforms | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255595 | Ping-pong avoidance for LTM | Ericsson | discussion |
10.2MRO Enhancements
| Yes |
No
| available | No | |||
| R3‑255596 | (TP for BL CR to 38.473 for SON) Ping-pong avoidance for LTM | Ericsson | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255597 | SON-MDT enhancements for NTN | Ericsson | discussion |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | |||
| R3‑255598 | (TP for BL CR to 38.413 for SON) Additional cause values and cell types for NTN | Ericsson | other | Agreement |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | ||
| R3‑255599 | (TP to TS 38.401, 38.413 and 38.423) TP for WAB support | LG Electronics | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255600 | Enhanced Rejected Slice Reporting for Dynamic Slice Optimization | Jio Platforms | discussion |
10.3.2Network Slicing
| Yes |
No
| available | No | |||
| R3‑255601 | Inter-CU LTM Robustness Enhancements | Jio Platforms | discussion |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑255602 | Reconsideration on NG Suspend/Resume Signaling for FLSO | Jio Platforms | discussion |
14.3Support of Regenerative payload
| Yes |
No
| available | No | |||
| R3‑255603 | Packet loss metric Observability in UE performance | Jio Platforms | discussion |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | |||
| R3‑255604 | Discussion for general issues in Inter-CU LTM | CATT | discussion | Decision |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255605 | (TP to BL CR for TS37.340) Discussion for Inter-CU LTM in DC | CATT | other | Decision |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255606 | (TP to 38.473) Discussion for C-LTM | CATT | other | Decision |
13.3Support for Conditional LTM
| Yes |
No
| available | No | ||
| R3‑255607 | (TP to BLCR for TS 36.300) Left issues in IoT NTN | CATT | other | Decision |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255608 | Define AIoT-FunctionIdentifier and AIoT-CorrelationIdentifier IEs | Jio Platforms Limited | CR | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255609 | Discussion on Wireless Access Backhaul | NTT DOCOMO INC. | discussion |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | |||
| R3‑255610 | (TP for XR BL CR for TS38.300) Clean-up for QNC | Huawei, CMCC, China Telecom | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255611 | (TP for XR BL CR for TS37.340) Clean-up for QNC | Huawei, CMCC, China Telecom | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255612 | Discussion on 5G Femto | NTT DOCOMO INC. | discussion |
12.35G Femto
| Yes |
No
| available | No | |||
| R3‑255613 | Correction on Intra-CU LTM shared preamble index limit per DU | LG Electronics Inc., Huawei, Samsung, Google, NEC, ZTE, CATT, Qualcomm, CMCC, China Telecom, Ericsson, Nokia, Lenovo | CR | Agreement |
9.2NR
| Yes |
Yes
| agreed | No | ||
| R3‑255614 | Discussions on finalizing the essential aspects of Inter-CU LTM | LG Electronics Inc. | discussion | Decision |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255615 | (TP for NR_Mob_Ph4 TS 38.423) Inter-CU LTM | LG Electronics Inc. | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255616 | (TPs for NR_Mob_Ph4 TS 38.473 and TS 38.401) Discussions on the remaining aspects of Conditional Intra-CU LTM | LG Electronics Inc. | other | Agreement |
13.3Support for Conditional LTM
| Yes |
No
| available | No | ||
| R3‑255617 | (TP for NR_NTN_Ph3 TS 38.300 BL CR) Stage-2 capturing logical connection between NG Removal/Setup and ephemeris info | LG Electronics Inc., Ericsson, Nokia, Nokia Shanghai Bell, Huawei | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255618 | Support Aerial UE Flight Information Failure Reporting in Filure Indicator message [UAS_Ph3] | CATT, Ericsson, CMCC | draftCR | Endorsement |
8.3Left over LSs / pending actions
| Yes |
No
| available | No | ||
| R3‑255619 | Inventory completion indication (via Inventory Report Transfer) | Jio Platforms Limited | CR | Agreement |
16.2RAN Architecture and Procedures
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑255620 | (TP for SON BL CR for TS38.401) MRO for LTM | Samsung | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255621 | (TP for SON BL CR for TS38.473) MRO for LTM | Samsung | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255622 | Failure scenarios on MRO for CHO with candidate SCGs | Samsung, Cybercore, Lenovo | discussion | Information |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255623 | (TP for SON BLCR for TS37.340, TS38.300 and TS38.423) MRO for CHO with candidate SCGs | Samsung, Jio Platforms, Cybercore | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255624 | (TP for SON BLCR for TS38.423) MRO for S-CPAC | Samsung, Jio Platforms, Cybercore | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255625 | Fetching reference configuration from candidate gNB in inter-CU LTM | Huawei, Google, Nokia, Jio Platforms, CATT, CMCC, NTT Docomo, Lenovo, China Telecom, Samsung | discussion |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑255626 | (TP for LTM BLCR for TS38.423): Fetching reference configuration from candidate gNB in inter-CU LTM | Huawei, Google, Nokia, Jio Platforms, CATT, CMCC, NTT Docomo, Lenovo, China Telecom, Samsung | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255627 | (TP for LTM BLCR for TS38.300): Fetching reference configuration from candidate gNB in inter-CU LTM | Huawei, Google, Nokia, Jio Platforms, CATT, CMCC, NTT Docomo, Lenovo, China Telecom, Samsung | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255628 | Clarification on the single UE XnAP association in inter-CU LTM | Huawei, NEC, LG Electronics | discussion |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑255629 | (TP for LTM BLCR for TS38.300): Clarification on the single Xn UE association in inter-CU LTM | Huawei, NEC, LG Electronics | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255630 | (TP for LTM BLCR for TS38.423): Clarification on the single Xn UE association in inter-CU LTM | Huawei, NEC, LG Electronics | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255631 | (draft LS) Discussion on the left issues for WAB | Samsung | discussion | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255632 | (TP to BLCR for TS 38.423) Enhancements for WAB | Samsung | other | Agreement |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | ||
| R3‑255633 | Discussion on the left issues for NR Femto | Samsung | discussion | Agreement |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255634 | (TP to BLCR for TS 38.300) Security verification for NR Femto | Samsung | other | Agreement |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255635 | Discussion on on-demand SSB SCell operation in low-carbon green network | Samsung | discussion | Agreement |
17.2Support on-demand SSB SCell operation
| Yes |
No
| available | No | ||
| R3‑255636 | (TP to BLCR for TS 38.470) On-demand SSB SCell operation | Samsung | other | Agreement |
17.2Support on-demand SSB SCell operation
| Yes |
No
| available | No | ||
| R3‑255637 | Discussion on on-demand SIB1 in low-carbon green network | Samsung | discussion | Agreement |
17.3Support on-demand SIB1 for UEs
| Yes |
No
| available | No | ||
| R3‑255638 | (draft LS to SA2) Discussion on other aspects for NR XR enhancements | Samsung | discussion | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255639 | (TP to BLCR for TS 38.473 and TS 38.413) NR XR enhancements | Samsung | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255640 | Optional NGAP IEs for node-level indication of temporary NTN feeder-link outage via RAN CONFIGURATION UPDATE (gNBAMF) | Jio Platforms Limited | CR | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255641 | (TP for 38.473 and 38.401) MRO for Rel-18 LTM | CATT | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255642 | (TP for 38.423 and 38.300) MRO for CHO with Candidate SCG(s) and S-CPAC | CATT | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255643 | (TP for 38.300) Intra-NTN mobility for SON | CATT | other | Agreement |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | ||
| R3‑255644 | (TP for 38.413 and 38.423) Intra-NTN mobility for MDT | CATT | other | Agreement |
10.3.1Intra-NTN Mobility
| Yes |
No
| available | No | ||
| R3‑255645 | Discussion on Evolution of Duplex Operation | CATT | discussion | Decision |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255646 | (TP for 38.423 and 38.473) Support on Evolution of Duplex Operation | CATT | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255647 | Disccsion on NR XR Enhancements for others | CATT | discussion | Decision |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255648 | (TP for 38.473 and 38.425) NR XR enhancement for others | CATT | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255649 | Discussion on Multi-hop U2N relay | CATT | discussion | Decision |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255650 | (TP for 38.473 and 38.401) Support on Multi-hop relay | CATT | other | Agreement |
22.2Support multi-hop Layer-2 UE-to-Network relay
| Yes |
No
| available | No | ||
| R3‑255651 | Handling of UE Radio Capability for Paging | Huawei | discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | |||
| R3‑255652 | Further discussion on paging capability loss issue | Huawei, China Unicom, China Telecom | discussion |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | |||
| R3‑255653 | Avoiding paging capability loss for CN paging | Huawei, China Unicom, China Telecom | CR | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255654 | Avoiding paging capability loss for CN paging | Huawei, China Unicom, China Telecom | CR | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255655 | Avoiding paging capability loss for CN paging | Huawei, China Unicom, China Telecom | CR | Agreement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255656 | Avoiding paging capability loss for CN paging | Huawei, China Unicom, China Telecom | draftCR | Endorsement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255657 | Avoiding paging capability loss for CN paging | Huawei, China Unicom, China Telecom | draftCR | Endorsement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255658 | Avoiding paging capability loss for CN paging | Huawei, China Unicom, China Telecom | draftCR | Endorsement |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255659 | (TP to BLCR for TS38.423 and TS38.473) Inter-gNB-CU LTM | Samsung | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255660 | Additional Discussion on inter-gNB-CU LTM | Samsung | discussion | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255661 | Discussion on AI/ML enabled slicing | Samsung | discussion | Approval |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255662 | Discussion on AI/ML enabled CCO | Samsung | discussion | Approval |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255663 | Discussion on AI/ML for mobility in NR-DC | Samsung | discussion | Approval |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255664 | Discusson on AI/ML for NG-RAN in split architecture | Samsung | discussion | Approval |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255665 | Further Discussion on continuous MDT collection | Samsung | discussion | Approval |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255666 | Text proposals on the support of enhancements on AIML for NG-RAN | Samsung | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255667 | Further discussion on information exchange for CLI handling | Samsung | discussion | Approval |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255668 | Text proposals to BLCRs of TS38.473 on CLI handling | Samsung | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255669 | Discussion on AI for positioning case 3a and case 3b | Samsung | discussion | Approval |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255670 | Discussion on Logged Data Handling During Handover | Samsung | other | Agreement |
20.2Support Positioning Accuracy Enhancements
| Yes |
No
| available | No | ||
| R3‑255671 | Discussion on impacts on Xn interface with SMTC enhancment | CSCN | discussion | Discussion |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255672 | (TP to BL CR for TS 38.300 on NR_NTN_Ph3) Stage 2 Updates for Regenerative Payload | NEC | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255673 | [Draft] LS on Multi-hop Topology Avoidance for WAB | CATT, China Telecom, Huawei, NTT Docomo, Lenovo, Samsung, NEC | LS out | Approval |
12.2Wireless Access Backhaul (WAB)
| Yes |
No
| available | No | R3‑253301 | |
| R3‑255674 | Consideration on LTE-based 5G Broadcast Phase 2 | Huawei, Qualcomm Incorporated, EBU | discussion | Approval |
23.2Signalling Support
| Yes |
No
| available | No | ||
| R3‑255675 | Introduction of LTE-based 5G Broadcast Phase 2 | Huawei, Qualcomm Incorporated, EBU | CR | Agreement |
23.2Signalling Support
| Yes |
No
| available | No | ||
| R3‑255676 | Discussion on MBS Communication Service Type | Huawei | discussion | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑255677 | Clarification on MBS communication service type for QMC configuration | Huawei | CR | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255678 | Clarification on MBS communication service type for QMC configuration | Huawei | CR | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255679 | Further discussion on remaining open issues | Huawei, China Telecom, China Unicom | discussion | Discussion |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255680 | Discussion on the exchange of SRS resource configurations | Huawei, China Telecom, China Unicom | discussion | Discussion |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255681 | (TP to BL CR for 38.423) miscellaneous clean-ups for Evolution of NR duplex operation Sub-band full duplex (SBFD) | Huawei, China Telecom, China Unicom | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255682 | (TP to BL CR for 38.423) introduction of SRS resource configurations for Evolution of NR duplex operation Sub-band full duplex (SBFD) | Huawei | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255683 | (TP to BL CR for 38.473) introduction of SRS resource configurations forEvolution of NR duplex operation Sub-band full duplex (SBFD) | Huawei | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255684 | Updated workplan for Evolution of NR Duplex Operation | Huawei, Sumsang | Work Plan | Information |
19.1General
| Yes |
Yes
| noted | No | ||
| R3‑255685 | Remaining issues on Intra-CU Conditional LTM | Samsung | discussion |
13.3Support for Conditional LTM
| Yes |
No
| available | No | |||
| R3‑255686 | [Draft]Reply LS to SA4 on MBS Communication Service Type | ZTE Corporation | LS out | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255687 | Correction on stage 2 QoE communication service type description | ZTE Corporation | draftCR | Endorsement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255688 | Correction on QoE communication service type | ZTE Corporation | CR | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255689 | Correction on QoE communication service type | ZTE Corporation | CR | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255690 | Discussion on QoE MBS communication service types | ZTE Corporation | discussion | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255691 | (TP to BLCR/draft CR for 38.300, 38.401, 38.423 and 38.473) SBFD | ZTE Corporation | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255692 | Discussion on information exchange for SBFD | ZTE Corporation | discussion | Approval |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255693 | Support Aerial UE Flight Information Reporting to CN | ZTE Corporation | CR | Agreement |
8.3Left over LSs / pending actions
| Yes |
No
| available | No | ||
| R3‑255694 | Correction on Location Reporting Procedure | ZTE Corporation | CR | Agreement |
31.1Corrections
| Yes |
No
| available | No | ||
| R3‑255695 | Discussion on UAV remaining issues | ZTE Corporation | discussion | Approval |
8.3Left over LSs / pending actions
| Yes |
Yes
| noted | No | ||
| R3‑255696 | Discussion on AIML based Mobility Optimization for NR-DC | CMCC | discussion | Discussion |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255697 | (TP to BLCR for TS 38.423) AIML based Mobility Optimization for NR-DC | CMCC | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255698 | (TP to BLCR for TS 38.473) Transfor Energy Cost through F1_v3 | CMCC, CATT, Huawei, Samsung, ZTE, Nokia, Ericsson | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255699 | (TP to BLCR for TS 38.425) Specify Delay for UE Performance Metric_v3 | CMCC, Samsung, ZTE | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255700 | (TP to BLCR for TS 38.470) F1-U function for AIML | CMCC | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255701 | (TP to BLCR for TS 38.401) UE Performance Requirement for AIML in Split Architecture | CMCC | other | Agreement |
11.4R18 leftovers
| Yes |
No
| available | No | ||
| R3‑255702 | (TP to BLCR for TS 38.300) Indicator for NG Suspend/Resume | CMCC | other | Agreement |
14.3Support of Regenerative payload
| Yes |
No
| available | No | ||
| R3‑255703 | (TPs to BLCR for TS 38.423 and TS 38.473) Discussion on supporting CLI handling in SBFD | CMCC | other | Agreement |
19.2Support CLI Handling
| Yes |
No
| available | No | ||
| R3‑255704 | (TP to BLCR for TS 38.423) AIML enabled network slice | CMCC | other | Agreement |
11.2AI/ML enabled Slicing
| Yes |
No
| available | No | ||
| R3‑255705 | (TP to BLCR for TS 38.401, TS 38.423, TS 38.473 and TS 38.300) AIML based CCO | CMCC | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255706 | Discussion on paging capability loss issue | CMCC | discussion | Discussion |
18.2Support LP-WUS Indicating Paging Monitoring
| Yes |
No
| available | No | ||
| R3‑255707 | Discussion on UAV information reporting | CMCC, CATT | discussion | Discussion |
8.3Left over LSs / pending actions
| Yes |
Yes
| noted | No | ||
| R3‑255708 | Discussion on RAN Architecture aspects for Ambient IoT | CMCC | discussion | Discussion |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255709 | Leftover issues on Inventory and Command Procedure | CMCC | discussion | Discussion |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255710 | Discussion on Session Release Aspects | CMCC | discussion | Discussion |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255711 | (TP to BLCR for TS 38.300) Introduction of Ambient IoT | CMCC | other | Agreement |
16.2RAN Architecture and Procedures
| Yes |
No
| available | No | ||
| R3‑255712 | Correction on UE radio capability for paging information | CMCC, Huawei, CATT, ZTE, Qualcomm, Ericsson | CR | Agreement |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑255713 | Correction on UE radio capability for paging information | CMCC, Huawei, CATT, ZTE, Qualcomm, Ericsson | CR | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255714 | Correction on UE radio capability for paging information | CMCC, Huawei, CATT, ZTE, Qualcomm, Ericsson | CR | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑255715 | (BL CR to 38.423) Xn support for inter-CU LTM | Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC, ZTE, LG Electronics, Ofinno, Qualcomm | CR | Agreement |
13.1General
| Yes |
No
| available | No | R3‑255063 | |
| R3‑255716 | On-Demand SIB1 Availability for Energy Saving in the Handover Scenario | ISSDU, NTU | discussion | Discussion |
17.3Support on-demand SIB1 for UEs
| Yes |
No
| available | No | ||
| R3‑255717 | Discussion on XR RAN Awareness and UL Rate Control | Meta | discussion |
21.3Others
| Yes |
No
| available | No | |||
| R3‑255718 | Essential corrections to TCI states for LTM | Ericsson, Lenovo, Google, Jio Platforms, CATT, Ofinno, Verizon Wireless | discussion |
9.2NR
| Yes |
No
| available | No | |||
| R3‑255719 | Essential corrections to TCI states for LTM | Ericsson, Lenovo, Google, Jio Platforms, CATT, Ofinno, Verizon Wireless | CR | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255720 | Correction to Criticality of Retrieve UE Context Request | CATT | CR | Agreement |
9.1LTE
| Yes |
Yes
| noted | No | ||
| R3‑255721 | Correction to Criticality of Retrieve UE Context Request | CATT | CR | Agreement |
9.1LTE
| Yes |
No
| available | No | ||
| R3‑255722 | Correction to Criticality of Retrieve UE Context Request | CATT | CR | Agreement |
9.1LTE
| Yes |
No
| available | No | ||
| R3‑255723 | Correction to Criticality of Retrieve UE Context Request | CATT | CR | Agreement |
9.1LTE
| Yes |
No
| available | No | ||
| R3‑255724 | Support for Semi-persistent CSI-RS transmission | Ericsson, Jio Platforms, Verizon Wireless, ZTE, Ofinno | discussion |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑255725 | (TP to BL CR for TS 38.423) Support for Semi-persistent CSI-RS transmission (Option 1) | Ericsson, Jio Platforms, Verizon Wireless, ZTE | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255726 | (TP to BL CR for TS 38.473) Support for Semi-persistent CSI-RS transmission (Option 1) | Ericsson, Jio Platforms, Verizon Wireless, ZTE | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255727 | (TP to BL CR for TS 38.423) Support for Semi-persistent CSI-RS transmission (Option 2) | Ericsson, Jio Platforms, Verizon Wireless, ZTE | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255728 | (TP to BL CR for TS 38.473) Support for Semi-persistent CSI-RS transmission (Option 2) | Ericsson, Jio Platforms, Verizon Wireless, ZTE | other | Agreement |
13.2Support for inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑255729 | Discussion on AI/ML assisted Coverage and Capacity Optimization | ZTE Corporation | discussion | Approval |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255730 | [TP to 38.473] Support of AI/ML assisted Coverage and Capacity Optimization | ZTE Corporation | other | Agreement |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | ||
| R3‑255731 | [TP to BLCR 38413, 38473, 37483, 38425, 38300] TPs for XR remaining issues on UL Bit Rate Control and Timely RLC retransmission | ZTE Corporation | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255732 | Discussion on remaing issues in XR with draft reply LS to SA2 | ZTE Corporation | discussion | Approval |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255733 | [TP for BL CR TS 38.473] Support of DL PDU Set Information Marking Indication | ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson | other | Agreement |
21.3Others
| Yes |
No
| available | No | ||
| R3‑255734 | (TP for SON BLCR for 38.473) LTM Ping Pong left Issues | ZTE Corporation | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255735 | (TP for SON BLCR for 38.473 and 38.401) LTM Beam and TA Left Issues | ZTE Corporation | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255736 | (TP for SON BLCR for 38.423) MRO for others | ZTE Corporation | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255737 | Clarification for propagation of MDT Configuration in stage2 | ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei | other | Agreement |
9.2NR
| Yes |
No
| available | No | R3‑253738 | |
| R3‑255738 | Clarify on UE context retrieval | ZTE Corporation | other | Agreement |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255739 | Discussion on LTE-based 5G Broadcast | ZTE Corporation | discussion |
23.2Signalling Support
| Yes |
No
| available | No | |||
| R3‑255740 | Correction for LTE-based 5G Broadcast | ZTE Corporation | other | Agreement |
23.2Signalling Support
| Yes |
No
| available | No | ||
| R3‑255741 | Consideration on Muting of always-on signals in 5G broadcast [5GB_CASMuting] | Huawei, Qualcomm Incorporated, EBU | discussion | Approval |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑255742 | Support of Muting of always-on signals in 5G broadcast [5GB_CASMuting] | Huawei, Qualcomm Incorporated, EBU | CR | Agreement |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑255743 | Signalling to support OD-SIB1 | Rakuten Mobile, Inc | discussion |
17.3Support on-demand SIB1 for UEs
| Yes |
No
| available | No | |||
| R3‑255744 | (TP to TS 38.413) on support of Femto | ZTE Corporation | other | Agreement |
12.35G Femto
| Yes |
No
| available | No | ||
| R3‑255745 | Timing Information for AIML based CCO | Rakuten Mobile, Inc | discussion |
11.3AI/ML enabled Coverage and Capacity Optimization
| Yes |
No
| available | No | |||
| R3‑255746 | (TP for SON BL CR for TS 38.473) Discussion on LTM MRO without RLF Report | Google, Ericsson, NEC, Lenovo, CATT | other | Agreement |
10.2MRO Enhancements
| Yes |
No
| available | No | ||
| R3‑255747 | Response to R3-255513 | Nokia, Nokia Shanghai Bell, ZTE Corporation, Qualcomm, CATT, China Telecom, CMCC, Samsung | discussion |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | |||
| R3‑255748 | Response to R3-255514 | ZTE Corporation, Nokia, Nokia Shanghai Bell, Qualcomm, CATT, China Telecom, CMCC, Samsung | response | Discussion |
15.2Support Full eNB as Regenerative Payload
| Yes |
No
| available | No | ||
| R3‑255749 | Response to R3-255233/255234 | ZTE Corporation, CMCC, Pengcheng Laboratory | discussion | Discussion |
9.2NR
| Yes |
No
| available | No | ||
| R3‑255750 | Downlink Transmission Suspend/Resume – Stage 2 TP | Ericsson, Thales, Huawei, Jio Platforms, Airbus, ESA, Sateliot, Deutsche Telekom | other | Agreement |
15.2Support Full eNB as Regenerative Payload
| No |
No
| reserved | No | R3‑255549 | |
| R3‑255751 | Correction on RRC establishment Cause for CIoT | Huawei, ZTE, Nokia, Qualcomm Incorporated | CR | Agreement |
9.1LTE
| No |
Yes
| agreed | No | R3‑255325 | |
| R3‑255752 | Introduction of 7 MHz Channel Bandwidth | Huawei, Nokia, Ericsson, ZTE, Qualcomm | CR | Agreement |
8.1New Incoming LSs
| No |
YesTechnically Endorsed
| endorsed | No | R3‑255340 | |
| R3‑255753 | Introduction of 7 MHz Channel Bandwidth | Huawei, Nokia, Ericsson, ZTE, Qualcomm | CR | Agreement |
8.1New Incoming LSs
| No |
YesTechnically Endorsed
| endorsed | No | R3‑255341 | |
| R3‑255754 | MBS Communication Service Type for QMC | Ericsson | CR | Agreement |
8.1New Incoming LSs
| No |
No
| reserved | No | R3‑255168 | |
| R3‑255755 | MBS Communication Service Type for QMC | Ericsson | CR | Agreement |
8.1New Incoming LSs
| No |
No
| reserved | No | R3‑255167 | |
| R3‑255756 | Discussion and Draft Reply LS on MBS Communication Service Type for QMC | Ericsson | discussion | Agreement |
8.1New Incoming LSs
| No |
No
| reserved | No | R3‑255166 | |
| R3‑255757 | Support Aerial UE Flight Information Reporting to CN | Ericsson, CMCC, ZTE, CATT, Nokia, Huawei | CR | Agreement |
31.3Endorsed TEI19 CRs Review
| No |
No
| reserved | No | R3‑255135 |