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

Glossary term · Core Network

MB-UPF

Multicast/Broadcast User Plane Function

Core Network →

MB-UPF is the 5G Core Network user plane function that efficiently distributes the same multicast or broadcast content to multiple users.

Introduced
Rel-17
Where
Core Network › 5G Core
Specifications
10 specs
MB-UPF Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

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

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 →

Technology family

Broadcast and multicast · Services

  1. Phase 1 CBC, CBCH, CBS, SMS-CB
  2. Phase 2 CBE
  3. R99 BMC, SABP
  4. Rel-6 ALC, BM-SC, FDT, FLUTE, LCT, MBMS, MBMS Bearer Service, MBMS download delivery method, MBMS streaming delivery method, MBMS User Service, TMGI
  5. Rel-7 MBSFN
  6. Rel-8 ETWS, MCE, PWS
  7. Rel-9 CBSP, CMAS, eMBMS, MBMS-GW
  8. Rel-10 KPAS
  9. Rel-11 EU-Alert
  10. Rel-12 MooD
  11. Rel-13 MBMS group communication delivery method, SC-PTM
  12. Rel-14 MBMS transparent delivery method, Receive Only Mode
  13. Rel-15 CBCF, PWS-IWF
  14. Rel-16 5G Broadcast
  15. Rel-17 5MBS, Broadcast MBS session, MB-SMF, MB-UPF, MBS, MBS Distribution Session, MBS User Service, MBSF, MBSSF, MBSTF, Multicast MBS session, Object Distribution Method, Packet Distribution Method
  • MB-UPF counterpart in another generation: MBMS-GW
    “The MBSTF distributes the received data to the MB-UPF at reference point Nmb9 and/or the MBMS-GW at reference point SGi-mb, when supported by operator network configuration.” TS 23.247
  • MB-UPF used together with MB-SMF
    “The selection and reselection of the MB-UPF are performed by the MB-SMF by considering MB-UPF deployment.” TS 23.247

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 sources

Documented changes in 3 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.

Rel-17 introduced

MB-UPF is specified for the first time in Rel-17 as the user plane function anchoring MBS sessions, receiving a single copy of MBS data and delivering it to NG-RAN and UPF over N3mb and N19mb tunnels.

  • “The MB-UPF acts as the MBS Session Anchor of an MBS session” TS 23.247 v17.12.0
  • “The MB-UPF sends multicast PDUs in the N3mb tunnel associated to the multicast MBS session to the NG-RAN.” TS 23.247 v17.12.0
  • “MB-UPF Multicast/Broadcast User Plane Function” TS 23.527 v17.6.0
Rel-18 specification text

MB-UPF behaviour changed in Rel-18: new PFCP flags (JMBSSM, PLLSSM, FSSM, MBSU), ingress tunnel allocation, MBS charging measurement, and N3mb path failure detection and reporting.

  • “If set, the MB-UPF shall provide a LLSSM address and a GTP-U Common Tunnel EndPoint Identifier (C-TEID) to the MB-SMF.” TS 29.244 v18.10.0
  • “Upon being so instructed, the MB-UPF shall measure and report the requested MBS data usage as defined in clause 5.2.2.” TS 29.244 v18.10.0
  • “The MB-UPF may detect a N3mb path failure, when unicast transport is used over the N3mb interface” TS 23.527 v18.6.0
Rel-19 specification text

Rel-19 adds MB-UPF behaviour: restoration after MB-UPF failure without restart, and detection and reporting of N3mb path failure towards the MB-SMF, with new handling of DL F-TEIDs.

  • “when the MB-UPF detects and reports an N3mb path failure towards the MB-SMF, the MB-SMF may initiate the Multicast Session Update procedure” TS 23.527 v19.5.0
  • “The MB-UPF detects the N3mb path failure upon no longer receiving responses to its GTP-U Echo Request messages.” TS 23.527 v19.5.0
  • “During a restoration procedure for an MB-UPF failure without Restart (see clause 8.2.3 of TS 23.527 []), if multicast transport is used over N19mb:” TS 29.244 v19.6.0

Defining Specifications

3GPP specifications that define or reference MB-UPF, 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
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