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.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (55 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-14, normative work from Rel-15.
In Release 15, the MKFC function was enhanced to support the Multi-talker feature, introducing new procedures such as "Floor Taken Multi-talker" and "Floor Release Multi-talker" for managing concurrent floor requests. It also added specific state machine diagrams for the floor participant and updated the floor control server's operation to handle multiple requests from the same user when queuing. Furthermore, support for functional aliases in floor control message coding and procedures for MBMS bearer announcement over an MBMS bearer were introduced.
- Multi-Talker floor control server TS 24.380CR0178
- Mutli-talker – floor control towards the participant TS 24.380CR0179
- Floor Participant procedures for Multi-talker feature TS 24.380CR0180
- Floor Taken Multi-talker TS 24.380CR0181
- Floor Release Multi-talker TS 24.380CR0182
- Updates to Non-controlling MCPTT function for Multi Talker TS 24.380CR0183
+ 12 more changes
In Release 16, the enhancements for the MKFC function primarily focused on correcting and clarifying floor control procedures. This included specific updates to handle the "Floor taken" message in the 'Pending request' state, improvements to both on-network and off-network floor control timers and events, and corrections for off-network floor control procedures. Furthermore, the release addressed scenarios like multi-talker floor requests and SSRC handling for implicit floor requests to improve reliability.
- Align the NOTE related to multitalker or dual floor for receive RTP event in any state TS 24.380CR0239
- Handle Floor taken message in 'Pending request' state of floor participant state m/c TS 24.380CR0240
- Include the missing events in floor participant state m/c TS 24.380CR0241
- EN on Floor Request multi talker TS 24.380CR0222
- Corrections to Off-Network Floor Control procedures TS 24.380CR0235
- SSRC handling for implicit floor request case TS 24.380CR0242
+ 1 more changes
In Release 17, the MKFC function was enhanced with specific corrections and clarifications to floor control procedures, including the handling of floor request queue cancellation and authorized user clearing of the entire queue. The release introduced alignments between the MCPTT client and Participating MCPTT function and provided updates to state transition diagrams for both floor participants and the floor control server. Furthermore, it delivered clarifications for the list of locations of granted floor participants and corrected procedures for scenarios like group regrouping and call setup over pre-established sessions.
- Cancel queued floor request and notify to users TS 24.380CR0275
- An authorized user clearing the entire floor request queue TS 24.380CR0304
- Corrections to floor indicator of On-Network Floor Control procedures TS 24.380CR0274
- Corrections to floor control messages handling for upgrade/downgrade of broadcast call TS 24.380CR0289
- Clarification for list of locations of granted floor participants TS 24.380CR0294
- MCPTT client and Participating MCPTT function alignments TS 24.380CR0296
+ 9 more changes
In Release 18, enhancements to the MKFC function included the addition of 5G Multicast/Broadcast Service (MBS) support within the MCPTT media plane and the specification of multiplexing procedures for RTP audio and RTCP floor control using Synchronization Source (SSRC) identifiers. These updates also introduced new timers and counters for MBS channel control within the participating MCPTT function and corrected several protocol message details, such as the Floor Ack message type and the handling of queued floor request retransmissions.
- Addition of 5G MBS in MCPTT media plane TS 24.380CR0332
- Add timers and counters in the participating MCPTT function for MBS channel control TS 24.380CR0347
- MCPTT Adding user ID in Floor Request message from NCF to CF TS 24.380CR0348
- MCPTT support of multiplexing - SSRC used in RTCP signalling over 5MBS TS 24.380CR0363
- MCPTT support of multiplexing - SSRCs used for RTP audio and RTCP floor control TS 24.380CR0356
- Correction of Floor Ack message type TS 24.380CR0324
+ 6 more changes
In Release 19, the MKFC function was enhanced with a specific procedure for an authorized user to revoke the floor, interrupting the current talker. This release also introduced additions to the floor control release message and included miscellaneous corrections to the overall floor control mechanisms.
Explore further
Broader topics and technologies where MKFC plays a role.
Defining Specifications
3GPP specifications that define or reference MKFC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.380 vj10 | MCPTT Media Plane Control Protocol | Rel-19 |
| TS 33.180 vk00 | Security of Mission Critical (MC) Service | Rel-20 |
| TS 33.880 vf10 | Security Study for Enhanced Mission Critical Services | Rel-15 |