Description
The 5G QoS Identifier (5QI) is a fundamental mechanism in 5G System (5GS) architecture for managing Quality of Service. It's a scalar value ranging from 1 to 255, where standardized values (1-89) have predefined QoS characteristics defined in 3GPP specifications, while dynamic values (90-254) can be assigned with operator-specific QoS parameters. Each 5QI value maps to a specific QoS profile containing five key parameters: Resource Type (GBR, Delay Critical GBR, or Non-GBR), Priority Level, Packet Delay Budget (PDB), Packet Error Rate (PER), and Averaging Window (for GBR flows only).
When a Protocol Data Unit (PDU) Session is established, the 5G Core Network (5GC) assigns one or more QoS Flows identified by their 5QI values. The Access and Mobility Management Function (AMF) communicates these QoS requirements to the Radio Access Network (RAN) via the N2 interface. The RAN then maps each QoS Flow to appropriate Data Radio Bearers (DRBs) using QoS Flow to DRB mapping rules. This hierarchical approach separates QoS control (in 5GC) from bearer management (in RAN), providing flexibility and scalability.
The 5QI mechanism works through standardized signaling procedures. During PDU Session Establishment or Modification, the Session Management Function (SMF) determines the appropriate 5QI based on the service requirements and subscriber profile. The SMF sends this information to the User Plane Function (UPF) for packet marking and to the RAN via the AMF. In the user plane, packets are marked with QoS Flow Identifiers (QFIs) derived from 5QI values, enabling consistent QoS treatment across network nodes. The RAN uses these markings to apply appropriate scheduling, admission control, and link layer configurations.
Key architectural components involved in 5QI implementation include the Policy Control Function (PCF), which provides policy rules containing 5QI assignments; the SMF, which enforces these policies; the UPF, which performs packet marking and rate policing; and the gNB, which implements radio resource scheduling based on 5QI parameters. The system supports both reflective QoS, where the UE can derive QoS rules from downlink traffic, and explicit QoS signaling via NAS and RRC protocols.
5QI plays a critical role in enabling network slicing and service differentiation. Different network slices can use different 5QI values to achieve their specific performance requirements. The standardized 5QI values cover a wide range of services including conversational voice, live streaming, autonomous driving, industrial automation, and massive IoT applications. This standardized approach ensures interoperability between different vendors' equipment and consistent QoS experience for end users.
Purpose & Motivation
5QI was created to address the limitations of previous QoS mechanisms in 4G/LTE networks, particularly the QCI (QoS Class Identifier). While QCI served well for 4G services, it lacked the granularity and flexibility needed for 5G's diverse use cases including ultra-reliable low-latency communications (URLLC), enhanced mobile broadband (eMBB), and massive machine-type communications (mMTC). The 4G system's bearer-based QoS model was too rigid for 5G's service-based architecture and network slicing requirements.
5QI solves several key problems: First, it provides finer granularity for delay-critical services with specific values for industrial automation, intelligent transport systems, and remote control applications. Second, it introduces the Delay Critical GBR resource type specifically for URLLC services requiring both guaranteed bitrate and strict latency bounds. Third, 5QI enables more efficient resource utilization through improved priority handling and the separation of QoS control from bearer management.
The historical context for 5QI development includes the need to support vertical industry requirements identified in 3GPP Study Items like TR 22.891 and TR 22.804. These studies revealed that previous QoS mechanisms couldn't adequately support services with conflicting requirements operating simultaneously on the same device, such as augmented reality (requiring high bandwidth) and vehicle-to-everything communication (requiring ultra-low latency). 5QI provides the foundation for meeting these diverse requirements through standardized yet flexible QoS profiles.
What changed in its specifications
The latest release-to-release comparison of specifications that define 5QI. Each summary describes the whole specification, not only this term.
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 →Rel-19 adds satellite NG-RAN access text, LP-WUS/WUR assistance and disabling, ATUC RAT utilization control, and network-controlled slice selection with S-NSSAI time validity to TS 24.501. It also adds ATSSS Phase 4 multi-access and 5G ProSe multi-hop relay support.
Full comparison in TS 24.501 →Technology family
Sessions, bearers and QoS · Core Network
- R96 PDP context
- R99 ARP, GBR, Radio Access Bearer (RAB), TFT, UMTS bearer service
- Rel-7 IP-CAN bearer, IP-CAN session, QCI
- Rel-8 APN-AMBR, Dedicated EPS bearer, Default EPS bearer, EPS bearer, EPS Bearer Identity (EBI), UE-AMBR
- Rel-9 Evolved ARP
- Rel-15 5QI, GFBR, MFBR, PDU Session, QoS Flow, Session-AMBR
- Rel-16 MA PDU Session
- 5QI counterpart in another generation: QCI
“For standardized 5QIs, the QCI is one to one mapped to the 5QI.” TS 23.502
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 5 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
5QI is defined for the first time as a scalar reference to a specific QoS forwarding behaviour (e.g. packet loss rate, packet delay budget) for a 5G QoS Flow, with standardized, pre-configured and dynamically assigned values.
- “A scalar that is used as a reference to a specific QoS forwarding behaviour (e.g. packet loss rate, packet delay budget) to be provided to a 5G QoS Flow.” TS 23.501 v15.13.0
- “The usage of a dynamically assigned 5QI for a QoS Flow requires in addition the signalling of the complete 5G QoS characteristics” TS 23.501 v15.13.0
- “the 5QI value may be used as the QFI of the QoS Flow.” TS 23.501 v15.13.0
Rel-16 changed 5QI handling: extended standardized 5QI to QoS characteristics mapping for V2X, added pre-configured 5QI and CN PDB rules for delay-critical GBR 5QI, and introduced 5QI 86.
- Extension of standardized 5QI to QoS characteristics mapping table to accommodate enhanced V2X requirements TS 23.501CR1735
- “Pre-configured 5QI: Pre-defined QoS characteristics configured in the AN and 5GC and referenced via a non-standardized 5QI value.” TS 23.501 v16.20.0
- 5QI 86 introduction TS 24.501CR1697
Rel-17 adds new standardized 5QI values for Advanced Interactive Services, a PDB value for 5QI 10, and 5QI determination for satellite access and backhaul.
- “New standardized 5QI values for Advanced Interactive Services” TS 23.501 v17.15.0
- PDB value for 5QI 10 TS 23.501CR3029
- 5QI value for services carried over satellite access/backhaul TS 29.513CR0284
5QI gained new behaviour in Rel-18: QoS constraints may now include 5QI Priority Level, new 5QIs were added for V2X/A2X via MBS, and pre-configured 5QI use is allowed when roaming.
- “The QoS constraints may contain 5QI(s), 5QI Priority Level and ARP for the QoS Flow associated with the default QoS rule” TS 23.501 v18.12.0
- “NOTE: Pre-configured 5QI values can be used when the UE is roaming if allowed by SLA between the operators.” TS 23.501 v18.12.0
- 5QI for AIML services TS 23.501CR4473
Rel-19 clarifies 5QI use for satellite access in TS 23.501, corrects the description of a 5QI value in TS 24.501, and adds MPS Action to the inputs for deriving the 5QI in TS 29.513.
- Clarification on 5QI for satellite access TS 23.501CR6252
- Correction on the wrong descprition of 5QI value TS 24.501CR6431
- “The MPS specific algorithm shall consider various inputs, including the received MPS Identifier, MPS Action and Reservation Priority, as applicable for the service, for deriving the 5QI.” TS 29.513 v19.6.0
Defining Specifications
3GPP specifications that define or reference 5QI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.822 vg00 | Satellite Access in 5G Study | Rel-16 read |
| TR 22.832 vh40 | Study on cyber-physical control in vertical domains | Rel-17 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TR 23.764 vh10 | Study on V2X Application Layer Enhancements | Rel-17 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.502 vj60 | 5G Multicast-Broadcast User Services | Rel-19 read |
| TR 26.928 vj00 | Study on eXtended Reality (XR) in 5G | Rel-19 read |
| TS 28.802 vf00 | Management Study for 5G Network Architecture | Rel-15 read |
| TS 29.061 vk10 | Packet Domain Interworking Requirements | Rel-20 read |
| TS 29.513 vk10 | 5G PCC Signalling Flows | Rel-20 read |
| TS 29.518 vk10 | AMF Service Based Interface | Rel-20 read |
| TS 29.520 vk10 | 5G NWDAF Services | Rel-20 read |
| TS 29.543 vk10 | Data Transfer Policy Control Services | Rel-20 read |
| TS 29.866 vj00 | IMS Disaster Prevention & Restoration Enhancement | Rel-19 read |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 read |
| TS 37.473 vj00 | W1 Application Protocol (W1AP) Specification | Rel-19 read |
| TS 37.483 vj40 | E1 Application Protocol (E1AP) | Rel-19 read |
| TS 38.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |
| TS 38.413 vj40 | NG Application Protocol (NGAP) Specification | Rel-19 read |
| TS 38.414 vj00 | NG Interface User Plane Protocol | Rel-19 read |
| TS 38.423 vj40 | NG-RAN Xn Application Protocol | Rel-19 read |
| TS 38.463 vj00 | E1 Application Protocol (E1AP) | Rel-19 read |
| TS 38.473 vj40 | F1 Application Protocol (F1AP) | Rel-19 read |