Reflective QoS Indication

Description

The Reflective QoS Indication (RQI) is a user-plane flag critical to the operation of the Reflective QoS mechanism in 5G networks. Unlike its control-plane counterpart, the RQA, the RQI is a single-bit indicator embedded within the encapsulation headers of user data packets traveling in the downlink direction. It is typically carried in the GTP-U extension header for N3/N9 interfaces or within the frame structure on the Uu air interface, associated with the QoS Flow ID (QFI). The entity setting the RQI can be the UPF (User Plane Function) or, in some deployments, the gNB, based on policies received from the SMF/PCF.

Architecturally, the RQI operates at the intersection of the user plane and the UE's QoS policy enforcement function. The network, upon determining that a specific downlink packet belongs to a QoS Flow configured for reflective treatment, sets the RQI bit in the packet header. This packet then traverses the N3 and Uu interfaces to the UE. The UE's protocol stack, specifically its SDAP (Service Data Adaptation Protocol) layer in 5G NR or its equivalent, inspects incoming downlink packets. Detection of the RQI bit is the key triggering event.

The mechanism works through a coordinated sequence. First, the UE must have previously received a control-plane QoS rule for that QoS Flow containing the RQA attribute, providing authorization. When the UE receives a downlink packet with the RQI bit set for that authorized flow, it initiates a reflective QoS action. This action involves the UE creating a new uplink QoS rule or updating an existing one. The UE derives the parameters for this uplink rule—such as the 5QI, Allocation and Retention Priority (ARP), and potentially flow-specific filters—from the characteristics of the observed downlink packet flow. The derived rule is then installed in the UE's uplink classifier and marker, ensuring subsequent uplink packets for that application flow receive the appropriate QoS treatment without needing a new request to the SMF.

Its role is to provide a real-time, in-band signaling mechanism that prompts the UE to self-configure its uplink QoS. This decouples the dynamic activation of symmetric QoS from the slower control-plane procedures. It is essential for achieving low latency in service setup, reducing signaling load on the core network, and enabling efficient support for applications where traffic patterns and required resources are mirrored between uplink and downlink. The RQI turns the downlink data stream itself into a control channel for QoS provisioning.

Purpose & Motivation

The RQI was developed to solve the problem of latency and signaling overhead associated with establishing symmetric QoS flows via traditional core-network-centric methods. In pre-5G systems, if an application started generating downlink traffic that required a corresponding uplink QoS flow, the network would need to detect this, formulate a policy (via PCF), instruct the SMF/ PGW, and then signal the new QoS rule to the UE—a process taking hundreds of milliseconds. For real-time interactive services, this delay is unacceptable.

The creation of RQI was motivated by the need for 'zero-touch' or immediate QoS activation. By marking a downlink packet, the network can instantly instruct a properly authorized UE to establish the necessary uplink resources. This is analogous to a network 'nudge' that leverages the existing data path for control. It addresses the limitations of purely reactive, signaling-based approaches which are too slow for URLLC and critical communication use cases envisioned for 5G.

In historical context, QoS markings like DSCP in IP headers provided hints, but the UE's response was not standardized or tied to secure, network-authorized policies. The 3GPP RQI, introduced in Release 15, formalizes this hint mechanism within the 3GPP protocol stack and securely couples it with the control-plane authorization (RQA). This solves the dual problem of speed and security, allowing for rapid adaptation while maintaining network control over which flows can use reflective QoS and what resources they can claim.