Tdoc List
2025-11-20 16:17
| TDoc | Title | Source | Type | For | Agenda | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
|---|---|---|---|---|---|---|---|---|---|---|---|
| R3‑258001 | RAN3#130 Meeting Agenda | RAN3 Chair | agenda | Approval |
3Approval of the Agenda
| Yes |
Yes
| approved | No | ||
| R3‑258002 | RAN3#129-bis Meeting Report | ETSI-MCC | report | Approval |
4Approval of the minutes from previous meetings
| Yes |
Yes
| approved | No | ||
| R3‑258003 | TR 30.531 v1.61.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC | draft TR | Endorsement |
7General, protocol principles and issues
| Yes |
Yes
| endorsed | No | ||
| R3‑258004 | Reply LS on AI/ML Positioning Case 3a | SA2(CATT) | LS in | Discussion |
9.2.11R19 AI/ML for air interface
| Yes |
No
| available | No | ||
| R3‑258005 | Reply LS on geographical area scope MDT | SA5(CATT) | LS in | Discussion |
9.2.1R19 SON/MDT
| Yes |
Yes
| noted | No | ||
| R3‑258006 | Reply LS on the handling of inter-DU L2 reset for LTM | RAN2(Ericsson) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258007 | LS Response on compatibility issue for PEI and emergency PDU session | SA2(ZTE) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258008 | Reply LS on allocation of CN assigned subgroup ID for LP-WUS | SA2(Ericsson) | LS in | Discussion |
9.2.9R19 Low Power WUS/WUR
| Yes |
Yes
| noted | No | ||
| R3‑258009 | LS Reply on uplink rate control | SA2(vivo) | LS in | Discussion |
9.2.12R19 NR XR Enhancements
| Yes |
Yes
| noted | No | ||
| R3‑258010 | Reply to Reply LS on removal of support of PWS over satellite NG-RAN in Rel-17 and 18 | SA2(Samsung) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258011 | LS on integrity failure | RAN2(Xiaomi) | LS in | Discussion |
9.2.7R19 Ambient IoT
| Yes |
Yes
| noted | No | ||
| R3‑258012 | Reply LS on Structure updates of AIoT Identifiers | SA2(CATT) | LS in | Discussion |
9.2.7R19 Ambient IoT
| Yes |
Yes
| noted | No | ||
| R3‑258013 | Reply LS on UE data collection and data transfer | RAN2(Nokia) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258014 | Reply LS on signalling feasibility of dataset and parameter sharing | RAN2(Samsung) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258015 | Reply LS on temporary suspension of trace production | RAN2(Ericsson) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258016 | Correction on UE Performance metrics | Huawei, FiberCop, BT, Jio Platforms, NEC, ZTE, Samsung, CATT, Ericsson, Nokia, CMCC | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257302 | |
| R3‑258017 | Correction on UE Performance metrics | Huawei, FiberCop, BT, Jio Platforms, NEC, ZTE, Samsung, CATT, Ericsson, Nokia, CMCC | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257303 | |
| R3‑258018 | Clarification on S1 Removal for IoT NTN | ZTE Corporation, LG Electronics, Ericsson, CMCC, Nokia, Nokia Shanghai Bell, CATT, Samsung, Huawei, Deutsche Telekom, Jio Platforms | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257199 | |
| R3‑258019 | Correction on the MME Name IE in the S1 REMOVAL RESPONSE message | Nokia, Nokia Shanghai Bell, Xiaomi, Qualcomm, Ericsson, CATT, Airbus, Jio Platforms, ZTE, LG Electronics, Huawei | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257200 | |
| R3‑258020 | Provision of S&F Mode Indication Information | Huawei, Deutsche Telekom, Jio Platforms, Ericsson, Nokia, Nokia Shanghai Bell, Xiaomi, CATT, ZTE, CMCC, NEC | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257201 | |
| R3‑258021 | Correction of Time Interleaving parameters | ZTE Corporation, Pengcheng Laboratory, China Unicom, China Telecom | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257202 | |
| R3‑258022 | Correction of time-based handover for IoT NTN | Huawei, Deutsche Telekom, Jio Platforms, CATT, Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257214 | |
| R3‑258023 | Correction of time-based handover for IoT NTN | Huawei, Deutsche Telekom, Jio Platforms, CATT, Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257215 | |
| R3‑258024 | Correction on the description of the geographical area scope | ZTE Corporation, Nokia, Huawei, Samsung, CATT, Ericsson | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑256658 | |
| R3‑258025 | Correction of the description of the geographical area scope | Huawei, Nokia, Samsung, CATT, ZTE, Ericsson | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑256674 | |
| R3‑258026 | Correction for LTM failure without RLF-report | NEC, Huawei, Ericsson, Nokia, Google, CATT, ZTE, Samsung | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257235 | |
| R3‑258027 | Correcting SCG activation time after CHO | Huawei, CMCC, Deutsche Telekom | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257305 | |
| R3‑258028 | Miscellaneous corrections on AI/ML for NG-RAN | ZTE Corporation, Huawei, NEC, Ericsson, Nokia | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257243 | |
| R3‑258029 | Correction to E1AP on AI/ML for NG-RAN | CATT, Huawei, Nokia, ZTE, CMCC | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
Yes
| revised | No | R3‑258764 | R3‑257245 |
| R3‑258030 | Correction for Slice UE performance metrics | Nokia, ZTE, Huawei, CMCC, NEC, Ericsson | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257246 | |
| R3‑258031 | Correction to E1AP for UE performance metrics | CMCC, ZTE, Huawei, Ericsson, Nokia, CATT | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
Yes
| revised | No | R3‑258714 | R3‑257247 |
| R3‑258032 | Miscellaneous corrections on AI/ML for NG-RAN | ZTE Corporation, CMCC, NEC, Ericsson, Nokia, Huawei | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257328 | |
| R3‑258033 | Correction of WAB | Ericsson, Jio Platforms, Qualcomm, CATT | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
Yes
| revised | No | R3‑258763 | R3‑256715 |
| R3‑258034 | Correction on the description of WAB-MT Identifier | CATT, China Telecomm | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑256761 | |
| R3‑258035 | Correction on the NG Setup related to WAB | Huawei, CANON Research Centre France, Lenovo, Samsung, Nokia, Nokia Shanghai Bell | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257258 | |
| R3‑258036 | Corrections to WAB stage-2 | CATT, Ericsson, China Telecomm | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257262 | |
| R3‑258037 | Correction of WAB | Huawei | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257263 | |
| R3‑258038 | Corrections of Xn-related issues for WAB-gNB | ZTE Corporation, Ericsson, Nokia, Nokia Shanghai Bell, CATT, Qualcomm, Canon, Huawei | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257306 | |
| R3‑258039 | Corrections for WAB | ZTE Corporation, Ericsson, Jio Platforms, Nokia, Nokia Shanghai Bell, Samsung, Qualcomm, Huawei | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257307 | |
| R3‑258040 | Correction on NR femto procedures | Huawei, Nokia | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257217 | |
| R3‑258041 | Corrections for Femto | ZTE Corporation, Nokia, LG Electronics | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
Yes
| revised | No | R3‑258706 | R3‑257225 |
| R3‑258042 | Correction of NR Femtos functions | Nokia, CATT, Huawei, ZTE, LG Electronics | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257312 | |
| R3‑258043 | Early Data Forwarding for subsequent inter-CU LTM | NEC, Huawei, Google, Jio Platforms, Qualcomm Inc, Nokia, Samsung, Lenovo, CATT, LG Electronics, Ericsson, ZTE, Ofinno | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257219 | |
| R3‑258044 | Early Data Forwarding for subsequent MCG LTM | NEC, Huawei, Google, Jio Platforms, Qualcomm Inc, Nokia, Samsung, Lenovo, CATT, LG Electronics, Ericsson, ZTE, Ofinno | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257220 | |
| R3‑258045 | Correction on CSI-RS Resource Set and CSI IM Resource Transfer for inter-CU LTM | Huawei, Jio Platforms, CATT, China Telecom, Lenovo, Nokia, ZTE, LG Electronics, NEC, Google, Samsung, Ericsson, Offinno, Qualcomm | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257313 | |
| R3‑258046 | Correction on CSI-RS Resource Set and CSI IM Resource Transfer for inter-CU LTM | Huawei, Jio Platforms, CATT, China Telecom, Lenovo, Nokia, ZTE, LG Electronics, NEC, Google, Samsung, Ericsson, Offinno, Qualcomm | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257314 | |
| R3‑258047 | Semi-Persistent CSI-RS activation with TCI state | Nokia, CATT, China Telecom, Ericsson, Huawei, NEC, ZTE, Google, Samsung, LG Electronics, Qualcomm, Ofinno, Lenovo, Jio Platforms | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
Yes
| revised | No | R3‑258715 | R3‑257315 |
| R3‑258048 | Semi-Persistent CSI-RS activation with TCI state | CATT, Nokia, ZTE, China Telecom, Ericsson, LG Electronics, Samsung, Huawei, NEC, ZTE, Google, LG Electronics, Qualcomm, Ofinno,Lenovo | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257316 | |
| R3‑258049 | Adding Extended AMF Name to NG REMOVAL RESPONSE message | Ericsson, Thales, LG Electronics, Xiaomi, CATT, ZTE, Nokia, Nokia Shanghai Bell, Eutelsat Group, Deutsche Telekom, Qualcomm Incorporated, Airbus, Jio Platforms, Huawei, NEC, CMCC, Samsung | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257221 | |
| R3‑258050 | Correction of O&M requirements for NTN | Huawei, Deutsche Telekom, Jio Platforms, ZTE | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257222 | |
| R3‑258051 | Correction on A-IoT leftovers on IE details | Huawei, CMCC, China Unicom, China Telecom, Nokia, LG Electronics, CATT, NEC | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
Yes
| revised | No | R3‑258744 | R3‑257251 |
| R3‑258052 | Correction on Interface Management procedures for A-IoT | Huawei, CMCC, Lenovo, China Unicom, China Telecom, Nokia, LG Electronics, CATT, NEC | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257252 | |
| R3‑258053 | Corrections to A-IoT procedure texts | CATT, Huawei, Nokia, LG Electronics, NEC, ZTE, Samsung | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257253 | |
| R3‑258054 | Corrections to Xn support for on-demand SIB1 coordination | Ericsson, Qualcomm, Jio Platforms , ZTE, Deutsche Telekom, Huawei, Samsung, NEC, Rakuten, Nokia, CATT, Telecom Italia | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
Yes
| revised | No | R3‑258716 | R3‑257317 |
| R3‑258055 | Correction of OD-SIB1 procedure for network energy saving | Huawei, Ericsson, Qualcomm, Jio Platforms, ZTE, Deutsche Telekom, Samsung, NEC, Rakuten, Nokia, CATT, Telecom Italia | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257318 | |
| R3‑258056 | Introducing of LP-WUS disabling | ZTE Corporation, Ericsson, Nokia, Huawei, Qualcomm, CATT | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑256956 | |
| R3‑258057 | Introducing LP-WUS disabling indication | Ericsson, ZTE, Huawei, CATT, Nokia, Qualcomm Inc. | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257019 | |
| R3‑258058 | On introducing LP-WUS disabling indication | CATT, Nokia, Huawei, Ericsson, ZTE, Qualcomm | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257227 | |
| R3‑258059 | Correction of RAN Paging for low-power wake-up signal and receiver | Huawei, Nokia, Ericsson, Qualcomm, ZTE, CATT | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257229 | |
| R3‑258060 | Correction of LP-WUS Assistance Information | Nokia, Ericsson, Huawei, NTT Docomo Inc. | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257319 | |
| R3‑258061 | Corrections to SBFD operation | Huawei, Nokia, Samsung | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257320 | |
| R3‑258062 | Correction on the ASN.1 of Positioning Data Information for data collection | Samsung, Ericsson, Nokia, CATT, ZTE, Huawei, Xiaomi, NEC, CMCC | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257232 | |
| R3‑258063 | Correction on Positioning Data Collection Needed | Ericsson, Xiaomi, ZTE, Huawei, Samsung, CATT, Nokia, CEWIT, NEC, Qualcomm Inc. | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257237 | |
| R3‑258064 | Miscellaneous corrections for supporting for AI/ML-based positioning | Huawei, CATT, Nokia, NEC, Ericsson, CEWiT, ZTE, Samsung, Xiaomi | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257321 | |
| R3‑258065 | Correction to TS 37.483 for XR | Samsung | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
Yes
| revised | No | R3‑258717 | R3‑257142 |
| R3‑258066 | Correction on PDU Set based QoS handling | CATT, Nokia, Nokia Shanghai Bell, Huawei, Ofinno, ZTE, Ericsson, China Telecom | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257264 | |
| R3‑258067 | Correction on PDU set handling during handover | Huawei, Nokia, Nokia Shanghai Bell, Ericsson, CATT, Ofinno, ZTE | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257265 | |
| R3‑258068 | Add the missing behavior text for DL PDU Set Information Marking Support Indication | Nokia, Nokia Shanghai Bell, CATT, Qualcomm, ZTE, Ericsson, Ofinno, Huawei, China Telecom | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257266 | |
| R3‑258069 | Add procedure texts on XR uplink rate control in NGAP | Ofinno, ZTE Corporation, Nokia, Nokia Shanghai Bell, CATT, Qualcomm, Huawei, Ericsson, Samsung, China Telecom | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257267 | |
| R3‑258070 | Correction on RLC enhancement for XR | Huawei, Nokia, Nokia Shanghai Bell, CATT | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257290 | |
| R3‑258071 | Correction on the Notification Cause IE in NGAP | ZTE Corporation | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257291 | |
| R3‑258072 | Corrections for Multi-hop relay | ZTE Corporation, Samsung, Ericsson, LG Electronics | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257283 | |
| R3‑258073 | Corrections on Multi-hop relay | LG Electronics Inc., Nokia, Nokia Shanghai Bell, CATT, ZTE Corporation, Huawei, Ericsson | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257322 | |
| R3‑258074 | Correction to Positioning activation and deactivation procedure | CATT, Samsung, ZTE, Huawei, China Telecom, Xiaomi | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257268 | |
| R3‑258075 | Correction to Positioning activation and deactivation procedure | CATT, Samsung, ZTE, Huawei, China Telecom, Xiaomi | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257269 | |
| R3‑258076 | Correction to positioning activation and deactivation procedure | Samsung, CATT, ZTE Corporation, Huawei, China Telecom, Xiaomi | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257270 | |
| R3‑258077 | Correction to positioning activation and deactivation procedure | Samsung, CATT, ZTE Corporation, Huawei, China Telecom, Xiaomi | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
Yes
| revised | No | R3‑258750 | R3‑257271 |
| R3‑258078 | Correction to positioning activation and deactivation procedure | Huawei, Samsung, CATT, ZTE, China Telecom, Xiaomi | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257272 | |
| R3‑258079 | Correction to positioning activation and deactivation procedure | Huawei, Samsung, CATT, ZTE, China Telecom, Xiaomi | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257273 | |
| R3‑258080 | Correction to positioning activation and deactivation procedure | ZTE Corporation, Samsung, CATT, Huawei, China Telecom, Xiaomi | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257274 | |
| R3‑258081 | Correction to positioning activation and deactivation procedure | ZTE Corporation, Samsung, CATT, Huawei, China Telecom, Xiaomi | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257275 | |
| R3‑258082 | Correction of UE Radio Capability for Paging | Nokia, Ericsson, Jio Platforms, Huawei, ZTE, CATT, NTT Docomo | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257277 | |
| R3‑258083 | Correction of UE Radio Capability for Paging | Nokia, Ericsson, Jio Platforms, Huawei, ZTE, CATT, NTT Docomo | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257278 | |
| R3‑258084 | Correction of UE Radio Capability for Paging | Nokia, Ericsson, Jio Platforms, Huawei, ZTE, CATT, NTT Docomo | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑257279 | |
| R3‑258085 | Correction of the description of the geographical area scope | Nokia, ZTE, Huawei, CATT, Samsung, Ericsson | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑256628 | |
| R3‑258086 | TR38.745 v0.1.1 for Study on Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN Phase 3 | ZTE Corporation, NEC | draft TR | Endorsement |
12.1General
| Yes |
Yes
| endorsed | No | R3‑257331 | |
| R3‑258087 | TR38.760-3 v0.1.1 for Study on 6G Radio RAN3 aspects | Vodafone GmbH | draft TR | Endorsement |
10.1General
| Yes |
Yes
| endorsed | No | R3‑257330 | |
| R3‑258088 | (pCR to TR 38.765) Study on Integrated Sensing and Communication (ISAC) for NR | China Telecom, Xiaomi | pCR | Endorsement |
13.1General
| Yes |
Yes
| endorsed | No | R3‑257332 | |
| R3‑258089 | Discussion on AI/ML for Intra-CU LTM | Nokia | discussion | Agreement |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | ||
| R3‑258090 | Discussion on remaining Inter-CU LTM Issues | Nokia | discussion | Agreement |
9.2.5R19 Mobility enhancements
| No |
Yes
| withdrawn | Yes | ||
| R3‑258091 | LS to SA2 on the paging in Store and Forward | RAN2(Huawei) | LS in | Discussion |
9.1.1R19 IoT NTN enhancements
| Yes |
Yes
| noted | No | ||
| R3‑258092 | Reply LS on the maximum supported AIoT NAS container length | RAN2(Lenovo) | LS in | Discussion |
9.2.7R19 Ambient IoT
| Yes |
Yes
| noted | No | ||
| R3‑258093 | LS on Early Alignment on Access Stratum security aspects | RAN2(Vodafone) | LS in | Discussion |
10.1General
| Yes |
Yes
| noted | No | ||
| R3‑258094 | Correction of Transmission Bandwidth Asymmetric | Nokia, Huawei, Qualcomm, China Telecom | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑256566 | |
| R3‑258095 | Correction of Transmission Bandwidth Asymmetric | Nokia, Huawei, Qualcomm, China Telecom | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑256567 | |
| R3‑258096 | Correction of Transmission Bandwidth Asymmetric | Nokia, Huawei, Qualcomm, China Telecom | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑256568 | |
| R3‑258097 | Correction of Transmission Bandwidth Asymmetric | Nokia, Huawei, Qualcomm, China Telecom | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑256569 | |
| R3‑258098 | Correction of Transmission Bandwidth Asymmetric | Nokia, Huawei, Qualcomm, China Telecom | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑256570 | |
| R3‑258099 | Correction of Transmission Bandwidth Asymmetric | Huawei, Nokia, Qualcomm, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | R3‑256669 | ||
| R3‑258100 | Correction of Transmission Bandwidth Asymmetric | Huawei, Nokia, Qualcomm, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | R3‑256670 | ||
| R3‑258101 | Correction of Transmission Bandwidth Asymmetric | Huawei, Nokia, Qualcomm, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | R3‑256671 | ||
| R3‑258102 | Correction of Transmission Bandwidth Asymmetric | Huawei, Nokia, Qualcomm, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | R3‑256672 | ||
| R3‑258103 | Correction of Transmission Bandwidth Asymmetric | Huawei, Nokia, Qualcomm, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | R3‑256673 | ||
| R3‑258104 | LS on Rel-19 higher layers parameters list Post RAN1#122bis | RAN1(Ericsson) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258105 | Discussion on R17 and R18 PWS for NTN feature removal alignment between RAN and SA | ZTE Corporation | discussion |
8.1New Incoming LSs
| Yes |
No
| available | No | |||
| R3‑258106 | Additional procedure text for Data Collection Update | ZTE Corporation, Ercisson, Samsung, NEC, Nokia, Huawei, CATT, Jio Platforms, Qualcomm, FiberCop, Orange | CR | Agreement |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258724 | R3‑256563 |
| R3‑258107 | Work plan for Study on AI/ML for NG-RAN Phase 3 | ZTE Corporation, NEC | Work Plan |
12.1General
| Yes |
Yes
| noted | No | |||
| R3‑258108 | (TP to TR 38.745) Consideration on Multi-hop UE trajectory | ZTE Corporation | pCR |
12.2.1Multi-hop UE trajectory across gNBs
| Yes |
No
| available | No | |||
| R3‑258109 | Consideration on AI/ML assisted intra-CU LTM | ZTE Corporation | pCR |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | |||
| R3‑258110 | (TP to TR 38.745) Consideration on other handover enhancements | ZTE Corporation | pCR |
12.2.3Handover enhancements
| Yes |
No
| available | No | |||
| R3‑258111 | Introduction of NR TA Type 1 measurement in NR E-CID | Comtech Telecommunications Corp, Polaris Wireless, FirstNet, Verizon | discussion | Decision |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258112 | Add Tadv Type 1 measurement in NR UL E-CID | Comtech Telecommunications Corp, Polaris Wireless, FirstNet, Verizon | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258113 | Control-plane latency and message overhead in split RAN architectures | Boost Mobile Network | discussion | Decision |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258114 | (TP to pCR 38.765) ISAC general aspects and protocol stacks | Xiaomi | other |
13.2Network architecture
| Yes |
Yes
| noted | No | |||
| R3‑258115 | (TP to pCR 38.765) Sensing procedures and singalling | Xiaomi | other |
13.3RAN-CN procedures and signaling
| Yes |
Yes
| noted | No | |||
| R3‑258116 | (TP for pCR) Network architecture for ISAC | Huawei | other |
13.2Network architecture
| Yes |
No
| available | No | |||
| R3‑258117 | (TP for pCR) RAN-CN procedures and signaling for ISAC | Huawei | other |
13.3RAN-CN procedures and signaling
| Yes |
Yes
| noted | No | |||
| R3‑258118 | Specifying procedure texts for the Core Network Assistance Information for RRC INACTIVE IE | Huawei, Ericsson, Nokia, ZTE | CR | Agreement |
9.2.14Other
| Yes |
Yes
| agreed | No | R3‑256682 | |
| R3‑258119 | Further consideration on RAN-CN interface principles and functions | Huawei | pCR | Agreement |
10.3.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258120 | Consideration on RAN-CN interface options | Huawei | pCR | Agreement |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | ||
| R3‑258121 | Consideration on A-IoT dedicated Cause values | Huawei, CMCC, Futurewei, Lenovo, China Unicom, China Telecom, Nokia, Ericsson | discussion | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| noted | No | ||
| R3‑258122 | Correction on A-IoT dedicated Cause values | Huawei, CMCC, Futurewei, Lenovo, China Unicom, China Telecom, Nokia, Ericsson | CR | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| revised | No | R3‑258732 | |
| R3‑258123 | Correction on A-IoT related Network Identities | Huawei, Nokia, Ericsson, CMCC, China Unicom, China Telecom | draftCR | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| revised | No | R3‑258733 | |
| R3‑258124 | Consideration on the presence of Reader Report List | Huawei, CMCC, China Unicom, China Telecom | discussion | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| noted | No | ||
| R3‑258125 | Correction on the presence of Reader Report List | Huawei, CMCC, China Unicom, China Telecom | CR | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| revised | No | R3‑258735 | |
| R3‑258126 | [TPs to BL CRs] Consideration on Ambient IoT Topology 2 | Huawei, China Unicom, China Telecom | other | Agreement |
14.2Topology 2
| Yes |
No
| available | No | ||
| R3‑258127 | Correction on LTE-based 5G Broadcast | Huawei, EBU, Qualcomm Incorporated, ZTE | CR | Agreement |
9.1.2R19 LTE-based 5G Broadcast
| Yes |
Yes
| revised | No | R3‑258705 | |
| R3‑258128 | Discussion on AI/ML assisted Intra-CU LTM | Lekha Wireless Solutions | discussion | Decision |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | ||
| R3‑258129 | (TP to TR38.760-3) Initial discussion on 6G AI/ML for RAN | ZTE Corporation | pCR |
10.5.1AI/ML use cases
| Yes |
No
| available | No | |||
| R3‑258130 | Network Architecture and Protocol Aspects for NR Sensing Support | Qualcomm Incorporated | other |
13.2Network architecture
| Yes |
No
| available | No | |||
| R3‑258131 | Signalling and Procedures for NR Sensing Support | Qualcomm Incorporated | other |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | |||
| R3‑258132 | Service Based Core Network | InterDigital inc. | pCR | Agreement |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | ||
| R3‑258133 | 6G AI/ML Use Cases | InterDigital Inc. | pCR | Agreement |
10.5.1AI/ML use cases
| Yes |
No
| available | No | ||
| R3‑258134 | 6G Xn General Principles | InterDigital Inc. | pCR | Agreement |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258135 | RAN Architecture | InterDigital Inc. | pCR | Agreement |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | ||
| R3‑258136 | RAN-CN General Principles | InterDigital Inc | pCR | Agreement |
10.3.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258137 | NR ISAC Network Architecture | InterDigital Inc. | discussion | Decision |
13.2Network architecture
| Yes |
No
| available | No | ||
| R3‑258138 | NR ISAC RAN-CN Procedures and Signaling | InterDigital Inc. | discussion | Discussion |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | ||
| R3‑258139 | RAN3 naming | InterDigital Inc. | discussion | Decision |
10.2.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258140 | Service Aware RAN Requirements for 6G | T-Mobile USA Inc. | discussion |
10.2.1General principles and requirements
| Yes |
No
| available | No | |||
| R3‑258141 | Native support for E911 Voice in 6G | T-Mobile USA Inc. | discussion |
10.2.1General principles and requirements
| Yes |
No
| available | No | |||
| R3‑258142 | Discussion on the reply LS on AI/ML assisted positioning | ZTE Corporation, Ericsson, Xiaomi, CATT | discussion |
9.2.11R19 AI/ML for air interface
| Yes |
No
| available | No | |||
| R3‑258143 | Correction on Positioning Data Unavailable IE | ZTE Corporation, Ericsson, Xiaomi, CATT | CR |
9.2.11R19 AI/ML for air interface
| Yes |
No
| available | No | |||
| R3‑258144 | Discussion on Multiple-hop UE trajectory | Lekha Wireless Solutions | discussion | Decision |
12.2.1Multi-hop UE trajectory across gNBs
| Yes |
No
| available | No | ||
| R3‑258145 | (pCR to TR38.760-3) Further discussion on principles of RAN-CN interface | ZTE Corporation | pCR | Approval |
10.3.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258146 | (pCR to TR38.760-3) Further discussion on internal functional split and interfaces | ZTE Corporation | pCR | Approval |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258147 | (TP to pCR 38.765) Further discussion on Network Architecture for ISAC | ZTE Corporation | other | Approval |
13.2Network architecture
| Yes |
Yes
| noted | No | ||
| R3‑258148 | (TP to pCR 38.765) Further discussion on RAN-CN Procedures and Signalling for ISAC | ZTE Corporation | other | Approval |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | ||
| R3‑258149 | Correction on MRO for SCG failure in EN-DC | ZTE Corporation, China Telecom, Pengcheng Laboratory | draftCR | Endorsement |
9.2.1R19 SON/MDT
| Yes |
Yes
| revised | No | R3‑258708 | |
| R3‑258150 | Correction on procedural description of Cell A ID | ZTE Corporation, CATT, Samsung | CR | Approval |
9.2.8R19 Network Energy Saving
| Yes |
No
| available | No | ||
| R3‑258151 | Exchange of early RACH Resources Requester ID for inter-CU LTM | Huawei, Ericsson, Samsung, Jio Platforms, CATT, CMCC, China Telecom, Lenovo, Nokia | discussion |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| noted | No | |||
| R3‑258152 | Exchange of early RACH Resources Requester ID for inter-CU LTM | Huawei, Ericsson, Samsung, Jio Platforms, CATT, CMCC, China Telecom, Lenovo, Nokia | CR | Approval |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| noted | No | ||
| R3‑258153 | Introduction of missing LTM Indicator for inter-CU LTM | Huawei, Nokia, LG Electronics, NTT DoCoMo. Offinno, Jio Platforms, CMCC | CR |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| revised | No | R3‑258780 | ||
| R3‑258154 | Correction on Reference Configuration in LTM Configuration Update for inter-CU LTM | Huawei, NTT DoCoMo, Offinno, Jio Platforms, CMCC, Lenovo, CATT | CR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258155 | Correction on the CSI-RS Coordination procedure | Huawei, LG Electronics, ZTE, Offinno, NTT Docomo, Jio Platforms, CMCC, Lenovo | CR |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| revised | No | R3‑258779 | ||
| R3‑258156 | Interaction between Handover Success and Cell Switch Notification | Huawei, Nokia, LG Electronics, NTT DoCoMo, ZTE, Offinno, Jio Platforms, CMCC | CR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258157 | Correction to inter-CU LTM and conditional intra-CU LTM | Huawei, Jio Platforms, CATT, China Telecom, Lenovo, Ericsson, LG Electronics, Qualcomm Incorporated, Google, Ofinno | CR |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| revised | No | R3‑258778 | ||
| R3‑258158 | MRO enhancements for Inter-CU LTM | Qualcomm Incorporated | discussion | Discussion |
11.2.1Inter-CU LTM
| Yes |
Yes
| noted | No | ||
| R3‑258159 | MRO enhancements for Intra-CU CLTM | Qualcomm Incorporated | discussion | Discussion |
11.2.2Intra-CU conditional LTM
| Yes |
No
| available | No | ||
| R3‑258160 | (pCR to TR 38.760-3) 6G-RAN-CN interface: General principles and requirements | Qualcomm Incorporated, NTT Docomo Inc, Fibercop, Reliance JIO, KT Corp, Charter Communications | pCR | Agreement |
10.3.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258161 | (pCR to TR 38.760-3) 6G RAN internal functional split and interfaces | Qualcomm Incorporated | pCR | Agreement |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258162 | Discussion on AQP priority | ZTE Corporation, Nokia, Ericsson, Huawei | discussion | Approval |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258163 | Correction on prioritized alternative QoS profile | ZTE Corporation, Nokia, Ericsson, Huawei | CR | Approval |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258164 | Correction on prioritized alternative QoS profile | ZTE Corporation, Nokia, Ericsson, Huawei | CR | Approval |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258165 | Correction on prioritized alternative QoS profile | ZTE Corporation, Nokia, Ericsson, Huawei | CR | Approval |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258166 | Correction on prioritized alternative QoS profile | ZTE Corporation, Nokia, Ericsson, Huawei | CR | Approval |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258167 | Correction on Configured TAC | Huawei, China Unicom, China Telecom, Lenovo | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258168 | Resilient 6G RAN Architecture | Nokia, Jio Platforms, NTT DoCoMo | pCR | Approval |
10.2.2RAN functions and logical architecture
| Yes |
Yes
| revised | No | R3‑258734 | |
| R3‑258169 | Considerations on the 6G RAN internal functional split and possible work plan for RAN3 | Nokia, Orange | pCR | Approval |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258170 | Correction of the NES Cell ID criticality in OD-SIB1 configuration provision response message | Huawei, CMCC, Deutsche Telekom, CATT | CR |
9.2.8R19 Network Energy Saving
| Yes |
No
| available | No | |||
| R3‑258171 | Correction of references of NES Cell and Cell A for OD-SIB1 configuration provision procedure | Huawei, CMCC, Deutsche Telekom, CATT | CR |
9.2.8R19 Network Energy Saving
| Yes |
No
| available | No | |||
| R3‑258172 | Correction of Exit Conditions | Nokia | CR |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | |||
| R3‑258173 | Discussion on Continuous Management Based MDT | Nokia, Qualcomm | discussion |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| noted | No | |||
| R3‑258174 | Clarification of procedural text for POSITIONING DATA COLLECTION REPORT message | Nokia, CATT, Ericsson | CR |
9.2.11R19 AI/ML for air interface
| Yes |
Yes
| revised | No | R3‑258793 | ||
| R3‑258175 | AI/ML Use Cases in 6G | Nokia | pCR |
10.5.1AI/ML use cases
| Yes |
No
| available | No | |||
| R3‑258176 | Multi-hop UE trajectory across gNBs | Nokia | pCR |
12.2.1Multi-hop UE trajectory across gNBs
| Yes |
No
| available | No | |||
| R3‑258177 | AI/ML-based Handover Enhancements | Nokia | pCR |
12.2.3Handover enhancements
| Yes |
No
| available | No | |||
| R3‑258178 | RAN Split Architecture Commercial Deployment Benefits | Verizon Switzerland AG | discussion | Agreement |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258179 | (pCR to BLCR for TR 38.760-3) Protocol stack evolution in 6G | Qualcomm Incorporated | pCR | Agreement |
10.2.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258180 | (pCR to BLCR for TR 38.760-3) Discussion on 6G RAN logical architecture | Qualcomm Incorporated | pCR | Agreement |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | ||
| R3‑258181 | (pCR to BLCR for TR 38.760-3) 6G RAN-CN interface: General principles and requirements | Qualcomm Incorporated | other | Discussion |
10.3.1General principles and requirements
| No |
Yes
| withdrawn | Yes | ||
| R3‑258182 | (pCR to BLCR for TR 38.760-3) Characteristics of point-to-point and service-based interfaces | Qualcomm Inc, KT Corp, Jio Platforms, NTT Docomo, FiberCop, CEWiT, Reliance JIO, Deutsche Telekom, Sony | pCR | Agreement |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | ||
| R3‑258183 | (pCR to BLCR for TR 38.760-3) 6G RAN internal functional split and interfaces | Qualcomm Incorporated | other | Discussion |
10.4RAN internal functional split and interfaces
| No |
Yes
| withdrawn | Yes | ||
| R3‑258184 | Discussion on RAN-CN procedures and signaling for ISAC | discussion | Discussion |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | |||
| R3‑258185 | Consideration on A-IoT Device Identification | Huawei, CMCC, China Unicom, China Telecom, Lenovo | discussion | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| noted | No | ||
| R3‑258186 | Correction on A-IoT Device Identification | Huawei, CMCC, China Unicom, China Telecom, Lenovo | CR | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| noted | No | ||
| R3‑258187 | RAN functions and logical architecture | Tejas Network Limited | discussion | Decision |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | ||
| R3‑258188 | RAN internal functional split and interfaces | Tejas Network Limited | discussion | Decision |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258189 | Overall RAN architecture | Tejas Network Limited | discussion | Decision |
10.2Overall RAN architecture
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑258190 | AI/ML Use Cases for 6G RAN | Tejas Network Limited | discussion | Discussion |
10.5.1AI/ML use cases
| Yes |
No
| available | No | ||
| R3‑258191 | Discussion on AI/ML for Intra CU LTM | Tejas Network Limited | discussion | Discussion |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | ||
| R3‑258192 | Discussion on Inter-CU LTM | Qualcomm Incorporated, CATT, CMCC, NEC, NTT Docomo, Vodafone | discussion | Agreement |
12.2.3Handover enhancements
| Yes |
No
| available | No | ||
| R3‑258193 | (pCR To TR 38.745) Discussion on Intra-CU LTM | Qualcomm Incorporated | pCR | Agreement |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | ||
| R3‑258194 | Discussion on Multi-hop UE Trajectory Prediction and Feedback | Qualcomm Incorporated | discussion | Agreement |
12.2.1Multi-hop UE trajectory across gNBs
| Yes |
No
| available | No | ||
| R3‑258195 | (pCR to TR 38.760-3) Discussion on 6G AI/ML Use Cases | Qualcomm Incorporated, JIO Platforms | pCR | Agreement |
10.5.1AI/ML use cases
| Yes |
No
| available | No | ||
| R3‑258196 | Network Architecture and Protocol stack for NR ISAC | Tejas Network Limited | discussion | Discussion |
13.2Network architecture
| Yes |
No
| available | No | ||
| R3‑258197 | RAN-CN procedures and signaling for NR ISAC | Tejas Network Limited | other |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | |||
| R3‑258198 | MRO Enhancements for Inter-CU LTM | Nokia | discussion | Discussion |
11.2.1Inter-CU LTM
| Yes |
Yes
| noted | No | ||
| R3‑258199 | Correction on the OAM requirements for NTN | Nokia, Nokia Shanghai Bell, Qualcomm, LG Electronics, ZTE, CATT, Ericsson, Huawei | draftCR |
9.1.1R19 IoT NTN enhancements
| Yes |
Yes
| revised | No | R3‑258704 | ||
| R3‑258200 | Correction of WAB-MT handover a target WAB-gNB | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, CATT, China Telecom, Canon, Qualcomm | CR |
9.2.3R19 WAB
| Yes |
Yes
| revised | No | R3‑258769 | R3‑257259 | |
| R3‑258201 | Add the missing behavior text for the MMSID IE and the Indication of Bitrate Adaptation IE | Nokia, Nokia Shanghai Bell, Ericsson, Ofinno, China Telecom, Qualcomm, ZTE, Samsung, Huawei, Lenovo | CR | Agreement |
9.2.12R19 NR XR Enhancements
| Yes |
Yes
| agreed | No | ||
| R3‑258202 | Correction on Notification Control Indication | Nokia, Nokia Shanghai Bell, Huawei, CMCC, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | R3‑256892 | ||
| R3‑258203 | Correction on Notification Control Indication | Nokia, Nokia Shanghai Bell, Huawei, CMCC, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | R3‑256893 | ||
| R3‑258204 | Rapporteur update | Nokia, Nokia Shanghai Bell | CR |
9.3R19 Rapporteur Corrections
| No |
Yes
| withdrawn | Yes | |||
| R3‑258205 | Rapporteur corrections | Nokia, Nokia Shanghai Bell | CR | Agreement |
9.3R19 Rapporteur Corrections
| Yes |
Yes
| noted | No | ||
| R3‑258206 | Rapporteur corrections | Nokia, Nokia Shanghai Bell | CR |
9.3R19 Rapporteur Corrections
| Yes |
Yes
| noted | No | |||
| R3‑258207 | Discussion on architecture for ISAC | Nokia, Nokia Shanghai Bell | discussion |
13.2Network architecture
| Yes |
No
| available | No | |||
| R3‑258208 | (TP to pCR) Discussion on RAN-CN procedures and signaling for ISAC | Nokia, Nokia Shanghai Bell | other |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | |||
| R3‑258209 | (TP for SON BL CR for TS 38.300) MRO Enhancements for Conditional Intra-CU LTM | Nokia | other | Agreement |
11.2.2Intra-CU conditional LTM
| Yes |
No
| available | No | ||
| R3‑258210 | Correction on the reference to TS 36.331 IEs | Nokia, Nokia Shanghai Bell | CR | Agreement |
9.3R19 Rapporteur Corrections
| Yes |
Yes
| noted | No | R3‑257226 | |
| R3‑258211 | Beam measurement report quantity | Huawei, Ericsson, Nokia, ZTE | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258212 | Beam measurement report quantity | Huawei, Ericsson, Nokia, ZTE | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258213 | Beam measurement report quantity | Huawei, Ericsson, Nokia, ZTE | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258214 | Miscellaneous corrections to E1AP for support of AI/ML NG-RAN | ZTE Corporation, CATT, China Unicom, China Telecom | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| revised | No | R3‑258711 | |
| R3‑258215 | Miscellaneous corrections to the support of split architecture | ZTE Corporation, CMCC, China Unicom, China Telecom | CR |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| revised | No | R3‑258812 | ||
| R3‑258216 | Support for Continuous Management-based MDT | ZTE Corporation, Huawei, CATT, CMCC, Samsung, China Unicom, China Telecom, Ericsson, FiberCop, Deutsche Telekom, Jio Platforms | draftCR | Endorsement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| noted | No | ||
| R3‑258217 | Correction on procedural text for Coverage and Capacity Optimization | ZTE Corporation, Jio Platforms, CMCC, China Unicom, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258218 | Correction on procedural text for Coverage and Capacity Optimization | ZTE Corporation, Jio Platforms, CMCC, China Unicom, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258219 | Correction on procedural text for Coverage and Capacity Optimization | ZTE Corporation, Jio Platforms, CMCC, China Unicom, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258220 | Correction of time-based handover for NR NTN | Huawei, Jio Platforms, CATT, Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, Deutsche Telekom, Samsung | draftCR | Endorsement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258221 | Correction of time-based handover for NR NTN | Huawei, Jio Platforms, CATT, Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, Deutsche Telekom, Samsung | draftCR | Endorsement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258222 | Correction on prioritized alternative QoS profile | Ericsson, ZTE Corporation, Huawei, Nokia | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258223 | Correction on prioritized alternative QoS profile | Ericsson, ZTE Corporation, Huawei, Nokia | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258224 | Correction on prioritized alternative QoS profile | Ericsson, ZTE Corporation, Huawei, Nokia | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258225 | Correction on prioritized alternative QoS profile | Ericsson, ZTE Corporation, Huawei, Nokia | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258226 | ASN1 Usage in 6G AP | Vodafone, Ericsson, Interdigital, Nokia, Telecom Italia | pCR | Approval |
10.2.1General principles and requirements
| Yes |
Yes
| noted | No | ||
| R3‑258227 | Correction on prioritized alternative QoS profile | Nokia, Ericsson, ZTE Corporation, Huawei | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258228 | Correction on prioritized alternative QoS profile | Nokia, Ericsson, ZTE Corporation, Huawei | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258229 | SBI and Point2Point definitions | Vodafone, Deutsche Telekom | pCR | Approval |
10.3.2RAN-CN interface options
| Yes |
Yes
| noted | No | ||
| R3‑258230 | Correction on prioritized alternative QoS profile | Nokia, Ericsson, ZTE Corporation, Huawei | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258231 | Correction on prioritized alternative QoS profile | Nokia, Ericsson, ZTE Corporation, Huawei | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258232 | Requirements for 6G RAN architecture design | FiberCop, CEWiT, Fujitsu, Jio Platform, KT Corp., Qualcomm Inc., Rakuten, Teja Networks, TIM-Telecom Italia,T-Mobile USA, Verizon Wireless | pCR | Agreement |
10.2.1General principles and requirements
| Yes |
Yes
| revised | No | R3‑258747 | |
| R3‑258233 | TR 38.760-3 V0.1.1 | Vodafone | draft TR | Approval |
10.1General
| No |
Yes
| withdrawn | Yes | ||
| R3‑258234 | Preliminary analysis on RAN-CN interface evolution towards Service Based Interface (SBI) | FiberCop, CEWiT, Deutsche Telekom, Qualcomm Inc., KT Corp | pCR | Agreement |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | ||
| R3‑258235 | NG-C Requirements (Legacy Services) | Vodafone, Telecom Italia, Deutsche Telekom | pCR | Approval |
10.3.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258236 | [pCR to TR38.760-3] 6G overall RAN architecture principle and requirements | NEC | pCR | Agreement |
10.2.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258237 | [pCR to TR38.760-3] 6G RAN logical architecture and RAN side function | NEC | pCR | Agreement |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | ||
| R3‑258238 | Correction on positioning data collection for assisting in the pairing with the TRP's measurement. | NEC | CR | Decision |
9.2.11R19 AI/ML for air interface
| Yes |
Yes
| noted | No | ||
| R3‑258239 | Correction to stage 2 description of Hard Feeder Link Switchover for regenerative payload | NEC | draftCR | Agreement |
9.2.6R19 NR NTN enhancements
| Yes |
Yes
| noted | No | ||
| R3‑258240 | Correction on A-IoT Inventory and Command procedure figures | NEC | draftCR | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| revised | No | R3‑258736 | |
| R3‑258241 | Discussion on Device identifier privacy protection impact on RAN3 | NEC | discussion | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| noted | No | ||
| R3‑258242 | Correction on A-IoT device identifier privacy protection impact on RAN3 | NEC | CR | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| noted | No | R3‑256790 | |
| R3‑258243 | (TP to BL pCR of TR38.765) The discussion on ISAC network architecture | NEC | other | Agreement |
13.2Network architecture
| Yes |
No
| available | No | ||
| R3‑258244 | (TP to BL pCR of TR38.765)The discussion on ISAC RAN-CN procedure and signaling | NEC | other | Agreement |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | ||
| R3‑258245 | Discussion on Topology 2 of Ambient IoT | NEC | discussion | Agreement |
14.2Topology 2
| Yes |
No
| available | No | ||
| R3‑258246 | MRO for Intra-CU conditional LTM | NEC | discussion | Agreement |
11.2.2Intra-CU conditional LTM
| Yes |
No
| available | No | ||
| R3‑258247 | (pCR for TR38.745) Multi-hop UE trajectory across gNBs | NEC | pCR | Agreement |
12.2.1Multi-hop UE trajectory across gNBs
| Yes |
Yes
| revised | No | R3‑258791 | |
| R3‑258248 | (pCR for TR38.745) AI/ML based intra-CU LTM | NEC | pCR | Agreement |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | ||
| R3‑258249 | (pCR for TR38.745) Other AI/ML based handover enhancements | NEC, Qualcomm | pCR | Agreement |
12.2.3Handover enhancements
| Yes |
No
| available | No | ||
| R3‑258250 | (pCR to TR38.760-3) 6G RAN-CN interface protocol consideration | NEC | pCR | Agreement |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | ||
| R3‑258251 | (pCR to TR38.760-3) Transport Layer protocol consideration for 6G RAN | NEC | pCR | Agreement |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | ||
| R3‑258252 | (pCR to TR38.760-3) AI/ML use cases for 6G | NEC | pCR | Agreement |
10.5.1AI/ML use cases
| Yes |
No
| available | No | ||
| R3‑258253 | reserved | NEC | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| No |
Yes
| withdrawn | Yes | ||
| R3‑258254 | Correction on inter-gNB Cell A indicator transfer | NEC, Nokia | CR | Agreement |
9.2.8R19 Network Energy Saving
| Yes |
Yes
| noted | No | ||
| R3‑258255 | (pCR to TR38.760-3) Discussion on RAN internal functional split and interfaces | NEC | pCR | Agreement |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258256 | MRO for inter-CU LTM | NEC | discussion | Decision |
11.2.1Inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑258257 | Discussion on RAN-CN procedures and signaling for ISAC | KPN N.V. | discussion | Decision |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | ||
| R3‑258258 | Progress of ETSI ISG ISAC Work Items | ETSI ISG ISAC(Interdigital) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258259 | Beam measurement report quantity | Ericsson, Jio Platforms, Huawei, Nokia, ZTE | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258260 | Beam measurement report quantity | Ericsson, Jio Platforms, Huawei, Nokia, ZTE | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258261 | Beam measurement report quantity | Ericsson, Jio Platforms, Huawei, Nokia, ZTE | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258262 | Discussion on the Issues of Topology 2 for A-IoT | Ofinno | discussion | Decision |
14.2Topology 2
| Yes |
No
| available | No | ||
| R3‑258263 | Correction on SN initiated inter-SN SCG LTM procedure | Ofinno, Ericsson, CATT, Qualcomm, Huawei, Google, LG Electronics, Nokia, Samsung, Lenovo, China Telecom | draftCR | Endorsement |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| endorsed | No | R3‑257033 | |
| R3‑258264 | Functionalities and signaling to support Topology 2 | Qualcomm Incorporated | discussion | Discussion |
14.2Topology 2
| Yes |
No
| available | No | ||
| R3‑258265 | Stage-2 Correction of WAB Xn Connection Management | Ericsson | CR | Agreement |
9.2.3R19 WAB
| Yes |
Yes
| revised | No | R3‑258771 | |
| R3‑258266 | (pCR for TR 38.760-3): 6G Data Collection | Ericsson | pCR | Agreement |
10.2.2RAN functions and logical architecture
| Yes |
Yes
| noted | No | ||
| R3‑258267 | (pCR for TR 38.760-3): Principles for 6G RAN AI-ML Use Case Study | Ericsson | pCR | Agreement |
10.5.1AI/ML use cases
| Yes |
Yes
| noted | No | ||
| R3‑258268 | Discussion on 6G RAN general principles and requirements | Nokia | pCR |
10.2.1General principles and requirements
| Yes |
No
| available | No | |||
| R3‑258269 | Corrections of enhancements on AI/ML for NG-RAN | Nokia | draftCR |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | |||
| R3‑258270 | Corrections of enhancements on AI/ML for NG-RAN | Nokia | CR |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | |||
| R3‑258271 | Corrections of AI/ML-based CCO | Nokia, Ofinno, Jio Platforms | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | ||
| R3‑258272 | Revocation of NZP CSI-RS resources | Nokia | CR |
9.2.10R19 Evolution of Duplex Operation
| Yes |
No
| available | No | |||
| R3‑258273 | Revocation of NZP CSI-RS resources | Nokia | CR |
9.2.10R19 Evolution of Duplex Operation
| Yes |
No
| available | No | |||
| R3‑258274 | [pCR to draft TR 38.760-3] 6G RAN Requirements for cloud native deployments | Qualcomm Inc, T-Mobile USA, AT&T, Verizon Wireless, Charter Communications, Apple Inc, Boost Mobile, Reliance Jio, KT Corp, NTT DOCOMO, Deutsche Telecom, Telstra, CEWiT, FiberCop, JIO Platforms, Fujitsu, LG Electronics, Tejas Networks, IIT-Hyderabad, WiSi | pCR | Agreement |
10.2.1General principles and requirements
| Yes |
Yes
| noted | No | ||
| R3‑258275 | [Draft TP for TS 38.473, TS 38.423] Remaining issues in Inter-CU LTM | Qualcomm Incorporated | other | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | ||
| R3‑258276 | Correction on prioritized alternative QoS profile | Huawei, ZTE, Ericsson, Nokia | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258277 | Correction on prioritized alternative QoS profile | Huawei, ZTE, Ericsson, Nokia | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258278 | Correction on prioritized alternative QoS profile | Huawei, ZTE, Ericsson, Nokia | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258279 | Correction on prioritized alternative QoS profile | Huawei, ZTE, Ericsson, Nokia | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258280 | Correction on Criticality in the OD-SIB1 Configuration Provision Response and Failure message | ZTE Corporation | CR | Approval |
9.2.8R19 Network Energy Saving
| Yes |
No
| available | No | ||
| R3‑258281 | RAN logical architecture and functions | Xiaomi | pCR |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | |||
| R3‑258282 | RAN3 Considerations on 6GR Data transfer | Xiaomi | pCR |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | |||
| R3‑258283 | General principles and functions on RAN-CN interface | Xiaomi | pCR |
10.3.1General principles and requirements
| Yes |
No
| available | No | |||
| R3‑258284 | RAN-CN interface and protocol options | Xiaomi | pCR |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | |||
| R3‑258285 | RAN internal functional split and interfaces | Xiaomi | pCR |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | |||
| R3‑258286 | Discussion on 6G RAN functionalities | OPPO | pCR | Decision |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | ||
| R3‑258287 | Discussion on 6G RAN-CN interfaces | OPPO | discussion | Decision |
10.3.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258288 | Discussion on 6G RAN internal interfaces | OPPO | discussion | Decision |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258289 | Discussion on protocol stack for sensing reporting | OPPO | discussion | Decision |
13.2Network architecture
| Yes |
No
| available | No | ||
| R3‑258290 | Discussion on RAN-CN procedures and signalling for sensing | OPPO | discussion | Decision |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | ||
| R3‑258291 | Correction on LTM Cell Switch Notification | LG Electronics, CATT, China Telecom, Ericsson, Google, Huawei, Jio Platforms, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Verizon, ZTE | CR | Approval |
9.2.5R19 Mobility enhancements
| No |
Yes
| withdrawn | Yes | ||
| R3‑258292 | Correction related to LTM Security Information | LG Electronics, CATT, China Telecom, Ericsson, Google, Huawei, Jio Platforms, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Verizon, ZTE | CR | Approval |
9.2.5R19 Mobility enhancements
| No |
Yes
| withdrawn | Yes | ||
| R3‑258293 | Correction on LTM Cell Switch Notification | LG Electronics, CATT, China Telecom, Ericsson, Google, Huawei, Jio Platforms, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Verizon, ZTE | CR | Approval |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| agreed | No | R3‑257125 | |
| R3‑258294 | Correction related to LTM Security Information | LG Electronics, CATT, China Telecom, Ericsson, Google, Huawei, Jio Platforms, NEC, Nokia, NTT Docomo, Ofinno, Qualcomm, Samsung, Verizon, ZTE | CR | Approval |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| agreed | No | R3‑257126 | |
| R3‑258295 | Correction on load measurement function | ZTE Corporation, Jio Platforms, China Unicom, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258296 | Correction on load measurement function | ZTE Corporation, Jio Platforms, China Unicom, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258297 | Correction on load measurement function | ZTE Corporation, Jio Platforms, China Unicom, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258298 | (TP to TR38.760-3) Initial discussion on functional framework for 6G AIRAN | ZTE Corporation | pCR |
10.2.1General principles and requirements
| Yes |
No
| available | No | |||
| R3‑258299 | Correction on the description of UE Context Information – Retrieve UE Context Response | ZTE Corporation, Nokia, Huawei, CATT, Samsung | CR | Agreement |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258725 | R3‑256564 |
| R3‑258300 | Correction on sending GW release indication | CATT | draftCR | Approval |
9.2.4R19 NR Femto
| Yes |
Yes
| revised | No | R3‑258712 | |
| R3‑258301 | Correction on OD-SIB1 Configuration Provision Failure | CATT, ZTE, Samsung | CR | Approval |
9.2.8R19 Network Energy Saving
| Yes |
No
| available | No | ||
| R3‑258302 | Corrections on termination of OD-SIB1 operation and status update | CATT, Huawei | CR | Approval |
9.2.8R19 Network Energy Saving
| Yes |
Yes
| revised | No | R3‑258810 | R3‑256765 |
| R3‑258303 | On maximum number of subgroups and RAN paging | CATT | CR | Approval |
9.2.9R19 Low Power WUS/WUR
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑258304 | Correction of URCP for RAN paging | CATT | CR | Approval |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258755 | |
| R3‑258305 | Correction of URCP for RAN paging | CATT | CR | Approval |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258756 | |
| R3‑258306 | Correction of URCP for RAN paging | CATT | CR | Approval |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258757 | |
| R3‑258307 | Correction on Extended UE Identity Index Value for PEI | CATT, ZTE, China Telecomm | draftCR | Approval |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258308 | Correction on Extended UE Identity Index Value for PEI | CATT, ZTE, China Telecomm | draftCR | Approval |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258309 | (TP to BL pCR for TR38.765) Discussion on network architecture for ISAC | CATT | other | Approval |
13.2Network architecture
| Yes |
No
| available | No | ||
| R3‑258310 | (TP to BL pCR for TR38.765) RAN-CN procedures and signaling on ISAC | CATT | other | Approval |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | ||
| R3‑258311 | Discussion on Topology-2 for Ambient IoT | CATT | discussion | Decision |
14.2Topology 2
| Yes |
No
| available | No | ||
| R3‑258312 | Discussion on supporting inter-CU SCG LTM and the L2 reset function in inter-CU LTM | discussion | Decision |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | R3‑257157 | ||
| R3‑258313 | Correction to L2 reset in inter-CU LTM | Google, Nokia, CATT, Ericsson | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | R3‑257158 | |
| R3‑258314 | Discussion on allocation of CN assigned subgroup ID for LP-WUS | Huawei, Qualcomm, vivo | discussion |
9.2.9R19 Low Power WUS/WUR
| Yes |
No
| available | No | |||
| R3‑258315 | Allocation of CN assigned subgroup ID for LP-WUS | Huawei, Qualcomm, vivo | draftCR |
9.2.9R19 Low Power WUS/WUR
| Yes |
Yes
| revised | No | R3‑258760 | ||
| R3‑258316 | [Draft] Reply LS on allocation of CN assigned subgroup ID for LP-WUS | Huawei, Qualcomm, vivo | LS out |
9.2.9R19 Low Power WUS/WUR
| Yes |
No
| available | No | |||
| R3‑258317 | Correction to L2 reset in inter-CU LTM (option 2) | Google, Huawei | CR |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| revised | No | R3‑258781 | ||
| R3‑258318 | Discussion on 6G RAN internal split | Fujitsu Limited | discussion |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | |||
| R3‑258319 | Correction to LTM MCG configuration management for inter-CU SCG LTM | Google, Huawei | CR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258320 | Discussion on Reply LS on geographical area scope MDT | Huawei | discussion |
9.2.1R19 SON/MDT
| Yes |
Yes
| noted | No | |||
| R3‑258321 | [Draft]Reply LS on geographical area scope MDT | Huawei | LS out |
9.2.1R19 SON/MDT
| Yes |
Yes
| noted | No | |||
| R3‑258322 | Correction on the Rel-19 set ID assignment in inter-CU LTM | Huawei, Nokia, Jio Platforms, CATT, China Telecom, Lenovo | discussion |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258323 | Correction on the Rel-19 set ID assignment in inter-CU LTM (Option 1) | Huawei, Jio Platforms, CATT, China Telecom, Lenovo | draftCR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258324 | Correction on the Rel-19 set ID assignment in inter-CU LTM (Option 2) | Huawei, Nokia, Jio Platforms, CATT, China Telecom | CR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258325 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM | Huawei, NEC,Jio Platforms, CMCC, China Telecom, Lenovo | discussion |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258326 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 1) | Huawei, NEC, Jio Platforms, CMCC, China Telecom, Lenovo | CR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258327 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 1) | Huawei | CR |
9.2.5R19 Mobility enhancements
| No |
Yes
| withdrawn | Yes | |||
| R3‑258328 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 2) | Huawei, NEC, Jio Platforms, CMCC, China Telecom | CR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258329 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 2) | Huawei | CR |
9.2.5R19 Mobility enhancements
| No |
Yes
| withdrawn | Yes | |||
| R3‑258330 | Consideration on RAN internal function split and interfaces | Huawei | pCR | Agreement |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258331 | Correction on multi-hop avoidance during handover | Huawei, Nokia, Nokia Shanghai Bell, China Telecom | CR | Approval |
9.2.3R19 WAB
| Yes |
Yes
| revised | No | R3‑258770 | |
| R3‑258332 | Correction on multi-modality, uplink rate control and available bit rate monitoring | Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Ofinno, ZTE, Lenovo | draftCR | Endorsement |
9.2.12R19 NR XR Enhancements
| Yes |
Yes
| revised | No | R3‑258797 | |
| R3‑258333 | Correction on QoS parameters for QoS Notification Control | Huawei, Nokia, Nokia Shanghai Bell, China Telecom, CMCC | draftCR |
9.2.14Other
| Yes |
No
| available | No | R3‑256804 | ||
| R3‑258334 | Correction on QoS parameters for QoS Notification Control | Huawei, Nokia, Nokia Shanghai Bell, China Telecom, CMCC | draftCR |
9.2.14Other
| Yes |
No
| available | No | R3‑256805 | ||
| R3‑258335 | Discussion on support of Topology 2 | LG Electronics | discussion |
14.2Topology 2
| Yes |
No
| available | No | |||
| R3‑258336 | Discussion on Cause values for Ambient IoT | CATT | discussion | Decision |
9.2.7R19 Ambient IoT
| Yes |
No
| available | No | ||
| R3‑258337 | Correction to A-IoT specific cause values | CATT | CR | Approval |
9.2.7R19 Ambient IoT
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑258338 | Correction to A-IoT security information | CATT | CR | Approval |
9.2.7R19 Ambient IoT
| Yes |
Yes
| noted | No | ||
| R3‑258339 | Orange views on RAN internal functional split in 6G | Orange | discussion | Discussion |
10.4RAN internal functional split and interfaces
| Yes |
Yes
| withdrawn | Yes | R3‑258409 | |
| R3‑258340 | Discussion on RAN-CN interface | Tejas Network Limited | discussion | Discussion |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | ||
| R3‑258341 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 1) | Huawei, NEC, Jio Platforms, CMCC, China Telecom, Lenovo | CR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258342 | Correction on CSI Report Configuration for CSI Acquisition for inter-CU LTM (Option 2) | Huawei, NEC, Jio Platforms, CMCC, China Telecom | CR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258343 | Avoiding paging capability loss after handover resource allocation and path switch request procedure | Huawei, China Unicom, China Telecom, CATT | CR |
9.2.14Other
| Yes |
Yes
| noted | No | R3‑256816 | ||
| R3‑258344 | Avoiding paging capability loss after handover resource allocation and path switch request procedure | Huawei, China Unicom, China Telecom, CATT | CR |
9.2.14Other
| Yes |
No
| available | No | R3‑256817 | ||
| R3‑258345 | Avoiding paging capability loss after handover resource allocation and path switch request procedure | Huawei, China Unicom, China Telecom, CATT | CR |
9.2.14Other
| Yes |
No
| available | No | R3‑256818 | ||
| R3‑258346 | Avoiding paging capability loss after handover resource allocation and path switch request procedure | Huawei, China Unicom, China Telecom | draftCR |
9.2.14Other
| Yes |
Yes
| noted | No | R3‑256819 | ||
| R3‑258347 | Avoiding paging capability loss after handover resource allocation and path switch request procedure | Huawei, China Unicom, China Telecom | draftCR |
9.2.14Other
| Yes |
No
| available | No | R3‑256820 | ||
| R3‑258348 | Avoiding paging capability loss after handover resource allocation and path switch request procedure | Huawei, China Unicom, China Telecom | draftCR |
9.2.14Other
| Yes |
No
| available | No | R3‑256821 | ||
| R3‑258349 | [Draft] Reply LS on paging capability loss issue | Huawei, China Unicom, China Telecom | LS out | Approval |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258723 | |
| R3‑258350 | RAN-CN interface considerations | China Telecom | discussion | Decision |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | ||
| R3‑258351 | Support of Ambient IoT Topology 2 | China Telecom | discussion | Decision |
14.2Topology 2
| Yes |
No
| available | No | ||
| R3‑258352 | Consideration on 6G RAN internal functional split and interfaces | China Telecom | discussion | Decision |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258353 | Discussion on high priority use cases for 6G | China Telecom | discussion | Decision |
10.5.1AI/ML use cases
| Yes |
Yes
| noted | No | ||
| R3‑258354 | Discussion on multi-hop UE trajectory prediction | China Telecom | discussion | Decision |
12.2.1Multi-hop UE trajectory across gNBs
| Yes |
No
| available | No | ||
| R3‑258355 | Discussion on support of AIML based intra-CU LTM | China Telecom | discussion | Decision |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | ||
| R3‑258356 | Discussion on support of AIML based inter-CU LTM | China Telecom | discussion | Decision |
12.2.3Handover enhancements
| Yes |
No
| available | No | ||
| R3‑258357 | Work plan for study on Integrated Sensing And Communication (ISAC) for NR | China Telecom, Xiaomi | Work Plan | Decision |
13.1General
| Yes |
Yes
| noted | No | ||
| R3‑258358 | On protocol stack solution for ISAC | China Telecom | discussion | Decision |
13.2Network architecture
| Yes |
No
| available | No | ||
| R3‑258359 | (TP to 38.473) On RAN-CN functions and procedures for supporting ISAC | China Telecom, BUPT | other | Agreement |
13.3RAN-CN procedures and signaling
| Yes |
Yes
| noted | No | ||
| R3‑258360 | General Principles and Requirements of 6G RAN Architecture | Lenovo | pCR |
10.2.1General principles and requirements
| Yes |
No
| available | No | |||
| R3‑258361 | 6G RAN Logical Architecture | Lenovo | pCR |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | |||
| R3‑258362 | General Principles and Requirements of 6G RAN-CN Functional Split and Interface | Lenovo | pCR |
10.3.1General principles and requirements
| Yes |
No
| available | No | |||
| R3‑258363 | 6G RAN-CN Interface Options | Lenovo | pCR |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | |||
| R3‑258364 | 6G RAN Internal Functional Split and Interfaces | Lenovo | discussion |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | |||
| R3‑258365 | Considerations for Data Collection Framework | Lenovo | pCR |
10.2.2RAN functions and logical architecture
| Yes |
Yes
| noted | No | |||
| R3‑258366 | Considerations for AIML for RAN use cases | Lenovo | pCR |
10.5.1AI/ML use cases
| Yes |
No
| available | No | |||
| R3‑258367 | Discussion on MRO for inter-CU LTM | Lenovo | discussion |
11.2.1Inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑258368 | (TP for TS38.300) Discussion on MRO for intra-CU CLTM | Lenovo | other | Agreement |
11.2.2Intra-CU conditional LTM
| Yes |
Yes
| revised | No | R3‑258758 | |
| R3‑258369 | (pCR to TR38.745) Discussion on multi-hop UE trajectory | Lenovo | pCR |
12.2.1Multi-hop UE trajectory across gNBs
| Yes |
No
| available | No | |||
| R3‑258370 | AI/ML for intra-CU LTM | Lenovo | discussion |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | |||
| R3‑258371 | (TP to TR 38.765) Discussion on ISAC network architecture | Lenovo | other |
13.2Network architecture
| Yes |
No
| available | No | |||
| R3‑258372 | (TP to TR 38.765) Discussion on general procedures for gNB-based sensing | Lenovo | other |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | |||
| R3‑258373 | On UE Reader Selection in Topology 2 | Lenovo | discussion |
14.2Topology 2
| Yes |
No
| available | No | |||
| R3‑258374 | Correction on assigned criticality for NES | Samsung | CR | Agreement |
9.2.8R19 Network Energy Saving
| Yes |
No
| available | No | ||
| R3‑258375 | Correction on Burst Size for XR | Samsung | draftCR | Endorsement |
9.2.12R19 NR XR Enhancements
| Yes |
Yes
| revised | No | R3‑258798 | |
| R3‑258376 | Discussion on network architecture for ISAC | Samsung | discussion | Agreement |
13.2Network architecture
| Yes |
No
| available | No | ||
| R3‑258377 | Discussion on RAN-CN procedures and signaling | Samsung | discussion | Agreement |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | ||
| R3‑258378 | Discussion on RAN logical architecture and functions | ZTE Corporation | discussion | Decision |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | ||
| R3‑258379 | Discussion on LS Response on compatibility issue for PEI and emergency PDU session | ZTE Corporation | discussion | Decision |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258380 | Corrections for additional ULI for WAB | ZTE Corporation, China Telecom, Pengcheng Laboratory, Samsung | CR | Approval |
9.2.3R19 WAB
| Yes |
Yes
| noted | No | ||
| R3‑258381 | Corrections on GUAMI List for Femto | ZTE Corporation, China Telecom, Pengcheng Laboratory | CR | Approval |
9.2.4R19 NR Femto
| Yes |
Yes
| noted | No | ||
| R3‑258382 | Discussion on the reply LS on allocation of CN assigned subgroup ID for LP-WUS | ZTE Corporation | discussion | Decision |
9.2.9R19 Low Power WUS/WUR
| Yes |
No
| available | No | ||
| R3‑258383 | [draft] Reply LS on allocation of CN assigned subgroup ID for LP-WUS | ZTE Corporation | other | Approval |
9.2.9R19 Low Power WUS/WUR
| Yes |
No
| available | No | ||
| R3‑258384 | Correction on the Extended UE Identity Index Value for PEI | ZTE Corporation, CATT, China Telecom | draftCR | Approval |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258385 | Corrections on L2 reset for LTM | ZTE Corporation | CR | Approval |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258386 | Corrections on L2 reset for LTM | ZTE Corporation | CR | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑258387 | Corrections on L2 reset for LTM | ZTE Corporation | CR | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑258388 | Corrections on L2 reset for LTM | ZTE Corporation | CR | Approval |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑258389 | Discussion on 6G AI/ML Network Energy Savings use case | Fujitsu Limited | discussion |
10.5.1AI/ML use cases
| Yes |
No
| available | No | |||
| R3‑258390 | Essential correction on inter-CU LTM in DC | CATT,Huawei, China Telecom, Nokia, Samsung, NEC, Ericsson | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| revised | No | R3‑258713 | R3‑256873 |
| R3‑258391 | (pCR to TR 38.745) AI/ML based mobility – Multi-hop UE trajectory | Ericsson | pCR |
12.2.1Multi-hop UE trajectory across gNBs
| Yes |
No
| available | No | |||
| R3‑258392 | Essential correction for inter-CU LTM on F1AP | CATT,Huawei, China Telecom, LG Electronics, Nokia, Samsung, ZTE, Ofinno, Ericsson | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| revised | No | R3‑258787 | R3‑256871 |
| R3‑258393 | (pCR to TR 38.745) AI/ML based mobility – Intra-CU LTM | Ericsson | pCR |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | |||
| R3‑258394 | Paging capability loss in RAN | Vodafone | CR | Agreement |
9.2.14Other
| Yes |
Yes
| noted | No | ||
| R3‑258395 | (pCR to TR 38.745) AI/ML based mobility – Handover Enhancements | Ericsson | pCR |
12.2.3Handover enhancements
| Yes |
No
| available | No | |||
| R3‑258396 | Rel-17 Introduction of IAB-related Definitions | Ericsson | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258397 | Rel-18 Introduction of IAB-related Definitions | Ericsson | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258398 | Rel-19 Introduction of IAB-related Definitions | Ericsson | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258399 | General principles and requirements for 6G RAN-CN interface | LG Electronics | pCR |
10.3.1General principles and requirements
| Yes |
No
| available | No | |||
| R3‑258400 | Consideration on RAN-CN interface options | LG Electronics | pCR | Agreement |
10.3.2RAN-CN interface options
| Yes |
Yes
| noted | No | ||
| R3‑258401 | Paging capability loss in RAN | Vodafone Ireland Plc | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258402 | Correction on Criticality in the OD-SIB1 Configuration Provision Status Update message | ZTE Corporation | CR | Approval |
9.2.8R19 Network Energy Saving
| Yes |
No
| available | No | ||
| R3‑258403 | Paging capability loss in RAN | Vodafone Ireland Plc | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258404 | Rapporteur correction of TS 38.410 | Nokia | CR | Agreement |
9.3R19 Rapporteur Corrections
| Yes |
Yes
| revised | No | R3‑258718 | |
| R3‑258405 | Rapporteur correction of TS 38.415 | Nokia | CR | Agreement |
9.3R19 Rapporteur Corrections
| Yes |
Yes
| revised | No | R3‑258719 | |
| R3‑258406 | Discussion on TNLA handling during Xn handover | NTT DOCOMO INC.. | discussion |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258407 | Correction of Inventory Report | Nokia | CR |
9.2.7R19 Ambient IoT
| Yes |
No
| available | No | |||
| R3‑258408 | Clarification on TNLA handling during Xn handover | NTT DOCOMO | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑257134 | |
| R3‑258409 | Orange views on RAN internal functional split in 6G | Orange | discussion |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | R3‑258339 | ||
| R3‑258410 | Correction of LP-WUS | Nokia | CR | Agreement |
9.2.9R19 Low Power WUS/WUR
| Yes |
No
| available | No | ||
| R3‑258411 | Clarification on TNLA handling during Xn handover | NTT DOCOMO | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑257135 | |
| R3‑258412 | Correction of Served PLMN | Nokia | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258413 | Clarification on TNLA handling during Xn handover | NTT DOCOMO | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑257136 | |
| R3‑258414 | Clarification on TNLA handling during Xn handover | NTT DOCOMO | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑257137 | |
| R3‑258415 | Handling of emergency PDU session and PEI | Nokia | discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | |||
| R3‑258416 | Support of Continuous Management Based MDT | Nokia | CR |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | |||
| R3‑258417 | Introduction of support for Continuous Management Based MDT in stage 2 | Nokia | draftCR |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | |||
| R3‑258418 | Requirements and deployment scenarios toward 6G RAN | NTT DOCOMO INC.. | discussion |
10.2.1General principles and requirements
| Yes |
No
| available | No | |||
| R3‑258419 | Requirements for 6G RAN functions | NTT DOCOMO INC.. | discussion |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | |||
| R3‑258420 | Reply LS on compatibility issue for PEI and emergency PDU session | Nokia | LS out |
8.1New Incoming LSs
| Yes |
No
| available | No | |||
| R3‑258421 | Requirements toward 6G RAN-CN functional split | NTT DOCOMO INC.. | discussion |
10.3.1General principles and requirements
| Yes |
No
| available | No | |||
| R3‑258422 | Correction on CCO prediction cancel | NEC | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | ||
| R3‑258423 | Correction on OD-SIB1 failure cause | NEC, Rakuten | CR | Agreement |
9.2.8R19 Network Energy Saving
| Yes |
No
| available | No | ||
| R3‑258424 | Necessary considerations for 6G RAN-CN interface options | NTT DOCOMO INC.. | discussion |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | |||
| R3‑258425 | 6G Service Awareness in RAN | Nokia, T-Mobile USA, DT | pCR |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | |||
| R3‑258426 | 6G RAN-CN Interface Requirements | Nokia, Orange | pCR |
10.3.1General principles and requirements
| Yes |
No
| available | No | |||
| R3‑258427 | 6G RAN-CN cloud friendly P2P Solution | Nokia | pCR |
10.3.2RAN-CN interface options
| Yes |
Yes
| revised | No | R3‑258767 | ||
| R3‑258428 | Inventory Procedure for AIoT Topology 2 UEs | Nokia | discussion |
14.2Topology 2
| Yes |
No
| available | No | |||
| R3‑258429 | SRB ID correction | Ericsson, Jio Platforms, Nokia | CR | Approval |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258430 | SRB ID correction | Ericsson, Jio Platforms, Nokia | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258431 | Discussion on 6G RAN architecture of data collection | Samsung | pCR | Agreement |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | ||
| R3‑258432 | Discussion on RAN-CN interface design | Samsung | pCR | Agreement |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | ||
| R3‑258433 | Continuous MDT support | Ericsson, Deutsche Telekom, FiberCop, Jio Platforms, InterDigital, BT, Orange, Verizon, ZTE, Huawei, Telecom Italia, NEC, Samsung, CATT, China Telecom, China Unicom | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| noted | No | R3‑257309 | |
| R3‑258434 | Abnormal conditions for F1: gNB-CU Configuration Update | Ericsson, Jio Platforms, InterDigital, Fibercop | discussion | Approval |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | ||
| R3‑258435 | Abnormal conditions for gNB-CU Configuration Update with updated Presence IE | Ericsson, Jio Platforms, InterDigital, Fibercop | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑258436 | Correction for gNB-DU Configuration Update | Ericsson, Jio Platforms, InterDigital, Fibercop | discussion | Approval |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | ||
| R3‑258437 | Correction for gNB-DU Configuration Update | Ericsson, Jio Platforms, InterDigital, Fibercop | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑258438 | Stage 2 corrections for AI/ML based CCO | Ericsson, Jio Platforms, InterDigital, Fibercop | discussion | Approval |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | ||
| R3‑258439 | Stage 2 corrections for AI/ML based CCO | Ericsson, Jio Platforms, InterDigital, Fibercop | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑258440 | Corrections on SBFD support | Ericsson | CR | Agreement |
9.2.10R19 Evolution of Duplex Operation
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑258441 | General Principles and Requirements for the 6G RAN architecture | Ericsson, Jio Platforms | pCR | Agreement |
10.2.1General principles and requirements
| No |
Yes
| withdrawn | Yes | ||
| R3‑258442 | Functions and Architecture for the 6G RAN | Ericsson | pCR | Agreement |
10.2.2RAN functions and logical architecture
| No |
Yes
| withdrawn | Yes | ||
| R3‑258443 | Rapporteur Corrections | Huawei | CR | Agreement |
9.3R19 Rapporteur Corrections
| Yes |
Yes
| noted | No | R3‑256965 | |
| R3‑258444 | Discussion on general principles and requirements for 6G RAN | CATT | pCR | Decision |
10.2.1General principles and requirements
| Yes |
Yes
| revised | No | R3‑258745 | |
| R3‑258445 | Discussion on Deployment Principles and Scenarios for 6G RAN | CATT | pCR | Decision |
10.2.1General principles and requirements
| Yes |
Yes
| noted | No | ||
| R3‑258446 | Discussion on 6G RAN Logical Architecture | CATT | pCR | Decision |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | ||
| R3‑258447 | Consideration on general principles and requirements on RAN-CN interface | CATT | pCR | Decision |
10.3.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258448 | Considerations on 6G RAN-CN interface options | CATT | pCR | Decision |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | ||
| R3‑258449 | Consideration on AI/ML use cases | CATT | pCR | Decision |
10.5.1AI/ML use cases
| Yes |
No
| available | No | ||
| R3‑258450 | Consideration on internal interfaces within 6G RAN | CATT | pCR | Decision |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258451 | Discussion on UL data forwarding | CATT,Huawei | discussion | Decision |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258452 | Corrections to TS 38.420 on support of Network Energy Saving Enhancement | Ericsson | CR | Agreement |
9.2.8R19 Network Energy Saving
| Yes |
Yes
| noted | No | R3‑257090 | |
| R3‑258453 | Corrections to OD-SIB1 Configuration Provision Status Update | Ericsson | CR | Agreement |
9.2.8R19 Network Energy Saving
| Yes |
Yes
| revised | No | R3‑258809 | R3‑257091 |
| R3‑258454 | ISAC Logical Architecture and Protocol Stack | Ericsson | other | Agreement |
13.2Network architecture
| Yes |
No
| available | No | ||
| R3‑258455 | Support of multi-hop UE trajectory prediction/feedback | CATT | pCR | Decision |
12.2.1Multi-hop UE trajectory across gNBs
| Yes |
No
| available | No | ||
| R3‑258456 | Discussion on support of AI/ML enabled intra-CU LTM | CATT | pCR | Decision |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | ||
| R3‑258457 | Discussion on support of AI/ML enabled inter-CU LTM | CATT | discussion | Decision |
12.2.3Handover enhancements
| Yes |
No
| available | No | ||
| R3‑258458 | Support for continuous management-based MDT | CATT, Ericsson,ZTE, CMCC, Samsung, NEC | draftCR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| revised | No | R3‑258799 | |
| R3‑258459 | Semi-Persistent CSI-RS activation with TCI state for CSI Acquisition | CATT | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | ||
| R3‑258460 | Correction of Failure report without RLF report | Huawei, Nokia, JIO plattforms, Ericsson | CR | Agreement |
9.2.1R19 SON/MDT
| Yes |
Yes
| revised | No | R3‑258762 | |
| R3‑258461 | Rapporteur Corrections | Huawei | CR | Agreement |
9.3R19 Rapporteur Corrections
| Yes |
Yes
| noted | No | ||
| R3‑258462 | (TP for BLCR for 38.413) Inter-CU LTM | Huawei | other |
11.2.1Inter-CU LTM
| Yes |
Yes
| revised | No | R3‑258803 | ||
| R3‑258463 | Intra-CU conditional LTM | Huawei | other |
11.2.2Intra-CU conditional LTM
| Yes |
No
| available | No | |||
| R3‑258464 | UE Retention in NG-RAN | Ericsson, Huawei, Jio Platforms, Thales | discussion | Discussion |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258465 | UE Context Retention for NG - Stage 2 | Ericsson, Huawei, Jio Platforms, Thales | draftCR | Endorsement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258466 | Discussion on removal of support of PWS over satellite NG-RAN in Rel-17 and Rel-18 | Huawei | discussion | Agreement |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258467 | Correction of PWS support for IoT NTN | Huawei | draftCR | Endorsement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑258468 | Correction of PWS support for IoT NTN | Huawei | draftCR | Endorsement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑258469 | Reply LS on removal of support of PWS for NR NTN and IoT NTN in Rel-17 and 18 | Huawei | LS out | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑258470 | UE Context Retention for NG - Stage 2 | Ericsson, Huawei, Jio Platforms, Thales | draftCR | Endorsement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258471 | LTM Cell Swicth Type Indication | Nokia, LGE, Huawei | CR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258472 | Inter-Satellite Links and Transparent Payloads | Ericsson, Aalyria, Thales, Airbus | discussion | Discussion |
9.2.6R19 NR NTN enhancements
| Yes |
Yes
| noted | No | ||
| R3‑258473 | LTM Cell Swicth Type Indication | Nokia, LGE, Huawei | CR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258474 | Inter-Satellite Links and Transparent Payloads - NR NTN | Ericsson, Aalyria, Thales, Airbus | draftCR | Endorsement |
9.2.6R19 NR NTN enhancements
| Yes |
Yes
| noted | No | ||
| R3‑258475 | [Draft] Reply LS on Continuous MDT | Huawei, ZTE, FiberCop, Jio Platforms | LS out | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| revised | No | R3‑258773 | |
| R3‑258476 | Correction on procedural text for reporting of predicted radio resource status per slice | Huawei | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| noted | No | ||
| R3‑258477 | Discussion on XnAP reporting of predicted radio resource status per slice | Huawei | discussion | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| noted | No | ||
| R3‑258478 | Support for partial reporting in Data Collection Reporting procedure | Huawei, FiberCop, Verizon, Jio Platforms, Qualcomm, ZTE | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| revised | No | R3‑258774 | |
| R3‑258479 | [Draft] LS on definition of “ground truth label” in AI/ML-based Positioning Case 3a | Huawei, Ericsson, Nokia | LS out | Agreement |
9.2.11R19 AI/ML for air interface
| Yes |
Yes
| revised | No | R3‑258796 | |
| R3‑258480 | Discussion on the Reply LS from SA2 on AI/ML Positioning Case 3a | Huawei, Nokia, Qualcomm, Samsung | discussion | Decision |
9.2.11R19 AI/ML for air interface
| Yes |
No
| available | No | ||
| R3‑258481 | Further discussion on AI/ML for 6G RAN use cases | Huawei | pCR | Agreement |
10.5.1AI/ML use cases
| Yes |
No
| available | No | ||
| R3‑258482 | Further considerations on multi-hop UE trajectory in AI/ML-based mobility | Huawei | pCR | Agreement |
12.2.1Multi-hop UE trajectory across gNBs
| Yes |
No
| available | No | ||
| R3‑258483 | Further discussion on AI/ML assisted intra-CU LTM | Huawei | pCR | Agreement |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | ||
| R3‑258484 | Further discussion for Handover Enhancements | Huawei | pCR | Agreement |
12.2.3Handover enhancements
| Yes |
No
| available | No | ||
| R3‑258485 | Inter-Satellite Links and Transparent Payloads - IoT NTN | Ericsson, Aalyria, Thales, Airbus | draftCR | Endorsement |
9.1.1R19 IoT NTN enhancements
| Yes |
No
| available | No | ||
| R3‑258486 | Extensions for enumerated type definitions over several Releases - and what can go wrong | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | discussion | Discussion |
9.2.14Other
| Yes |
Yes
| noted | No | ||
| R3‑258487 | Correcting the extension of FR1-bandwidth type definition | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258737 | R3‑256996 |
| R3‑258488 | Correcting the extension of FR1-bandwidth type definition | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258738 | R3‑256997 |
| R3‑258489 | Correcting the IE extension definition for bandwidth SRS | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258739 | R3‑256998 |
| R3‑258490 | Correcting the IE extension definition for bandwidth SRS | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258740 | R3‑256999 |
| R3‑258491 | Correcting the IE extension definition for SRS Pos SIB Type | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258741 | R3‑257000 |
| R3‑258492 | X2AP rapporteur corrections | Ericsson | CR |
9.3R19 Rapporteur Corrections
| Yes |
Yes
| revised | No | R3‑258720 | ||
| R3‑258493 | Correction on ETA resource release in DU | Ofinno, Ericsson | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑257036 | |
| R3‑258494 | Correction on ETA resource release in DU | Ofinno, Ericsson | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑257117 | |
| R3‑258495 | LTM Resource consumption for the target cells | SONY, Ericsson, vivo, Jio Platforms, LG Electronics | discussion |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258496 | Correction for Cell Switch execution | SONY, Ericsson, vivo, Jio Platforms, LG Electronics | draftCR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258497 | Abnormal conditions for gNB-CU Configuration Update with updated Presence IE | Ericsson, Jio Platforms, InterDigital, Fibercop | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| No |
Yes
| withdrawn | Yes | ||
| R3‑258498 | Correction for gNB-DU Configuration Update | Ericsson, Jio Platforms, InterDigital, Fibercop | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| No |
Yes
| withdrawn | Yes | ||
| R3‑258499 | Stage 2 corrections for AI/ML based CCO | Ericsson, Jio Platforms, InterDigital, Fibercop | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| No |
Yes
| withdrawn | Yes | ||
| R3‑258500 | Corrections on SBFD support | Ericsson | CR | Agreement |
9.2.10R19 Evolution of Duplex Operation
| No |
Yes
| withdrawn | Yes | ||
| R3‑258501 | Network architecture enhancements for NR ISAC | Hanbat National University | discussion |
13.2Network architecture
| Yes |
No
| available | No | |||
| R3‑258502 | Corrections to stage-2 specification for support for on-demand SIB1 | Ericsson, Jio Platforms, China Telecom, Rakuten | CR | Agreement |
9.2.8R19 Network Energy Saving
| Yes |
No
| available | No | R3‑257087 | |
| R3‑258503 | Corrections to F1 support of Network Energy Saving Enhancement | Ericsson, China Telecom, Jio Platforms, Lenovo, Rakuten | CR | Approval |
9.2.8R19 Network Energy Saving
| Yes |
Yes
| revised | No | R3‑258743 | |
| R3‑258504 | Addition of OAM support for on-demand SIB1 | Ericsson, China Telecom, Jio Platforms, Lenovo | draftCR | Approval |
9.2.8R19 Network Energy Saving
| Yes |
No
| available | No | ||
| R3‑258505 | Workplan for Rel-20 Study of 6GR | Vodafone | Work Plan | Information |
10.1General
| Yes |
Yes
| noted | No | ||
| R3‑258506 | Correction on the UE Initial Access procedure | Ericsson | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑252063 | |
| R3‑258507 | Correction on the UE Initial Access procedure | Ericsson | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑252064 | |
| R3‑258508 | Corrections on Inter-CU LTM | Ericsson, Lenovo, LG Electronics, Nokia, Samsung, ZTE, Ofinno | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| agreed | No | R3‑257175 | |
| R3‑258509 | Summary of Essential Corrections and Open Issues for Rel-19 LTM | Ericsson, CATT, Jio Platforms, Ofinno | discussion |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258510 | Corrections for Rel-19 LTM | Ericsson, Jio Platforms, CATT, China Telecom, Lenovo, LG Electronics, Nokia, ZTE, Samsung, Ofinno | draftCR |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| endorsed | No | |||
| R3‑258511 | Correction on the UE Initial Access procedure | Ericsson | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑252065 | |
| R3‑258512 | Correction on the UE Initial Access procedure | Ericsson | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑252068 | |
| R3‑258513 | Correction on the UE Initial Access procedure | Ericsson | CR |
9.2.14Other
| Yes |
No
| available | No | |||
| R3‑258514 | Discussion on Exit Conditions | Nokia | discussion |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | |||
| R3‑258515 | Clarifying the MRO for LTM use-case | Ericsson | CR | Agreement |
9.2.1R19 SON/MDT
| Yes |
Yes
| noted | No | ||
| R3‑258516 | BFR in CSI-RS beam | Ericsson | CR | Agreement |
9.2.1R19 SON/MDT
| Yes |
Yes
| revised | No | R3‑258707 | |
| R3‑258517 | MRO for inter-gNB LTM | Ericsson | discussion |
11.2.1Inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑258518 | MRO for Conditional LTM | Ericsson | discussion |
11.2.2Intra-CU conditional LTM
| Yes |
No
| available | No | |||
| R3‑258519 | About 6G RAN-internal architecture topics | Ericsson | discussion | Agreement |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258520 | Discussion on 6G RAN Functions and Architecture | Jio Platforms, FiberCop | discussion |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | |||
| R3‑258521 | RAN-CN Principal Interface Option Discussions | Jio Platforms | discussion |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | |||
| R3‑258522 | On the Discussion of 6G RAN Internal Functional Split | Jio Platforms, FiberCop | discussion |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | |||
| R3‑258523 | AI/ML-based use cases and unified framework for 6G | Jio Platforms | discussion |
10.5.1AI/ML use cases
| Yes |
No
| available | No | |||
| R3‑258524 | CN assigned subgroup ID for LP-WUS | Ericsson | discussion | Discussion |
9.2.9R19 Low Power WUS/WUR
| Yes |
No
| available | No | ||
| R3‑258525 | Clarification on allocation of CN assigned subgroup ID for LP-WUS | Ericsson | draftCR | Endorsement |
9.2.9R19 Low Power WUS/WUR
| Yes |
No
| available | No | ||
| R3‑258526 | DRAFT Reply LS on CN assigned subgroup ID for LP-WUS | Ericsson | LS out | Agreement |
9.2.9R19 Low Power WUS/WUR
| Yes |
Yes
| revised | No | R3‑258761 | |
| R3‑258527 | Correction of Data Collection Report procedure and others | Ericsson, Huawei, Nokia, Xiaomi, ZTE, CATT, NEC, Samsung, Qualcomm Inc., CEWiT | draftCR | Endorsement |
9.2.11R19 AI/ML for air interface
| Yes |
Yes
| revised | No | R3‑258795 | |
| R3‑258528 | Addition of PDCP discard timer for scheduling with DSR | Ericsson, Qualcomm Inc., Jio Platforms | CR | Agreement |
9.2.14Other
| Yes |
Yes
| noted | No | R3‑257037 | |
| R3‑258529 | Addition of PDCP discard timer for scheduling with DSR | Ericsson, Qualcomm Inc., Jio Platforms | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑257039 | |
| R3‑258530 | Addition of 2Rx XR UE Capability | Ericsson, Qualcomm inc. Nokia, Nokia Shanghai Bell, ZTE | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑257013 | |
| R3‑258531 | Addition of 2Rx XR UE Capability | Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, ZTE | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑257014 | |
| R3‑258532 | NRPPa Rapporteur Corrections | Rapporteur (Ericsson) | CR | Agreement |
9.3R19 Rapporteur Corrections
| Yes |
Yes
| revised | No | R3‑258721 | |
| R3‑258533 | Discussion on RAN-CN procedures and signaling to support ISAC with TP to pCR | Ericsson | other | Agreement |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | ||
| R3‑258534 | Correction on Paging Loss issue | Ericsson | draftCR | Endorsement |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258752 | |
| R3‑258535 | Correction on Paging Loss issue | Ericsson | draftCR | Endorsement |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258753 | |
| R3‑258536 | Correction on Paging Loss issue | Ericsson | draftCR | Endorsement |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258754 | |
| R3‑258537 | [DRAFT] Reply LS on Response to Reply LS on paging capability loss issue | Ericsson | LS out | Agreement |
9.2.14Other
| Yes |
No
| available | No | ||
| R3‑258538 | On Restriction of PEIPS during emergency PDU session | Ericsson | discussion | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258539 | Correction on PEIPS | Ericsson | CR | Agreement |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258540 | Correction on PEIPS | Ericsson | CR | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑258541 | Correction on PEIPS | Ericsson | CR | Agreement |
8.1New Incoming LSs
| Yes |
No
| available | No | ||
| R3‑258542 | Rapporteur Rel-19 Corrections | Ericsson | CR | Agreement |
9.3R19 Rapporteur Corrections
| Yes |
Yes
| revised | No | R3‑258722 | |
| R3‑258543 | On General Principles and Requirements for the 6G RAN-CN interface | Ericsson | discussion | Agreement |
10.3.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258544 | [pCR for TR 38.760-3] Definitions and Requirements for the 6G RAN-CN interface | Ericsson | pCR | Agreement |
10.3.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258545 | Topology 2 - Continuing on starting points for discussions | Ericsson | discussion | Agreement |
14.2Topology 2
| Yes |
No
| available | No | ||
| R3‑258546 | Abnormal conditions for gNB-CU Configuration Update with updated Presence IE | Ericsson, Jio Platforms, InterDigital, Fibercop | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| noted | No | ||
| R3‑258547 | Correction for gNB-DU Configuration Update | Ericsson, Jio Platforms, InterDigital, Fibercop | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | ||
| R3‑258548 | Stage 2 corrections for AI/ML based CCO | Ericsson, Jio Platforms, InterDigital, Fibercop | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | ||
| R3‑258549 | Corrections on SBFD support | Ericsson | CR | Agreement |
9.2.10R19 Evolution of Duplex Operation
| Yes |
Yes
| noted | No | ||
| R3‑258550 | Considerations for 6G Higher Layer Split Architecture | BT plc | discussion |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | |||
| R3‑258551 | PRACH resources for Inter-CU LTM | Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | R3‑257043 | |
| R3‑258552 | PRACH resources for Inter-CU LTM | Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | R3‑257044 | |
| R3‑258553 | PRACH resource for Inter-CU LTM | Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | R3‑257045 | |
| R3‑258554 | PRACH resources for Inter-CU LTM | Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno | draftCR | Endorsement |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | R3‑257046 | |
| R3‑258555 | PRACH resources for Inter-CU LTM | Ericsson, Jio Platforms, Lenovo, Verizon Wireless, NTT DOCOMO, Ofinno | discussion |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | R3‑257042 | ||
| R3‑258556 | Fast LTM recovery for Inter-CU LTM | Ericsson, Jio Platforms, Lenovo, Ofinno | discussion |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | R3‑257047 | ||
| R3‑258557 | Fast LTM Recovery for Inter-CU LTM | Ericsson, Jio Platforms, Lenovo, Ofinno | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | R3‑257048 | |
| R3‑258558 | Support for Modification of LTM Configurations | Ericsson, Ofinno, Jio Platforms | discussion |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| noted | No | |||
| R3‑258559 | Support for Modification of LTM Configurations | Ericsson, Ofinno, Jio Platforms | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| noted | No | ||
| R3‑258560 | Removal of Request for CSI-RS resource configuration for Early CSI acquisition | Ericsson, Jio Platforms, Verizon Wireless, LG Electronics, ZTE | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | R3‑257173 | |
| R3‑258561 | Removal of Request for CSI-RS resource configuration for Early CSI acquisition | Ericsson, Jio Platforms, Verizon Wireless, LG Electronics, ZTE | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | R3‑257174 | |
| R3‑258562 | Correction for Cell Switch execution | Ericsson, Sony, Jio Platforms, LG Electronics, vivo, Qualcomm | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑257028 | |
| R3‑258563 | Correction for Cell Switch execution | Ericsson, Sony, Jio Platforms, LG Electronics, vivo, Qualcomm | CR | Agreement |
9.2.14Other
| Yes |
No
| available | No | R3‑257029 | |
| R3‑258564 | Data Framework Considerations for 6G | AT&T | discussion | Decision |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | ||
| R3‑258565 | 6G RAN internal functional split for NTN | THALES, ESA, EchoStar, Lockheed Martin, Novamint | discussion | Discussion |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258566 | Rapporteur's editorial corrections for E1AP | Ericsson | CR | Agreement |
9.3R19 Rapporteur Corrections
| Yes |
Yes
| noted | No | R3‑257120 | |
| R3‑258567 | General Principles and Requirements for the 6G RAN architecture | Ericsson, Jio Platforms | pCR | Agreement |
10.2.1General principles and requirements
| Yes |
Yes
| revised | No | R3‑258749 | |
| R3‑258568 | Functions and Architecture for the 6G RAN | Ericsson | pCR | Agreement |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | ||
| R3‑258569 | Discussion on 6G RAN logical architecture and 6G RAN function | Samsung | pCR | Agreement |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | ||
| R3‑258570 | Correction of BH-gNB for WAB | China Telecom,CATT, Nokia, Nokia Shanghai Bell, ZTE | draftCR | Endorsement |
9.2.3R19 WAB
| Yes |
Yes
| noted | No | ||
| R3‑258571 | Correction of BH-gNB and WAB-MT for WAB | China Telecom, CATT, Nokia, Nokia Shanghai Bell, Huawei, ZTE | CR | Agreement |
9.2.3R19 WAB
| Yes |
Yes
| revised | No | R3‑258772 | |
| R3‑258572 | Discussion on Principles and Requirements for 6G RAN-CN Interface | China Telecom | discussion | Discussion |
10.3.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258573 | Insights from a commercial deployment of multi-vendor standardized F1 interface | Rakuten Mobile, Inc, Samsung, NTT DOCOMO, Verizon, Qualcomm, Fibercop | discussion |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | |||
| R3‑258574 | Finalizing the compatibility issue for PEI and emergency PDU session | Huawei | discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | |||
| R3‑258575 | PEI usage in case of emergency PDU session | Huawei | draftCR |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | |||
| R3‑258576 | PEI usage in case of emergency PDU session | Huawei | draftCR |
8.1New Incoming LSs
| Yes |
No
| available | No | |||
| R3‑258577 | PEI usage in case of emergency PDU session | Huawei | draftCR |
8.1New Incoming LSs
| Yes |
No
| available | No | |||
| R3‑258578 | Workplan for Rel-20 SON_MDT Enhancement | China Unicom | Work Plan |
11.1General
| Yes |
Yes
| noted | No | |||
| R3‑258579 | Discussion on MRO enhancements for inter-CU LTM | China Unicom | discussion |
11.2.1Inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑258580 | Discussion on MRO enhancements for C-LTM | China Unicom | discussion |
11.2.2Intra-CU conditional LTM
| Yes |
No
| available | No | |||
| R3‑258581 | Considerations on 6G RAN-CN Interface | KDDI Corporation | discussion |
10.3.1General principles and requirements
| Yes |
No
| available | No | |||
| R3‑258582 | Correction on NG-RAN node UE XnAP IDs transfer after LTM failure | Huawei, Nokia, Offinno, Jio Platforms, CMCC | CR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258583 | UE context retrieval in the candidate gNB during subsequent LTM | Huawei, Nokia, Offinno, NTT Docomo, Jio Platforms, CMCC, Lenovo | CR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258584 | Corrections on inter-CU MCG LTM without SN change | Huawei, Jio Platforms, Lenovo, Google | discussion |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258585 | Stage 2 corrections to inter-CU MCG LTM | Huawei, Jio Platforms, Lenovo, Google | draftCR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258586 | Correction on security key update for inter-CU MCG LTM | Huawei, Jio Platforms, China Telecom, Lenovo, Google | CR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258587 | Discussion on candidate gNB initiated LTM modification (CRs included) | Huawei | discussion |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| noted | No | |||
| R3‑258588 | Candidate gNB-DU initiated LTM modification | Huawei | CR |
9.2.5R19 Mobility enhancements
| No |
Yes
| withdrawn | Yes | |||
| R3‑258589 | [Draft]LS on candidate gNB initiated LTM modification | Huawei | LS out | Approval |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | ||
| R3‑258590 | Stage 2 corrections on inter-CU LTM | Huawei | draftCR |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | |||
| R3‑258591 | Discussions on the architecture design of ISAC | China Unicom | discussion |
13.2Network architecture
| Yes |
No
| available | No | |||
| R3‑258592 | Standard impacts of RAN-CN procedures for ISAC | China Unicom | discussion |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | |||
| R3‑258593 | Discussion on general principles of RAN-CN interface | Samsung | other | Agreement |
10.3.1General principles and requirements
| No |
Yes
| withdrawn | Yes | ||
| R3‑258594 | [DRAFT] Reply LS on geographical area scope MDT | Samsung | LS out | Agreement |
9.2.1R19 SON/MDT
| Yes |
No
| available | No | ||
| R3‑258595 | Discussion on the encoding of AIOTF identifier | Samsung, Huawei, CMCC | discussion | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| noted | No | ||
| R3‑258596 | Correction to the encoding of AIOTF Identifier IE | Samsung, Huawei, CMCC | CR | Agreement |
9.2.7R19 Ambient IoT
| Yes |
No
| available | No | ||
| R3‑258597 | Discussion on MRO enhancement on inter-CU LTM | Samsung | discussion | Agreement |
11.2.1Inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑258598 | (TP for SON BLCR to TS 38.401 and TS 38.300) Discussion on MRO enhancement on intra-CU conditional LTM | Samsung | other | Agreement |
11.2.2Intra-CU conditional LTM
| Yes |
No
| available | No | ||
| R3‑258599 | Discussion on Topology 2 for AIoT | Samsung | discussion | Agreement |
14.2Topology 2
| Yes |
No
| available | No | ||
| R3‑258600 | (pCR to TR 38.745) Discussion on AI/ML based Multi-hop UE trajectory across gNBs | CMCC | pCR | Approval |
12.2.1Multi-hop UE trajectory across gNBs
| Yes |
No
| available | No | ||
| R3‑258601 | Discussion on AI/ML based handover enhancement | CMCC | discussion | Discussion |
12.2.3Handover enhancements
| Yes |
No
| available | No | ||
| R3‑258602 | Discussion on 6G AIML use cases | CMCC | discussion | Discussion |
10.5.1AI/ML use cases
| Yes |
No
| available | No | ||
| R3‑258603 | (TP for TS 38.300 BL CR) Discussion on Topology 2 for A-IoT | CMCC | other | Discussion |
14.2Topology 2
| Yes |
No
| available | No | ||
| R3‑258604 | Correction on CCO in split architecture for 38.401 | CMCC | CR | Approval |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | ||
| R3‑258605 | Correction on R19 AIML F1-U stage2 | CMCC, Samsung, Qualcomm, ZTE, CATT, Nokia | CR | Approval |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | ||
| R3‑258606 | Correction to support Continuous MDT through Xn interface | CMCC | CR | Approval |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | ||
| R3‑258607 | Correction on Evolution of NR duplex operation for 38.420 | CMCC, CATT | CR | Approval |
9.2.10R19 Evolution of Duplex Operation
| Yes |
No
| available | No | ||
| R3‑258608 | Discussion on 6G RAN internal functional split and interfaces | CMCC | discussion | Discussion |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258609 | Discussion on AIML based intra CU LTM use cases | CMCC | discussion | Discussion |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | ||
| R3‑258610 | Discussion on general principles and requirements for RAN-CN interface | CMCC | discussion | Discussion |
10.3.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258611 | Discussion on RAN-CN interface options | CMCC | discussion | Discussion |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | ||
| R3‑258612 | Discussion on Network Architecture for ISAC | CMCC | discussion | Discussion |
13.2Network architecture
| Yes |
No
| available | No | ||
| R3‑258613 | Discussion on RAN-CN Procedures Supporting ISAC | CMCC | discussion | Discussion |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | ||
| R3‑258614 | Correction on support for on-demand SIB1 | CMCC, Huawei | CR | Approval |
9.2.8R19 Network Energy Saving
| Yes |
No
| available | No | ||
| R3‑258615 | Corrections on uplink rate control | CMCC | CR | Agreement |
9.2.12R19 NR XR Enhancements
| Yes |
Yes
| noted | No | ||
| R3‑258616 | Discussion on the principle for 6G RAN architecture | CMCC | discussion | Discussion |
10.2.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258617 | (pCR to TR 38.760-3) Consideration on RAN data collection function for 6G | CMCC, NTT DOCOMO, FiberCop, T-Mobile USA | pCR | Approval |
10.2.2RAN functions and logical architecture
| Yes |
Yes
| noted | No | ||
| R3‑258618 | Discussion on MRO enhancements for inter-CU LTM | CMCC | discussion | Discussion |
11.2.1Inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑258619 | Correction on A-IoT security aspects | CMCC, Huawei | draftCR | Approval |
9.2.7R19 Ambient IoT
| Yes |
No
| available | No | ||
| R3‑258620 | Correction on A-IoT security aspects | CMCC, Huawei | CR | Approval |
9.2.7R19 Ambient IoT
| Yes |
No
| available | No | ||
| R3‑258621 | Discussion on general principles of RAN-CN interface | Samsung | pCR | Agreement |
10.3.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258622 | Correction to XnAP on CLI Indication | ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei | CR | Approval |
9.2.10R19 Evolution of Duplex Operation
| No |
Yes
| withdrawn | Yes | ||
| R3‑258623 | Correction to F1AP on CLI Indication | ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei | CR | Approval |
9.2.10R19 Evolution of Duplex Operation
| No |
Yes
| withdrawn | Yes | ||
| R3‑258624 | Correction to F1AP on SBFD RACH configuration | ZTE Corporation | CR | Approval |
9.2.10R19 Evolution of Duplex Operation
| No |
Yes
| withdrawn | Yes | ||
| R3‑258625 | Correction on semantic description for Notification Cause IE in NGAP | ZTE Corporation | CR | Approval |
9.2.12R19 NR XR Enhancements
| No |
Yes
| withdrawn | Yes | ||
| R3‑258626 | Correction on stage 3 description on Indication of Bitrate Adaptation IE in NGAP | ZTE Corporation, Nokia, Nokia Shanghai Bell,CATT, Qualcomm, Huawei, Ericsson, | CR | Approval |
9.2.12R19 NR XR Enhancements
| No |
Yes
| withdrawn | Yes | ||
| R3‑258627 | Discussion on UL Rate Control on XR with the correction and draft LS | ZTE Corporation | discussion | Approval |
9.2.12R19 NR XR Enhancements
| No |
Yes
| withdrawn | Yes | ||
| R3‑258628 | Discussion on average window for alternative QoS | ZTE Corporation | discussion | Approval |
8.1New Incoming LSs
| No |
Yes
| withdrawn | Yes | ||
| R3‑258629 | Considerations on 6G RAN internal functional split | LG Electronics Inc. | discussion | Decision |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | ||
| R3‑258630 | (TP to BL pCR to TR 38.765) Discussions for ISAC network architecture | LG Electronics Inc. | other | Approval |
13.2Network architecture
| Yes |
No
| available | No | ||
| R3‑258631 | (TP to BL pCR to TR 38.765) Discussions for ISAC RAN-CN aspects | LG Electronics Inc. | other | Approval |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | ||
| R3‑258632 | Correction on A-IoT Paging related information | ZTE Corporation, | CR | Approval |
9.2.7R19 Ambient IoT
| Yes |
Yes
| noted | No | ||
| R3‑258633 | Correction on AIoT Reader Report List | ZTE Corporation | CR | Approval |
9.2.7R19 Ambient IoT
| Yes |
Yes
| merged | No | ||
| R3‑258634 | Discussion on R20 A-IoT for Topology 2 | ZTE Corporation | discussion | Approval |
14.2Topology 2
| Yes |
No
| available | No | ||
| R3‑258635 | Correction to XnAP on CLI Indication | ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei | CR | Approval |
9.2.10R19 Evolution of Duplex Operation
| Yes |
Yes
| revised | No | R3‑258788 | R3‑257162 |
| R3‑258636 | Correction to F1AP on CLI Indication | ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei | CR | Approval |
9.2.10R19 Evolution of Duplex Operation
| Yes |
Yes
| revised | No | R3‑258789 | R3‑257163 |
| R3‑258637 | Discussion on CLI Indication message structure | ZTE Corporation, Pengcheng Laboratory | discussion | Approval |
9.2.10R19 Evolution of Duplex Operation
| Yes |
Yes
| noted | No | ||
| R3‑258638 | Consideration on 6G RAN-CN interface options | ZTE Corporation | other | Approval |
10.3.2RAN-CN interface options
| Yes |
Yes
| revised | No | R3‑258801 | |
| R3‑258639 | Clarification to UE-to-UE CLI mitigation in SBFD operation | Huawei, CATT, China Unicom | draftCR | Approval |
9.2.10R19 Evolution of Duplex Operation
| Yes |
No
| available | No | ||
| R3‑258640 | Clarification to CLI mitigation in SBFD operation | Huawei | CR | Approval |
9.2.10R19 Evolution of Duplex Operation
| Yes |
No
| available | No | R3‑257177 | |
| R3‑258641 | Further discussions on general requirement and principles for RAN architecture | Huawei | other | Decision |
10.2.1General principles and requirements
| Yes |
Yes
| revised | No | R3‑258748 | |
| R3‑258642 | Further discussions on RAN functions and logical architecture | Huawei | other | Decision |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | ||
| R3‑258643 | Discussion on 6G RAN functional split | Samsung, Verizon, NTT DoCoMo, Rakuten, Qualcomm, China Unicom, FiberCop, Jio Platforms, NEC, Google, T-Mobile USA, Fujitsu, Thales, Mavenir, Boost Mobile, Tejas Networks, Charter, Sony, CATT, Lenovo | pCR |
10.4RAN internal functional split and interfaces
| Yes |
No
| available | No | |||
| R3‑258644 | Discussion on paging in Store and Forward | ZTE Corporation | discussion | Discussion |
9.1.1R19 IoT NTN enhancements
| Yes |
Yes
| noted | No | ||
| R3‑258645 | Correction on MRO for S-CPAC and CHO with candidate SCG for 37.340 | CATT, Samsung | draftCR | Endorsement |
9.2.1R19 SON/MDT
| Yes |
Yes
| revised | No | R3‑258709 | |
| R3‑258646 | Correction on Evolution of NR duplex operation for 38.470 | CATT | CR | Approval |
9.2.10R19 Evolution of Duplex Operation
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑258647 | Correction on SBFD RACH configuration for F1AP | CATT | CR | Approval |
9.2.10R19 Evolution of Duplex Operation
| Yes |
Yes
| noted | No | ||
| R3‑258648 | Discussion on SON enhancement for inter-CU LTM | CATT | discussion | Decision |
11.2.1Inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑258649 | (TP for 38.300) Discussion on SON enhancement for conditional intra-CU LTM | CATT | other | Decision |
11.2.2Intra-CU conditional LTM
| Yes |
No
| available | No | ||
| R3‑258650 | Discussion on reply LS on geographical area scope MDT | CATT | discussion | Decision |
9.2.1R19 SON/MDT
| Yes |
Yes
| noted | No | ||
| R3‑258651 | Reply LS on geographical area scope MDT | CATT | LS out | Approval |
9.2.1R19 SON/MDT
| Yes |
Yes
| revised | No | R3‑258710 | |
| R3‑258652 | Discussion on RAN architecture principle and requirement | Samsung | pCR | Agreement |
10.2.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258653 | Discussion on other AI/ML use cases to be considered | LG Electronics Inc. | discussion |
10.5.1AI/ML use cases
| Yes |
No
| available | No | |||
| R3‑258654 | Discussion on open issues in multi-hop UE trajectory across gNBs use case | LG Electronics Inc. | discussion |
12.2.1Multi-hop UE trajectory across gNBs
| Yes |
No
| available | No | |||
| R3‑258655 | Discussion on open issues for intra-CU LTM use case | LG Electronics Inc. | pCR |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | |||
| R3‑258656 | 6G AI/ML Use Case | Ofinno | pCR | Decision |
10.5.1AI/ML use cases
| Yes |
No
| available | No | ||
| R3‑258657 | Discussion on AI/ML use cases for 6G | Samsung | pCR | Agreement |
10.5.1AI/ML use cases
| Yes |
No
| available | No | ||
| R3‑258658 | Clarification for propagation of roaming and access restrictions | Samsung | draftCR | Endorsement |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258726 | |
| R3‑258659 | Corrections on last target NG-RAN node UE XnAP ID transfer | ZTE Corporation, CATT, Huawei | CR | Approval |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | ||
| R3‑258660 | Discussion on remaining issues on early sync | ZTE Corporation | discussion | Decision |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | ||
| R3‑258661 | Corrections on Early RACH Resource Requester ID | ZTE Corporation | CR | Approval |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| noted | No | ||
| R3‑258662 | Corrections on Early RACH Resource Requester ID | ZTE Corporation | CR | Approval |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | ||
| R3‑258663 | Corrections on LTM Early Sync resource update | ZTE Corporation | CR | Approval |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | ||
| R3‑258664 | Corrections on LTM Early Sync resource update | ZTE Corporation | CR | Approval |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | ||
| R3‑258665 | Remaining Issues on Inter-CU LTM | Samsung | discussion | Discussion |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| noted | No | ||
| R3‑258666 | XnAP correction on the Inter-CU LTM procedure | Samsung | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| revised | No | R3‑258775 | |
| R3‑258667 | Correction on TA Information Transfer for inter-CU SCG LTM | Samsung, Huawei, Ericsson, Nokia, Google | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
No
| available | No | ||
| R3‑258668 | Correction on Early UL Sync Configuration IE for inter-CU LTM | Samsung, Huawei, Ericsson, Nokia, China Telecom, Google | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| revised | No | R3‑258776 | |
| R3‑258669 | Correction on the LTM Indicator for C-LTM | Samsung, Huawei, Ericsson, LG Electronics, Nokia, China Telecom, Google | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| revised | No | R3‑258777 | |
| R3‑258670 | R18 correction (SSB) on the CU-DU Mobility Initiation Request message | Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC | CR | Agreement |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258728 | R3‑256859 |
| R3‑258671 | R18 correction (SSB) on the CU-DU Mobility Initiation Request message | Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC | CR | Agreement |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258729 | R3‑256860 |
| R3‑258672 | R19 correction (CSI-RS) on the CU-DU Mobility Initiation Request message | Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC | CR | Agreement |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| agreed | No | ||
| R3‑258673 | Correction of missing stage 2 description of LTM MRO without RLF Report | ZTE Corporation, Google, NEC | CR | Agreement |
9.2.1R19 SON/MDT
| Yes |
Yes
| noted | No | ||
| R3‑258674 | Clarification for propagation of MDT Configuration in stage2 | ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei | other |
9.2.14Other
| Yes |
Yes
| revised | No | R3‑258727 | R3‑256527 | |
| R3‑258675 | Clarify on UE context retrieval | ZTE Corporation | discussion |
9.2.14Other
| Yes |
Yes
| noted | No | |||
| R3‑258676 | Correction on UHI | ZTE Corporation,China Telecom, Pengcheng Laboratory | CR |
9.2.14Other
| Yes |
No
| available | No | R3‑256753 | ||
| R3‑258677 | Correction on UHI | ZTE Corporation,China Telecom, Pengcheng Laboratory | CR |
9.2.14Other
| Yes |
No
| available | No | R3‑256754 | ||
| R3‑258678 | General principles and requirements | ZTE Corporation | pCR |
10.2.1General principles and requirements
| Yes |
Yes
| revised | No | R3‑258746 | ||
| R3‑258679 | Consideration on MRO for inter CU LTM | ZTE Corporation | discussion |
11.2.1Inter-CU LTM
| Yes |
No
| available | No | |||
| R3‑258680 | Consideration on MRO for CLTM | ZTE Corporation | discussion |
11.2.2Intra-CU conditional LTM
| Yes |
No
| available | No | |||
| R3‑258681 | Discussion on RAN-CN interface | Rakuten Mobile, Inc | discussion |
10.3.2RAN-CN interface options
| Yes |
No
| available | No | |||
| R3‑258682 | Discussion paper on ISAC network architecuture | CEWiT | discussion |
13.2Network architecture
| Yes |
No
| available | No | |||
| R3‑258683 | Discussion paper on ISAC procedures and signaling | CEWiT | discussion |
13.3RAN-CN procedures and signaling
| Yes |
No
| available | No | |||
| R3‑258684 | Discussion on AI/ML use cases for 6G Network | CEWiT | discussion |
10.5.1AI/ML use cases
| Yes |
No
| available | No | |||
| R3‑258685 | Support for Continuous Management-based MDT in split architecture | Samsung, CATT, ZTE, CMCC, China Telecom, Huawei, Ericsson, FiberCop, Deutsche Telekom, China Unicom, NEC | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| noted | No | R3‑256690 | |
| R3‑258686 | Discussion on the open issues regarding L1 UE-to-UE CLI configuration | Samsung, Qualcomm, Charter | discussion | Agreement |
9.2.10R19 Evolution of Duplex Operation
| Yes |
No
| available | No | ||
| R3‑258687 | Correction on the indication of L1 UE-to-UE CLI | Samsung, Qualcomm, Charter | CR | Agreement |
9.2.10R19 Evolution of Duplex Operation
| Yes |
No
| available | No | R3‑256692 | |
| R3‑258688 | Further discussion on Multi-hop UE trajectory across gNBs | Samsung | discussion | Agreement |
12.2.1Multi-hop UE trajectory across gNBs
| Yes |
No
| available | No | ||
| R3‑258689 | Discussion on AI-based intra-CU LTM | Samsung | discussion | Agreement |
12.2.2Intra-CU LTM
| Yes |
No
| available | No | ||
| R3‑258690 | Discussion on other handover enhancement | Samsung | discussion | Agreement |
12.2.3Handover enhancements
| Yes |
No
| available | No | ||
| R3‑258691 | Correction to A-IoT specific cause values | CATT | CR | Approval |
9.2.7R19 Ambient IoT
| Yes |
No
| available | No | ||
| R3‑258692 | Connection of Secondary RAT Data Usage Report for NG based handover | Huawei, China Unicom, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | R3‑257182 | ||
| R3‑258693 | Connection of Secondary RAT Data Usage Report for Xn based handover | Huawei, China Unicom, China Telecom | CR |
9.2.14Other
| Yes |
No
| available | No | R3‑257183 | ||
| R3‑258694 | Considerations on RAN Sharing requirements of RAN Architecture | China Unicom | discussion | Decision |
10.2.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258695 | Support for Modification of LTM Configurations | Ericsson, Jio Platforms, Ofinno | draftCR | Endorsement |
9.2.5R19 Mobility enhancements
| Yes |
Yes
| noted | No | ||
| R3‑258696 | Discussion on AI/ML use cases for 6G | AUMOVIO | discussion | Decision |
10.5.1AI/ML use cases
| Yes |
No
| available | No | ||
| R3‑258697 | Considerations on new 6G AI/ML Use Cases for RAN | China Unicom | discussion | Decision |
10.5.1AI/ML use cases
| Yes |
No
| available | No | ||
| R3‑258698 | Response to R3-258173 | ZTE Corporation | response |
9.2.2R19 AI/ML for NG-RAN
| Yes |
No
| available | No | |||
| R3‑258699 | LS on DTLS for SCTP Progress Report | IETF Transport and Services WG(TSVWG)(Huawei) | LS in | Discussion |
8.1New Incoming LSs
| Yes |
Yes
| noted | No | ||
| R3‑258700 | Response to R3-258480 | Ericsson | response |
9.2.11R19 AI/ML for air interface
| Yes |
No
| available | No | |||
| R3‑258701 | Response to R3-258486 | Huawei | response | Discussion |
9.2.14Other
| Yes |
Yes
| noted | No | ||
| R3‑258702 | Response to R3-258140, R3-258641, R3-258652 | OPPO | response | Discussion |
10.2.1General principles and requirements
| Yes |
No
| available | No | ||
| R3‑258703 | Response to R3-258173 | Ericsson | response | Agreement |
9.2.2R19 AI/ML for NG-RAN
| Yes |
Yes
| withdrawn | Yes | ||
| R3‑258704 | Correction on the OAM requirements for NTN | Nokia, Nokia Shanghai Bell, Qualcomm, LG Electronics, ZTE, CATT, Ericsson, Huawei, Samsung | draftCR | Endorsement |
9.1.1R19 IoT NTN enhancements
| Yes |
Yes
| endorsed | No | R3‑258199 | |
| R3‑258705 | Correction on LTE-based 5G Broadcast | Huawei, EBU, Qualcomm Incorporated, ZTE | CR | Agreement |
9.1.2R19 LTE-based 5G Broadcast
| Yes |
Yes
| revised | No | R3‑258742 | R3‑258127 |
| R3‑258706 | Corrections for Femto | ZTE Corporation, Nokia, LG Electronics | CR | Agreement |
9.4Endorsed CRs Review
| No |
No
| reserved | No | R3‑258041 | |
| R3‑258707 | BFR in CSI-RS beam | Ericsson | CR | Agreement |
9.2.1R19 SON/MDT
| No |
No
| reserved | No | R3‑258516 | |
| R3‑258708 | Correction on MRO for SCG failure in EN-DC | ZTE Corporation, China Telecom, Pengcheng Laboratory | draftCR | Endorsement |
9.2.1R19 SON/MDT
| No |
No
| reserved | No | R3‑258149 | |
| R3‑258709 | Correction on MRO for S-CPAC and CHO with candidate SCG for 37.340 | CATT, Samsung | draftCR | Endorsement |
9.2.1R19 SON/MDT
| No |
No
| reserved | No | R3‑258645 | |
| R3‑258710 | Reply LS on geographical area scope MDT | RAN3(CATT) | LS out | Approval |
9.2.1R19 SON/MDT
| No |
No
| reserved | No | R3‑258651 | |
| R3‑258711 | Miscellaneous corrections to E1AP for support of AI/ML NG-RAN | ZTE Corporation, CATT, China Unicom, China Telecom | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| No |
No
| reserved | No | R3‑258214 | |
| R3‑258712 | Correction on sending GW release indication | CATT | draftCR | Approval |
9.2.4R19 NR Femto
| No |
No
| reserved | No | R3‑258300 | |
| R3‑258713 | Essential correction on inter-CU LTM in DC | CATT,Huawei, China Telecom, Nokia, Samsung, NEC, Ericsson | CR | Agreement |
9.2.5R19 Mobility enhancements
| No |
Yes
| agreed | No | R3‑258390 | |
| R3‑258714 | Correction to E1AP for UE performance metrics | CMCC, ZTE, Huawei, Ericsson, Nokia, CATT | CR | Agreement |
9.4Endorsed CRs Review
| No |
No
| reserved | No | R3‑258031 | |
| R3‑258715 | Semi-Persistent CSI-RS activation with TCI state | Nokia, CATT, China Telecom, Ericsson, Huawei, NEC, ZTE, Google, Samsung, LG Electronics, Qualcomm, Ofinno, Lenovo, Jio Platforms | CR | Agreement |
9.4Endorsed CRs Review
| No |
No
| reserved | No | R3‑258047 | |
| R3‑258716 | Corrections to Xn support for on-demand SIB1 coordination | Ericsson, Qualcomm, Jio Platforms , ZTE, Deutsche Telekom, Huawei, Samsung, NEC, Rakuten, Nokia, CATT, Telecom Italia | CR | Agreement |
9.4Endorsed CRs Review
| No |
No
| reserved | No | R3‑258054 | |
| R3‑258717 | Correction to TS 37.483 for XR | Samsung | CR | Agreement |
9.4Endorsed CRs Review
| No |
No
| reserved | No | R3‑258065 | |
| R3‑258718 | Rapporteur correction of TS 38.410 | Nokia | CR | Agreement |
9.3R19 Rapporteur Corrections
| No |
No
| reserved | No | R3‑258404 | |
| R3‑258719 | Rapporteur correction of TS 38.415 | Nokia | CR | Agreement |
9.3R19 Rapporteur Corrections
| No |
No
| reserved | No | R3‑258405 | |
| R3‑258720 | X2AP rapporteur corrections | Ericsson | CR | - |
9.3R19 Rapporteur Corrections
| Yes |
No
| available | No | R3‑258492 | |
| R3‑258721 | NRPPa Rapporteur Corrections | Rapporteur (Ericsson) | CR | Agreement |
9.3R19 Rapporteur Corrections
| Yes |
No
| available | No | R3‑258532 | |
| R3‑258722 | Rapporteur Rel-19 Corrections | Ericsson | CR | Agreement |
9.3R19 Rapporteur Corrections
| No |
No
| reserved | No | R3‑258542 | |
| R3‑258723 | Reply LS on paging capability loss issue | RAN3(Huawei) | LS out | Approval |
9.2.14Other
| No |
No
| reserved | No | R3‑258349 | |
| R3‑258724 | Additional procedure text for Data Collection Update | ZTE Corporation, Ercisson, Samsung, NEC, Nokia, Huawei, CATT, Jio Platforms, Qualcomm, FiberCop, Orange | CR | Agreement |
9.2.14Other
| Yes |
Yes
| agreed | No | R3‑258106 | |
| R3‑258725 | Correction on the description of UE Context Information – Retrieve UE Context Response | ZTE Corporation, Nokia, Huawei, CATT, Samsung | CR | Agreement |
9.2.14Other
| Yes |
Yes
| agreed | No | R3‑258299 | |
| R3‑258726 | Clarification for propagation of roaming and access restrictions | Samsung | draftCR | Endorsement |
9.2.14Other
| No |
Yes
| endorsed | No | R3‑258658 | |
| R3‑258727 | Clarification for propagation of MDT Configuration in stage2 | ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei | draftCR | Endorsement |
9.2.14Other
| No |
No
| reserved | No | R3‑258674 | |
| R3‑258728 | Correction (SSB) on the CU-DU Mobility Initiation Request message | Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC | CR | Agreement |
9.2.14Other
| Yes |
Yes
| agreed | No | R3‑258670 | |
| R3‑258729 | Correction (SSB) on the CU-DU Mobility Initiation Request message | Samsung, Nokia, China Telecom, Jio Platforms, LG Electronics, Ericsson, Qualcomm, Huawei, Lenovo, CATT, ZTE Corporation, Google, NEC | CR | Agreement |
9.2.14Other
| Yes |
Yes
| agreed | No | R3‑258671 | |
| R3‑258730 | SoD of MRO for inter-CU LTM | Ericsson | discussion | discussion |
11.2.1Inter-CU LTM
| Yes |
No
| available | No | ||
| R3‑258731 | SoD of MRO for CLTM | Samsung | discussion | discussion |
11.2.2Intra-CU conditional LTM
| Yes |
No
| available | No | ||
| R3‑258732 | Correction on A-IoT dedicated Cause values | Huawei, CMCC, Futurewei, Lenovo, China Unicom, China Telecom, Nokia, Ericsson, CATT, NEC, Xiaomi, Samsung, ZTE | CR | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| agreed | No | R3‑258122 | |
| R3‑258733 | Correction on A-IoT related Network Identities | Huawei, Nokia, Ericsson, CMCC, China Unicom, China Telecom | draftCR | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| endorsed | No | R3‑258123 | |
| R3‑258734 | Resilient 6G RAN Architecture | Nokia, Jio Platforms, NTT DoCoMo, T-Mobile USA Inc. | pCR | Approval |
10.2.2RAN functions and logical architecture
| Yes |
No
| available | No | R3‑258168 | |
| R3‑258735 | Correction on the presence of Reader Report List | Huawei, CMCC, China Unicom, China Telecom, CATT, ZTE, Samsung, Nokia, Xiaomi | CR | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| agreed | No | R3‑258125 | |
| R3‑258736 | Correction on A-IoT Inventory and Command procedure figures | NEC | draftCR | Agreement |
9.2.7R19 Ambient IoT
| Yes |
Yes
| endorsed | No | R3‑258240 | |
| R3‑258737 | Correcting the extension of FR1-bandwidth type definition | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement |
9.2.14Other
| No |
No
| reserved | No | R3‑258487 | |
| R3‑258738 | Correcting the extension of FR1-bandwidth type definition | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement |
9.2.14Other
| No |
No
| reserved | No | R3‑258488 | |
| R3‑258739 | Correcting the IE extension definition for bandwidth SRS | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement |
9.2.14Other
| No |
No
| reserved | No | R3‑258489 | |
| R3‑258740 | Correcting the IE extension definition for bandwidth SRS | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement |
9.2.14Other
| No |
No
| reserved | No | R3‑258490 | |
| R3‑258741 | Correcting the IE extension definition for SRS Pos SIB Type | Ericsson, Jio Platforms, China Telecom, CMCC, Nokia | CR | Agreement |
9.2.14Other
| No |
No
| reserved | No | R3‑258491 | |
| R3‑258742 | Correction on LTE-based 5G Broadcast | Huawei, EBU, Qualcomm Incorporated, ZTE | CR | Agreement |
9.1.2R19 LTE-based 5G Broadcast
| Yes |
Yes
| agreed | No | R3‑258705 | |
| R3‑258743 | Corrections to F1 support of Network Energy Saving Enhancement | Ericsson, China Telecom, Jio Platforms, Lenovo, Rakuten | CR | Approval |
9.2.8R19 Network Energy Saving
| Yes |
Yes
| revised | No | R3‑258807 | R3‑258503 |
| R3‑258744 | Correction on A-IoT leftovers on IE details | Huawei, CMCC, China Unicom, China Telecom, Nokia, LG Electronics, CATT, NEC | CR | Agreement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑258051 | |
| R3‑258745 | Discussion on general principles and requirements for 6G RAN | CATT | pCR | Decision |
10.2.1General principles and requirements
| No |
No
| reserved | No | R3‑258444 | |
| R3‑258746 | General principles and requirements | ZTE Corporation | pCR | - |
10.2.1General principles and requirements
| No |
No
| reserved | No | R3‑258678 | |
| R3‑258747 | Requirements for 6G RAN architecture design | FiberCop, CEWiT, Fujitsu, Jio Platform, KT Corp., Qualcomm Inc., Rakuten, Teja Networks, TIM-Telecom Italia,T-Mobile USA, Verizon Wireless | pCR | Agreement |
10.2.1General principles and requirements
| No |
No
| reserved | No | R3‑258232 | |
| R3‑258748 | Further discussions on general requirement and principles for RAN architecture | Huawei | pCR | Decision |
10.2.1General principles and requirements
| No |
Yes
| agreed | No | R3‑258641 | |
| R3‑258749 | General Principles and Requirements for the 6G RAN architecture | Ericsson, Jio Platforms | pCR | Agreement |
10.2.1General principles and requirements
| No |
Yes
| agreed | No | R3‑258567 | |
| R3‑258750 | Correction to positioning activation and deactivation procedure | Samsung, CATT, ZTE Corporation, Huawei, China Telecom, Xiaomi | CR | Agreement |
9.4Endorsed CRs Review
| No |
No
| reserved | No | R3‑258077 | |
| R3‑258751 | Summary of Offline Discussion on a 6G_DataCollection (CB: # 16) | Ericsson | discussion | discussion |
10.2.2RAN functions and logical architecture
| No |
No
| reserved | No | ||
| R3‑258752 | Correction on Paging Loss issue | Ericsson, Nokia | draftCR | Endorsement |
9.2.14Other
| No |
No
| reserved | No | R3‑258534 | |
| R3‑258753 | Correction on Paging Loss issue | Ericsson, Nokia | draftCR | Endorsement |
9.2.14Other
| No |
No
| reserved | No | R3‑258535 | |
| R3‑258754 | Correction on Paging Loss issue | Ericsson, Nokia | draftCR | Endorsement |
9.2.14Other
| No |
No
| reserved | No | R3‑258536 | |
| R3‑258755 | Correction of URCP for RAN paging | CATT, Huawei | CR | Approval |
9.2.14Other
| No |
No
| reserved | No | R3‑258304 | |
| R3‑258756 | Correction of URCP for RAN paging | CATT, Huawei | CR | Approval |
9.2.14Other
| No |
No
| reserved | No | R3‑258305 | |
| R3‑258757 | Correction of URCP for RAN paging | CATT, Huawei | CR | Approval |
9.2.14Other
| No |
No
| reserved | No | R3‑258306 | |
| R3‑258758 | (TP for TS38.300) Discussion on MRO for intra-CU CLTM | Lenovo | other | Agreement |
11.2.2Intra-CU conditional LTM
| Yes |
Yes
| revised | No | R3‑258806 | R3‑258368 |
| R3‑258759 | LS on the encoding of NfInstanceId | RAN3(Samsung) | LS out | Approval |
9.2.7R19 Ambient IoT
| No |
No
| reserved | No | ||
| R3‑258760 | Allocation of CN assigned subgroup ID for LP-WUS | Huawei, Ericsson | draftCR | - |
9.2.9R19 Low Power WUS/WUR
| No |
No
| reserved | No | R3‑258315 | |
| R3‑258761 | DRAFT Reply LS on CN assigned subgroup ID for LP-WUS | RAN3(Ericsson) | LS out | Agreement |
9.2.9R19 Low Power WUS/WUR
| No |
No
| reserved | No | R3‑258526 | |
| R3‑258762 | Correction of Failure report without RLF report | Huawei, Nokia, JIO plattforms, Ericsson | CR | Agreement |
9.2.1R19 SON/MDT
| No |
No
| reserved | No | R3‑258460 | |
| R3‑258763 | Correction of WAB | Ericsson, Jio Platforms, Qualcomm, CATT | draftCR | Endorsement |
9.4Endorsed CRs Review
| Yes |
No
| available | No | R3‑258033 | |
| R3‑258764 | Correction to E1AP on AI/ML for NG-RAN | CATT, Huawei, Nokia, ZTE, CMCC | CR | Agreement |
9.4Endorsed CRs Review
| No |
No
| reserved | No | R3‑258029 | |
| R3‑258765 | summary of CB: # 1_R19_SONMDT | CATT | discussion | Agreement |
9.2.1R19 SON/MDT
| No |
No
| reserved | No | ||
| R3‑258766 | LS on the signalling design of SCG LTM related parameters | RAN2(ZTE) | LS in | discussion |
8.2LSin received during the meeting
| Yes |
No
| available | No | ||
| R3‑258767 | 6G RAN-CN cloud friendly P2P Solution | Nokia | pCR | - |
10.3.2RAN-CN interface options
| Yes |
Yes
| agreed | No | R3‑258427 | |
| R3‑258768 | Clarification of handover for WAB-MT | Qualcomm | CR | Agreement |
9.2.3R19 WAB
| No |
No
| reserved | No | ||
| R3‑258769 | Clarification of handover for WAB-MT | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, CATT, China Telecom, Canon, Qualcomm | CR | - |
9.2.3R19 WAB
| No |
No
| reserved | No | R3‑258200 | |
| R3‑258770 | Clarification of handover for WAB-MT | Huawei, Nokia, Nokia Shanghai Bell, China Telecom | CR | Approval |
9.2.3R19 WAB
| No |
No
| reserved | No | R3‑258331 | |
| R3‑258771 | Stage-2 Correction of WAB Xn Connection Management | Ericsson | CR | Agreement |
9.2.3R19 WAB
| No |
No
| reserved | No | R3‑258265 | |
| R3‑258772 | Correction of BH-gNB and WAB-MT for WAB | China Telecom, CATT, Nokia, Nokia Shanghai Bell, Huawei, ZTE | CR | Agreement |
9.2.3R19 WAB
| No |
No
| reserved | No | R3‑258571 | |
| R3‑258773 | Reply LS on Continuous MDT | RAN3(Huawei) | LS out | Approval |
9.2.2R19 AI/ML for NG-RAN
| No |
No
| reserved | No | R3‑258475 | |
| R3‑258774 | Support for partial reporting in Data Collection Reporting procedure | Huawei, FiberCop, Verizon, Jio Platforms, Qualcomm, ZTE | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| No |
No
| reserved | No | R3‑258478 | |
| R3‑258775 | XnAP correction on the Inter-CU LTM procedure | Samsung | CR | Agreement |
9.2.5R19 Mobility enhancements
| No |
No
| reserved | No | R3‑258666 | |
| R3‑258776 | Correction on Early UL Sync Configuration IE for inter-CU LTM | Samsung, Huawei, Ericsson, Nokia, China Telecom, Google | CR | Agreement |
9.2.5R19 Mobility enhancements
| No |
No
| reserved | No | R3‑258668 | |
| R3‑258777 | Correction on the LTM Indicator for C-LTM | Samsung, Huawei, Ericsson, LG Electronics, Nokia, China Telecom, Google | CR | Agreement |
9.2.5R19 Mobility enhancements
| No |
No
| reserved | No | R3‑258669 | |
| R3‑258778 | Correction to inter-CU LTM and conditional intra-CU LTM | Huawei, Jio Platforms, CATT, China Telecom, Lenovo, Ericsson, LG Electronics, Qualcomm Incorporated, Google, Ofinno | CR | - |
9.2.5R19 Mobility enhancements
| No |
No
| reserved | No | R3‑258157 | |
| R3‑258779 | Correction on the CSI-RS Coordination procedure | Huawei, LG Electronics, ZTE, Offinno, NTT Docomo, Jio Platforms, CMCC, Lenovo | CR | - |
9.2.5R19 Mobility enhancements
| No |
No
| reserved | No | R3‑258155 | |
| R3‑258780 | Introduction of missing LTM Indicator for inter-CU LTM | Huawei, Nokia, LG Electronics, NTT DoCoMo. Offinno, Jio Platforms, CMCC, Ericsson | CR | - |
9.2.5R19 Mobility enhancements
| No |
No
| reserved | No | R3‑258153 | |
| R3‑258781 | Correction to L2 reset in inter-CU LTM (option 2) | Google, Huawei | CR | - |
9.2.5R19 Mobility enhancements
| No |
No
| reserved | No | R3‑258317 | |
| R3‑258782 | Summary of the offline discussion on CB Rel-20_A-IoT | Huawei | discussion | Agreement |
14.2Topology 2
| No |
No
| reserved | No | ||
| R3‑258783 | (TP to 38.300 BL CR) Architecture aspects for T2 | CMCC | other | Agreement |
14.2Topology 2
| No |
No
| reserved | No | ||
| R3‑258784 | (TP to 38.300 BL CR) Topology 2 Call Flows | NEC | other | Agreement |
14.2Topology 2
| No |
No
| reserved | No | ||
| R3‑258785 | (TP to 38.413 BL CR) UE Reader Authorization | Huawei | other | Agreement |
14.2Topology 2
| No |
No
| reserved | No | ||
| R3‑258786 | (TP to 38.423 BL CR) UE Reader Authorization | Samsung | other | Agreement |
14.2Topology 2
| No |
No
| reserved | No | ||
| R3‑258787 | Essential correction for inter-CU LTM on F1AP | CATT,Huawei, China Telecom, LG Electronics, Nokia, Samsung, ZTE, Ofinno, Ericsson | CR | Agreement |
9.2.5R19 Mobility enhancements
| No |
No
| reserved | No | R3‑258392 | |
| R3‑258788 | Correction to XnAP on CLI Indication | ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei, Qualcomm, Samsung, Eircsson, Charter, Nokia, LGE, CATT, CMCC | CR | Approval |
9.2.10R19 Evolution of Duplex Operation
| No |
Yes
| agreed | No | R3‑258635 | |
| R3‑258789 | Correction to F1AP on CLI Indication | ZTE Corporation, China Telecom, Pengcheng Laboratory, Huawei | CR | Approval |
9.2.10R19 Evolution of Duplex Operation
| No |
Yes
| agreed | No | R3‑258636 | |
| R3‑258790 | Clarification for propagation of MDT Configuration in stage2 | ZTE Corporation,China Unicom,China Telecom,CMCC, Huawei | draftCR | Endorsement |
9.2.14Other
| No |
No
| reserved | No | ||
| R3‑258791 | (pCR for TR38.745) Multi-hop UE trajectory across gNBs | NEC | pCR | Agreement |
12.2.1Multi-hop UE trajectory across gNBs
| No |
No
| reserved | No | R3‑258247 | |
| R3‑258792 | Summary of Offline Discussion for CB: # AIMLMultiHop | NEC | discussion | Agreement |
12.2.1Multi-hop UE trajectory across gNBs
| No |
No
| reserved | No | ||
| R3‑258793 | Clarification of procedural text for POSITIONING DATA COLLECTION REPORT message | Nokia, CATT, Ericsson | CR | - |
9.2.11R19 AI/ML for air interface
| No |
Yes
| agreed | No | R3‑258174 | |
| R3‑258794 | Reply to Reply LS on removal of support of PWS over satellite NG-RAN in Rel-17 and 18 | SA2(Samsung) | LS in | discussion |
8.2LSin received during the meeting
| Yes |
No
| available | No | ||
| R3‑258795 | Correction of Data Collection Report procedure and others | Ericsson, Huawei, Nokia, Xiaomi, ZTE, CATT, NEC, Samsung, Qualcomm Inc., CEWiT | draftCR | Endorsement |
9.2.11R19 AI/ML for air interface
| Yes |
Yes
| endorsed | No | R3‑258527 | |
| R3‑258796 | [Draft] LS on definition of “ground truth label” in AI/ML-based Positioning Case 3a | Huawei, Ericsson, Nokia | LS out | Agreement |
9.2.11R19 AI/ML for air interface
| No |
Yes
| approved | No | R3‑258479 | |
| R3‑258797 | Correction on multi-modality, uplink rate control and available bit rate monitoring | Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Ofinno, ZTE, Lenovo | draftCR | Endorsement |
9.2.12R19 NR XR Enhancements
| No |
Yes
| endorsed | No | R3‑258332 | |
| R3‑258798 | Correction on Burst Size for XR | Samsung | draftCR | Endorsement |
9.2.12R19 NR XR Enhancements
| No |
Yes
| endorsed | No | R3‑258375 | |
| R3‑258799 | Support for continuous management-based MDT | CATT, Ericsson,ZTE, CMCC, Samsung, NEC | draftCR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| No |
No
| reserved | No | R3‑258458 | |
| R3‑258800 | Summary of the offline discussion on CB#18 | Vodafone | discussion | discussion |
10.4RAN internal functional split and interfaces
| No |
No
| reserved | No | ||
| R3‑258801 | pCR to TR 38.760-3 on 6G RAN-CN interface options | ZTE Corporation | pCR | Agreement |
10.3.2RAN-CN interface options
| No |
No
| reserved | No | R3‑258638 | |
| R3‑258802 | Summary of the offline discussion on CB # 24_R19 | CATT | discussion | Agreement |
9.2.10R19 Evolution of Duplex Operation
| No |
No
| reserved | No | ||
| R3‑258803 | (TP for BLCR for 38.413) Inter-CU LTM | Huawei | other | - |
11.2.1Inter-CU LTM
| No |
No
| reserved | No | R3‑258462 | |
| R3‑258804 | On maximum number of subgroups and RAN paging | CATT | draftCR | Endorsement |
9.2.9R19 Low Power WUS/WUR
| No |
No
| reserved | No | ||
| R3‑258805 | Summary of the offline discussion on CB # 15_Definitions&Principles | FiberCop | discussion | Approval |
10.2Overall RAN architecture
| No |
No
| reserved | No | ||
| R3‑258806 | (TP for TS38.300) Discussion on MRO for intra-CU CLTM | Lenovo, CATT | other | Agreement |
11.2.2Intra-CU conditional LTM
| No |
Yes
| agreed | No | R3‑258758 | |
| R3‑258807 | Corrections to F1 support of Network Energy Saving Enhancement | Ericsson, China Telecom, Jio Platforms, Lenovo, Rakuten | CR | Approval |
9.2.8R19 Network Energy Saving
| No |
Yes
| agreed | No | R3‑258743 | |
| R3‑258808 | Summary of the offline discussion on CB # 11_Rel-19 Network Energy Saving | Ericsson | discussion | Approval |
9.2.8R19 Network Energy Saving
| No |
No
| reserved | No | ||
| R3‑258809 | Corrections to OD-SIB1 Configuration Provision Status Update | Ericsson, ZTE, Samsung | CR | Agreement |
9.2.8R19 Network Energy Saving
| No |
No
| reserved | No | R3‑258453 | |
| R3‑258810 | Corrections on termination of OD-SIB1 operation and status update | CATT, Huawei, Ericsson, CMCC | CR | Approval |
9.2.8R19 Network Energy Saving
| No |
No
| reserved | No | R3‑258302 | |
| R3‑258811 | Summary of the offline discussion on CB: # 2_R19_AIMLNGRAN | ZTE Corporation | discussion | Approval |
9.2.2R19 AI/ML for NG-RAN
| No |
No
| reserved | No | ||
| R3‑258812 | Miscellaneous corrections to the support of split architecture | ZTE Corporation, CMCC, China Unicom, China Telecom | CR | Agreement |
9.2.2R19 AI/ML for NG-RAN
| No |
No
| reserved | No | R3‑258215 | |
| R3‑258813 | Summary of the offline discussion on CB: # 5_R19_MobEnh | Samsung | discussion | Approval |
9.2.5R19 Mobility enhancements
| No |
No
| reserved | No |