Description
The QoS Flow Identifier (QFI) is a 6-bit field (values 0-63) that serves as the primary handle for QoS management in the 5G user plane. Defined extensively in 3GPP TS 23.501 (system architecture) and TS 38.415 (NG user plane protocol), a QoS Flow is the finest granularity of QoS differentiation in a 5G PDU Session. Each QoS Flow is characterized by a set of QoS parameters, such as 5G QoS Identifier (5QI), Allocation and Retention Priority (ARP), Guaranteed Flow Bit Rate (GFBR), and Maximum Flow Bit Rate (MFBR). The QFI uniquely tags all packets belonging to a specific QoS Flow between the User Plane Function (UPF) and the gNodeB (gNB).
Architecturally, the QFI is assigned by the Session Management Function (SMF) during QoS Flow establishment or modification. The SMF determines the need for a new QoS Flow based on policy requests from the Policy Control Function (PCF) or application function, or from the UE via QoS Rules. Once assigned, the QFI is communicated to the gNB and UPF. In the data plane, the QFI is encapsulated within the General Packet Radio Service Tunneling Protocol for the user plane (GTP-U) header on the N3 (gNB-UPF) and N9 (inter-UPF) interfaces, specifically in the PDU Session Container extension header. This allows every intermediate node to identify the flow without deep packet inspection.
How it works involves consistent mapping throughout the data path. When the UPF receives uplink data, it classifies packets to a QoS Flow based on Packet Detection Rules (PDRs), marks them with the corresponding QFI in the GTP-U header, and forwards them to the gNB. The gNB uses the QFI to map the packets to the appropriate Data Radio Bearer (DRB) for over-the-air transmission, applying the corresponding QoS profile (scheduling, link-layer configuration). In the downlink, the gNB may also mark the QFI based on UE QoS Rules. This end-to-end tagging ensures that the QoS treatment is consistent across the radio and core network segments, enabling features like reflective QoS and efficient support for network slicing.
Purpose & Motivation
The QoS Flow Identifier (QFI) was introduced in 3GPP Release 15 as a cornerstone of the new 5G QoS model, designed to overcome limitations of the 4G Evolved Packet System (EPS) bearer model. In LTE, QoS was tied to EPS bearers, which were relatively static constructs linking a QoS Class Identifier (QCI) to a specific tunnel (GTP TEID). This model was inefficient for sessions requiring multiple concurrent services with dynamic QoS needs, as each new QoS requirement often necessitated a new bearer, increasing signaling overhead and radio resource complexity.
QFI solves this by decoupling the QoS logic from the transport tunnel. A single PDU Session (analogous to an EPS bearer) can support multiple QoS Flows, each identified by a QFI and with independent QoS characteristics. This allows for dynamic addition, modification, or removal of QoS Flows within an existing session with minimal signaling. The primary motivation was to support 5G's diverse service landscape—from massive IoT to critical communications—where a single device (e.g., an autonomous vehicle) might simultaneously run navigation, sensor data, and infotainment applications, each with vastly different latency, reliability, and bandwidth needs.
Furthermore, QFI enables more flexible network slicing. Different slices can employ different mappings between QFIs and radio resources. It also facilitates edge computing and local breakout scenarios by providing a clear QoS identifier that is understood by both the core and access network. By being a small, in-band header field, QFI allows for efficient, scalable packet processing in high-speed user plane functions, which is critical for meeting 5G's performance targets. It represents a shift towards a more fluid, service-driven QoS architecture.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (13 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the QFI was newly introduced as a core identifier for QoS Flows, carried in the encapsulation header on the N3 and N9 interfaces to ensure consistent traffic forwarding treatment within a PDU Session. Its usage was specified for procedures like PDU Session Establishment and Modification, where it is provided to the (R)AN and included within QoS rules and 5GSM messages sent to the UE. The release also defined its role in Reflective QoS control, where the QFI in a downlink packet, along with an RQI, enables the UE to create or update UE-derived QoS rules.
In Release 16, the specification introduced new procedures and corrections for handling the QoS Flow Identifier (QFI). This included defining a QFI allocation event, correcting procedures for PDU session modification when the QFI changes, and adding semantic checks to prevent duplicate QFI values. Additionally, corrections were made to ensure the accurate reporting of the QFI value in QoS Enforcement Rule (QER) operations.
In Release 17, enhancements were made to the QFI function to improve error handling for scenarios where the network sets the Reflective QoS Indication (RQI) and QFI to zero. Additionally, the specification addressed a gap to ensure that QFI allocation event notifications correctly include the associated PDU Session ID for proper identification.
In Release 18, a correction was specified regarding the assignment of the QFI for the QoS flow of non-default rules. This update ensures proper handling and consistency for QoS flows that are not governed by the default QoS rule within a PDU Session. The change clarifies the procedures for QFI assignment and signaling in these specific scenarios.
- Correction on the QFI for the QoS flow of non-default rules TS 24.193CR0131
In Release 19, the updates to the QFI function focused on correcting procedural parameters for its allocation, change, and deallocation. This included a specific correction to the categorization of the QFI itself to ensure clarity and consistency within the specification framework.
Explore further
Broader topics and technologies where QFI plays a role.
Defining Specifications
3GPP specifications that define or reference QFI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 24.193 vj50 | ATSSS Procedures Specification | Rel-19 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 24.502 vj20 | 5G Core Access via Non-3GPP Networks; Stage 3 | Rel-19 |
| TS 24.890 vg00 | 5G NAS Protocol for 5GS Stage 3 | Rel-16 |
| TS 26.510 vj10 | Media Delivery APIs for 5GMS and RTC Systems | Rel-19 |
| TS 26.804 vj10 | 5G Media Streaming Extensions Study | Rel-19 |
| TR 26.806 vi00 | Technical Report on Smartly Tethering AR Glasses | Rel-18 |
| TS 26.891 vg00 | Media Distribution Services in 5G System | Rel-16 |
| TR 26.926 vj00 | Traffic Models & Quality Evaluation for Media/XR in 5G | Rel-19 |
| TR 26.928 vj00 | Study on eXtended Reality (XR) in 5G | Rel-19 |
| TS 29.503 vj50 | UDM Service Based Interface Stage 3 | Rel-19 |
| TS 29.508 vj40 | 5G Session Management Event Exposure Service | Rel-19 |
| TS 29.513 vj40 | 5G PCC Signalling Flows & QoS Mapping | Rel-19 |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 |
| TS 32.255 vk10 | Telecom Management; Charging for 5G Data Connectivity | Rel-20 |
| TS 32.291 vj40 | Charging Management: Service-Based Interface Protocol | Rel-19 |
| TS 37.324 vj00 | Service Data Adaptation Protocol (SDAP) | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TS 38.415 vj10 | PDU Session User Plane Protocol | Rel-19 |
| TR 38.835 vi01 | Technical Report on XR Enhancements for NR | Rel-18 |