Description
The Quality of Service Class Identifier (QCI) is a fundamental mechanism within the 3GPP Evolved Packet System (EPS) for managing and enforcing Quality of Service (QoS). It is a standardized integer value, ranging from 1 to 9 in its initial definition and later extended, that maps to a pre-configured set of QoS characteristics. These characteristics are not signaled on a per-bearer basis but are instead node-specific parameters that are pre-provisioned within network elements like the eNodeB, Serving Gateway (S-GW), and Packet Data Network Gateway (P-GW). When a bearer is established or modified, it is associated with a specific QCI. This QCI value acts as a reference pointer, instructing each network node on how to handle the packets belonging to that bearer.
Each QCI value is linked to a specific resource type (Guaranteed Bit Rate - GBR or Non-GBR), priority level, Packet Delay Budget (PDB), and Packet Error Loss Rate (PELR). The priority is an integer where a lower value indicates a higher priority for scheduling. The PDB defines an upper bound for the time a packet may be delayed between the UE and the P-GW (or UE and the RAN node in 5G). The PELR defines an upper bound for a rate of non-congestion related packet losses. For GBR bearers, the QCI also implies the need for admission control based on the guaranteed bit rate. The network uses these parameters to make scheduling, queue management, and link layer configuration decisions to meet the service requirements.
Architecturally, QCI is a core part of the EPS bearer model. It is used in the S5/S8 interface between the S-GW and P-GW, the S1 interface between the eNodeB and the MME/S-GW, and over the radio Uu interface. In the control plane, the MME receives the authorized QCI for a bearer from the P-GW (via the S-GW) and communicates it to the eNodeB during bearer setup. The eNodeB then uses this QCI, along with its locally configured mapping tables, to apply the appropriate radio resource scheduling (e.g., in the MAC layer). In 5G, the QoS model evolved with the 5G QoS Identifier (5QI), which is a direct conceptual successor to QCI, though with an expanded range of standardized values and more flexible parameters for new service types.
Purpose & Motivation
QCI was introduced to solve the critical problem of traffic differentiation and guaranteed service performance in all-IP mobile networks. Prior to 3GPP Release 8 and the EPS, circuit-switched and packet-switched domains were separate, with QoS often tied to specific, rigid bearer services. The move to a flat IP architecture required a new, scalable, and efficient method to manage diverse traffic—from voice and video streaming to web browsing and background file downloads—over a shared infrastructure. QCI provides this by standardizing a limited set of well-understood QoS profiles, enabling multi-vendor interoperability and simplifying network configuration and policy management.
Its creation was motivated by the need to support IMS-based services like Voice over LTE (VoLTE) which demand low latency and guaranteed bandwidth, alongside best-effort internet traffic. Without a mechanism like QCI, all packets would be treated equally, leading to poor user experience for real-time applications. QCI allows operators to create a virtual 'pipe' (the bearer) with specific characteristics for a service or application, ensuring that network resources are allocated appropriately. It abstracts complex per-flow QoS parameters into a simple integer, reducing signaling overhead and enabling fast, consistent policy enforcement across the entire network path from the core to the radio interface.
What changed in its specifications
The latest release-to-release comparison of specifications that define QCI. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.
Full comparison in TS 23.203 →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
- QCI counterpart in another generation: 5QI
“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 14 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.
QCI is specified for the first time in the PCC specifications: PCRF provisions authorized QoS and MBR per QCI, PCC rules carry a QCI, and QCI is mapped to a UMTS QoS profile.
- “4.5.5.5 Provisioning of authorized QoS per QCI” TS 29.212 v7.16.0
- “Each QoS Class Identifier (QCI) parameter value has a 1:1 mapping to a set of QoS parameters defined for GPRS” TS 23.203 v7.14.1
- “The selected bearer shall have the same QCI as the one indicated by the PCC rule.” TS 29.213 v7.12.0
QCI is defined for the first time in Rel-8 EPS specs as a scalar referencing node-specific packet forwarding parameters, forming part of the EPS bearer QoS profile, with standardized characteristics.
- “A QCI is a scalar that is used as a reference to access node-specific parameters that control bearer level packet forwarding treatment” TS 23.401 v8.18.0
- “QoS class identifier (QCI): A scalar that is used as a reference to a specific packet forwarding behaviour” TS 23.203 v8.15.0
- “The EPS bearer QoS profile includes the parameters QCI, ARP, GBR and MBR, described in this clause.” TS 23.401 v8.18.0
QCI handling was changed in Rel-9: emergency sessions use an inactivity timer keyed on QCI, bearer binding now checks QCI together with ARP, and QCI/Release 99 mapping notes were updated.
- “the PCEF shall check the QCI and ARP indicated by the PCC Rule(s) and bind the PCC rule with an IP-CAN bearer” TS 29.213 v9.16.0
- “removes all PCC rules with a QCI other than the default bearer QCI and the QCI used for IMS signalling” TS 23.203 v9.14.0
- “For certain APNs (e.g. the IMS APN defined by the GSMA) the QCI value is strictly defined and therefore remapping of QCI is not permitted.” TS 23.401 v9.16.0
Rel-10 adds MPS handling of QCI: the PCRF sets or changes ARP/QCI in PCC/QoS rules and default bearers for prioritized service, and the BBF/PCEF modifies the bearer QCI as requested.
- “For MPS service, the PCRF shall generate the corresponding PCC/QoS rule(s) with the ARP/QCI parameters as appropriate for the prioritized service.” TS 23.203 v10.10.0
- “Upon the same modification of the QCI and/or ARP of all the PCC rules bound to the same bearer, the PCEF should modify the QCI and/or ARP for that bearer.” TS 29.212 v10.17.0
- “QCI reservation for eMPS” TS 23.203 v10.10.0
Rel-11 adds QCI-related behaviour: PCC rules with application identifier may be assigned to other non-GBR QCI bearers, and the PCRF may assign the default bearer's QCI for preliminary service information.
- “PCC Rules that contain an application identifier may be assigned to other bearer(s) with non-GBR QCI (e.g. the default bearer)” TS 29.212 v11.19.0
- “the PCRF may assign the QCI and ARP of the default bearer to avoid signalling to the UE” TS 29.212 v11.19.0
- QCI=1 usage in SRVCC TS 23.216CR0215
Rel-12 adds Mission Critical QCI values 66, 67, 69 and 70, QCI modification rules for PCRF and default bearer handling, and RAT-change handling for QCIs not supported by all RATs.
- “The MissionCriticalQCIs supported feature indicates support for the Mission Critical QCI values 66, 67, 69 and 70 within the QoS-Class-Identifier AVP” TS 29.212 v12.14.0
- “If there is a QCI assigned to a PCC/QoS rule which is not supported by all RATs of the IP-CAN, the PCRF shall subscribe to the event trigger 'RAT change'.” TS 23.203 v12.11.0
- “the PCRF shall simultaneously modify the QCI and/or ARP of all PCC/QoS Rules that, according to the operator policy, shall have the same QoS as the default bearer” TS 29.212 v12.14.0
QCI handling changed in Rel-13: QCI-related priority sharing, ARP rederivation, resource sharing for GBR QCIs, and revised Mission Critical QCI values (65, 66, 69, 70) with updated definitions.
- “For PCC Rules related to the same IP-CAN session with the same assigned QCI and with the priority sharing indicator enabled” TS 29.212 v13.13.0
- “This feature indicates support for the Mission Critical QCI values 65, 69 and 70, and the Non Mission Critical QCI value 66” TS 29.212 v13.13.0
- Correction of definition of QCI 65, 66, 69 and 70 TS 23.203CR1012
Rel-14 adds new QCI values for V2X services and lets the PCRF authorize a deferred change of the default EPS bearer QCI and ARP at a specific point in time.
- “Add new QCI values for V2X services” TS 29.212 v14.11.0
- “It shall be possible for the PCRF to authorize the QCI and ARP of the default EPS bearer to be enforced by the PCEF immediately” TS 23.203 v14.6.0
- Deferred default EPS bearer QCI and ARP change TS 23.203CR1068
QCI behaviour was extended in Rel-15: a new Mission Critical Video QCI 67 was added, and the eNodeB may use ARP priority level in addition to QCI for packet handling.
- “This feature indicates support for the Mission Critical Video QCI value 67 within the QoS-Class-Identifier AVP defined in subclause 5.3.17.” TS 29.212 v15.9.0
- “the eNodeB can be configured to use the ARP priority level in addition to the QCI priority level to determine the relative priority” TS 23.203 v15.5.0
- Extension on QCI for MC Video TS 23.203CR1111
PCRF/PCC handling of QCI was extended: QCI values for FLUS support, QCI derivation for live uplink streaming and QoS-hint applications, and QCI-1 packet loss rate provisioning with CHEM.
- “Support of QCI values for Framework for Live Uplink Streaming (FLUS)” TS 29.212 v16.4.0
- “The "live" uplink streaming algorithm may consider various inputs, including the received FLUS-Identifier AVP, Desired-Max-Latency AVP” TS 29.213 v16.3.0
- Missing QCI to CAPC mapping TS 36.300CR1240
For MPS for Data Transport Service, the PCRF must change the ARP and QCI of the default bearer and PCC rules on invocation and revoke them on revocation.
- “Set the QCI of the default bearer as appropriate for MPS for DTS.” TS 29.212 v17.3.0
- “the PCRF shall set the ARP and the QCI of the default bearer as appropriate for PCRF decision.” TS 29.212 v17.3.0
- “Upon successful authorization the PCRF performs the necessary actions to achieve appropriate ARP and QCI settings for the bearers” TS 23.401 v17.11.0
TS 23.401 in Rel-18 adds rules for QCI remapping at inter-PLMN mobility and Home Routed roaming, including operator-specific QCI values, and a new QCI 10 is introduced for satellite access.
- “If remapping of QCI at inter-PLMN mobility is to be performed, the target PLMN chooses the QCI value based on inter-PLMN agreement” TS 23.401 v18.8.0
- “the MME can remap QCI value. The remapping of the QCI value based on local policy can result in service degradation.” TS 23.401 v18.8.0
- New QCI 10 for QoS control for satellite access – Cat A TS 24.301CR3829
The MPS-specific algorithm for deriving the QCI now also considers the MPS-Action AVP, and QCI handling for satellite access was clarified in TS 23.203.
- “The MPS specific algorithm shall consider various inputs, including the received MPS-Identifier AVP, MPS-Action AVP and Reservation-Priority AVP as applicable, for deriving the QCI.” TS 29.213 v19.3.0
- Clarification on QCI for satellite access TS 23.203CR1142
For NB-IoT over GEO satellite access, a PDB of 1100 ms is assumed for QCI 5 instead of 100 ms, with the QCI 1 value left for further study.
- “a PDB of 1100 ms can be assumed for QCI 5 and a PDB of FFS ms can be assumed for QCI 1” TS 23.203 v20.1.0
- “The PDB value for QCI 1 in NOTE 19 in Table 6.1.7-A is FFS” TS 23.203 v20.1.0
Defining Specifications
3GPP specifications that define or reference QCI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 23.203 vk10 | Policy and Charging Control Architecture | Rel-20 read |
| TS 23.282 vk31 | Mission Critical Data Architecture | Rel-20 read |
| TS 23.379 vk40 | Mission Critical Push-to-Talk Architecture | Rel-20 read |
| TS 23.401 vk10 | Evolved Packet System Architecture | Rel-20 read |
| TS 23.468 vj00 | Group Communication System Enablers for LTE | Rel-19 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TS 23.795 vg10 | V2X Application Architecture Study | Rel-16 read |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 read |
| TS 24.281 vk10 | MCVideo Signalling Control | Rel-20 read |
| TS 24.282 vk10 | MCData Signalling Control Protocols | Rel-20 read |
| TS 24.301 vk10 | EPS NAS Mobility and Session Management | Rel-20 read |
| TS 24.379 vk10 | MCPTT Call Control Protocol | Rel-20 read |
| TS 26.114 vk11 | IMS Multimedia Telephony Client | Rel-20 read |
| TS 26.348 vj00 | xMB Interface Specification | Rel-19 read |
| TR 26.928 vj00 | Study on eXtended Reality (XR) in 5G | Rel-19 read |
| TS 29.061 vk10 | Packet Domain Interworking Requirements | Rel-20 read |
| TS 29.116 vj00 | REST-based protocol for xMB reference point | Rel-19 read |
| TS 29.213 vj30 | PCC Procedures and Flows | Rel-19 read |
| TS 29.866 vj00 | IMS Disaster Prevention & Restoration Enhancement | Rel-19 read |
| TS 32.130 vj20 | Network Sharing OAM&P Requirements | Rel-19 read |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.314 vj00 | E-UTRA Radio Measurements Specification | Rel-19 read |
| TS 36.331 vj40 | E-UTRA Radio Resource Control (RRC) Protocol | Rel-19 read |
| TS 36.579 | 3GPP TR 36.579 | Rel-7 read |
| TS 36.880 vd00 | MDT Enhancements for E-UTRAN | Rel-13 read |
| TS 37.320 vj40 | MDT Overall Description (Stage 2) | Rel-19 read |
| TS 37.579 vi50 | Mission Critical (MC) services | Rel-18 read |
| TR 37.901 vf10 | UE Application Layer Data Throughput Performance | Rel-15 read |
| TR 38.835 vi01 | Technical Report on XR Enhancements for NR | Rel-18 read |