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

Glossary term · QoS

MBS QoS Flow

Multicast/Broadcast Services QoS Flow

QoS →

MBS QoS Flow is the finest granularity for QoS forwarding treatment of MBS data in the 5G System, requiring a separate flow for each distinct QoS treatment to enable differentiated handling of multicast and broadcast traffic.

Introduced
Rel-17
Where
Core Network › 5G Core
Specifications
2 specs
MBS QoS Flow Description Purpose What changed Neighbours Specifications

Description

An MBS QoS Flow is the finest granularity for QoS forwarding treatment of Multicast/Broadcast Services (MBS) data in the 5G System (5GS). It is defined in the 5G MBS architecture specifications 23.247 (Architecture and functional description to support 5G MBS) and 23.757 (Study on architectural enhancements for 5G multicast-broadcast services). The concept mirrors the unicast QoS Flow model in 5GS: just as a PDU session carries one or more QoS Flows, each with its own QoS profile, an MBS session carries one or more MBS QoS Flows, each defining a distinct forwarding treatment for the broadcast or multicast data it carries.

The MBS QoS Flow is the mechanism by which the 5GS differentiates treatment of MBS traffic. If two streams of MBS data require different QoS forwarding treatment—for example, different packet delay budgets, error rates, or priority levels—they must be carried on separate MBS QoS Flows. Each MBS QoS Flow is associated with an MBS QoS profile that defines parameters such as 5QI (5G QoS Identifier), allocation and retention priority (ARP), and, where applicable, guaranteed flow bit rate (GFBR) and maximum flow bit rate (MFBR). The QoS profile is used by the gNB and the User Plane Function (UPF) to apply the appropriate scheduling, queueing, and forwarding treatment.

Architecturally, MBS QoS Flows are established as part of an MBS session. The MBS session is set up between the application function (AF), the policy control function (PCF), the session management function (SMF), and the UPF, with the QoS requirements translated into MBS QoS Flows. The SMF provides the QoS flow information to the NG-RAN (gNB) so that the radio access network can map the MBS QoS Flows to appropriate radio bearers and scheduling policies. On the user plane, the UPF marks packets belonging to each MBS QoS Flow (for example, using the QFI—QoS Flow Identifier—in the GTP-U header), and the gNB uses this marking to apply the correct treatment over the air interface.

The MBS QoS Flow model enables differentiated handling of broadcast and multicast content within a single MBS session. For example, a live video stream might be carried on one MBS QoS Flow with a stringent delay budget, while accompanying metadata or lower-priority content is carried on another MBS QoS Flow with a more relaxed profile. This separation ensures that the network can prioritize critical content and manage radio resources efficiently, even when multiple services share the same MBS session.

The concept was introduced in Release 17 as part of the initial 5G MBS architecture. It represents an evolution of the QoS framework from unicast-only to a unified model that covers both unicast and MBS traffic, ensuring consistency in how QoS is managed across the 5GS. The definition remained stable through Releases 17–20, indicating a mature and settled architectural concept.

Purpose & Motivation

The MBS QoS Flow exists to bring the proven QoS differentiation model of 5GS unicast traffic to multicast and broadcast services. Before 5G MBS, broadcast and multicast delivery in 3GPP systems (such as LTE MBMS) had limited QoS differentiation: broadcast bearers were largely treated uniformly, making it difficult to prioritize critical content or to serve diverse applications with different requirements over the same broadcast infrastructure. As 5G MBS targets use cases such as live media, public safety, and software delivery—each with distinct QoS needs—a finer-grained QoS mechanism became necessary.

By defining the MBS QoS Flow as the finest granularity for QoS forwarding treatment, 3GPP ensures that MBS traffic can be handled with the same precision as unicast traffic. This allows operators to offer service-level guarantees for broadcast content, to differentiate treatment of multiple streams within a session, and to integrate MBS into the existing policy and charging framework. The concept also supports the architectural goal of reusing 5G QoS mechanisms (5QI, ARP, QFI) across unicast and MBS, reducing complexity and ensuring consistent behaviour in the network.

What changed in its specifications

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

TS 23.247Rel-17 → Rel-18

Rel-18 adds 5G MBS Phase 2 features such as group message delivery and power-saving support for MBS reception. It also adds NR RedCap UE long eDRX support in RRC_INACTIVE, SEAL data delivery architecture with new reference points, and a new Nnef_MBSGroupMsgDelivery service.

Full comparison in TS 23.247 →

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-17 Initial

Initial definition introduced: 'The finest granularity for QoS forwarding treatment for MBS data. Providing different QoS forwarding treatment requires separate MBS QoS Flows in 5GS supporting MBS.' Established the MBS QoS Flow as part of the initial 5G MBS architecture.

Definition carried over unchanged from Rel-17.

Definition carried over unchanged from Rel-17.

Definition carried over unchanged from Rel-17.

Defining Specifications

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

SpecificationTitleRelease
TS 23.247 vk00 5G Multicast and Broadcast Services Rel-20 read
TR 23.757 vh00 5G MBS Architectural Enhancements Study Rel-17 read