Description
The Multicast/Broadcast Service Function (MBSF) is a pivotal network function within the 5G Core (5GC) architecture, specifically designed to orchestrate and manage Multicast/Broadcast Service (MBS) sessions. It acts as the central control point for MBS, interfacing with other core network functions to enable efficient point-to-multipoint data delivery. The MBSF is responsible for the entire lifecycle of an MBS session, from initiation and modification to termination, ensuring that content is delivered reliably to multiple User Equipments (UEs) simultaneously. Its architecture is based on the 5G service-based framework, allowing it to communicate via standardized interfaces like Nmbsf for management and Nmbst for data transport.
In terms of operation, the MBSF works by receiving service requests from applications or network operators, often via the Network Exposure Function (NEF) or directly from the Session Management Function (SMF). Upon receiving a request, the MBSF authenticates and authorizes the MBS session, applying policies defined by the Policy Control Function (PCF). It then coordinates with the SMF and User Plane Function (UPF) to establish the necessary data paths for multicast/broadcast traffic. The MBSF also interacts with the Radio Access Network (RAN), particularly the gNB, to allocate radio resources and configure transmission parameters, using identifiers like the Frequency Selection Area Identity (MBS) to optimize resource usage.
Key components and interfaces of the MBSF include the MBSF control plane, which handles signaling and session management, and the MBSF user plane, which may be integrated with UPFs for data forwarding. The function supports both broadcast mode, where content is sent to all UEs in an area, and multicast mode, where only subscribed UEs receive the data. It employs mechanisms for dynamic group management, allowing UEs to join or leave sessions seamlessly. The MBSF also plays a role in charging and accounting, interfacing with the Charging Function (CHF) to track usage for MBS services.
The role of the MBSF in the network is to enable scalable and efficient group communication, reducing network congestion by minimizing duplicate unicast streams. It is essential for applications requiring wide-area content distribution, such as live television, emergency alerts, software updates for IoT devices, and V2X communications. By centralizing MBS management, the MBSF ensures consistent policy enforcement, security, and QoS across the 5G system, integrating with network slicing to provide dedicated MBS slices for different service requirements.
Purpose & Motivation
The MBSF was created to address the limitations of earlier multicast/broadcast solutions in cellular networks, such as LTE's MBMS, which lacked a dedicated, flexible core network function for service management. In LTE, MBMS relied on evolved MBMS (eMBMS) with functions like the Broadcast Multicast Service Center (BM-SC), but this was not fully integrated into the 5G service-based architecture. The motivation for MBSF stems from the need for a more agile and scalable approach to group communication in 5G, driven by emerging use cases like massive IoT, autonomous driving, and ultra-high-definition media streaming.
Previous approaches suffered from inefficiencies in session management and resource allocation, often leading to suboptimal performance and high operational complexity. The MBSF solves these problems by providing a standardized, cloud-native function that can dynamically orchestrate MBS sessions across the core and RAN. It enables network operators to offer MBS as a native 5G service, with better support for edge computing and low-latency applications. This is crucial for scenarios where real-time data must be distributed to many devices, such as in smart cities or industrial automation.
Historically, the development of MBSF began in 3GPP Release 17 as part of the broader 5G MBS framework, reflecting the industry's shift towards converged networks that support both unicast and multicast efficiently. The purpose of MBSF is to leverage 5G's architectural advancements, such as network slicing and service-based interfaces, to deliver group communication services with enhanced reliability, security, and efficiency. It addresses the growing demand for content-centric networks and supports regulatory requirements for public safety communications, making it a cornerstone of modern 5G deployments.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (35 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 16, the MBSF was introduced within the service-based architecture to support multicast and broadcast services, with its Nmbsf service-based interface defined in TS 23.247. The release specifically enhanced capabilities for forwarding multicast and broadcast traffic within 5G Virtual Networks (5G VN) and for Ethernet-type PDU Sessions, utilizing a UPF internal interface for group communication. It also provided clarifications on the management of IP multicast mechanisms and PDU Sessions for 5G-LAN multicast services.
- Support of forwarding of broadcast and multicast packets TS 23.501CR1659
- Clarification on PDU Session management for 5G-LAN multicast TS 23.501CR1202
- Data forwarding for 5G-LAN multicast TS 23.501CR1328
- Multicast forwarding for Ethernet type PDU Session TS 23.501CR1722
- Updates to the 5G VN broadcast solution TS 23.501CR1857
- Clarification on the 5G VN usage of IP Multicast mechanisms from TS 23.316 TS 23.501CR2028
+ 3 more changes
In Release 17, the MBSF (Multicast/Broadcast Service Function) was enhanced with new procedures for the robust restoration of both Broadcast and Multicast MBS sessions following an NG-RAN failure, with or without a restart. The release also introduced a dedicated Broadcast Delivery Status event, standardized the handling of a Multicast Transport Address Change event, and clarified the multicast security context handling within the session creation procedure. Furthermore, the MBSF was defined as a consumer of the Nbsf_Management_Discovery service.
- Restoration of a Broadcast MBS session upon NG-RAN failure with or without restart TS 23.527CR0048
- Restoration of a Multicast MBS session upon NG-RAN failure with or without restart TS 23.527CR0049
- Support of Broadcast MBS Session with an AMF set being deployed TS 23.527CR0056
- Broadcast Delivery Status event TS 29.532CR0012
- Multicast Transport Address Change Context Status event TS 29.532CR0014
- Corrections to the Broadcast MBS session restoration procedures TS 23.527CR0059
+ 5 more changes
In Release 18, the MBSF saw enhancements for improved service resilience and support for new device types. Key additions included procedures for Multicast MBS session (de)activation or update after an AMF failure and for Broadcast MBS session restoration following an N3mb path failure. The release also introduced support for RedCap UEs in MBS Broadcast and enabled Location Dependent MBS broadcast sessions involving multiple MB-SMFs.
- SNPN broadcast system information and manual network selection for localized service TS 23.501CR4095
- Multicast MBS session (de)activation or update after an AMF failure TS 23.527CR0063
- RedCap UEs Information for a broadcast MBS session TS 29.532CR0085
- Clarifications of Event ID broadcast in SIB9 TS 23.501CR5039
- Correction for multiple broadcast TA reporting in NR Satellite access TS 23.501CR5214
- Broadcast MBS session restoration procedure for N3mb path failure TS 23.527CR0072
+ 4 more changes
In Release 19, the MBSF saw enhancements including the introduction of AMF event exposure to support on-demand broadcast of LCS assistance data and a defined multicast MBS session restoration procedure for N3mb path failure. The release also provided clarifications to the restoration procedure for NG-RAN restart and made corrections to the MBSF API OAuth definitions and notification events.
- AMF event exposure for supporting on-demand broadcast of LCS assistant data TS 23.501CR5580
- Multicast MBS session restoration procedure for N3mb path failure TS 23.527CR0082
- Clarification to the Multicast MBS session restoration procedure for NG-RAN restart TS 23.527CR0086
- Corrections to the MBSF APIs Oauth definition TS 29.580CR0062
- [5MBUSA] MBSF notification event corrections TS 26.502CR0048
Explore further
Broader topics and technologies where MBSF plays a role.
Defining Specifications
3GPP specifications that define or reference MBSF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 23.527 vj50 | 5G System Restoration Procedures | Rel-19 |
| TS 26.502 vj30 | 5G Multicast-Broadcast User Services Architecture | Rel-19 |
| TS 26.517 vj10 | 5G MBS User Service Protocols and Formats | Rel-19 |
| TS 26.802 vj20 | Multicast Enhancements for 5G Media Streaming | Rel-19 |
| TS 26.804 vj10 | 5G Media Streaming Extensions Study | Rel-19 |
| TS 29.244 vj40 | PFCP Specification for Control/User Plane Separation | Rel-19 |
| TS 29.513 vj40 | 5G PCC Signalling Flows & QoS Mapping | Rel-19 |
| TS 29.521 vj40 | 5G Binding Support Management Service 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.580 vj30 | 5G MBSF Service Interface Stage 3 Specification | Rel-19 |
| TS 29.581 vj20 | MBSTF Service Based Interface Protocol Specification | Rel-19 |
| TS 33.501 vk00 | 5G Security Architecture and Procedures | Rel-20 |
| TR 33.850 vh00 | 5G MBS Security Study | Rel-17 |