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

Glossary term · Core Network

MB-SMF

Multicast/Broadcast Session Management Function

Core Network →

MB-SMF is the 5G core network function that manages the establishment, modification, and release of multicast/broadcast sessions, handling user plane resources for efficient group data delivery.

Introduced
Rel-17
Where
Core Network › 5G Core
Specifications
13 specs
Also in
Management
MB-SMF Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Multicast/Broadcast Session Management Function (MB-SMF) is a specialized 5G Core Network (5GC) function defined in 3GPP Release 17 and beyond to support 5G Multicast-Broadcast Services (5G MBS). It is responsible for the session management aspects of point-to-multipoint data delivery. Unlike the standard Session Management Function (SMF) that manages unicast PDU sessions for individual UEs, the MB-SMF manages multicast/broadcast sessions that serve a group of UEs, such as those receiving live video streaming, software updates, or public warning messages.

Architecturally, the MB-SMF is a logical network function that can be deployed as a separate entity or co-located with a unicast SMF. It interfaces with other core network functions using the 5GC service-based architecture. Key interfaces include the Nmbmf interface to the Multicast/Broadcast Service Management Function (MB-UPF) for controlling the user plane, the Namf interface to the Access and Mobility Management Function (AMF) for coordinating with UEs joining/leaving a session, and the Npcf interface to the Policy Control Function (PCF) for applying multicast-specific policies. The MB-SMF is responsible for the lifecycle of a multicast session: it receives session establishment requests (e.g., from an Application Function), allocates a multicast IP address or tunnel endpoint identifier, selects and configures the appropriate MB-UPF(s) to create a multicast distribution tree, and manages the quality of service (QoS) for the multicast flow.

Its operation involves two primary modes: broadcast (where data is sent to all UEs in a service area) and multicast (where data is sent only to UEs that have explicitly joined a group). The MB-SMF works in tandem with the RAN, which has been enhanced with multicast capabilities (e.g., Single-Cell Point-To-Multipoint - SC-PTM, Multicast Broadcast Service - MBS). It provides the RAN with the necessary session context, including QoS profiles and multicast traffic routing information. For multicast mode, it also interacts with the AMF to manage the dynamic joining and leaving of UEs via IGMP/MLD proxy functionality or direct signaling, ensuring efficient use of radio and transport network resources by activating multicast bearers only when and where there are active receivers.

Purpose & Motivation

The MB-SMF was created to address the fundamental limitation of 5G networks prior to Release 17: the lack of native, efficient support for point-to-multipoint services within the 5G Core. While LTE had evolved with eMBMS (evolved Multimedia Broadcast Multicast Service), the initial 5G specifications focused on ultra-reliable low-latency and massive IoT use cases, leaving broadcast/multicast as an afterthought. The MB-SMF solves the problem of inefficient resource usage for group communication; using unicast transmissions to deliver the same content (like a live sports event) to thousands of users in the same cell wastes precious radio spectrum and core network bandwidth.

Its development was motivated by emerging use cases requiring efficient mass communication, such as live event streaming, in-vehicle infotainment, public safety communications, and over-the-air software updates for massive IoT device fleets. The MB-SMF, as part of the holistic 5G MBS architecture, provides a standardized, network-native mechanism to manage these services. It addresses the limitations of previous approaches (like eMBMS in LTE, which had complex integration and limited adoption) by being designed from the ground up within the flexible, service-based 5G Core. This allows for more dynamic session management, better integration with unicast services, and support for both broadcast and on-demand multicast, enabling new business models and services for operators.

What changed in its specifications

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

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

Rel-19 added procedures for UDR restoration during subscriber data migration, AMF resynchronization indication, and multicast MBS session restoration for N3mb path failure.

Full comparison in TS 23.527 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (15 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-17 8 changes
  • MB-SMF registration and discovery TS 29.510CR0552
  • MB-SMF registration and discovery - Updates TS 29.510CR0577
  • Selection of collocated MB-SMF/SMF and MB-UPF/UPF TS 29.510CR0606
  • MB-SMF discovery by AMF using MBS Session ID and Area Session ID TS 29.510CR0636
  • MB-SMF discovering AMF(s) TS 29.510CR0717
  • Handling of QoS mapping procedures in PCF and MB-SMF. TS 29.513CR0396

+ 2 more changes

Rel-18 7 changes
  • Add MB-SMF in charging architecture for 5GS TS 32.240CR0470
  • Add MB-SMF as consumer of ConvergedCharging service TS 32.290CR0200
  • Add MB-SMF and MB-UPF to NodeID over N4mb TS 29.244CR0852
  • Error handling support in MBSSession API when MBS service area is not supported by the MB-SMF(s). TS 29.522CR1106
  • Error handling support in MBSTMGI API when MBS service area is not supported by the MB-SMF(s) TS 29.522CR1107
  • Reduced area indication when MBS service area is larger than MB-SMF service area TS 29.522CR1105

+ 1 more changes

Defining Specifications

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

SpecificationTitleRelease
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.510 vk10 NRF Service-Based Interface Rel-20 read
TS 29.513 vk10 5G PCC Signalling Flows Rel-20 read
TS 29.518 vk10 AMF Service Based Interface Rel-20 read
TS 29.522 vk10 NEF Northbound Interface Rel-20 read
TS 29.532 vk00 Nmbsmf Service Based Interface Specification Rel-20 read
TS 29.537 vk00 MBS Policy Control Services (Stage 3) Rel-20 read
TS 29.581 vk00 Nmbstf Service Based Interface Stage 3 Rel-20 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.290 vk00 5G Charging Service-Based Architecture Rel-20 read
TS 32.291 vk10 5G Charging Service-Based Interface Rel-20 read