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

Glossary term · Security

MBSSF

Multicast/Broadcast Service Security Function

Security →

MBSSF is the 5G Core network function that provides security services for multicast and broadcast traffic by handling key management, authentication, and encryption to ensure secure content delivery.

Introduced
Rel-17
Where
Security
Specifications
1 specs
MBSSF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Multicast/Broadcast Service Security Function is a critical security component within the 5G Core Network's Multicast/Broadcast Service architecture. It is responsible for the complete security lifecycle of a Multicast/Broadcast Service (MBS) session. The MBSSF generates, manages, and distributes the cryptographic keys used to protect MBS traffic (user plane confidentiality and integrity) and related signaling. It interfaces with other core network functions, primarily the MB-SMF (MBS Session Management Function) and the UDM (Unified Data Management), to authenticate and authorize UEs for specific MBS sessions.

Operationally, when an MBS session is established, the MB-SMF requests the MBSSF to initiate security procedures. The MBSSF generates a Master Session Key (MSK) for the MBS session. For each UE joining the session, the MBSSF derives a User-specific Key (UK) from the MSK and the UE's subscription identifier. This UK is then provisioned to the UE through a secure unicast channel, typically via the MB-SMF and the Access and Mobility Management Function (AMF) using NAS security. The UE uses this UK to derive the necessary traffic encryption keys (TEKs) for decrypting the multicast/broadcast data flow.

The MBSSF also supports key renewal and revocation processes to maintain security over time. It can periodically update the MSK and push new derived keys to authorized UEs, mitigating the risk of key compromise. Architecturally, the MBSSF may be a standalone Network Function (NF) or collocated with another function like the MB-SMF. It uses the 3GPP-defined service-based interfaces, notably Nmbsf, to communicate with other NFs. Its design ensures that multicast/broadcast security is integrated into the 5G security framework, leveraging the existing authentication infrastructure (5G AKA) while addressing the unique point-to-multipoint delivery model.

Purpose & Motivation

The MBSSF was created to address the specific security challenges inherent in multicast and broadcast services, which were reintroduced and enhanced in 5G. In a point-to-multipoint model, traditional unicast security mechanisms (like those between a UPF and a single UE) are inefficient and inadequate. The purpose of the MBSSF is to provide a standardized, scalable, and secure method for managing keys and access control for potentially massive numbers of receivers.

It solves the problem of secure key distribution for broadcast groups. Without a dedicated function like the MBSSF, the network would need to establish individual secure contexts with each UE for the same content, wasting signaling resources and complicating synchronized key updates. Previous MBMS security in 4G used the BM-SC for similar functions, but the MBSSF is redesigned as a native 5G Core service-based function, integrating with the new authentication framework and network slicing capabilities.

The motivation for its specification in Release 17 was driven by the expanded use cases for 5G MBS, including mission-critical group communications, public safety, V2X applications, and IPTV. These services demand robust security to prevent eavesdropping, service theft, and spoofing. The MBSSF provides the necessary foundation for commercial broadcast services where content protection (Digital Rights Management) is paramount, and for public safety where communication integrity and group authentication are critical.

What changed in its specifications

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

TS 33.501Rel-18 → Rel-19

Rel-19 TS 33.501 adds roaming and inter-PLMN indirect communication authorization, fast re-authentication for non-3GPP mobility, and AI/ML security clauses for positioning and federated learning. It also adds NPN security, NRF access token key retrieval, LTM security, and monitoring-of-signalling-traffic protection.

Full comparison in TS 33.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
  • MBSSF used together with MBSF
    “The MBSSF, as a logical function co-located with either the MBSF or the MBSTF, is responsible for key generation, management and distribution, including both MBS Session Keys and MBS Traffic Keys” 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 2 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

MBSSF is defined for the first time as a logical function collocated with MBSF or MBSTF, handling key management, UE authentication via GBA/AKMA, and UE authorization for MBS user services.

  • “The MBS Security Function (MBSSF) is a logical function, which needs to be collocated with either MBSF or MBSTF” TS 33.501 v17.16.0
  • “MBSSF takes the role of the BM-SC in TS 33.246 [102].” TS 33.501 v17.16.0
  • “The UE authenticates to the MBSSF (i.e. MBSF or MBSTF) based on the GBA as in MBMS security” TS 33.501 v17.16.0
Rel-18 specification text

For MOCN network sharing, the AF may generate common MSK/MTK and their IDs and provide them to the MBSSFs of the participating PLMNs at session creation and key update.

  • “The AF provides the generated MSK, MSK ID, MTK and MTK ID to the MBSSF(s) of the participating PLMNs” TS 33.501 v18.12.0
  • “If the MBSSF uses MSK and MTK generated by itself to protect the traffic, the resource sharing during network sharing will not be used.” TS 33.501 v18.12.0

Defining Specifications

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

SpecificationTitleRelease
TS 33.501 vk30 5G Security Architecture Rel-20 read