MKFC

Multicast Key for Floor Control

Security
Introduced in Rel-14
A cryptographic key used in Multimedia Broadcast/Multicast Service (MBMS) to secure floor control signaling for group communication. It ensures that only authorized users can request or be granted the 'floor' (permission to speak) in mission-critical services like MCPTT.

Description

The Multicast Key for Floor Control (MKFC) is a security key defined within the 3GPP Multimedia Broadcast/Multicast Service (MBMS) security framework, specifically for securing floor control procedures in mission-critical group communication services. Floor control is a mechanism that arbitrates access to a shared communication channel, determining which user in a group has the 'floor' or permission to transmit media at any given time. In mission-critical push-to-talk (MCPTT) and similar services, this arbitration is crucial for orderly and efficient communication, especially in high-stakes scenarios like public safety operations. The MKFC is used to protect the integrity and authenticity of floor control messages exchanged between the user equipment (UE) and the network, preventing unauthorized users from seizing the floor or disrupting ongoing communication.

The MKFC operates within the MBMS User Services (MBMS-US) layer and is part of the MBMS key hierarchy. It is derived from higher-level keys, such as the MBMS Service Key (MSK) or the MBMS Group Key (MGK), depending on the service configuration and security mode. The key derivation process is specified in 3GPP security specifications (TS 33.180, TS 33.880) and ensures that only users subscribed to a particular MBMS bearer service and authorized for floor control can generate or validate the correct MKFC. The key is typically used with cryptographic algorithms to generate message authentication codes (MACs) for floor control signaling messages, ensuring that a floor request, grant, deny, or release command is legitimate and has not been tampered with.

Architecturally, the MKFC is managed by the BM-SC (Broadcast Multicast Service Centre) or the mission-critical service application server in coordination with the Key Management Function (KMF). The KMF is responsible for generating and distributing the necessary keying material to authorized UEs. When a UE joins an MBMS-based group communication session, it receives the relevant keys, including the MKFC, through secure key delivery procedures, often leveraging the MBMS key distribution mechanism defined in the Generic Authentication Architecture (GAA). The UE then uses this MKFC to secure its floor control signaling for the duration of the session.

The role of MKFC in the network is to enable secure, trusted, and efficient floor management for group communications over LTE and 5G NR broadcast/multicast bearers. By cryptographically binding floor control actions to authorized users and the specific service session, it prevents spoofing, replay attacks, and denial-of-service attacks targeting the floor control mechanism. This is particularly vital for mission-critical services where communication reliability, precedence, and security are paramount. The MKFC thus forms a foundational element in securing the signaling plane of MBMS-based group communication services as standardized by 3GPP.

Purpose & Motivation

The MKFC was introduced to address the specific security requirements of floor control in mission-critical group communication services delivered via MBMS. Prior to its standardization, group communication services often relied on unicast connections or less secure multicast mechanisms that did not provide robust, cryptographic protection for arbitration signaling. In critical scenarios like public safety, emergency response, or railway communications, ensuring that only authorized personnel can request and be granted the floor is essential to prevent chaos, impersonation, or malicious disruption of communications.

The creation of MKFC was motivated by the 3GPP's work on enhancing LTE and later 5G for critical communications, particularly within the framework of Mission Critical Services (MCS) starting from Release 13 and evolving through subsequent releases. The need for a dedicated security key arose from the analysis of threats specific to multicast/broadcast delivery and floor control protocols. Without such a key, floor control messages could be forged, allowing unauthorized users to monopolize the channel or deny legitimate users the ability to speak, severely compromising the effectiveness of mission-critical operations.

By defining MKFC, 3GPP provided a standardized, cryptographically secure method to authenticate and integrity-protect floor control signaling within the MBMS architecture. This addressed limitations of previous ad-hoc or non-standardized approaches, enabling interoperability across different vendors and network operators while meeting the stringent security and reliability requirements of public safety and industry verticals. It forms part of a comprehensive security framework for MBMS, ensuring that the efficiency gains of multicast delivery do not come at the expense of security for critical control functions.

Key Features

  • Derived from higher-level MBMS security keys (e.g., MSK, MGK) as part of a defined key hierarchy
  • Used to integrity-protect and authenticate floor control request, grant, deny, and release messages
  • Enables secure arbitration of the 'floor' in MBMS-based group communication services like MCPTT
  • Managed and distributed by the Key Management Function (KMF) and BM-SC
  • Integrates with the Generic Authentication Architecture (GAA) for secure key delivery to UEs
  • Protects against spoofing, replay, and denial-of-service attacks on floor control signaling

Evolution Across Releases

Rel-14 Initial

Introduced the Multicast Key for Floor Control (MKFC) as part of the enhanced security framework for MBMS-based Mission Critical Services. Defined its derivation from the MBMS Service Key (MSK) or MBMS Group Key (MGK) and its use in securing floor control signaling for MCPTT over MBMS, as specified in TS 33.180 and TS 33.880.

Defining Specifications

SpecificationTitle
TS 24.380 3GPP TS 24.380
TS 33.180 3GPP TR 33.180
TS 33.880 3GPP TR 33.880