Description
The Multicast/Broadcast User Plane Function (MB-UPF) is a specialized network function within the 5G Core (5GC) architecture, introduced to support point-to-multipoint delivery of data. It operates as part of the 5G Multicast-Broadcast Service (5MBS) framework. The MB-UPF is responsible for processing and forwarding user plane packets for multicast and broadcast traffic. It interfaces with the Radio Access Network (RAN) via the N3/N9 interfaces and with the Session Management Function (SMF) via the N4 interface for control. Its key role is to replicate and route data packets received from a multicast source (e.g., via N6 interface) towards the appropriate RAN nodes serving user equipment (UEs) subscribed to a specific multicast session. This differs from a standard UPF, which primarily handles unicast traffic, by optimizing for one-to-many distribution.
Architecturally, the MB-UPF can be deployed as a standalone function or integrated with a standard UPF. It supports both multicast and broadcast delivery modes. In multicast mode, it delivers content only to UEs that have explicitly joined a multicast group, managed via the Multicast Session Management Function (M-SMF) and Multicast Control Plane Function (M-CPF). In broadcast mode, it pushes content to all UEs within a designated service area. The MB-UPF performs packet replication based on multicast group identifiers and QoS flows, ensuring efficient use of transport and radio resources. It also handles traffic policing, forwarding rule enforcement, and charging data collection for multicast/broadcast sessions as per policies from the Policy Control Function (PCF).
From a protocol perspective, the MB-UPF utilizes GTP-U tunnels over the N3 interface towards the RAN. For multicast, it may establish a single GTP-U tunnel to a RAN node, which then further distributes the traffic over the air interface using Single-Cell Point-To-Multipoint (SC-PTM) or Multicast-Broadcast Single Frequency Network (MBSFN) techniques. The MB-UPF is a critical enabler for efficient content delivery, as it prevents the network from establishing separate unicast bearers for each user receiving the same content, thereby conserving core and RAN resources and reducing latency for simultaneous delivery to large audiences.
Purpose & Motivation
The MB-UPF was created to address the inherent inefficiency of using unicast connections for delivering popular live or on-demand content to many users simultaneously. Prior to its introduction in 3GPP Release 17, 5G networks lacked a standardized, efficient core network mechanism for multicast and broadcast services. While LTE had evolved Multimedia Broadcast Multicast Service (eMBMS), its integration with the 5G Core was not fully defined. The rise of applications like live sports streaming, emergency alerts, over-the-air software updates for IoT devices, and public safety communications created a clear need for a native 5G multicast/broadcast solution.
The primary problem the MB-UPF solves is network congestion and resource waste. In a unicast-only model, if 1,000 users in a stadium request the same live video stream, the network sets up 1,000 separate data flows from the content server, through the core, and over the radio, consuming significant bandwidth and processing power. The MB-UPF, as part of the 5MBS architecture, allows a single content flow from the source to be intelligently replicated at optimal points (in the core and RAN), dramatically reducing transport load and improving spectral efficiency on the radio interface. This enables scalable, high-quality service delivery to massive audiences, which is crucial for the commercial viability of new media services and for mission-critical public warnings.
What changed in its specifications
The latest release-to-release comparison of specifications that define MB-UPF. Each summary describes the whole specification, not only this term.
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 →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 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (11 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- MBS session restoration upon MB-UPF failure with restart TS 23.527CR0041
- MBS session restoration upon MB-UPF failure without restart TS 23.527CR0042
- Restoration procedure for MB-UPF restart TS 29.244CR0617
- Tunnel between MBSTF and MB-UPF TS 23.247CR0119
- Restoration procedure for MB-UPF restart TS 23.527CR0044
- Removal of Editor's note for MB-UPF failure without restart TS 23.527CR0053
+ 2 more changes
Defining Specifications
3GPP specifications that define or reference MB-UPF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.247 vk00 | 5G Multicast and Broadcast Services | Rel-20 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.527 vk00 | 5G Restoration Procedures for N4 Interface | Rel-20 read |
| TS 29.244 vk10 | PFCP for Control and User Plane Separation | Rel-20 read |
| TS 29.532 vk00 | Nmbsmf Service Based Interface Specification | Rel-20 read |
| TS 29.561 vk10 | 5G Network Interworking Procedures | Rel-20 read |
| TS 29.581 vk00 | Nmbstf Service Based Interface Stage 3 | Rel-20 read |
| TS 32.255 vk30 | 5G Data Connectivity Converged Charging | Rel-20 read |
| TS 32.279 vj00 | 5G MBS Session Converged Charging | Rel-19 read |
| TS 38.415 vj10 | PDU Session User Plane Protocol | Rel-19 read |