MUK

Multicast User Key

Security →
Introduced in Rel-8 Also in: Services

MUK is a security key used in MBMS to encrypt broadcast traffic, ensuring only authorized subscribers who have purchased the service can decrypt and consume the content.

Category
Security
Introduced
Rel-8
Where
Security
Also touches
1 segments
Specifications
6 specs
MUK Description Purpose Related Classification Detected Changes Specifications

Description

The Multicast User Key (MUK) is a cryptographic key central to the service-level security of the Multimedia Broadcast Multicast Service (MBMS) and evolved MBMS (eMBMS). It is a service-specific key used to encrypt the actual multimedia content (the MBMS traffic) delivered over the broadcast/multicast bearer. Each distinct MBMS service (e.g., a specific TV channel or file delivery session) is encrypted with its own unique MUK. This ensures confidentiality and access control at the service level.

The MUK is part of a key hierarchy defined in the MBMS security architecture. It is derived from, or associated with, a service key called the MBMS Service Key (MSK). The MSK is delivered securely to authorized user equipments (UEs) via point-to-point signaling using the existing unicast security mechanisms (rooted in the USIM). The UE then uses the MSK to derive or retrieve the corresponding MUK for a service it is authorized to receive. The MUK itself is then used by the UE's decryption engine to decrypt the ciphertext received over the broadcast radio interface on the Multicast Traffic Channel (MTCH).

On the network side, the BM-SC (Broadcast Multicast Service Center) is responsible for service announcement, key management, and content encryption. The BM-SC generates or obtains the MUK for a service, uses it to encrypt the content streams, and manages the distribution of the associated MSK to the GAA (Generic Authentication Architecture) server or directly to subscribers' UEs via the MBMS Key Distribution Center. The encryption typically uses standardized algorithms, such as Advanced Encryption Standard (AES).

The use of the MUK enables flexible business models. A network operator can broadcast multiple services (some free, some premium) over the same geographic area. Only UEs that possess the correct MUK for a premium service can decrypt it. This allows for pay-TV-like models over cellular broadcast networks. The MUK can be changed periodically (e.g., monthly for a subscription, or per-event for a pay-per-view) to enhance security and manage subscription periods, with new keys delivered via the MSK mechanism.

Purpose & Motivation

The MUK was created to solve the fundamental business and security challenge of broadcast/multicast services over cellular networks: how to monetize content. Unlike unicast, where a dedicated, secure connection exists to each user, broadcast transmits the same data to all users in a cell. Without encryption, any UE could receive premium content for free. The MUK provides the necessary access control, ensuring only paying subscribers can decrypt the content.

It addresses the limitations of simple network access security. While a UE must be authenticated to attach to the network, this does not control access to specific broadcast services. The MUK introduces a separate, service-level security layer. This was crucial for the adoption of MBMS, as content providers (like media companies) would not offer valuable content without a robust mechanism to protect their revenue streams.

Furthermore, the MUK system, as part of the MBMS security framework specified in 3GPP TS 33.246, enables sophisticated service models. It allows for different service keys for different user groups (e.g., different subscription tiers), regional blackouts, and time-limited access. The creation of the MUK and its associated key hierarchy allowed cellular broadcast to compete with traditional broadcast media (like satellite TV) by offering equivalent content protection, thereby motivating the development and deployment of eMBMS for services like LTE Broadcast and 5G Broadcast.

Classification

Part ofMBMS
Specific typesGSK

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-8, normative work from Rel-15.

Rel-15 1 change

In Release 15, the MUK (Multicast User Key) function was newly introduced through the support for SAND (Service and Network-Assisted Delivery) for MBMS. This enhancement specifically relates to the MBMS user service delivery methods, building upon the existing download and streaming methods. The introduction of SAND provides a framework for network-assisted delivery mechanisms within the MBMS architecture.

Rel-16 1 change

In Release 16, the specification introduced the Multicast User Key (MUK) function as a new security procedure for MBMS user service delivery. This addition provided a dedicated key management mechanism for multicast mode, enhancing service protection beyond the existing broadcast security framework. The update also involved correcting the XML data type definitions for attributes within the MBMS User Service Description (USD) to properly support this new function.

  • Missing XML Data Type for Attributes in MBMS USD TS 26.346CR0658
Rel-19 2 changes

In Release 19, the MUK function was enhanced to support in-session unicast repair for MBMS object distribution, allowing for the recovery of lost data during a multicast session. This improvement was complemented by advancements in time synchronization mechanisms for MBMS, increasing the reliability and efficiency of content delivery. These updates provided more robust error recovery and timing coordination for multicast user services.

  • [AMD_PRO-MED] In-session Unicast Repair for MBMS Object Distribution TS 26.346CR0677
  • Improved Time Synchronization for MBMS TS 26.346CR0672

Explore further

Broader topics and technologies where MUK plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 26.346 vj20 MBMS User Services Media Codecs & Protocols Rel-19
TR 26.946 vj00 MBMS User Services Overview Rel-19
TS 31.102 vj40 USIM Application Specification Rel-19
TS 33.246 vj00 MBMS Security Specification Rel-19
TR 33.850 vh00 5G MBS Security Study Rel-17
TS 33.888 vc10 Security Study for Group Communication in LTE Rel-12