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

Glossary term · Services

MBSTF

Multicast/Broadcast Service Transport Function

Services →

MBSTF is the 5G network function that delivers multicast and broadcast traffic efficiently to multiple UEs by enabling point-to-multipoint data distribution.

Introduced
Rel-17
Where
Core Network › 5G Core
Specifications
12 specs
Also in
Services, Security
MBSTF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Multicast/Broadcast Service Transport Function (MBSTF) is a core network function introduced in 5G System (5GS) architecture to support Multimedia Broadcast Multicast Service (MBMS) delivery. It operates within the 5G Core (5GC) and is responsible for managing the transport of multicast and broadcast user plane data. The MBSTF interfaces with other network functions such as the Session Management Function (SMF) and User Plane Function (UPF) to establish and maintain multicast/broadcast sessions. It handles key procedures including session announcement, modification, and termination, ensuring that data is efficiently distributed to the Radio Access Network (RAN) for transmission to user equipment (UE).

Architecturally, the MBSTF can be deployed as a standalone function or integrated with other user plane functions. It receives multicast/broadcast traffic from content providers or the UPF and forwards it using IP multicast protocols towards the RAN nodes (gNBs). The function supports both broadcast mode, where data is sent to all UEs in a service area, and multicast mode, where data is sent only to UEs that have joined a specific multicast group. It works in conjunction with the Broadcast/Multicast Service Center (BM-SC) for service provisioning and the Access and Mobility Management Function (AMF) for UE registration in multicast services.

The MBSTF plays a critical role in optimizing network resources by reducing duplicate transmissions of the same data over the core network. Instead of sending individual data streams to each UE, it aggregates traffic and uses point-to-multipoint delivery, which is especially beneficial for high-demand content like live sports or emergency broadcasts. It supports dynamic session management, allowing network operators to scale services based on demand and manage Quality of Service (QoS) parameters for multicast flows. The function also incorporates security mechanisms, integrating with authentication and key management functions to ensure that multicast content is delivered securely to authorized users only.

Purpose & Motivation

The MBSTF was created to address the growing demand for efficient group communication services in 5G networks. Previous generations like 4G LTE supported MBMS through the BM-SC and MCE (Multi-cell/multicast Coordination Entity), but the architecture was not fully integrated into the core network as a standardized function. This led to limitations in scalability, flexibility, and support for new 5G use cases such as massive IoT and ultra-reliable low-latency communications (URLLC). The MBSTF provides a native, cloud-native approach to multicast/broadcast within the 5GC, enabling seamless service delivery across diverse deployment scenarios.

The primary problem it solves is inefficient use of network bandwidth when delivering the same content to multiple users. Traditional unicast delivery would require separate data streams for each user, congesting the network and increasing latency. MBSTF enables network operators to offload popular content through multicast, reducing core network load and improving user experience. This is particularly important for bandwidth-intensive applications like 4K/8K video streaming, where unicast delivery becomes unsustainable during peak demand.

Furthermore, the MBSTF supports emerging 5G services such as Vehicle-to-Everything (V2X) communications, public safety networks, and software updates for IoT devices. By providing a standardized, scalable mechanism for group data delivery, it facilitates the commercialization of multicast/broadcast services and enables new revenue streams for operators. The function's integration with network slicing also allows dedicated multicast slices for specific services, ensuring performance isolation and tailored QoS.

What changed in its specifications

The latest release-to-release comparison of specifications that define MBSTF. 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 26.502Rel-18 → Rel-19

Refined MBS distribution session parameters, object repair conditions, and MBS AS capability descriptions. Added Nmb10 to baseline procedures.

Full comparison in TS 26.502 →

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
  • MBSTF counterpart in another generation: BM-SC
    “Figure 5.2-1 depicts the system architecture for interworking between E-UTRAN/EPC eMBMS and MBS at service layer, with collocated BM-SC and MBSF/MBSTF functionalities.” TS 23.247
  • MBSTF used together with MBSF
    “The MBSF (clause 4.3.2) offers control plane functionality while the MBSTF (clause 4.3.3) offers user plane functionality.” TS 26.502

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

The MBSTF is specified for the first time in Rel-17 as the user plane function of MBS, with the Nmb2 reference point, ingest and distribution session handling, and the Nmbstf service API.

  • “The MBSF and MBSTF offer service layer functionality for sending data via MBS Sessions.” TS 26.502 v17.13.0
  • “The MBSTF performs the following functions to support MBS if deployed:” TS 23.247 v17.12.0
  • “The present document specifies the stage 3 protocol and data model for the Nmbstf Service Based Interface.” TS 29.581 v17.7.0
Rel-18 specification text

MBSTF gained new Rel-18 behaviour: group message delivery via file ingestion from the NEF over the new Nmb14 reference point, plus redirection handling between MBSTFs in an MBSTF set.

  • “Nmb14: Reference point between the NEF and the MBSTF.” TS 23.247 v18.8.0
  • “The NEF performs the User Data Ingestion towards the MBSTF as specified in TS 26.502 [18].” TS 23.247 v18.8.0
  • “If an MBSTF redirects a service request to a different MBSTF using an 307 Temporary Redirect or 308 Permanent Redirect status code” TS 29.581 v18.6.0
Rel-19 specification text

Rel-19 adds MBS-12 ingest of objects from the MBSTF by the MBS AS (pull or push) to support in-session Object Repair, with new MBSTF configuration and repair-request behaviour.

  • “the MBSTF establishes an Object Repair ingest session with the MBS AS, and the latter ingests the relevant user data via reference point MBS-12.” TS 26.502 v19.6.0
  • “Push-based ingest at reference point MBS-12: The MBSTF publishes one or more objects to the MBS AS.” TS 26.502 v19.6.0
  • “After the back-off time period has elapsed, the MBSTF requests missing data from the MBS AS.” TS 26.502 v19.6.0

Defining Specifications

3GPP specifications that define or reference MBSTF, 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 26.502 vj60 5G Multicast-Broadcast User Services Rel-19 read
TS 26.512 vj30 5G Media Streaming Protocols and APIs Rel-19 read
TS 26.517 vj30 5G MBS User Service Protocols Rel-19 read
TS 26.802 vk00 5G Media Streaming Multicast Enhancements Rel-20 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions 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.580 vk00 MBSF Nmbsf Service-Based Interface Rel-20 read
TS 29.581 vk00 Nmbstf Service Based Interface Stage 3 Rel-20 read
TS 33.501 vk30 5G Security Architecture Rel-20 read
TR 33.850 vh00 5G MBS Security Study Rel-17 read