MB-SMF

Multicast/Broadcast Session Management Function

Core Network →
Introduced in Rel-17

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.

Category
Core Network
Introduced
Rel-17
Where
Core Network › 5G Core
Specifications
13 specs
MB-SMF Description Purpose Related Classification 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.

Classification

Part ofSMF
Specific typesMBSSF
Related approachesMB-UPFSC-PTM

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 12 changes

In Release 17, the MB-SMF was enhanced with new registration and discovery procedures, including discovery by the AMF using MBS Session ID and Area Session ID. The release also introduced mechanisms for the selection of collocated MB-SMF/SMF functions and defined the handling of QoS mapping procedures between the PCF and MB-SMF. Furthermore, it specified new capabilities for the MB-SMF to discover AMF(s) and to receive NG-RAN failure reports and node IDs from the AMF.

  • 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
  • Reporting NG-RAN failure to MB-SMF TS 29.518CR0746
  • MB-SMF discovering AMF(s) TS 29.510CR0717

+ 6 more changes

Rel-18 4 changes

In Release 18, the MB-SMF was integrated into the charging architecture, enabling it to act as a consumer of the ConvergedCharging service. The release also specified the inclusion of the MB-SMF and MB-UPF in NodeID procedures over the N4mb interface and addressed scenarios where an MBS Service Area is not contained within the MB-SMF's service area. Furthermore, the MB-SMF's service-based interface, Nmbsmf, was formally defined, with its Nmbsmf_TMGI service for TMGI management being explicitly referenced.

  • 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
  • MBS Service Area not contained within the MB-SMF service area TS 29.532CR0075

Explore further

Broader topics and technologies where MB-SMF plays a role.

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 vk00 5G System Architecture Stage 2 Rel-20
TS 23.527 vj50 5G System Restoration Procedures Rel-19
TS 29.244 vj40 PFCP Specification for Control/User Plane Separation Rel-19
TS 29.510 vj50 NRF Service Based Interface Protocol Rel-19
TS 29.513 vj40 5G PCC Signalling Flows & QoS Mapping Rel-19
TS 29.518 vj50 AMF Service Based Interface Protocol Rel-19
TS 29.522 vj40 5G NEF Northbound APIs Stage 3 Rel-19
TS 29.532 vj30 MB-SMF Service Based Interface Protocol Rel-19
TS 29.537 vj10 5G Multicast/Broadcast Policy Control Services Rel-19
TS 29.581 vj20 MBSTF Service Based Interface Protocol Specification Rel-19
TS 32.240 vj40 Charging Management Architecture & Principles Rel-19
TS 32.290 vj50 5G Charging for Service Based Interface Rel-19
TS 32.291 vj40 Charging Management: Service-Based Interface Protocol Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.