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

Glossary term · Security

MSCCK

MBMS Sub-Channel Control Key

Security →

MSCCK is a security key used in MBMS to protect the integrity and confidentiality of sub-channel control information, such as scheduling and configuration data, preventing unauthorized access and service disruption.

Introduced
Rel-13
Where
Services
Specifications
4 specs
MSCCK Description Purpose What changed Neighbours Specifications

Description

The MBMS Sub-Channel Control Key (MSCCK) is a cryptographic key defined within the 3GPP security architecture for Multimedia Broadcast Multicast Service (MBMS). Its primary function is to secure the control plane information associated with MBMS sub-channels. An MBMS service can be divided into multiple sub-channels, each potentially carrying different content or quality levels. The control information for these sub-channels, which includes scheduling details, configuration parameters, and service announcements, is transmitted over the air interface and must be protected to ensure service reliability and prevent spoofing or denial-of-service attacks.

The MSCCK is derived within the BM-SC (Broadcast Multicast Service Centre) as part of the MBMS key hierarchy. It is generated from a parent key, the MBMS Service Key (MUK), using a Key Derivation Function (KDF) with specific input parameters that identify the service and the control channel. This derived key is then used to compute integrity protection values (MACs) and, optionally, to encrypt the control messages sent on channels like the MCCH (MBMS Control Channel) or MSCH (MBMS Scheduling Channel). The UE (User Equipment) receiving the MBMS service must also derive the same MSCCK using the MUK it has securely obtained, allowing it to verify the integrity and decrypt the control information.

Architecturally, the MSCCK operates within the MBMS security framework defined in TS 33.246 and related specs. It is a crucial element for enabling secure selective decryption in MBMS. By having separate keys for control and traffic, the network can provide free-to-air control information (protected by MSCCK) while keeping the actual media content encrypted with a different key (the MTK - MBMS Traffic Key). This separation allows for flexible service models, such as enabling users to discover and subscribe to services via protected control channels before purchasing the key for the content itself. The MSCCK's role is therefore foundational for secure service provisioning, efficient key management, and robust protection against attacks targeting the service discovery and configuration mechanisms in broadcast networks.

Purpose & Motivation

The MSCCK was introduced to address specific security vulnerabilities in the MBMS control plane. Early MBMS deployments focused on securing the user plane traffic (the actual video or data stream) with the MTK. However, the control information necessary for a UE to find, subscribe to, and correctly receive an MBMS service was often sent in the clear or with insufficient protection. This created a vector for attacks where malicious actors could inject false scheduling information, causing UEs to tune to incorrect frequencies or time slots, leading to service disruption (denial-of-service) or battery drain.

The creation of the MSCCK was motivated by the need for a holistic security approach for broadcast services. It solves the problem of ensuring the authenticity and integrity of critical service metadata. Without it, an attacker could forge service announcements or modify scheduling parameters, undermining the entire MBMS service model. The MSCCK enables the network to cryptographically bind control information to the legitimate service provider (the BM-SC), ensuring that UEs only act on commands from a trusted source. This is especially important for commercial services, including mobile TV and public safety communications, where reliable and tamper-proof service discovery is essential. Its introduction in Rel-13 as part of enhanced MBMS security (eMBMS) reflects the growing emphasis on robust security for broadcast-based 5G enablers like LTE-based 5G Broadcast.

What changed in its specifications

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

TS 24.380Rel-17 → Rel-18

Rel-18 adds media plane multiplexing via mc_floor_ssrc fmtp and Audio SSRC in floor control. It adds an MBS subchannel control protocol. It also adds invited user identity, group call setup, and floor control SSRC/SDP fields.

Full comparison in TS 24.380 →
TS 33.180Rel-18 → Rel-19

Rel-19 adds recording admin and replay access-token claims to TS 33.180 and removes the MC user event audit and service media collection text. It also adds Annex B recommendations on client registration, authentication request handling, public key distribution, and Issuer claim verification of the access token.

Full comparison in TS 33.180 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-13 Initial

Initially introduced as part of enhanced MBMS (eMBMS) security enhancements. Defined the key hierarchy where MSCCK is derived from the MUK to specifically protect sub-channel related control information (e.g., on MSCH). Established its role in securing scheduling and configuration data for MBMS services.

Defining Specifications

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

SpecificationTitleRelease
TS 24.380 vk10 MCPTT Media Plane Control Protocols Rel-20 read
TS 33.179 vdc0 MCPTT Security Architecture and Procedures Rel-13 read
TS 33.180 vk10 Security of the Mission Critical Service (MCX) Rel-20 read
TS 33.880 vf10 Security Study for Enhanced Mission Critical Services Rel-15 read