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

Glossary term · QoS

Authorised QoS

Authorised Quality of Service

QoS →

Authorised QoS is the maximum Quality of Service, including its class and data rate, that the network permits for a specific data flow to enforce policy control and resource management.

Introduced
Rel-7
Where
Core Network › 5G Core
Specifications
2 specs
Authorised QoS Description Purpose What changed Neighbours Specifications

Description

Authorised QoS is a fundamental concept in 3GPP policy and charging control (PCC) architecture, introduced in Release 7 as part of the evolved packet system (EPS) to enable differentiated treatment of service data flows. It represents the maximum quality of service that the network authorises for a particular service data flow, based on subscription information, operator policies, and application requirements. The Authorised QoS is determined by the Policy and Charging Rules Function (PCRF) in EPS or the Policy Control Function (PCF) in 5G, and is enforced by the Policy and Charging Enforcement Function (PCEF) or User Plane Function (UPF).

The Authorised QoS contains two key parameters: the QoS Class Identifier (QCI) in 4G or 5G QoS Identifier (5QI) in 5G, and the data rate parameters such as Guaranteed Bit Rate (GBR) and Maximum Bit Rate (MBR). The QCI/5QI defines the packet forwarding treatment in terms of priority, packet delay budget, packet error loss rate, and other characteristics. The data rate parameters specify the bandwidth limits for the flow. When multiple service data flows are aggregated within a single IP-CAN bearer (e.g., a PDP context in GPRS or an EPS bearer in LTE), the Authorised QoS for the bearer is derived by combining the Authorised QoS of the individual flows, typically taking the maximum of the QoS parameters to ensure that the bearer can support the most demanding flow.

In the 5G System (5GS), the concept evolved to operate at the QoS Flow level rather than the IP-CAN bearer level. A QoS Flow is the finest granularity of QoS treatment in 5G, and multiple service data flows can be mapped to the same QoS Flow. The Authorised QoS for a QoS Flow is the combination of the Authorised QoS of the individual service data flows mapped to it. This allows for more flexible and efficient QoS management, as flows with similar QoS requirements can share the same QoS Flow, reducing signalling overhead and resource consumption.

The Authorised QoS is communicated from the PCRF/PCF to the PCEF/UPF via the Gx interface (in 4G) or the N7 interface (in 5G) using Diameter or HTTP/2 protocols. The PCEF/UPF then enforces these parameters by configuring the bearer or QoS Flow accordingly. The Authorised QoS is also used by the PCRF/PCF to make policy decisions, such as whether to allow or deny a service data flow request, and to perform charging and usage monitoring.

Overall, Authorised QoS is a critical enabler for network operators to control and monetise the quality of service experienced by users, ensuring that premium services receive appropriate treatment while preventing abuse and ensuring fair usage of network resources. It is a key component of the 3GPP QoS framework, which has evolved from the bearer-centric model in 4G to the flow-based model in 5G, supporting the diverse requirements of enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC).

Purpose & Motivation

Authorised QoS exists to provide a standardised mechanism for network operators to control the maximum quality of service that can be granted to a service data flow. It solves the problem of resource contention and ensures that the network can enforce policy decisions based on subscription, operator preferences, and application requirements. Without Authorised QoS, the network would lack a unified way to limit and manage the QoS of individual flows, leading to potential abuse, unfair resource allocation, and inability to guarantee service level agreements (SLAs).

Historically, before the introduction of PCC in Release 7, QoS control was more static and less granular. The Authorised QoS concept was introduced to enable dynamic policy control and charging, allowing operators to differentiate services and charge accordingly. It addresses the limitations of earlier approaches where QoS was largely determined by the bearer type and not easily adjustable per flow. With the evolution to 5G, the concept was adapted to QoS Flows to support the new service-based architecture and the need for more flexible QoS handling.

The Authorised QoS also plays a crucial role in enabling new business models, such as sponsored data, where third-party applications can request specific QoS treatment, and network slicing, where different slices can have different QoS policies. It provides the foundation for end-to-end QoS management across multiple access technologies and core networks.

What changed in its specifications

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

TS 23.203Rel-16 → Rel-17

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 →
TS 23.503Rel-18 → Rel-19

Rel-19 TS 23.503 adds Network Slice Replacement and Energy Saving Indicator reporting, Application Function influence on payload header handling, and Local Offloading Management Policy for edge computing. It also adds ATSSS Phase 4 multi-access steering (MPQUIC-E, ATSSS-LL), spending-limit policy for roaming, and PCF use of network analytics.

Full comparison in TS 23.503 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-7 Initial

Initial definition introduced as part of the PCC architecture. Authorised QoS is defined as the maximum QoS for a service data flow, with aggregation rules for IP-CAN bearers, containing QCI and data rate.

Definition carried over unchanged from Rel-7, with no modifications to the text.

Definition carried over unchanged from Rel-7, with no modifications to the text.

Definition carried over unchanged from Rel-7, with no modifications to the text.

Definition carried over unchanged from Rel-7, with no modifications to the text.

Definition carried over unchanged from Rel-7, with no modifications to the text.

Definition carried over unchanged from Rel-7, with no modifications to the text.

Definition carried over unchanged from Rel-7, with no modifications to the text.

Definition carried over unchanged from Rel-7, with no modifications to the text.

Definition carried over unchanged from Rel-7, with no modifications to the text.

Definition carried over unchanged from Rel-7, with no modifications to the text.

Definition carried over unchanged from Rel-7, with no modifications to the text.

Definition carried over unchanged from Rel-7, with no modifications to the text.

Wording changed to reflect 5G terminology: 'IP-CAN bearer' replaced with 'QoS Flow', 'QoS class identifier' replaced with '5QI', and aggregation now refers to QoS Flow instead of IP-CAN bearer. This aligns the definition with the 5G System architecture.

Defining Specifications

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

SpecificationTitleRelease
TS 23.203 vk10 Policy and Charging Control Architecture Rel-20 read
TS 23.503 vk30 5G Policy and Charging Control Framework Rel-20 read