Description
UE Initiated Report Indication (UEIRI) is a protocol feature within the 3GPP Radio Access Network (RAN) specifications. It modifies the traditional reporting paradigm where the network (via the gNB) typically triggers reporting by sending a measurement configuration or request to the UE. With UEIRI, the UE is empowered to initiate the transmission of a report based on internal triggers or detected conditions. This report can contain various types of information, such as channel quality measurements (CQI), beamforming information, location data, battery status, or application-layer requirements.
The mechanism works by defining new signaling messages or extending existing ones (e.g., within the RRC protocol or via MAC Control Elements) that the UE can send uplink without a preceding downlink command. The network must be capable of receiving and processing these unsolicited indications. The specifications (38.212, 38.213, 38.214, 38.300) detail the conditions under which a UE may initiate a report, the format of the report content, and how the network should respond. This often involves pre-configuration during connection setup, where the network grants the UE permission for certain types of initiated reports.
Its role is to create a more responsive and efficient RAN. By allowing the UE to report immediately when it detects a significant change (e.g., a sudden drop in signal quality, or entering a power-saving mode), the network can react faster than if it had to poll UEs periodically. This supports enhanced mobility handling, improved QoS management for bursty traffic, and better support for UE-centric features like conditional handover or dynamic power saving.
Purpose & Motivation
UEIRI was created to address limitations in the reactive, network-controlled reporting model, especially for advanced 5G and future 6G scenarios. In traditional systems, the network might not have timely information about sudden UE state changes, leading to delayed handover decisions, inefficient resource allocation, or missed opportunities for energy saving. UEIRI gives the UE a degree of autonomy to inform the network proactively, enabling faster optimization loops.
The motivation stems from use cases requiring low latency and high efficiency, such as ultra-reliable low-latency communication (URLLC), integrated sensing and communication, and advanced mobility in high-frequency bands. It also supports IoT devices that may have very sporadic communication needs; instead of the network constantly polling them, they can report only when necessary. Release 19 introduced UEIRI as part of ongoing enhancements to make the RAN more intelligent and adaptive, reducing control overhead and improving overall system performance.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (105 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the UEIRI (UE Initiated Report Indication) function was newly introduced, specifying procedures for when a UE multiplexes UEIRI with HARQ-ACK on a PUSCH or transmits UEIRI on a PUCCH. The specification details how existing procedures for CG-UCI and SR are adapted by replacing those terms with UEIRI, and it establishes that at most one of CG-UCI, UTO-UCI, or UEIRI can overlap with a PUSCH transmission.
- Delay budget report and MAC CE adaptation for NR for TS 38.300 TS 38.300CR0042
- CR on UE procedure for reporting multiple UCI types TS 38.213CR0033
- Correction on CRC assumption for multi-CSI resource selection and CSI report(s) selection TS 38.213CR0041
- CR on UE procedure for reporting multiple UCI types TS 38.213CR0052
- CR on beta_offset values for UCI reporting in PUSCH TS 38.213CR0062
- CR on PDSCH beam indication TS 38.214CR0017
+ 3 more changes
In Release 16, the UEIRI function was enhanced with specific procedures for multiplexing it with HARQ-ACK on a PUSCH and for its transmission on a PUCCH, where it can also be jointly indicated with an SR. The release introduced clarifications for scenarios where UEIRI overlaps with other UCI types on a PUSCH, stating that at most one of CG-UCI, UTO-UCI, or UEIRI should overlap. Furthermore, the specifications detailed the bitwidth determination and mapping order for associated CSI reports when a CSI-ReportSubConfig is configured alongside UEIRI.
- Aperiodic CSI-RS Triggering for UE reporting beamSwitchTiming values of 224 and 336 TS 38.214CR0060
- Behaviour for triggered with a CSI report for non-active BWP TS 38.214CR0061
- Correction on Transmission configuration indication in DCI format 1_2 TS 38.212CR0057
- Correction on LBT Type and CP Extension Indication for Semi-Static Channel Occupancy TS 38.212CR0063
- Clarify starting slot within DCI 2_5 indication TS 38.213CR0126
- CR to 38.213 on BWP triggering via SCell dormancy indication TS 38.213CR0134
+ 23 more changes
In Release 17, the UEIRI function was enhanced with clarified procedures for its multiplexing with HARQ-ACK on a PUSCH, specifying that it follows the same process as CG-UCI. Additionally, the specification detailed how UEIRI is transmitted on a PUCCH, including rules for its joint indication with Scheduling Requests.
- Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] TS 38.300CR0474
- CR on the description of the SRS resource set indication for PUSCH repetition TS 38.212CR0117
- CR on channel access type indication in non-fallback DCI TS 38.212CR0125
- Correction on the short message indicator when TRS availability indication is present TS 38.212CR0132
- CR on CSI reporting TS 38.212CR0134
- Correction of CSI assumptions over multiplexing NCJT CSI reports in PUCCH TS 38.213CR0354
+ 23 more changes
In Release 18, the UEIRI function was enhanced with new procedures for multiplexing UEIRI with HARQ-ACK on a PUSCH, analogous to the existing rules for CG-UCI. The specification now explicitly states that a UE expects at most one of CG-UCI, UTO-UCI, or UEIRI to overlap with a PUSCH. Furthermore, detailed procedures were defined for transmitting UEIRI on a PUCCH, including handling its potential joint indication with an SR.
- Correction on SDT RRC Release with resume indication [SDT_ReleaseEnh] TS 38.300CR0872
- Correction of RRC parameter names for UTO-UCI indication TS 38.212CR0179
- Correction on SL-U COT sharing flag indication TS 38.212CR0205
- Correction of RRC parameter names and applicable configuration for UTO-UCI indication TS 38.213CR0592
- Correction on sidelink starting symbol index for indications of UL slots in PSBCH in SL-U TS 38.213CR0616
- Correction on priority for LTM CSI report TS 38.213CR0643
+ 23 more changes
In Release 19, the new UEIRI (UE Initiated Report Indication) function was specifically defined for multiplexing with other uplink channels. The release introduced procedures for transmitting UEIRI multiplexed into a PUSCH alongside HARQ-ACK, as well as rules for its transmission on a PUCCH, including provisions for a joint indication with SR.
- Introduction of UE-initiated/event-driven beam management TS 38.214CR0678
- TEI19 Counting of CSI-RS resource referred by N CSI reporting settings [SimCSI_count] TS 38.214CR0681
- Support Aerial UE Flight Information Reporting TS 38.300CR1031
- CR on UEIRI multiplexed into PUSCH in TS 38.212 TS 38.212CR0244
- CR on UEIRI multiplexed into PUSCH in TS 38.213 TS 38.213CR0762
- Correction on sending GW release indication TS 38.300CR1070
+ 3 more changes
Explore further
Broader topics and technologies where UEIRI plays a role.
Defining Specifications
3GPP specifications that define or reference UEIRI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.212 vj10 | NR Multiplexing and Channel Coding | Rel-19 |
| TS 38.213 vj10 | NR Physical Layer Control Procedures | Rel-19 |
| TS 38.214 vj10 | NR Physical Layer Procedures for Data | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |