Tdoc List
2024-08-19 19:12
Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Opening of the meeting |   | ||||||||||
2 | Reminders |   | ||||||||||
2.1 | IPR Declaration |   | ||||||||||
2.2 | Statement of Antitrust Compliance |   | ||||||||||
2.3 | Responsible IT Behavior |   | ||||||||||
2.4 | Additional reminders |   | ||||||||||
3 | Approval of the Agenda | R3‑244001 | RAN3#125 Meeting Agenda | RAN3 Chair | agenda | Approval | Yes |
Yes
| approved | No | ||
4 | Approval of the minutes from previous meetings | R3‑244002 | RAN3#124 Meeting Report | ETSI-MCC | report | Approval | Yes |
Yes
| approved | No | ||
5 | Documents for immediate consideration | R3‑244003 | Guidelines for RAN3 Meetings | RAN3 Chair, RAN3 Vice-Chairs | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||
6 | Organizational topics |   | ||||||||||
7 | General, protocol principles and issues | R3‑244004 | TR 30.531 v1.53.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC | draft TR | Endorsement | Yes |
Yes
| revised | No | R3‑244648 | |
R3‑244648 | TR 30.531 v1.53.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC | draft TR | Endorsement | No |
Yes
| endorsed | No | R3‑244004 | |||
8 | Incoming LSs |   | ||||||||||
8.1 | New Incoming LSs | R3‑244026 | LS on RFC 9543, "A Framework for Network Slices in Networks Built from IETF Technologies" | IETF | LS in | Discussion | Yes |
Yes
| noted | No | ||
R3‑244027 | LS on "A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies" | IETF | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑244501 | Discussion on the Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies | Huawei | discussion | Yes |
Yes
| noted | No | |||||
R3‑244502 | [draft] Reply LS on the Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies | Huawei | LS out | Yes |
Yes
| revised | No | R3‑244660 | ||||
R3‑244660 | [draft] Reply LS on the Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies | Huawei | LS out | - | No |
No
| reserved | No | R3‑244502 | |||
R3‑244613 | Discuss LS on A Realization of Network Slices for 5G Networks Using Current IPMPLS Technologies | ZTE Corporation | discussion | Yes |
Yes
| noted | No | |||||
R3‑244614 | [Draft]Reply LS on A Realization of Network Slices for 5G Networks Using Current IPMPLS Technologies | ZTE Corporation | other | Yes |
Yes
| noted | No | |||||
R3‑244016 | LS on Avoiding Cross-TSG TEI | TSG RAN(NECLab) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑244017 | Reply LS on Restoration of N3mb Failure for MBS broadcast | SA2(Ericsson) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑244005 | Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | CT1(Huawei) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑244006 | Reply LS on 5GS missing CBC support for shared networks | CT1(Ericsson) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑244007 | Reply LS on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | RAN1(Ericsson) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑244013 | Reply LS on Rel-18 higher-layers parameter list | RAN2(Ericsson) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑244015 | Reply LS RP-240891 on NTZ solution impacts to RAN. | TSG RAN(Interdigital) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑244021 | LS on NTZ solution impacts to RAN | SA2(Ericsson) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
R3‑244023 | Reply LS on the MBS broadcast service continuity and MBS session identification | SA4(Qualcomm) | LS in | Discussion | Yes |
Yes
| noted | No | ||||
8.2 | LSin received during the meeting |   | ||||||||||
8.3 | Left over LSs / pending actions | R3‑244052 | Discussion on emergency call support for (e)RedCap and 2RX XR UEs in barred cells | ZTE Corporation, China Telecom, China Unicom | discussion | Yes |
Yes
| noted | No | |||
R3‑244053 | Introduction of barring exemption for (e)RedCap and 2RX XR UEs [EM_Call_Exemption] | ZTE Corporation, China Telecom, China Unicom | CR | Agreement | Yes |
Yes
| revised | No | R3‑244649 | |||
R3‑244649 | Introduction of barring exemption for (e)RedCap and 2RX XR UEs [EM_Call_Exemption] | ZTE Corporation, China Telecom, China Unicom | CR | Agreement | No |
No
| reserved | No | R3‑244053 | |||
R3‑244078 | Introduction of barring exemption for (e)RedCap and 2RX XR UEs | China Telecom, ZTE, China Unicom | CR | Approval | Yes |
Yes
| revised | No | R3‑244650 | R3‑243159 | ||
R3‑244650 | Introduction of barring exemption for (e)RedCap and 2RX XR UEs | China Telecom, ZTE, China Unicom | CR | Approval | No |
No
| reserved | No | R3‑244078 | |||
R3‑244054 | [Draft] Reply LS on emergency call support for (e)RedCap in barred cells | ZTE Corporation | LS out | Agreement | Yes |
No
| available | No | ||||
R3‑244131 | Support of Emergency Calls for (e)RedCap UEs in barred cells | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑244132 | Support of Emergency Calls for (e)RedCap UEs in barred cells | Nokia | CR | Yes |
No
| available | No | |||||
R3‑244133 | Support of Emergency Calls for (e)RedCap UEs in barred cells | Nokia | CR | Yes |
No
| available | No | |||||
R3‑244134 | Reply LS on Support of Emergency Calls for (e)RedCap UEs in barred cells | Nokia | LS out | Agreement | Yes |
No
| available | No | ||||
R3‑244285 | Discussion on Emergency call Support for (e)RedCap UEs | Qualcomm Incorporated | discussion | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244398 | Considerations on RAN2 LS on emergency call support for UE in barred cells | Ericsson | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244399 | Introduction of barring exemption for UE in emergency calls [EM_Call_Exemption] [RedCap_EM_Call] | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
R3‑244400 | Introduction of barring exemption for UE in emergency calls [EM_Call_Exemption] [RedCap_EM_Call] | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
R3‑244401 | Introduction of barring exemption for UE in emergency calls [EM_Call_Exemption] [RedCap_EM_Call] | Ericsson | CR | Agreement | Yes |
No
| available | No | ||||
R3‑244402 | [DRAFT]Response LS on LS on emergency call support for (e)RedCap in barred cells | Ericsson | LS out | Approval | Yes |
No
| available | No | ||||
R3‑244496 | Emergency call support in barred cells | Huawei | discussion | Yes |
No
| available | No | |||||
R3‑244497 | Introduction of Emergency call support in barred cells [RedCap_EM_Call] | Huawei | CR | Yes |
No
| available | No | |||||
R3‑244498 | Introduction of Emergency call support in barred cells [RedCap_EM_Call] | Huawei | CR | Yes |
No
| available | No | |||||
R3‑244499 | Introduction of Emergency call support in barred cells [RedCap_EM_Call] | Huawei | CR | Agreement | Yes |
Yes
| revised | No | R3‑244651 | |||
R3‑244651 | Introduction of Emergency call support in barred cells [RedCap_EM_Call] | Huawei | CR | Agreement | No |
Noneed to check TEI identifier
| reserved | No | R3‑244499 | |||
R3‑244500 | [draft] Reply LS on Emergency call support in barred cells | Huawei | LS out | Agreement | Yes |
No
| available | No | ||||
R3‑244585 | Discussion on support barring exemption for emergency calls | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244587 | Introduction of barring exemption for emergency calls | CMCC | CR | Approval | Yes |
No
| available | No | ||||
R3‑244588 | Introduction of barring exemption for emergency calls | CMCC | CR | Approval | Yes |
No
| available | No | ||||
R3‑244586 | Draft Reply LS on support barring exemption for emergency calls | CMCC | LS out | Agreement | Yes |
No
| available | No | ||||
R3‑244126 | Switch to RRC Connected after SDT Partial Context Transfer | Nokia, Ericsson | discussion | Yes |
YesResp in R3-244643
| noted | No | |||||
R3‑244643 | Response to R3-244126, R3-244127, R3-244128, R3-244130 | Huawei | response | Discussion | Yes |
Yes
| noted | No | ||||
R3‑244127 | Correction of switch to RRC connected after SDT Partial Context Transfer | Nokia, Ericsson | draftCR | Yes |
Yes
| noted | No | |||||
R3‑244128 | Correction of switch to RRC connected after SDT Partial Context Transfer | Nokia, Ericsson | CR | Yes |
Yes
| noted | No | |||||
R3‑244130 | Response LS on SDT signalling optimization for partial context transfer | Nokia, Ericsson | LS out | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244220 | Discussions on UE's awareness of MBS Communication Service Type for QMC | Huawei | discussion | Decision | Yes |
YesResp in R3-244647
| noted | No | ||||
R3‑244647 | Response to R3-244220 on UE awareness of MBS QoE | ZTE Corporation | discussion | Decision | Yes |
Yes
| noted | No | ||||
R3‑244282 | MBS Communication Service Type for QMC | Ericsson | discussion | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244283 | [DRAFT] LS on MBS Communication Service Type | Ericsson | LS out | Agreement | Yes |
Yes
| noted | No | ||||
9 | Corrections to Rel-18 or earlier releases |   | ||||||||||
9.1 | LTE | R3‑244286 | (TP for TS36.300) Discussion on UE Location for NTN NB-IoT UE | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Inmarsat, Thales | other | Agreement | Yes |
Yes
| noted | No | ||
R3‑244345 | Support User Location Information reporting for NB-IoT NTN | Nokia, Nokia Shanghai Bell, Qualcomm | CR | Agreement | Yes |
Yes
| noted | No | R3‑243348 | |||
R3‑244358 | Discussion on UE Location Information for NB-IoT NTN | Huawei, Ericsson | discussion | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244602 | Discussion on UE location information for NB-IoT NTN | CMCC, China Telecom, China Unicom | discussion | Discussion | Yes |
Yes
| noted | No | ||||
R3‑244601 | Correction of TS 36.300 on UE location information for NB-IoT NTN | CMCC, China Telecom, China Unicom | draftCR | Approval | Yes |
No
| available | No | ||||
R3‑244612 | Correction on mapping of tracking area and fixed geographical area for NB-IoT NTN | ZTE Corporation | draftCR | Approval | Yes |
Yes
| noted | No | ||||
R3‑244368 | E-SMLC OAM Configuration for IoT NTN | Ericsson, Thales, Huawei | draftCR | Endorsement | Yes |
Yes
| noted | No | R3‑243373 | |||
R3‑244367 | [DRAFT] Reply LS on UE Location Information for NB-IoT NTN | Ericsson, Huawei, Apple, Thales | LS out | Agreement | Yes |
No
| available | No | R3‑243372 | |||
R3‑244603 | Draft Reply LS to UE location information for NB-IoT NTN | CMCC, China Telecom, China Unicom | LS out | Approval | Yes |
No
| available | No | ||||
R3‑244637 | Draft Reply for LS on UE Location Information for NB-IoT NTN | Qualcomm Incorporated | LS out | Agreement | Yes |
No
| available | No | ||||
R3‑244652 | CB:#4_CoarseLocationInfor | Ericsson | discussion | discussion | No |
No
| reserved | No | ||||
R3‑244403 | Correction on inter-system S1/NG-handover | Ericsson, Qualcomm Inc., China Telecom, Vodafone, ZTE | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244404 | Correction on inter-system S1/NG-handover | Ericsson, Qualcomm Inc., China Telecom, Vodafone, ZTE | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244506 | Clarification on indication of cell re-activation | CATT, Nokia, Huawei, CMCC | discussion | Decision | Yes |
Yes
| noted | No | ||||
R3‑244610 | Clarification on indication of dormant cell re-activation | CATT, Nokia, Huawei,CMCC | CR | Agreement | Yes |
Yes
| noted | No | ||||
9.2 | NR | R3‑244081 | Update of stage 2 positioning information | Nokia, CATT, Ericsson, Huawei, Samsung, Xiaomi, ZTE | draftCR | Endorsement | Yes |
Yes
| revised | No | R3‑244653 | R3‑243570 |
R3‑244653 | Update of stage 2 positioning information | Nokia, CATT, Ericsson, Huawei, Samsung, Xiaomi, ZTE | draftCR | Endorsement | No |
No
| reserved | No | R3‑244081 | |||
R3‑244189 | Corrections to Positioning SRS BW Aggregation and Tx Hopping | CATT, Ericsson, ZTE, Samsung | CR | Approval | Yes |
Yes
| noted | No | ||||
R3‑244397 | Correction to SRS for positioning aggregation | Qualcomm Incorporated | CR | Yes |
Yes
| noted | No | |||||
R3‑244405 | Positioning correction to F1AP | Ericsson, CATT, ZTE, Samsung | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244359 | Value UE Rx-Tx Time Difference ASN.1 presence correction | Huawei, Nokia, CATT, ZTE, Samsung, Ericsson | CR | Agreement | Yes |
Yes
| revised | No | R3‑244654 | |||
R3‑244654 | Value UE Rx-Tx Time Difference ASN.1 presence correction | Huawei, Nokia, CATT, ZTE, Samsung, Ericsson, Xiaomi | CR | Agreement | No |
Yes
| agreed | No | R3‑244359 | |||
R3‑244360 | Positioning ASN.1 correction (AggregatedPRSResourceSetList, kminus values) | Huawei, Nokia, CATT, ZTE, Samsung, Ericsson | CR | Agreement | Yes |
Yes
| revised | No | R3‑244655 | |||
R3‑244655 | Positioning ASN.1 correction (AggregatedPRSResourceSetList, kminus values) | Huawei, Nokia, CATT, ZTE, Samsung, Ericsson, Xiaomi | CR | Agreement | No |
No
| reserved | No | R3‑244360 | |||
R3‑244125 | NRPPa support for sub 1s location information reporting periodicity [Sub_1s_periodicity] | Ericsson, ZTE, CATT | CR | Agreement | Yes |
Yes
| revised | No | R3‑244656 | |||
R3‑244656 | NRPPa support for sub 1s location information reporting periodicity [Sub_1s_periodicity] | Ericsson, ZTE, CATT | CR | Agreement | No |
Yes
| agreed | No | R3‑244125 | |||
R3‑244091 | F1AP support for sub 1s location information reporting periodicity [Sub_1s_periodicity] | ZTE Corporation, Ericsson, CATT | CR | Agreement | Yes |
Yes
| revised | No | R3‑244657 | |||
R3‑244657 | F1AP support for sub 1s location information reporting periodicity [Sub_1s_periodicity] | ZTE Corporation, Ericsson, CATT | CR | Agreement | No |
Yes
| agreed | No | R3‑244091 | |||
R3‑244406 | Support positioning of L2 UE-to-network remote UE [PosL2RemoteUE] | Ericsson, CATT, Xiaomi, ZTE | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244407 | Correction of TRP Geographical coordinates [PosLocalCoords] | Ericsson, Qualcomm Inc., CATT, Xiaomi | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244408 | Correction of TRP Geographical coordinates [PosLocalCoords] | Ericsson, Qualcomm Inc., CATT, Xiaomi | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244187 | Support of pre-configured SRS activation | CATT, Huawei, ZTE, Samsung | draftCR | Approval | Yes |
Yes
| noted | No | ||||
R3‑244205 | Support of preconfigured SRS activation | ZTE Corporation, CATT, Huawei, Samsung | CR | Yes |
No
| available | No | |||||
R3‑244226 | Support of pre-configured SRS activation | Huawei, CATT, ZTE, Samsung | CR | Agreement | Yes |
No
| available | No | ||||
R3‑244391 | Missing procedure description for pre-configured SRS activation | Qualcomm Incorporated, Ericsson, Nokia, Xiaomi | draftCR | Yes |
No
| available | No | |||||
R3‑244190 | Support of the pre-Configured SRS activation | Xiaomi, Ericsson, Nokia, Qualcomm Incorporated | CR | Agreement | Yes |
No
| available | No | R3‑243307 | |||
R3‑244412 | Support of pre-Configured SRS activation using full context relocation | Ericsson, Xiaomi, Nokia, Qualcomm Incorporated | CR | Agreement | Yes |
No
| available | No | R3‑243430 | |||
R3‑244188 | Support of UE specific SRS Reservation | CATT, Huawei, ZTE, Samsung | draftCR | Approval | Yes |
No
| available | No | ||||
R3‑244206 | Support of UE specific SRS reservation | ZTE Corporation, CATT, Huawei, Samsung | CR | Yes |
No
| available | No | |||||
R3‑244216 | Support of UE specific SRS reservation | Samsung, CATT, Huawei, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
R3‑244227 | Support of UE specific SRS reservation | Huawei, CATT,Samsung, ZTE | CR | Agreement | Yes |
No
| available | No | ||||
R3‑244281 | Aligning procedure code between releases | Huawei, Ericsson, Nokia | CR | Yes |
No
| available | No | |||||
R3‑244361 | Correction on Measurement Time Window | Huawei | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244362 | Clarification on TRP ID for SRS Bandwidth Aggregation | Huawei | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244393 | Correction to Requested DL PRS Transmission Characteristics | Qualcomm Incorporated, Huawei | CR | Yes |
No
| available | No | |||||
R3‑244658 | CB:#7_Positioning | CATT | discussion | discussion | No |
No
| reserved | No | ||||
R3‑244064 | Triggering reporting of requested DL LBT information | Nokia, Ericsson, Huawei, ZTE, Samsung | CR | Agreement | Yes |
Yes
| agreed | No | ||||
R3‑244122 | Stage 2 correction for reporting of requested DL LBT information | Ericsson, Nokia, Samsung, Huawei, ZTE | CR | Agreement | Yes |
Yes
| revised | No | R3‑244659 | |||
R3‑244659 | Stage 2 correction for reporting of requested DL LBT information | Ericsson, Nokia, Samsung, Huawei, ZTE | CR | Agreement | No |
Yes
| agreed | No | R3‑244122 | |||
R3‑244221 | Correction on SPR retrieval and forwarding | Samsung, Lenovo, Cybercore, Qualcomm | draftCR | Endorsement | Yes |
Yes
| revised | No | R3‑244661 | |||
R3‑244661 | Correction on SPR retrieval and forwarding | Samsung, Lenovo, Cybercore, Qualcomm, Nokia, Ericsson, Huawei, ZTE, CATT | draftCR | Endorsement | No |
Yes
| endorsed | No | R3‑244221 | |||
R3‑244261 | Correction on successful PSCell Addition/Change Report | CATT, Lenovo | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244222 | Correction of SON for fast MCG recovery in stage 2 | Samsung, Lenovo, CATT, Nokia | draftCR | Endorsement | Yes |
Yes
| noted | No | ||||
R3‑244244 | Correction on CPA failure states and detection mechanism in stage 2 | Nokia, CATT, CMCC, Qualcomm Inc. | draftCR | Endorsement | Yes |
Yes
| revised | No | R3‑244662 | |||
R3‑244662 | Correction on CPA failure states and detection mechanism in stage 2 | Nokia, CATT, CMCC, Qualcomm Inc., Huawei, ZTE | draftCR | Endorsement | No |
Yes
| endorsed | No | R3‑244244 | |||
R3‑244262 | Correction on conditional PSCell addition or change failure | CATT, CMCC, ZTE | draftCR | Endorsement | Yes |
Yes
| noted | No | ||||
R3‑244486 | Correction of the Signalling based MDT PLMN List IE | Huawei, China Unicom, China Telecom | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244487 | Correction of the Signalling based MDT PLMN List IE | Huawei, China Unicom, China Telecom | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244488 | Correction of the Signalling based MDT PLMN List IE | Huawei, China Unicom, China Telecom | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244174 | Corrections on information element to support both CPAC and S-CPAC | ZTE Corporation, Ericsson, CATT, China Telecom, CMCC, Samsung, Nokia, Lenovo, NEC, Google, LG Electronics, Huawei | CR | Agreement | Yes |
Yes
| revised | No | R3‑244663 | R3‑243833 | ||
R3‑244663 | Corrections on information element to support both CPAC and S-CPAC | ZTE Corporation, Ericsson, CATT, China Telecom, CMCC, Samsung, Nokia, Lenovo, NEC, Google, LG Electronics, Huawei | CR | Agreement | No |
Yes
| agreed | No | R3‑244174 | |||
R3‑244557 | LTM supports feature of MIMO with 2TA | Samsung, Nokia, CATT, Huawei, ZTE, Ericsson, LG Electronics, Google, CMCC, NEC, Lenovo | CR | Agreement | Yes |
Yes
| revised | No | R3‑244664 | |||
R3‑244664 | LTM supports feature of MIMO with 2TA | Samsung, Nokia, CATT, Huawei, ZTE, Ericsson, LG Electronics, Google, CMCC, NEC, Lenovo | CR | Agreement | No |
Yes
| agreed | No | R3‑244557 | |||
R3‑244489 | Further clarification on MIMO with 2TA in LTM | Huawei, China Unicom, CMCC | discussion | Discussion | Yes |
Yes
| noted | No | ||||
R3‑244490 | Correction on MIMO with 2TA in LTM | Huawei, China Unicom, CMCC | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244491 | Correction on MIMO with 2TA in LTM | Huawei, China Unicom, CMCC | draftCR | Endorsement | Yes |
Yes
| noted | No | ||||
R3‑244492 | [DRAFT] LS on MIMO with 2 TA in LTM | Huawei | LS out | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244100 | Correction on S-CPAC Complete Configuration Indicator | Huawei, LG Electronics, ZTE, CMCC, Ericsson | CR | Agreement | Yes |
Yes
| revised | No | R3‑244665 | |||
R3‑244665 | Correction on S-CPAC Complete Configuration Indicator | Huawei, LG Electronics, ZTE, CMCC, Ericsson, Nokia | CR | Agreement | No |
No
| reserved | No | R3‑244100 | |||
R3‑244582 | Correction on Early Sync Information from DU to CU | CMCC, ZTE, NEC, CATT, Huawei | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244276 | Missing agreement about UE conext release required | CATT, CMCC, ZTE | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244558 | Discussion on remaining issues on R18 LTM | Samsung | discussion | Approval | Yes |
Yes
| noted | No | ||||
R3‑244090 | LTM interwork with L3 measurements | Nokia | CR | Agreement | Yes |
No
| available | No | ||||
R3‑244177 | Discussion for Early TA acquisition and Preamble Resources for PDCCH order in LTM | discussion | Discussion | Yes |
No
| available | No | |||||
R3‑244178 | Corrections for Early TA acquisition and Preamble Resources for PDCCH order in LTM | Google, CATT | CR | Agreement | Yes |
No
| available | No | ||||
R3‑244179 | Clarification on SpCell ID replacement | CR | Agreement | Yes |
No
| available | No | |||||
R3‑244353 | LTM stage 2 corrections for split architecture | Ericsson | CR | Yes |
No
| available | No | |||||
R3‑244354 | LTM stage 2 corrections for non-split architecture | Ericsson | draftCR | Yes |
No
| available | No | |||||
R3‑244474 | Rel-18 correction on LTM with gNB-CU-UP change | LG Electronics Inc. | CR | Approval | Yes |
No
| available | No | ||||
R3‑244475 | Correction on the CHO Initiation IE name | LG Electronics Inc. | CR | Approval | Yes |
No
| available | No | ||||
R3‑244275 | Discussion on supporting Tag ID Pointer for LTM | CATT | discussion | Decision | Yes |
Yes
| noted | No | ||||
R3‑244666 | CB:#8_MobilityEnh | Samsung | discussion | discussion | No |
No
| reserved | No | ||||
R3‑244336 | Changing presence of IE extension for QoE related IE | Nokia, Ericsson, Huawei, CATT, Samsung, ZTE | CR | Agreement | Yes |
Yes
| agreed | No | ||||
R3‑244386 | Changing presence of IE extensions for QoE related IEs | Ericsson, Nokia, Huawei, CATT, Samsung, ZTE | CR | Yes |
Yes
| agreed | No | |||||
R3‑244230 | QoE measurement handling in RRC_IDLE and RRC_INACTIVE states | CATT, Ericsson, ZTE, Xiaomi | draftCR | Approval | Yes |
Yes
| noted | No | R3‑243326 | |||
R3‑244549 | Discussion on QMC support in NR-DC for RRC segmentation | Samsung, ZTE, CATT, China Unicom, Lenovo | discussion | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244550 | Corrections to QMC support in NR-DC for RRC Segmentation (Option 1) | Samsung, Lenovo, Ericsson | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244551 | Correction to QMC support in NR-DC for RRC segmentation (Option 2) | Samsung, ZTE, CATT, Lenovo | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244217 | Correction on the QMC information in the SN modification required message | Huawei, China Unicom, Ericsson, Lenovo | CR | Approval | Yes |
Yes
| revised | No | R3‑244667 | R3‑243710 | ||
R3‑244667 | Correction on the QMC information in the SN modification required message | Huawei, China Unicom, Ericsson, Lenovo | CR | Approval | No |
Yes
| agreed | No | R3‑244217 | |||
R3‑244218 | Further miscellaneous corrections to 38.300 | Huawei, China Unicom, Lenovo | draftCR | Endorsement | Yes |
Yes
| noted | No | ||||
R3‑244219 | Further miscellaneous corrections to 37.340 | Huawei, China Unicom, Lenovo | draftCR | Endorsement | Yes |
Yes
| noted | No | ||||
R3‑244305 | Correction on inter MN handover without SN change for QMC | Lenovo, Huawei | draftCR | Approval | Yes |
Yes
| noted | No | ||||
R3‑244376 | QoE/RVQoE measurement continuity for SCG failure scenarios | Nokia | draftCR | Yes |
No
| available | No | |||||
R3‑244384 | Changing presence of IE extensions for MBS related IEs | Ericsson, Nokia, Huawei, CATT, Samsung, ZTE | CR | Yes |
Yes
| revised | No | R3‑244668 | ||||
R3‑244668 | Changing presence of IE extensions for MBS related IEs | Ericsson, Nokia, Huawei, CATT, Samsung, ZTE | CR | Agreement | No |
Yes
| agreed | No | R3‑244384 | |||
R3‑244385 | Changing presence of IE extensions for MBS related IEs | Ericsson, Nokia, Huawei, CATT, Samsung, ZTE | CR | Agreement | Yes |
Yes
| revised | No | R3‑244669 | |||
R3‑244669 | Changing presence of IE extensions for MBS related IEs | Ericsson, Nokia, Huawei, CATT, Samsung, ZTE | CR | Agreement | No |
Yes
| agreed | No | R3‑244385 | |||
R3‑244504 | Add Cause IE in MULTICAST CONTEXT NOTIFICATION REFUSE message | CATT, Nokia, ZTE, Ericsson,Huawei,Samsung | CR | Agreement | Yes |
Yes
| agreed | No | ||||
R3‑244097 | Correction on PDCP packets discard in case of MBS broadcast path update | Huawei, CBN, CMCC, Qualcomm Incorporated, Ericsson | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244098 | Correction on Multicast Group Paging | Huawei, CBN, Samsung, Nokia, CMCC, Qualcomm Incorporated, CATT, Ericsson | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244099 | Correction on Multicast Group Paging | Huawei, CBN, Samsung, Nokia, CMCC, Qualcomm Incorporated, CATT, Ericsson | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244135 | Correction of MBS in TS 38.401 | Nokia, Huawei, CATT, Qualcomm Incorporated, ZTE, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
R3‑244284 | Correction on configuration update for an inactive Multicast session | ZTE Corporation, CATT, Ericsson, Nokia | CR | Agreement | Yes |
Yes
| revised | No | R3‑244670 | |||
R3‑244670 | Correction on configuration update for an inactive Multicast session | ZTE Corporation, CATT, Ericsson, Nokia | CR | Agreement | No |
Yes
| agreed | No | R3‑244284 | |||
R3‑244092 | Discussion on Uu Relay RLC channel setup during UE context setup procedure | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell | discussion | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244093 | Corrections on Uu Relay RLC channel configuration | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244094 | Corrections on Uu Relay RLC channel configuration | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | R3‑244672 | |||
R3‑244672 | Corrections on Uu Relay RLC channel configuration | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell | CR | Agreement | No |
Yes
| agreed | No | R3‑244094 | |||
R3‑244628 | Corrections on Uu Relay RLC channel setup | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | R3‑244671 | |||
R3‑244671 | Corrections on Uu Relay RLC channel setup | ZTE Corporation, China Telecom, Samsung, Nokia, Nokia Shanghai Bell | CR | Agreement | No |
Yes
| agreed | No | R3‑244628 | |||
R3‑244239 | Correction on IAB authorization | CATT, Nokia, Nokia Shanghai Bell, Huawei | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244240 | Correction on IAB authorization | CATT, Nokia, Nokia Shanghai Bell, Huawei | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244640 | Correction on IAB-node authorization | ZTE Corporation, Lenovo, Xiaomi | CR | Yes |
Yes
| noted | No | |||||
R3‑244641 | Correction on IAB-node authorization | ZTE Corporation, Lenovo, Xiaomi | CR | Yes |
Yes
| noted | No | |||||
R3‑244642 | Correction on mobile IAB-node authorization | ZTE Corporation, Lenovo, Xiaomi | CR | Yes |
Yes
| noted | No | |||||
R3‑244521 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
R3‑244522 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT | CR | Agreement | Yes |
Yes
| revised | No | R3‑244673 | |||
R3‑244673 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT | CR | Agreement | No |
Yes
| agreed | No | R3‑244522 | |||
R3‑244523 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT | CR | Agreement | Yes |
Yes
| revised | No | R3‑244674 | |||
R3‑244674 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT | CR | Agreement | No |
Yes
| agreed | No | R3‑244523 | |||
R3‑244524 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT | CR | Agreement | Yes |
Yes
| revised | No | R3‑244675 | |||
R3‑244675 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT | CR | Agreement | No |
Yes
| agreed | No | R3‑244524 | |||
R3‑244525 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT | CR | Yes |
Yes
| revised | No | R3‑244676 | ||||
R3‑244676 | Correction on SSB transmission periodicity for IAB | Huawei, Samsung, Lenovo, CATT | CR | - | No |
Yes
| agreed | No | R3‑244525 | |||
R3‑244243 | Correction of TSC Traffic Characteristics in the PDU Session Resource Modification Info - MN terminated | Huawei, Nokia, Deutsche Telekom | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244263 | Adding ECN reporting status in RAN-triggered modification procedure | CATT, Nokia, Nokia Shanghai Bell, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
R3‑244300 | Stage 2 correction for AI/ML for NG-RAN | Ericsson, Huawei, Nokia, InterDigital, NEC, CATT, Lenovo, Deutsche Telekom | draftCR | Endorsement | Yes |
Yes
| noted | No | ||||
R3‑244503 | Clarification of UE performance | CATT, Huawei, Nokia, Qualcomm, Deutsche Telekom, NTT Docomo, Lenovo, NEC, China Telecom, China Unicom, Ericsson, ZTE, Samsung, InterDigital | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244473 | Correction on PDU session-level indirect data forwarding [Indirect Data Forwarding] | LG Electronics Inc., Huawei | CR | Agreement | Yes |
Yes
| noted | No | ||||
R3‑244074 | Correction of QoS Flow List | Huawei, Deutsche Telekom, CATT, Ericsson, ZTE | CR | Agreement | Yes |
Yes
| noted | No | R3‑243184 | |||
R3‑244075 | Correction of PDU Sessions List To Be Released - UPError | Huawei, Nokia, ZTE, Ericsson | CR | Agreement | Yes |
Yes
| revised | No | R3‑244677 | |||
R3‑244677 | Correction of PDU Sessions List To Be Released - UPError | Huawei, Nokia, ZTE, Ericsson | CR | Agreement | No |
Yes
| agreed | No | R3‑244075 | |||
R3‑244110 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom | CR | Approval | Yes |
No
| available | No | ||||
R3‑244111 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE,CATT,China Unicom | CR | Approval | Yes |
No
| available | No | ||||
R3‑244600 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE,CATT,China Unicom | CR | Approval | Yes |
No
| available | No | R3‑244112 | |||
R3‑244598 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom, ZTE, CATT, China Unicom | CR | Approval | Yes |
No
| available | No | R3‑244113 | |||
R3‑244114 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom, ZTE, CATT, China Unicom | CR | Approval | Yes |
No
| available | No | ||||
R3‑244115 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom, ZTE, CATT, China Unicom | CR | Approval | Yes |
No
| available | No | ||||
R3‑244599 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom | CR | Approval | Yes |
No
| available | No | R3‑244116 | |||
R3‑244597 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom, ZTE, CATT, China Unicom | CR | Approval | Yes |
No
| available | No | R3‑244117 | |||
R3‑244518 | Discussion on DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi | discussion | Yes |
No
| available | No | |||||
R3‑244519 | Correction on DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi | CR | Yes |
No
| available | No | R3‑243337 | ||||
R3‑244520 | Correction on DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi | CR | Yes |
No
| available | No | R3‑243338 | ||||
R3‑244583 | Correction on XR PSI based SDU Discard | CMCC, Huawei, CATT, Lenovo | CR | Approval | Yes |
No
| available | No | ||||
R3‑244129 | Use of Establishment Cause to determine DSCP | Peraton Labs, CISA ECD, Verizon | CR | Approval | Yes |
No
| available | No | ||||
R3‑244467 | Correction of Extended UE Identity Index Value | Nokia, Huawei, Qualcomm Incorporated, CATT | CR | Yes |
No
| available | No | |||||
R3‑244136 | Correction of Extended UE Identity Index Value | Nokia, Huawei, Qualcomm Incorporated, CATT | CR | Yes |
No
| available | No | |||||
R3‑244629 | Corrections on PEI subgrouping | ZTE Corporation, China Unicom, Samsung | CR | Approval | Yes |
No
| available | No | ||||
R3‑244630 | Corrections on PEI subgrouping | ZTE Corporation, China Unicom, Samsung | CR | Approval | Yes |
No
| available | No | ||||
R3‑244079 | Correction on new SIB17bis for TRS in Idle and Inactive | China Telecom,ZTE,CATT,China Unicom | CR | Approval | Yes |
No
| available | No | ||||
R3‑244080 | Correction on new SIB17bis for TRS in Idle and Inactive | China Telecom | CR | Approval | Yes |
No
| available | No | ||||
R3‑244175 | Correction on Transmission Bandwidth less than 5MHz | ZTE Corporation, China Telecom, CATT, China Unicom | CR | Yes |
No
| available | No | |||||
R3‑244176 | Correction on Transmission Bandwidth less than 5MHz | ZTE Corporaton, China Telecom, CATT, China Unicom | CR | Yes |
No
| available | No | |||||
R3‑244241 | Correction of Served Cell Specific Info Request in NG-RAN node configuration update procedure | Huawei, Nokia, CMCC | CR | Yes |
No
| available | No | |||||
R3‑244242 | Correction of Served Cell Specific Info Request in NG-RAN node configuration update procedure | Huawei, Nokia, CMCC | CR | Yes |
No
| available | No | |||||
R3‑244346 | Introduction of cell DTX/DRX information | Ericsson, Nokia, BT | CR | Yes |
No
| available | No | |||||
R3‑244627 | Introduction of cell DTX/DRX information | Nokia, Ericsson, BT | CR | Yes |
No
| available | No | R3‑244382 | ||||
R3‑244517 | Discussion on the PDCP SN gap report handling during UE’s handover | Huawei, CATT, Xiaomi, China Telecom | discussion | Yes |
No
| available | No | |||||
R3‑244456 | Correction on Location Reporting Control procedure for NR NTN_R17 | ZTE Corporation, CMCC, China Telecom | CR | Approval | Yes |
No
| available | No | ||||
R3‑244457 | Correction on Location Reporting Control procedure for NR NTN_R18 | ZTE Corporation, CMCC, China Telecom | CR | Approval | Yes |
No
| available | No | ||||
R3‑244458 | Correction on Location Reporting Control procedure for IoT NTN_R17 | ZTE Corporation, CMCC, China Telecom | CR | Approval | Yes |
No
| available | No | ||||
R3‑244459 | Correction on Location Reporting Control procedure for IoT NTN_R18 | ZTE Corporation, CMCC, China Telecom | CR | Approval | Yes |
No
| available | No | ||||
R3‑244413 | Issue with AoI Reporting for Slice subject to Area Restriction | Nokia, Deutsche Telekom, ZTE | discussion | Yes |
No
| available | No | |||||
R3‑244617 | Correction on Area of Interest RAN Node for location report | ZTE Corporation | CR | Yes |
No
| available | No | |||||
R3‑244618 | Correction on Area of Interest RAN Node for location report | ZTE Corporation | CR | Yes |
No
| available | No | |||||
R3‑244619 | Correction on Area of Interest RAN Node for location report | ZTE Corporation | CR | Yes |
No
| available | No | |||||
R3‑244620 | Correction on Area of Interest RAN Node for location report | ZTE Corporation | CR | Yes |
No
| available | No | |||||
R3‑244621 | Correction on Area of Interest RAN Node for location report | ZTE Corporation | CR | Yes |
No
| available | No | |||||
R3‑244622 | Correction on Area of Interest RAN Node for location report | ZTE Corporation | CR | Yes |
No
| available | No | |||||
R3‑244623 | Correction on Area of Interest RAN Node for location report | ZTE Corporation | CR | Yes |
No
| available | No | |||||
R3‑244624 | Correction on Area of Interest RAN Node for location report | ZTE Corporation | CR | Yes |
No
| available | No | |||||
R3‑244493 | Correction of CP Transport Layer Information and DL UP TNL Information | Huawei, China Unicom, China Telecom | CR | Yes |
No
| available | No | |||||
R3‑244494 | Correction of CP Transport Layer Information and DL UP TNL Information | Huawei, China Unicom, China Telecom | CR | Yes |
No
| available | No | |||||
R3‑244495 | Correction of CP Transport Layer Information and DL UP TNL Information | Huawei, China Unicom, China Telecom | CR | Yes |
No
| available | No | |||||
R3‑244505 | Handling GTP-U exceptions for tunnels delivering PDCP PDU | CATT | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244137 | Correction of recovery of split PDU Session | Nokia | CR | Yes |
No
| available | No | |||||
R3‑244149 | Security Indication behavior | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244150 | Correction for Security Indication behavior | NEC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑244151 | Correction for Security Indication behavior | NEC | CR | Agreement | Yes |
No
| available | No | ||||
R3‑244455 | Missing Iuant interface reference in NR specification | Ericsson | CR | Yes |
No
| available | No | |||||
R3‑244608 | PDCP version information over the E1 interface | Samsung | CR | Agreement | Yes |
No
| available | No | R3‑243757 | |||
R3‑244609 | Discussion on providing the PDCP version from the eNB-CP to the eNB-UP over the E1 interface | Samsung | other | Discussion | Yes |
No
| available | No | ||||
R3‑244048 | Correction on IAB-node authorization | ZTE Corporation | CR | No |
Yes
| withdrawn | Yes | |||||
R3‑244049 | Correction on IAB-node authorization | ZTE Corporation | CR | No |
Yes
| withdrawn | Yes | |||||
R3‑244050 | Correction on mobile IAB-node authorization | ZTE Corporation | CR | No |
Yes
| withdrawn | Yes | |||||
R3‑244083 | Handling of authorization for (mobile) IAB node | ZTE Corporation | discussion | Yes |
Yes
| withdrawn | Yes | |||||
R3‑244112 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom | CR | Approval | Yes |
Yes
| withdrawn | Yes | R3‑244600 | |||
R3‑244113 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom | CR | Approval | Yes |
Yes
| withdrawn | Yes | R3‑244598 | |||
R3‑244116 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom | CR | Approval | Yes |
Yes
| withdrawn | Yes | R3‑244599 | |||
R3‑244117 | Correction on asymmetric UL and DL for TDD Carrier | China Telecom,ZTE, CATT,China Unicom | CR | Approval | Yes |
Yes
| withdrawn | Yes | R3‑244597 | |||
R3‑244382 | Introduction of cell DTX/DRX information | Nokia, Ericsson, BT | CR | Yes |
Yes
| withdrawn | Yes | R3‑244627 | ||||
10 | Data Collection for SON_MDT in NR standalone and MR-DC WI (RAN3-led) |   | ||||||||||
10.1 | General | R3‑244532 | Workplan for Rel-19 SON_MDT Enhancement | China Unicom, CMCC | Work Plan | Yes |
No
| available | No | |||
10.2 | MRO Enhancements | R3‑244264 | Discussion on MRO for mobility | CATT | discussion | Decision | Yes |
No
| available | No | ||
R3‑244335 | MRO Enhancements for LTM and CHO with Candidate SCG(s) | Nokia | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244433 | MRO enhancements for LTM and CHO with candidate SCGs | Ericsson | discussion | Yes |
No
| available | No | |||||
R3‑244278 | (TP for SON BLCR for 38.300, 38.401, 38.473, 37.340) MRO enhancement for R18 mobility mechanisms | Huawei | other | Yes |
No
| available | No | |||||
R3‑244065 | [TP for TS 37.340 BL CR, SON] Failure handling and optimal use of Subsequent CPAC | Nokia | other | Agreement | Yes |
No
| available | No | ||||
R3‑244160 | MRO for LTM | NEC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244207 | Discussion on MRO for LTM | Samsung | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244223 | Failure scenarios on MRO for CHO with candidate SCGs | Samsung, Cybercore, ZTE | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244224 | Discussion on MRO for CHO with candidate SCGs and S-CPAC | Samsung | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244256 | Discussion on MRO enhancements for LTM | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244306 | Discussion on MRO for LTM | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244307 | (TP for SON BLCR for 37.340) Discussion on MRO for subsequent CPAC and CHO with candidate SCG(s) | Lenovo | other | Approval | Yes |
No
| available | No | ||||
R3‑244430 | MRO enhancements for R18 mobility mechanisms | Qualcomm Incorporated | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244533 | Discussion on MRO Enhancements | China Unicom | discussion | Yes |
No
| available | No | |||||
R3‑244536 | Discussion on MRO issues related to LTM | LG Electronics Inc. | discussion | Yes |
No
| available | No | |||||
R3‑244604 | Discussion on MRO enhancements for LTM | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244615 | (TP for TS 38.300 TS37.340)Discussion on MRO | ZTE Corporation | discussion | Yes |
No
| available | No | |||||
10.3 | SON/MDT for NTN and Slicing |   | ||||||||||
10.3.1 | Intra-NTN Mobility | R3‑244460 | (TP to BL CR for TS 38.300) Further discussion on SONMDT enhancements for NTN | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||
R3‑244431 | SON MDT for NTN | Qualcomm Incorporated | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244265 | Discussion on intra-NTN mobility for SONMDT | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244066 | [TP to TS 38.423 BL CR, SON] Solution to avoid restarting MRO in NTN deployments | Nokia | other | Agreement | Yes |
No
| available | No | ||||
R3‑244260 | Discussion on SON enhancements for NTN | Samsung | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244308 | Discussion on MRO for intra-NTN mobility | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244434 | SON/MDT enhancements for NTN | Ericsson | discussion | Yes |
No
| available | No | |||||
R3‑244481 | SON for Intra-NTN mobility | Huawei | discussion | Yes |
No
| available | No | |||||
R3‑244534 | Discussion on SONMDT enhancements for NTN mobility | China Unicom | discussion | Yes |
No
| available | No | |||||
R3‑244575 | (TP to 38.300) Discussion on SONMDT enhancement for NTN | CMCC | other | Discussion | Yes |
No
| available | No | ||||
10.3.2 | Network Slicing | R3‑244435 | On slice specific MDT measurements and SON enhancements | Ericsson | discussion | Yes |
No
| available | No | |||
R3‑244067 | [TP to TS 38.300 BL CR, SON] MDT solution for slice support and slice-related mobility enhancements | Nokia | other | Agreement | Yes |
No
| available | No | ||||
R3‑244257 | Discussion on SON enhancements for network slicing | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244266 | Discussion on network slicing for SONMDT | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244279 | SON for Network Slicing | Huawei | discussion | Yes |
No
| available | No | |||||
R3‑244432 | SON MDT for network slicing | Qualcomm Incorporated | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244436 | (TP for SON BL CR for TS 38.413) MDT Area Scope for Network Slicing | Ericsson, InterDigital, Deutsche Telekom, Telecom Italia, T-Mobile USA | other | Agreement | Yes |
No
| available | No | ||||
R3‑244535 | Discussion on SONMDT enhancements for network slicing | China Unicom | discussion | Yes |
No
| available | No | |||||
R3‑244573 | Discussion on SONMDT for network slicing | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244616 | Further consideration on SON/MDT for Slicing | ZTE Corporation | discussion | Yes |
No
| available | No | |||||
10.4 | R18 leftovers | R3‑244011 | Reply LS on support of MRO for MR-DC SCG failure | RAN2(ZTE) | LS in | Discussion | Yes |
No
| available | No | ||
R3‑244225 | Discussion on the support of the leftovers in Rel-18 SON/MDT | Samsung | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244309 | (TP for SON BLCR for 36.300) Discussion on MRO for MR-DC SCG failure | Lenovo | other | Approval | Yes |
No
| available | No | ||||
R3‑244461 | (TP to BL CR for TS 36.300) Rel-18 leftovers | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
R3‑244267 | Discussion on SON enhancement for MR-DC SCG failure | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244280 | (TP for SON BLCR for 36.300, 36.423) Rel-18 SON and MDT leftovers | Huawei | other | Yes |
No
| available | No | |||||
R3‑244437 | Further discussion on RACH optimization for SDT | Ericsson | discussion | Yes |
No
| available | No | |||||
11 | AI/ML for NG-RAN SI (RAN3-led) |   | ||||||||||
11.1 | General | R3‑244028 | Skeleton for TR38.743 | ZTE, NEC | draft TR | Endorsement | Yes |
No
| available | No | R3‑243971 | |
R3‑244625 | Work plan for Study on enhancements for Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN | ZTE Corporation, NEC | discussion | Yes |
No
| available | No | |||||
R3‑244515 | (TP to 38.743) Conclusion on AI/ML NG-RAN Enhancements | ZTE Corporation, NEC, Samsung, Lenovo, CATT, Qualcomm, Nokia, Huawei, CMCC, China Telecom, China Unicom | other | Yes |
No
| available | No | |||||
11.2 | AI/ML enabled Slicing | R3‑244636 | Discussion on AIML based Network Slicing | Rakuten Mobile, Inc | discussion | Yes |
No
| available | No | |||
R3‑244507 | Support of AI/ML enabled slicing | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244303 | AIML for Network Slicing | Ericsson, InterDigital, T-Mobile USA, Lenovo, Telecom Italia, Qualcomm, Deutsche Telekom | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244442 | AI/ML Network Slicing Discussion | Nokia, Jio | discussion | Yes |
No
| available | No | |||||
R3‑244571 | Discussion on AI-based network slice | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244084 | (TP to 38.743) AIML assisted Network Slicing | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244138 | (TP for TR 38.743) TP on General Corrections for CCO and Slicing | InterDigital Communications | other | Decision | Yes |
No
| available | No | ||||
R3‑244162 | (TP to TR38.743) AI/ML enabled Slicing | NEC | other | Decision | Yes |
No
| available | No | ||||
R3‑244208 | (TP to TR 38.743) AI/ML enabled slicing | Samsung | pCR | Approval | Yes |
No
| available | No | ||||
R3‑244292 | Discussion on NG-RAN AI/ML for Network Slicing | Qualcomm Incorporated | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244294 | (TP to TR 38.743) Discussion on the AI/ML-enabled Network Slicing | Huawei | other | Discussion | Yes |
No
| available | No | ||||
R3‑244304 | TP for TR 38.743 on AIML for Network Slicing | Ericsson, InterDigital, T-Mobile USA, Lenovo, Telecom Italia, Qualcomm, Deutsche Telekom | other | Agreement | Yes |
No
| available | No | ||||
R3‑244311 | Discussion on AIML based network slicing | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244312 | TP to 38.743 for AIML based network slicing | Lenovo | other | Approval | Yes |
No
| available | No | ||||
R3‑244472 | (TP to TR 38.743) AI/ML Network Slicing | Nokia, Jio | other | Yes |
No
| available | No | |||||
R3‑244508 | (TP for TR38.743) Support of AI/ML enabled slicing | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244581 | TP to 38.743 AI/ML based CCO | CMCC | other | Approval | Yes |
No
| available | No | ||||
R3‑244638 | TP for TR 38.743 on AIML for Network Slicing | Rakuten Mobile, Inc | discussion | Yes |
No
| available | No | |||||
R3‑244039 | Discussion on NG-RAN AI/ML for Network Slicing | Tejas Networks Limited | discussion | Discussion | Yes |
No
| available | No | ||||
11.3 | AI/ML enabled Coverage and Capacity Optimization | R3‑244291 | (TP for TR 38.743) AI/ML enabled CCO | Qualcomm Incorporated, ZTE, CATT, SS, CMCC | other | Approval | Yes |
No
| available | No | ||
R3‑244377 | Discussion on how to determine the future CCO state | Nokia, Telecom Italia, Jio, Vodafone | discussion | Yes |
No
| available | No | |||||
R3‑244085 | (TP to 38.743) AIML assisted CCO | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244310 | Discussion on AI/ML based CCO | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244302 | Discussinos on timing aspects of AI/ML based CCO | Ericsson, InterDigital, Telecom Italia, Deutsche Telekom, Vodafone | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244452 | Further discussion on AIML support for CCO | Ericsson, InterDigital | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244038 | Discussion on AIML based CCO | Jio | discussion | Yes |
No
| available | No | |||||
R3‑244035 | AIML CCO as SON use case | Jio | discussion | Yes |
No
| available | No | |||||
R3‑244036 | Discussion on Enhancements for AIML based CCO | Jio | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244037 | Enhancements for AI ML NG-RAN CCO | Jio | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244062 | Discussion on Centralized beam prediction for AI/ML based CCO | Jio | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244163 | (TP to TR38.743) AI/ML enabled CCO | NEC | other | Decision | Yes |
No
| available | No | ||||
R3‑244209 | Discussion on AI/ML enabled CCO | Samsung | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244210 | (TP to TR 38.743) AI/ML enabled CCO | Samsung | pCR | Approval | Yes |
No
| available | No | ||||
R3‑244249 | Discussion on AI/ML based Coverage and Capacity Optimization | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244250 | (TP to 38.743) Support of AI/ML based Coverage and Capacity Optimization | China Telecom | other | Approval | Yes |
No
| available | No | ||||
R3‑244290 | Discussion on AI/ML enabled CCO | Qualcomm Incorporated | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244295 | (TP to TR 38.743) AI/ML-based Coverage and Capacity Optimization | Huawei | other | Discussion | Yes |
No
| available | No | ||||
R3‑244313 | TP to 38.743 for AIML based CCO | Lenovo | other | Approval | Yes |
No
| available | No | ||||
R3‑244378 | Discussion on solution for AI/ML-based CCO | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑244379 | (TP for TR 38.743) Solution for AI/ML-based CCO | Nokia | other | Yes |
No
| available | No | |||||
R3‑244451 | TP on AIML support for CCO | Ericsson, InterDigital | other | Agreement | Yes |
No
| available | No | ||||
R3‑244509 | (TP for TR38.743) Open issues on the CCO use case | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244537 | Remaining issues of AIML-based CCO | LG Electronics Inc. | discussion | Yes |
No
| available | No | |||||
R3‑244538 | (TP to TR 38.743) Remaining issues of AIML-based CCO | LG Electronics Inc. | other | Yes |
No
| available | No | |||||
R3‑244572 | Discussion on AI/ML-based CCO | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244034 | Further Enhancements on AIML CCO as SON use case | Jio | discussion | Discussion | Yes |
Yes
| withdrawn | Yes | ||||
R3‑244063 | Discussion on AIML based CCO De-Centralized beam prediction | Jio | discussion | Discussion | Yes |
Yes
| withdrawn | Yes | ||||
R3‑244071 | Discussion on beam prediction for AIML based CCO | Jio | discussion | Yes |
Yes
| withdrawn | Yes | |||||
R3‑244072 | (TP to TR 38.743) Further Enhancements for AI ML NG-RAN mobility | Jio | discussion | Decision | Yes |
Yes
| withdrawn | Yes | ||||
R3‑244073 | (TP for TR 38.744) Enhancements in AI ML NG-RAN mobility | Jio | discussion | Yes |
Yes
| withdrawn | Yes | |||||
R3‑244438 | TP on AIML support for CCO | Ericsson, InterDigital | other | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
R3‑244644 | Response to R3-244085 | Jio | discussion | No |
Yes
| withdrawn | Yes | |||||
11.4 | R18 leftovers | R3‑244440 | Improved granularity for Energy Cost | Ericsson | discussion | Agreement | Yes |
No
| available | No | ||
R3‑244447 | Finer Granularity Energy Cost Discussion | Nokia, Telecom Italia, T-Mobile USA, BT | discussion | Yes |
No
| available | No | |||||
R3‑244298 | Rel-18 AI/ML for NG-RAN leftovers: Energy Saving Enhancements | Huawei | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244089 | Discussion on Finer granularity of Energy Cost | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244164 | Energy Saving Enhancements | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244565 | TP to TR38.743 on Finer granularity of Energy Cost | CMCC,Samsung | other | Approval | Yes |
No
| available | No | ||||
R3‑244040 | Enhancements on AI-ML Network Energy Saving | Jio | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244197 | Discussion on AIML for energy saving | NTT DOCOMO INC.. | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244441 | TP on Improved granularity for Energy Cost | Ericsson | other | Agreement | Yes |
No
| available | No | ||||
R3‑244448 | (TP to TR 38.743) Finer Granularity Energy Cost | Nokia, Telecom Italia, T-Mobile USA, BT | other | Yes |
No
| available | No | |||||
R3‑244512 | (TP for TR 38.743Finer granularity of Energy Cost | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244087 | (TP to 38.743) Mobility Optimization for NR-DC | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244211 | (TP to TR 38.743) AI/ML for mobility in NR-DC | Samsung | pCR | Approval | Yes |
No
| available | No | ||||
R3‑244296 | (TP to TR 38.743) AI/ML-based Mobility Enhancements in NR-DC | Huawei | other | Discussion | Yes |
No
| available | No | ||||
R3‑244453 | Further discussion on Mobility Optimization for NR-DC | Ericsson, InterDigital, AT&T | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244539 | Remaining issues of mobility optimization for NR-DC | LG Electronics Inc. | discussion | Yes |
No
| available | No | |||||
R3‑244574 | (TP to 38.743) Discussion on AIML based Mobility Optimization for NR-DC | CMCC | other | Discussion | Yes |
No
| available | No | ||||
R3‑244443 | Discussion on AI/ML Mobility Optimization for NR-DC | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑244510 | (TP for TR 38.743) Discussion on left over issues on DC and split architecture | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244166 | Split architecture and NR-DC mobility optimization | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244444 | (TP to TR 38.743) Mobility Optimization for NR-DC | Nokia | other | Yes |
No
| available | No | |||||
R3‑244454 | TP on Mobility Optimization for NR-DC | Ericsson, InterDigital, AT&T | other | Agreement | Yes |
No
| available | No | ||||
R3‑244540 | (TP to TR 38.743) Remaining issues of mobility optimization for NR-DC | LG Electronics Inc. | other | Yes |
No
| available | No | |||||
R3‑244566 | TP to TR38.743 Discussion on AIML for split architecure use cases | CMCC,ZTE,Lenovo,Qualcomm | other | Approval | Yes |
No
| available | No | ||||
R3‑244446 | (TP to TR 38.743) Split Architecture Support for the Rel-18 AI/ML Use Cases | Nokia, Telecom Italia, Huawei | other | Yes |
No
| available | No | |||||
R3‑244088 | (TP to 38.743) Support of AI/ML NG-RAN in split architecture | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244212 | (TP to TR 38.743) AI/ML for NG-RAN in split architecture | Samsung | pCR | Approval | Yes |
No
| available | No | ||||
R3‑244297 | (TP to TR 38.743) Split architecture support for Rel-18 “AI/ML for NG-RAN” use cases | Huawei | other | Discussion | Yes |
No
| available | No | ||||
R3‑244417 | Further discussion on AI/ML for split architecture use cases | Ericsson | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244418 | TP on Split architecture support for Rel-18 use cases | Ericsson | other | Agreement | Yes |
No
| available | No | ||||
R3‑244445 | On the Support of Split Architecture for the Rel-18 AI/ML Use Cases | Nokia, Telecom Italia, Huawei | discussion | Yes |
No
| available | No | |||||
R3‑244314 | Discussion on other leftover issues | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244315 | TP to 38.743 for other leftover issues | Lenovo | other | Approval | Yes |
No
| available | No | ||||
R3‑244449 | Continuous Management-based MDT | Nokia, Telecom Italia, Qualcomm | discussion | Yes |
No
| available | No | |||||
R3‑244086 | (TP to 38.743) Continuous MDT collection enhancements | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244165 | Continuous MDT collection for AI/ML | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244213 | (TP to TR 38.743) Continuous MDT collection targeting the same UE across RRC states | Samsung | pCR | Approval | Yes |
No
| available | No | ||||
R3‑244251 | Discussion on Continuous MDT measurement | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244252 | (TP to 38.743) Support of Continuous MDT measurement | China Telecom | other | Approval | Yes |
No
| available | No | ||||
R3‑244293 | Discussion on Continuous MDT | Qualcomm Incorporated | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244299 | On Continuous MDT for AI/ML | Huawei | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244350 | (TP for TR 38.743) TP on Continuous MDT feasibility | Ericsson, InterDigital, Deutsche Telekom | other | Agreement | Yes |
No
| available | No | ||||
R3‑244351 | Continuous MDT feasibility | Ericsson, InterDigital, Deutsche Telekom | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244450 | (TP to TR 38.743) Towards a Continuous Management-based MDT solution | Nokia, Telecom Italia, Qualcomm | other | Yes |
No
| available | No | |||||
R3‑244567 | TP to TR38.743 on continuous MDT | CMCC | other | Approval | Yes |
No
| available | No | ||||
R3‑244511 | (TP for TR 38.743)Enhancement of UE performance metrics | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244041 | Enhancements for AI ML Energy Savings | Jio | discussion | Discussion | Yes |
Yes
| withdrawn | Yes | ||||
R3‑244046 | (TP for TR 38.744) AI/ML NG-RAN mobility | Jio | discussion | Decision | Yes |
Yes
| withdrawn | Yes | ||||
R3‑244047 | (TP to TR 38.743) Enhancements for AI ML NG-RAN mobility | Jio | discussion | Yes |
Yes
| withdrawn | Yes | |||||
R3‑244352 | Network Energy Saving for EC in mobility | Jio | discussion | Discussion | Yes |
Yes
| withdrawn | Yes | ||||
R3‑244439 | TP on Mobility Optimization for NR-DC | Ericsson, InterDigital | other | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
12 | Additional topological enhancements for NR SI (RAN3-led) |   | ||||||||||
12.1 | General | R3‑244029 | TR skeleton for additional topological enhancements for NR | NTT DOCOMO INC., AT&T | draft TR | Endorsement | Yes |
No
| available | No | R3‑243970 | |
12.2 | Wireless Access Backhaul (WAB) | R3‑244019 | LS on questions regarding FS_VMR_Ph2 | SA2(Samsung) | LS in | Discussion | Yes |
No
| available | No | ||
R3‑244140 | (draft Reply LS) Discussion on reply LS to SA2 on questions regaring VS_VMR_Ph2 | Qualcomm Inc. | other | Discussion | Yes |
No
| available | No | ||||
R3‑244526 | Discussion on the Architecture, access control and QoS mappingsupport of WAB | Huawei | pCR | Yes |
No
| available | No | |||||
R3‑244338 | (TP to TR 38.799) Discussion on WAB mobility | Nokia, Nokia Shanghai Bell | other | Yes |
No
| available | No | |||||
R3‑244270 | (pCR for TR 38.799): Handling of Reliability and Latency for WAB | Ericsson | pCR | Agreement | Yes |
No
| available | No | ||||
R3‑244118 | (TP to TR 38.799) Discussion on supporting WAB and the reply LS to SA2 | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244119 | (TP to TR 38.799) Discussion on WAB mobility | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244120 | (TP to TR 38.799) Discussion on other aspects in WAB | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244121 | Discussion on Network Selection for WAB | Fraunhofer IIS, Fraunhofer HHI | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244141 | (TP to TR 38.799) Remaining issues for WAB | Qualcomm Inc. | other | Discussion | Yes |
No
| available | No | ||||
R3‑244142 | (TP to TR 38.799) Conclusion of study on WAB | Qualcomm Inc. | other | Discussion | Yes |
No
| available | No | ||||
R3‑244154 | Discussion on the architecture and mobility for WAB | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244231 | (TP to TR 38.799 & draft reply LS) On WAB architecture and authorization | CATT | other | Discussion | Yes |
No
| available | No | ||||
R3‑244232 | (TP to TR 38.799) Discussion on WAB mobility | CATT | other | Discussion | Yes |
No
| available | No | ||||
R3‑244233 | (TP to TR 38.799) Discusson on resource multiplexing for WAB | CATT | other | Discussion | Yes |
No
| available | No | ||||
R3‑244269 | (pCR for TR 38.799): Functional Aspects of WAB-Nodes | Ericsson | pCR | Agreement | Yes |
No
| available | No | ||||
R3‑244271 | Reply to SA2 Questions Regarding UE Access Control and Additional ULI | Ericsson | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244316 | Discussion on architecture and QoS mapping for WAB | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244317 | (TP to TR 38.799) Discussion on WAB-gNB migration | Lenovo | other | Approval | Yes |
No
| available | No | ||||
R3‑244318 | (TP to TR 38.799) Discussion on resource multiplexing for WAB node | Lenovo | other | Approval | Yes |
No
| available | No | ||||
R3‑244334 | Discussion on enhancements for WAB | CANON Research Centre France | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244337 | (TP to TR 38.799) Discussion on Xn support for WAB-gNB and Traffic Mapping | Nokia, Nokia Shanghai Bell | other | Yes |
No
| available | No | |||||
R3‑244339 | Discussion on SA2 LS | Nokia, Nokia Shanghai Bell | discussion | Yes |
No
| available | No | |||||
R3‑244392 | (TP for TR 38.799) Remaining open issues in WAB | LG Electronics | other | Yes |
No
| available | No | |||||
R3‑244394 | (TP for TR 38.799) Access control and location information in WAB | LG Electronics | other | Yes |
No
| available | No | |||||
R3‑244395 | Reply LS on questions regarding FS_VMR_Ph2 | LG Electronics | LS out | Agreement | Yes |
No
| available | No | ||||
R3‑244527 | Discussion on WAB mobility and other some remaining issues | Huawei | pCR | Yes |
No
| available | No | |||||
R3‑244528 | Discussion on SA2's LS (S2-2407345) on questions regarding FS_VMR_Ph2 | Huawei | discussion | Yes |
No
| available | No | |||||
R3‑244541 | (TP to TR 38.799) Discussion on support WAB | Samsung | pCR | Agreement | Yes |
No
| available | No | ||||
R3‑244542 | Discussion on WAB mobility | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244543 | (draft Reply LS) Discussion on LS for VMR from SA2 | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244562 | On WAB Awareness and Authorization | China Telecom | discussion | Yes |
No
| available | No | |||||
R3‑244563 | On Xn Connection Management | China Telecom | discussion | Yes |
No
| available | No | |||||
R3‑244631 | Discussion on Wireless Access Backhaul | NTT DOCOMO INC. | discussion | Yes |
No
| available | No | |||||
12.3 | 5G Femto | R3‑244012 | Reply LS on Support of UE move between CAG cell of 5G Femto and CSG cell | RAN2(LGE) | LS in | Discussion | Yes |
No
| available | No | ||
R3‑244415 | Answer to SA2 LS on UE Move between CAG cell and CSG cell | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑244167 | (Draft reply LS) Mobility between CAG cell and CSG cell | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244143 | (draft Reply LS) Discussion on reply LS to SA2 on Support of UE move between CAG cell of 5G Femto and CSG cell | Qualcomm Inc. | other | Discussion | Yes |
No
| available | No | ||||
R3‑244369 | (Non-Opinionated) Analysis of CAG-CSG Mobility Support | Ericsson, NTT Docomo, Huawei, ZTE, LG Electronics Inc., Deutsche Telekom | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244319 | Discussion on interworking between CAG and CSG cells | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244258 | (TP to TR 38.799) On Access Control and Mobility for NR Femto | China Telecom | other | Agreement | Yes |
No
| available | No | ||||
R3‑244320 | (TP to TR 38.799) Access control and handover for NR Femto with CAG | Lenovo | other | Approval | Yes |
No
| available | No | ||||
R3‑244545 | (TP to TR 38.799) Discussion on access control and handover for NR Femto | Samsung | pCR | Agreement | Yes |
No
| available | No | ||||
R3‑244171 | (TP to TR 38.799)Discussion on architecture and access control of NR Femto | ZTE Corporation | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244371 | NR Femto Node Access Control with CAG | Ericsson | pCR | Agreement | Yes |
No
| available | No | R3‑243409 | |||
R3‑244590 | Discussion on access control for 5G Femto with CAG | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244416 | [TP for TR 38.799] Temporary Access Control for NR Femtos and Mobility | Nokia | other | Yes |
No
| available | No | |||||
R3‑244236 | (TP to TR 38.799) On 5G Femto access control mechanism | CATT | other | Discussion | Yes |
No
| available | No | ||||
R3‑244321 | Local services for NR Femto via collocated local UPF | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244172 | (TP to TR 38.799)Discussion on support of local services | ZTE Corporation | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244101 | (TP for TR 38.799) Access to local services from the 5G Femto via distributed UPF | Huawei | other | Approval | Yes |
No
| available | No | ||||
R3‑244144 | Support of local services with UPF at NR Femto | Qualcomm Inc. | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244259 | (TP to TR 38.799) On local service access for NR Femto | China Telecom | other | Agreement | Yes |
No
| available | No | ||||
R3‑244530 | Discussion on the access control for NR Femto | Huawei | pCR | Yes |
No
| available | No | |||||
R3‑244372 | Access to Local Services via Local UPF | Ericsson | pCR | Agreement | Yes |
No
| available | No | R3‑243411 | |||
R3‑244419 | [TP for TR 38.799] Access to Local Services | Nokia | other | Yes |
No
| available | No | |||||
R3‑244414 | [TP for TR 38.799] Conclusion on NR Femto Architecture Options | Nokia, TMO US, AT&T, Verizon Wireless, British Telekom, NTT Docomo, KDDI, Charter | other | Yes |
No
| available | No | |||||
R3‑244173 | (TP for TR 38.799)Evaluation of NR Femto Architecture Options | ZTE Corporation | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244202 | (TP to TR 38.799) Proposals on NR Femto Architecture | Baicells | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244544 | (TP to TR 38.799) Discussion on Femto architecture | Samsung | pCR | Agreement | Yes |
No
| available | No | ||||
R3‑244234 | (TP to TR 38.799) Discussion on 5G Femto architecture | CATT | other | Discussion | Yes |
No
| available | No | ||||
R3‑244370 | Discussion and Potential Conclusions for NR Femto | Ericsson | pCR | Agreement | Yes |
No
| available | No | ||||
R3‑244589 | Discussion on 5G Femto architecture | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244529 | Discussion on the architecture for NR Femto | Huawei | pCR | Yes |
No
| available | No | |||||
R3‑244632 | Discussion on 5G Femto | NTT DOCOMO INC. | discussion | Yes |
No
| available | No | |||||
R3‑244145 | Conclusion of study on NR Femto | Qualcomm Inc. | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244168 | NR femto | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244396 | (TP for TR 38.799) Remaining open issues in 5G Femto | LG Electronics | other | Yes |
No
| available | No | |||||
R3‑244235 | (TP to TR 38.799) On 5G Femto local service access | CATT | other | Discussion | Yes |
No
| available | No | ||||
R3‑244591 | Draft Reply LS to request clarification on the potential baseline system architecture of 5G NR Femto | CMCC | LS out | Agreement | Yes |
No
| available | No | ||||
13 | NR Mobility Enhancements WI |   | ||||||||||
13.1 | General |   | ||||||||||
13.2 | Support for inter-CU LTM | R3‑244022 | Reply LS to RAN2 on security handling for inter-CU LTM in non-DC cases | SA3(Apple) | LS in | Discussion | Yes |
No
| available | No | ||
R3‑244273 | Common impact in RAN3 for security key update | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244253 | Discussion on signaling enhancement for inter-CU LTM | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244152 | inter-CU LTM issues | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244180 | Discussion on Early Sync and CFRA resource configurations in inter-CU LTM | discussion | Agreement | Yes |
No
| available | No | |||||
R3‑244198 | Discussion on inter-CU LTM non-DC case | NTT DOCOMO INC.. | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244584 | Discussion on inter-CU LTM | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244204 | Data forwarding and transmission in Inter-CU LTM | Rakuten Mobile, Inc | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244483 | Discussion on Inter-CU LTM procedure | Huawei | discussion | Yes |
No
| available | No | |||||
R3‑244355 | Further discussion on XnAP signaling for inter-CU LTM | Ericsson | discussion | Yes |
No
| available | No | |||||
R3‑244042 | Discussion on Inter-gNB-CU LTM Procedure | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑244055 | Discussion on inter-CU LTM | ZTE Corporation | discussion | Yes |
No
| available | No | |||||
R3‑244476 | Further discussion on Inter-CU LTM signaling design | LG Electronics Inc. | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244322 | General aspects of inter-CU LTM | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244272 | Discussion for Inter-CU LTM | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244559 | Discussion on Inter-gNB-CU LTM | Samsung | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244229 | Signalling enhancements for inter-CU LTM HO | Qualcomm Incorporated | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244203 | Resource management Inter-CU LTM | Rakuten Mobile, Inc | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244043 | Discussion on RRC Implications to RAN3 Signaling for Inter-gNB-CU LTM | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑244560 | Additional discussion on Inter-gNB-CU LTM | Samsung | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244228 | Inter-gNB LTM with no change of RRC/PDCP anchor | Qualcomm Incorporated, NTT DOCOMO, Vodafone, Bharti AirTel (India), Sony | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244482 | Discussion on the PDCP anchor based solution | Huawei, Ericsson, CATT, China Telecom, CMCC, Samsung | discussion | Yes |
No
| available | No | |||||
R3‑244646 | Response to R3-244482 | Qualcomm Incorporated | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244484 | (TP for LTM BLCR for TS38.300): Inter-CU LTM basic procedure | Huawei | other | Yes |
No
| available | No | |||||
R3‑244357 | (TP for TS 38.300) Stage-2 signalings for inter-CU LTM | Ericsson | other | Yes |
No
| available | No | |||||
R3‑244056 | TP to 38.300 for inter-CU LTM | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244274 | TP for LTM BLCR for TS38.300 | CATT | other | Agreement | Yes |
No
| available | No | ||||
R3‑244324 | [TP for TS 38.300] Inter-CU LTM | Lenovo | other | Approval | Yes |
No
| available | No | ||||
R3‑244044 | TP (BL CR TS 38.401) L1/2 Triggered Mobility (LTM) Procedures | Nokia | other | Yes |
No
| available | No | |||||
R3‑244561 | (TP to BLCR for TS 38.401/38.300) Procedure for Inter-CU/gNB LTM | Samsung | other | Approval | Yes |
No
| available | No | ||||
R3‑244254 | (TP for TS38.420) On support of inter-CU LTM | China Telecom | other | Approval | Yes |
No
| available | No | ||||
R3‑244057 | TP to 38.423 for inter-CU LTM | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244255 | (TP for TS38.423) On support of inter-CU LTM | China Telecom | other | Approval | Yes |
No
| available | No | ||||
R3‑244356 | (TP for TS 38.423) Xn support for inter-CU LTM | Ericsson | other | Yes |
No
| available | No | |||||
R3‑244323 | [TP for TS 38.423] Inter-CU LTM | Lenovo | other | Approval | Yes |
No
| available | No | ||||
R3‑244478 | (TP for NR_Mob_Ph4 TS 38.423) | LG Electronics Inc. | other | Approval | Yes |
No
| available | No | ||||
R3‑244485 | (TP for LTM BLCR for TS 38.473): F1 impact for Inter-CU LTM | Huawei | other | Yes |
No
| available | No | |||||
R3‑244477 | Baseline CR for introducing Rel-19 Mobility enhancement in E1AP | LG Electronics Inc. | CR | Approval | Yes |
No
| available | No | R3‑243529 | |||
13.3 | Support for Conditional LTM |   | ||||||||||
14 | NR NTN Enhancements WI |   | ||||||||||
14.1 | General | R3‑244031 | (BL CR to 38.300) Support for Regenerative Payload in NR NTN | Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei, Dish Networks, Echostar, Eutelsat Group, Xiaomi, Samsung, CMCC, LG Electronics | draftCR | Endorsement | Yes |
No
| available | No | R3‑243949 | |
14.2 | Support MBS broadcast service | R3‑244181 | (TP to NTN BL CRs) Support of MBS broadcast service for NR NTN | CATT | other | Decision | Yes |
No
| available | No | ||
R3‑244342 | (TP to BL CR for TS 38.300) Discussion on the support of MBS Broadcast Service | Nokia, Nokia Shanghai Bell | other | Yes |
No
| available | No | |||||
R3‑244363 | (TP for TS 38.413 and TS 38.300) Support MBS broadcast service | Huawei | other | Agreement | Yes |
No
| available | No | ||||
R3‑244373 | Broadcast Service Area for NR NTN | Ericsson, SES, ESA | discussion | Discussion | Yes |
No
| available | No | R3‑243464 | |||
R3‑244468 | Discussion on NTN broadcast service supporting with TP to TS 38.300 and 38413 | ZTE Corporation | other | Approval | Yes |
No
| available | No | ||||
R3‑244123 | Way forward for MBS Broadcast intended service area discussion | THALES | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244155 | Discussion on NR NTN supporting MBS broadcast service | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244194 | Support of Broadcast service | Xiaomi | other | Approval | Yes |
No
| available | No | ||||
R3‑244246 | Further discussion on support MBS broadcast service for NTN | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244288 | (TP for TS38.300) Discussion on Support for NR NTN MBS Broadcast Service | Qualcomm Incorporated | other | Approval | Yes |
No
| available | No | ||||
R3‑244325 | Support of broadcast service in NTN | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244374 | Broadcast Service Area for NR NTN - NGAP Impacts | Ericsson, SES, ESA | other | Agreement | Yes |
No
| available | No | ||||
R3‑244552 | Discussion on support MBS broadcast service for NR NTN | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244568 | Discussion on Supporting MBS broadcast service for NR NTN | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244635 | Discussion on Support of MBS Broadcasting over NTN access | TCL | discussion | Decision | Yes |
No
| available | No | ||||
14.3 | Support of Regenerative payload | R3‑244051 | Regenerative payload considerations | Eutelsat Group | discussion | Discussion | Yes |
No
| available | No | ||
R3‑244182 | (TP to NTN BL CRs) Support of regenerative payload | CATT | other | Decision | Yes |
No
| available | No | ||||
R3‑244195 | (TP for TS 38.300) Support of regenerative payload | Xiaomi | other | Approval | Yes |
No
| available | No | ||||
R3‑244108 | (TP for TS 38.413) Introduce NG Removal procedure | Nokia, Nokia Shanghai Bell, Huawei, CATT, CMCC, Ericsson, Qualcomm | other | Yes |
No
| available | No | |||||
R3‑244156 | Discussion on NR NTN supporting regenerative NTN | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244200 | Discussion on Xn impact for NR NTN regenerative payload | NTT DOCOMO INC.. | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244201 | Discussion on support of regenerative payload | ETRI | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244247 | Further discussion on support of regenerative payload | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244289 | (TP for TS 38.300) Discussion on NG Signaling impacts for NR NTN Regenerative Payload | Qualcomm Incorporated | other | Yes |
No
| available | No | |||||
R3‑244326 | Mobility issues for regenerative payload in NTN | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244343 | (TP to BL CR for TS 38.300) Discussion on the support of Regenerative payload | Nokia, Nokia Shanghai Bell | other | Yes |
No
| available | No | |||||
R3‑244375 | Further Discussion on NTN Regenerative Payload Issues in Rel-19 | Ericsson, Thales, SES, ESA, Sateliot | discussion | Discussion | Yes |
No
| available | No | R3‑243414 | |||
R3‑244462 | Further discussion on support of regenerative payload | ZTE Corporation | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244479 | Discussion on N2/S1 connection management | LG Electronics Inc. | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244480 | (TP for NR_NTN_Ph3 TS 38.413) | LG Electronics Inc. | other | Approval | Yes |
No
| available | No | ||||
R3‑244547 | (TP for TS 38.410) Support for Regenerative Payload in NR NTN | Huawei, Nokia, Nokia Shanghai Bell, CATT, CMCC, Ericsson, Qualcomm Incorporated | other | Agreement | Yes |
No
| available | No | ||||
R3‑244548 | (TP for BLCR for TS 38.300) Support of regenerative payload | Huawei | other | Agreement | Yes |
No
| available | No | ||||
R3‑244553 | Discussion on support of regenerative payload for NR NTN | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244569 | Discussion on support of regenerative payload for NR NTN | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244634 | Discussion on NTN regenerative architecture | TCL | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244639 | NG Removal – Stage 2 Description | Ericsson, Huawei, Nokia | other | Agreement | Yes |
No
| available | No | ||||
R3‑244364 | (TP for BLCR for TS 38.300) Support of regenerative payload | Huawei | other | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
R3‑244365 | (TP for TS 38.410) Support for Regenerative Payload in NR NTN | Huawei, Nokia, Nokia Shanghai Bell, CATT, CMCC, Ericsson | other | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
R3‑244426 | NG Removal - Stage 2 Description | Ericsson, Huawei | other | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
15 | IoT NTN Enhancements WI |   | ||||||||||
15.1 | General | R3‑244463 | Work Plan for Rel-19 IoT NTN | ZTE Corporation, CATT, MediaTek Inc. | Work Plan | Information | Yes |
No
| available | No | ||
15.2 | Support Full eNB as Regenerative Payload | R3‑244464 | Initial considerations on support of store and forward satellite operation for IoT NTN | ZTE Corporation | discussion | Discussion | Yes |
No
| available | No | ||
R3‑244516 | Discussion on Support of Store and Forward in NTN | THALES, Novamint, Sateliot | discussion | Discussion | Yes |
No
| available | No | R3‑244124 | |||
R3‑244277 | Discussion about UE attachment in Store & Forward | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244196 | Support of Store and Forward in IoT NTN | Xiaomi | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244245 | Support for Store and Forward operation in IoT NTN | China Telecom | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244287 | Discussion on Support for IoT NTN for Regenerative Payload | Qualcomm Incorporated | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244344 | Discussion on the support of Store&Forward | Nokia, Nokia Shanghai Bell | discussion | Yes |
No
| available | No | |||||
R3‑244366 | Support store and forward for IoT NTN | Huawei | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244383 | Support for Regenerative Payload in IoT NTN | Ericsson, Sateliot | other | Agreement | Yes |
No
| available | No | ||||
R3‑244554 | Discussion on support of regenerative payload for IoT NTN | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244570 | Discussion on support of IoT NTN | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244124 | Discussion on Support of Store and Forward in NTN | THALES | discussion | Discussion | No |
Yes
| withdrawn | Yes | R3‑244516 | |||
16 | Ambient IoT SI |   | ||||||||||
16.1 | General | R3‑244030 | (BL pCR to TR 38.769) Study on solutions for Ambient IoT in NR | Huawei, CMCC | pCR | Endorsement | Yes |
No
| available | No | R3‑243972 | |
R3‑244592 | Work Plan for Ambient IoT SI | CMCC, Huawei, T-Mobile USA | Work Plan | Information | Yes |
No
| available | No | ||||
R3‑244014 | LS on RAN2 agreements and assumptions for Ambient IoT | RAN2(OPPO) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑244018 | LS on Clarification of requirements for Ambient IoT | SA2(Ericsson) | LS in | Discussion | Yes |
No
| available | No | ||||
16.2 | RAN Architecture | R3‑244387 | On AIoT RAN functional and logical architecture | Ericsson | discussion | Agreement | Yes |
No
| available | No | ||
R3‑244388 | [TP for TR 38.769] on AIoT Architecture aspects | Ericsson | other | Agreement | Yes |
No
| available | No | ||||
R3‑244427 | Architecture, interfaces and transport for Ambient IoT | Qualcomm Incorporated | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244102 | (TP for TR 38.769) RAN architecture aspects | Huawei | other | Approval | Yes |
No
| available | No | ||||
R3‑244593 | Discussion on RAN Architecture for Ambient IoT | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244058 | (TP for TR38.769) RAN architecture for Ambient-IoT | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244420 | [TP for TR 38.769] AIoT Architecture for Topology 1 and 2 | Nokia | other | Yes |
No
| available | No | |||||
R3‑244139 | [TP for TR 38.769] RAN Architecture for AIoT | InterDigital Communications | other | Decision | Yes |
No
| available | No | ||||
R3‑244148 | A-IoT Architecture | MediaTek Inc. | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244157 | RAN architecture discussion on ambient IoT | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244183 | (TP to TR 38.769) A-IoT architecture aspects | CATT | other | Decision | Yes |
No
| available | No | ||||
R3‑244191 | (TP for TR 38.769) AIoT RAN architecture | Xiaomi | other | Approval | Yes |
No
| available | No | ||||
R3‑244248 | (TP for TR 38.769) RAN architecture for Ambient-IoT | China Telecom | other | Approval | Yes |
No
| available | No | ||||
R3‑244327 | RAN architecture considerations of ambient IoT | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244555 | Discussion on RAN architecture for Ambient IoT | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
16.3 | RAN-CN Interface Impact | R3‑244104 | (TP for TR 38.769) Signalling and Procedures for Topology 1 | Huawei | other | Approval | Yes |
No
| available | No | ||
R3‑244428 | Inventory, Command and device context management for Ambient IoT | Qualcomm Incorporated | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244060 | Discussion on unified procedure for AIoT topology 1 and 2 | ZTE Corporation | discussion | Yes |
No
| available | No | |||||
R3‑244059 | (TP for TR38.769) NG interface impact for Ambient-IoT | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244105 | (TP for TR 38.769) Signalling and Procedures for Topology 2 | Huawei | other | Approval | Yes |
No
| available | No | ||||
R3‑244158 | RAN-CN interface impact on ambient IoT | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244184 | (TP to TR 38.769) Network signalling aspects for Topology 1 | CATT | other | Decision | Yes |
No
| available | No | ||||
R3‑244185 | (TP to TR 38.769) Network signalling aspects for Topology 2 | CATT | other | Decision | Yes |
No
| available | No | ||||
R3‑244192 | (TP for TR 38.769) AIoT interface impacts between RAN and CN | Xiaomi | other | Approval | Yes |
No
| available | No | ||||
R3‑244328 | Inventory procedure of ambient IoT | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244329 | Context Management and Data Transport of Ambient IOT | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244389 | [TP for TR 38.769] Elements for AIoT RAN – AIoT CN communication and overall signalling | Ericsson | other | Agreement | Yes |
No
| available | No | ||||
R3‑244421 | Inventory Signalling Reusing Paging procedures for AIoT Topology 2 | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑244422 | [TP for TR 38.769] Inventory Signalling reusing Paging procedures for AIoT Topology 2 | Nokia | other | Yes |
No
| available | No | |||||
R3‑244423 | [TP for TR 38.769] Data Transport and Context Management for AIoT | Nokia | other | Yes |
No
| available | No | |||||
R3‑244556 | Discussion on RAN-CN interface impact for Ambient IoT | Samsung | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244564 | Discussion on RAN-CN interface for Ambient IoT | China Telecom | discussion | Yes |
No
| available | No | |||||
R3‑244594 | Discussion on paging for Ambient IoT | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244595 | Discussion on Device Context Management and Data Transfer | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244607 | Discussion on NG impact for Ambient IoT | LG Electronics | discussion | Yes |
No
| available | No | |||||
16.4 | Others | R3‑244596 | Discussion on locating Ambient IoT device | CMCC | discussion | Discussion | Yes |
No
| available | No | ||
R3‑244061 | (TP for TR38.769) Locating an AIoT device | ZTE Corporation | other | Yes |
No
| available | No | |||||
R3‑244103 | (TP for TR 38.769) Ambient IoT device locating | Huawei | other | Approval | Yes |
No
| available | No | ||||
R3‑244159 | Further discussion on ambient IoT locating | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244186 | (TP to TR 38.879) Locating of A-IoT device | CATT | other | Decision | Yes |
No
| available | No | ||||
R3‑244193 | (TP for TR 38.769) Locating AIoT device | Xiaomi | other | Approval | Yes |
No
| available | No | ||||
R3‑244390 | [TP for TR 38.769] On locating AIoT devices | Ericsson | other | Agreement | Yes |
No
| available | No | ||||
R3‑244429 | Methods for locating Ambient IoT devices | Qualcomm Incorporated | discussion | Discussion | Yes |
No
| available | No | ||||
17 | Network ES Enhancements WI |   | ||||||||||
17.1 | General | R3‑244347 | WI Work plan for R19 Network Energy Savings | Ericsson | discussion | Yes |
No
| available | No | |||
17.2 | Support on-demand SSB SCell operation | R3‑244237 | On support on-demand SSB SCell operation | CATT | discussion | Decision | Yes |
No
| available | No | ||
R3‑244106 | (TP for TS 38.473) Discussion on on-demand SSB SCell operation | Huawei | other | Yes |
No
| available | No | |||||
R3‑244348 | On-demand SSB SCell operation | Ericsson | discussion | Yes |
No
| available | No | |||||
R3‑244169 | Support on-demand SSB operation | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244214 | Discussion on on-demand SSB SCell operation in low-carbon green network | Samsung | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244330 | Discussion on On-demand SSB for SCell | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244380 | On-Demand SSB SCell operation for UEs in connected mode | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑244465 | Further discussion on on-demand SSB Scell operation | ZTE Corporation | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244576 | (TP for TS 38.473) Discussion on On-Demand SSB SCell Operation | CMCC | other | Discussion | Yes |
No
| available | No | ||||
17.3 | Support on-demand SIB1 for UEs | R3‑244349 | On-demand SIB1 transmission | Ericsson | discussion | Yes |
No
| available | No | |||
R3‑244331 | Discussion on On-demand SIB1 for Idle/Inactive UE | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244466 | Further discussion on on-demand SIB1 | ZTE Corporation | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244146 | Aspects of on-demand SIB1 for NES enhancements | Qualcomm Inc. | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244107 | Discussion on on-demand SIB1 for UEs in idle or inactive mode | Huawei | discussion | Yes |
No
| available | No | |||||
R3‑244170 | Support on-demand SIB1 | NEC | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244215 | Discussion on on-demand SIB1 in low-carbon green network | Samsung | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244238 | On support on-demand SIB1 for idle UE | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244381 | Open Issues in support of On-Demand SIB1 | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑244577 | Support On-Demand SIB1 for UEs | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244633 | Discussion on OD-SIB1 | Rakuten Mobile, Inc | discussion | Yes |
No
| available | No | |||||
R3‑244645 | Response to R3-244107 | Jio | discussion | No |
Yes
| withdrawn | Yes | |||||
17.4 | Others |   | ||||||||||
18 | NR Low Power WUS/WUR WI |   | ||||||||||
18.1 | General | R3‑244069 | Work plan for Rel-19 WI on LP-WUSWUR | vivo | Work Plan | Approval | Yes |
No
| available | No | ||
18.2 | Support LP-WUS Indicating Paging Monitoring | R3‑244070 | Discussion on signaling design for LP-WUS subgrouping | vivo, NTT DOCOMO INC. | discussion | Discussion | Yes |
No
| available | No | ||
R3‑244513 | Discussion on potential RAN3 impacts of LP-WUS | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244424 | Overview of RAN3 impacts of LP-WUS | Nokia | discussion | Yes |
No
| available | No | |||||
R3‑244095 | (TP to TS 38.413, 38.473, 38.423) Discussion on LP-WUS subgrouping | ZTE Corporation | other | Agreement | Yes |
No
| available | No | ||||
R3‑244605 | Discussion on LP-WUS subgrouping | Samsung | other | Discussion | Yes |
No
| available | No | ||||
R3‑244409 | Discussion of LPWUS impacts on NG-RAN architecture | Ericsson | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244076 | (TP for TS 38.413 and TS 38.423) Discussion on Low-power wake-up signal and receiver for NR | Huawei | other | Yes |
No
| available | No | |||||
R3‑244096 | [draft] LS on LP-WUS subgrouping | ZTE Corporation | other | Approval | Yes |
No
| available | No | ||||
R3‑244147 | Support LP-WUS subgrouping | Qualcomm Inc. | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244199 | Initial discussion on LP-WUS subgrouping | NTT DOCOMO INC.. | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244425 | Support of LP-WUS | Nokia | draftCR | Yes |
No
| available | No | |||||
R3‑244514 | (TP on BLCR for TS 38.300)Support of LP-WUS | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244626 | BLCR for TS 38.300 on support of LP-WUS | vivo | draftCR | Discussion | Yes |
No
| available | No | ||||
R3‑244410 | Introduction of LP-WUS paging monitoring | Ericsson | CR | Endorsement | Yes |
No
| available | No | ||||
R3‑244077 | Introduction of low-power wake-up signal and receiver for NR | Huawei | CR | Yes |
No
| available | No | |||||
R3‑244606 | (TP to BLCR for TS 38.413, 38.423, 38.473) LP-WUS Assistance Information to support subgrouping | Samsung | other | Approval | Yes |
No
| available | No | ||||
R3‑244611 | Discussion on support LP-WUS indicating paging monitoring | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
19 | Evolution of Duplex Operation WI |   | ||||||||||
19.1 | General |   | ||||||||||
19.2 | Support CLI Handling |   | ||||||||||
20 | AI/ML for Air Interface WI |   | ||||||||||
20.1 | General |   | ||||||||||
20.2 | Support Positioning Accuracy Enhancements |   | ||||||||||
21 | NR XR Enhancements WI |   | ||||||||||
21.1 | General | R3‑244032 | (BL CR to 37.340) Support of XR enhancements | ZTE Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Inc, Lenovo, Huawei, Ericsson, CATT, CMCC, Samsung, Xiaomi, NEC | draftCR | Endorsement | Yes |
No
| available | No | R3‑243973 | |
R3‑244033 | Support of XR enhancements | CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC, NEC | CR | Endorsement | Yes |
No
| available | No | R3‑243974 | |||
R3‑244340 | Work Plan for Rel-19 on XR Enhancements for NR | Nokia, Qualcomm (Rapporteurs) | Work Plan | Yes |
No
| available | No | |||||
R3‑244009 | Reply LS on Application-Layer FEC Awareness at RAN | RAN2(Qualcomm) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑244024 | LS Reply to SA2 LS on Application-Layer FEC Awareness at RAN | SA4(Qualcomm) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑244010 | LS on multi-modality awareness at RAN | RAN2(Nokia) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑244008 | Reply LS to SA2 on FS_XRM PH2 | RAN2(Vivo) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑244025 | LS Reply on FS_XRM Ph2 | SA4(Huawei) | LS in | Discussion | Yes |
No
| available | No | ||||
R3‑244045 | LS on FS_XRM Ph2 | SA2(Vivo) | LS in | Discussion | Yes |
No
| available | No | R3‑244020 | |||
R3‑244469 | Discussion on SA2 LS with draft reply LS | ZTE Corporation, China Telecom | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244068 | Discussion on LS from SA2 on LS on FS_XRM Ph2 | vivo | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244332 | Discussion on LS on FS_XRM Ph2 | Lenovo | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244580 | Discussion on SA2’s LS (S2-2407351) on FS_XRM Ph2 | CMCC | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244020 | LS on FS_XRM Ph2 | SA2(Vivo) | LS in | Discussion | Yes |
Yes
| withdrawn | Yes | R3‑244045 | |||
21.2 | Support XR in DC | R3‑244153 | proposed reply to SA2 LS | NEC | discussion | Decision | Yes |
No
| available | No | ||
R3‑244411 | Discussion on SA2 LS questions to RAN3 | Ericsson | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244341 | (TP to BL CR for TS 37.340) Discussion on the support of XR in NR-NR DC | Nokia, Nokia Shanghai Bell | other | Yes |
No
| available | No | |||||
R3‑244531 | (TP for NR_XR_Ph3 BL CR) Discussion on NR-DC support of XR and SA2's LS | Huawei | other | Yes |
No
| available | No | |||||
R3‑244301 | Support for L4S in NR-NR DC | Ericsson, AT&T, BT, T-Mobile USA, Charter Communications, Qualcomm | CR | Agreement | Yes |
No
| available | No | ||||
R3‑244082 | R19 XR DC Remaining Signaling Enhancements | Qualcomm Incorporated | discussion | Agreement | Yes |
No
| available | No | ||||
R3‑244109 | Support of XR enhancements | Nokia, Nokia Shanghai Bell, Lenovo, Qualcomm, Xiaomi, CATT, Ericsson, CMCC, Samsung | draftCR | Endorsement | Yes |
No
| available | No | ||||
R3‑244470 | Further discussion on XR supporting | ZTE Corporation, China Telecom, China Unicom | discussion | Approval | Yes |
No
| available | No | ||||
R3‑244471 | TP to BLCR for 37.340 and 38.423 on XR supporting | ZTE Corporation, China Telecom, Nokia, Nokia Shanghai Bell | other | Approval | Yes |
No
| available | No | ||||
R3‑244579 | Further Discussion on XR Support in DC | CMCC, Lenovo, Xiaomi | discussion | Discussion | Yes |
No
| available | No | ||||
R3‑244578 | (TP to TS 38.423 and 37.340) PDU Set Based Handling Support in DC | CMCC, Lenovo, Qualcomm, Xiaomi, China Unicom | other | Discussion | Yes |
No
| available | No | ||||
R3‑244268 | Discussion on XR in DC | CATT | discussion | Decision | Yes |
No
| available | No | ||||
R3‑244546 | (TP to TS 38.423) Support XR in DC | Samsung | other | Agreement | Yes |
No
| available | No | ||||
R3‑244333 | (TP for 38.340 BLR) Corrections on XR in NR-DC | Lenovo | other | Approval | Yes |
Yes
| withdrawn | Yes | ||||
31 | Corrections and Enhancements to Rel-19 |   | ||||||||||
31.1 | Corrections |   | ||||||||||
31.2 | Enhancements |   | ||||||||||
32 | Any other business | R3‑244161 | Input to 3GPP AI/ML Consistency Alignment SI | NEC | discussion | Decision | Yes |
No
| available | No | ||
33 | Closing of the meeting |   |