Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · QoS

QFI

QoS Flow Identifier

QoS →

QFI is a scalar identifier that uniquely labels a QoS Flow within a 5G PDU Session to enable granular quality-of-service treatment for packet forwarding.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
21 specs
Also in
Services, Radio Access Network
QFI Description Purpose What changed Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define QFI. Each summary describes the whole specification, not only this term.

TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →
TS 24.193Rel-18 → Rel-19

Rel-19 adds MPQUIC-IP and MPQUIC-E steering, an ATSSS status parameter, non-3GPP access path switching, and ATSSS rule provisioning with MPQUIC-IP signalling over EPC-connected 3GPP access.

Full comparison in TS 24.193 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (14 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 4 changes
  • QFI in N9 TS 23.501CR0062
  • Clarifications required resulting from 6-bit QFI limit TS 23.501CR0313
  • QFI and QRI values in 5GSM messages TS 24.501CR0649
  • Presence of the precedence and QFI fields in QoS rules TS 24.501CR0892
Rel-16 4 changes
  • QFI allocation event TS 29.508CR0071
  • Correction for PDU session modification with QFI change. TS 24.501CR1174
  • Semantic error check for duplicate QRI or QFI TS 24.501CR2364
  • Correction of QFI value in QER TS 23.501CR1853
Rel-17 2 changes
  • Error handling for QRI and QFI set to zero by the network TS 24.501CR3695
  • Missing PDU Session ID from QFI allocation event notifications TS 29.508CR0141
Rel-18 1 change
  • Correction on the QFI for the QoS flow of non-default rules TS 24.193CR0131
Rel-19 2 changes
  • QFI allocation, change, and deallocation parameters corrections TS 29.508CR0396
  • Rel-19 CR 32.291 Correction of qFI category TS 32.291CR0638
Rel-20 1 change
  • Corrections on the presence of qfi and 5qi attributes TS 29.508CR0401

Defining Specifications

3GPP specifications that define or reference QFI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 24.193 vk10 ATSSS Stage 3 Procedures Rel-20 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 24.502 vk00 Non-3GPP Access Network Discovery and Selection Rel-20 read
TS 24.890 vg00 5G NAS Protocol for 5GS Stage 3 Rel-16 read
TS 26.510 vj20 5G Media Streaming and Real-Time Communication APIs Rel-19 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TR 26.806 vi00 Technical Report on Smartly Tethering AR Glasses Rel-18 read
TS 26.891 vg00 Media Distribution Services in 5G System Rel-16 read
TR 26.926 vj00 Traffic Models & Quality Evaluation for Media/XR in 5G Rel-19 read
TR 26.928 vj00 Study on eXtended Reality (XR) in 5G Rel-19 read
TS 29.503 vk10 UDM Service Based Interface Rel-20 read
TS 29.508 vk10 Session Management Event Exposure Service Rel-20 read
TS 29.513 vk10 5G PCC Signalling Flows Rel-20 read
TS 29.890 vg00 CT3 5G System Technical Report Rel-16 read
TS 32.255 vk30 5G Data Connectivity Converged Charging Rel-20 read
TS 32.291 vk10 5G Charging Service-Based Interface Rel-20 read
TS 37.324 vj00 Service Data Adaptation Protocol (SDAP) Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.415 vj10 PDU Session User Plane Protocol Rel-19 read
TR 38.835 vi01 Technical Report on XR Enhancements for NR Rel-18 read