Description
The Reflective QoS flow to DRB mapping Indication (RDI) is a fundamental concept within the 5G Quality of Service (QoS) framework, specifically defined for the User Plane. It operates on the principle that the QoS characteristics and requirements for a given service are often symmetrical between the uplink and downlink directions. The network explicitly configures the mapping of downlink QoS Flows to Data Radio Bearers (DRBs) for a UE via RRC signaling. The RDI mechanism allows the UE to observe this downlink mapping and then autonomously apply an identical or 'reflective' mapping for the corresponding uplink QoS Flows onto the same DRBs, without requiring additional explicit RRC configuration messages from the gNB for the uplink. This process is governed by Reflective QoS, where a QoS Flow is marked with a Reflective QoS Indicator (RQI) in the downlink packet headers (via the QFI and RQI markings in the encapsulation protocol, such as GTP-U). When the UE receives downlink packets for a flow with RQI set, it triggers the internal reflective QoS operation, which includes the DRB mapping aspect indicated by RDI. The UE's access stratum monitors these downlink mappings and maintains a reflective mapping for the uplink. This mapping remains valid for a lifetime timer; if no downlink packets for that flow are received before the timer expires, the UE releases the reflective mapping. The RDI concept is tightly integrated with the overall 5G QoS model defined in TS 23.501, where QoS Flows are the finest granularity for QoS differentiation, and DRBs are the radio bearers that actually carry the data. By leveraging RDI, the system achieves efficient and dynamic QoS enforcement with minimal control plane signaling, which is crucial for supporting a massive number of devices and low-latency services where signaling delays must be minimized. The mechanism ensures that the stringent latency, reliability, and bandwidth requirements of uplink traffic (e.g., for interactive services or URLLC) are met by using the same bearer configuration proven suitable for the downlink counterpart.
Purpose & Motivation
RDI was introduced to address the signaling scalability and efficiency challenges in 5G networks, which support an unprecedented density of devices and diverse service requirements. Prior to 5G, QoS bearer management often required explicit bidirectional configuration, leading to significant RRC signaling overhead, especially in scenarios with frequent QoS flow establishment or modification, such as in network slicing or dynamic service adaptation. The reflective QoS concept, including RDI, solves this by shifting part of the intelligence to the UE. It allows the network to configure the downlink path comprehensively and trust the UE to mirror this configuration for the uplink, based on observed network behavior. This is particularly valuable for services like Voice over NR (VoNR), augmented reality, or industrial IoT control, where uplink and downlink streams are inherently paired and have symmetric QoS needs. The reduction in explicit signaling commands speeds up session establishment and modification, reduces latency for time-critical applications, and decreases the processing load on both the gNB and the UE's RRC layer. Historically, LTE utilized dedicated bearers with explicit linking, but the 5G reflective model, enabled by mechanisms like RDI, represents a shift towards more autonomous, lean, and service-aware radio resource management, which is a core design principle for 5G's flexible architecture.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (12 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-4, normative work from Rel-15.
In Release 15, the newly introduced RDI function is not described by the provided grounding context or the listed Change Request titles. The available material discusses concepts like CSG indicators, E-RABs, and service delay, but does not contain any technical details pertaining to the Reflective QoS flow to DRB mapping Indication.
In Release 16, the new RDI function introduced the "Active Time And Strictly Periodic Registration Timer indication" for the +CMICO command. This enhancement provided a procedure indication for managing the back-off timer. Additionally, corrections were made to the AT-command +CIREPI to support non-3GPP VoPS indication.
In Release 17, the new RDI (Reflective QoS flow to DRB mapping Indication) function introduced a specific parameter for EDC policy indication to enhance QoS management. This addition provided a mechanism for more dynamic mapping between QoS flows and Data Radio Bearers (DRBs), as referenced in the context of E-RABs. The update aimed to improve service delivery by refining the association between service request indications and the underlying bearer resources.
In Release 18, the new RDI function introduced the capability for a UE area scope location indication to be used for Quality of Experience (QoE) measurements and reporting. This enhancement allows the network to associate QoE data with a specific geographical area where the service request indication is received. Furthermore, a new AT command, +CPEIPSS, was standardized to configure Paging Early Indication with Paging Subgrouping settings on the terminal.
In Release 19, the RDI function was not updated; the provided Change Request titles and grounding context exclusively detail other functionalities, such as the addition of a disaster roaming indication and definitions for service relationships and delay. There is no information present concerning new technical details, procedures, or capabilities specifically for Reflective QoS flow to DRB mapping Indication in this release.
- Rel-19 CR 32.298 Addition of disaster roaming indication TS 32.298CR1054
Explore further
Broader topics and technologies where RDI plays a role.
Defining Specifications
3GPP specifications that define or reference RDI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TR 23.910 v1400 | UMTS Circuit Switched Bearer Services Overview | Rel-5 |
| TS 27.007 vj40 | AT Command Set for UE | Rel-19 |
| TS 32.250 vj00 | Circuit Switched Offline Charging | Rel-19 |
| TS 32.298 vj30 | Charging Data Record (CDR) Parameter Specification | Rel-19 |
| TS 37.324 vj00 | Service Data Adaptation Protocol (SDAP) | Rel-19 |