Description
Floor control is a core functional element of Mission Critical Push To Talk (MCPTT) and related mission-critical services in 3GPP. In a push-to-talk system, multiple participants share a single communication channel, and only one party can speak at a time. Floor control is the arbitration system that determines who has the authority to transmit (talk) at a point in time during an MCPTT call. It manages joint or exclusive access to the shared communication resource, ensuring orderly and deterministic access to the channel.
The concept originates from generic conferencing and multimedia session control, where floor control manages access to shared resources as described in RFC 4376. 3GPP adopted this concept in its early mission-critical specifications and later specialized it for MCPTT. Architecturally, floor control in MCPTT is realized through a floor control server function that maintains the state of the floor (who currently holds it, who has requested it, and the queue of pending requests). MCPTT clients send floor requests to the floor control server, which grants, denies, or queues them according to configured policies, priorities, and the current floor state.
The floor control server interacts with the MCPTT server and uses signaling protocols to exchange floor requests and floor grants. Key procedures include floor request, floor grant, floor release, floor idle notification, and floor revocation. Priority handling allows higher-priority users (e.g., commanders or emergency responders) to preempt lower-priority users or to be placed at the head of the queue. The system also supports dual floor control and various queuing policies to handle congestion and contention among many participants.
Floor control is tightly coupled with the media plane: when the floor is granted, the MCPTT client is authorized to send media (typically RTP audio) to the group, and other participants receive it. When the floor is released, the floor becomes idle or is granted to the next queued requester. The floor control server must therefore coordinate with media distribution functions to ensure that only the authorized talker's media is distributed, preventing collisions and ensuring that emergency communications remain orderly.
Because mission-critical communications demand determinism, low latency, and priority handling, floor control is a critical enabler of MCPTT service quality. It ensures that in a group call among first responders, the right person gets the channel at the right time, that emergency preemption works, and that the system behaves predictably under heavy load. The concept has been carried forward across many 3GPP releases and extended to MCVideo and MCData services, where analogous floor control mechanisms govern access to shared media and data resources.
Purpose & Motivation
Push-to-talk communication inherently involves a shared channel where only one party can transmit at a time. Without a deterministic arbitration mechanism, participants would collide, transmissions would overlap, and critical voice communications would be unintelligible. Floor control exists to solve this problem by providing a formal, policy-driven mechanism for granting and revoking the right to transmit. It ensures orderly access to the shared resource, supports prioritization so that commanders and emergency callers can gain the floor when needed, and provides predictable behavior under contention.
The concept was originally developed in the conferencing and multimedia community, where RFC 4376 described floor control as a means to manage joint or exclusive access to shared resources. 3GPP initially adopted this generic definition in its early mission-critical specifications. However, as MCPTT matured, it became clear that the generic conferencing definition did not capture the specific mission-critical requirements: priority and preemption, queuing, emergency handling, and tight integration with the MCPTT media plane. In Rel-13, 3GPP replaced the generic definition with a service-specific one describing floor control as an arbitration system in an MCPTT Service that determines who has the authority to transmit at a point in time during an MCPTT call.
This specialization reflects the evolution from generic conferencing to mission-critical communications, where floor control is not merely a convenience but a safety-critical function. It enables first responders to communicate reliably in high-stress, high-contention environments, supports hierarchical command structures through priority handling, and integrates with the broader MCPTT architecture including group management, identity management, and media distribution.
What changed in its specifications
The latest release-to-release comparison of specifications that define Floor Control. Each summary describes the whole specification, not only this term.
Rel-17 added Mission Critical Push-to-talk Phase 3 to TS 22.179, covering general overview, Figure 6.15.3.1.1, and requirements. It also changed three other related items in the same release.
Full comparison in TS 22.179 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Definition wording was revised to specialize the concept for mission-critical services: floor control was redefined as an arbitration system in an MCPTT Service that determines who has the authority to transmit (talk) at a point in time during an MCPTT call, replacing the generic conferencing-oriented definition.
Defining Specifications
3GPP specifications that define or reference Floor Control, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.179 vl00 | MCPTT Service Requirements | Rel-21 read |
| TR 22.948 vj00 | IMS Convergent Multimedia Conferencing Requirements | Rel-19 read |
| TS 23.779 vd00 | MCPTT over LTE Stage 2 Study | Rel-13 read |