Talk Burst Control Protocol

Description

The Talk Burst Control Protocol (TBCP) is a client-server protocol operating over IP, typically using SIP and RTP as underlying carriers. It is a core component of the Open Mobile Alliance (OMA) Push-to-Talk over Cellular (PoC) service, which 3GPP has adopted and referenced for standardized mission-critical and commercial group communication services. TBCP messages are transported within the RTP Control Protocol (RTCP) or as standalone SIP messages, allowing for efficient, in-band control alongside the media stream. The protocol defines a state machine for floor control involving the PoC client (participant) and the PoC server (controlling entity).

The protocol works through a series of defined messages: Talk Burst Request, Talk Burst Granted, Talk Burst Deny, Talk Burst Release, and Talk Burst Taken. When a user wants to speak, their client sends a TBCP Talk Burst Request to the PoC server. The server, applying pre-configured rules (like queuing, pre-emption priorities, or first-come-first-served), decides to grant the floor. It then sends a Talk Burst Granted message to the requesting client and a Talk Burst Taken message to all other participants in the session, informing them the floor is occupied. The speaking client streams voice packets (the talk burst) over RTP. Upon finishing, the client sends a Talk Burst Release message, and the server updates the floor state to idle, potentially notifying participants.

Key architectural components include the Participating PoC Function (client) and the Controlling PoC Function (server). The server's floor control logic is critical, especially for mission-critical services where priorities, pre-emption, and queuing are vital. TBCP also supports notifications like Talk Burst Idle and Talk Burst Revoke (to take the floor away). Its integration with 3GPP systems is specified for Mission Critical Push To Talk (MCPTT), where it ensures disciplined, low-latency control over who transmits in a group call, which is essential for public safety and utility workforce communications. The protocol is designed for minimal latency in granting the floor to provide a natural 'walkie-talkie' user experience.

Purpose & Motivation

TBCP was created to solve the fundamental problem of coordinated access to a shared half-duplex communication channel in an IP-based group communication service. Early voice group calls in cellular networks were circuit-switched and network-controlled. With the move to all-IP networks (IMS), a standardized, efficient floor control protocol was needed to enable Push-to-Talk services that emulate the instant, one-to-many nature of traditional walkie-talkies but over wide-area cellular networks.

The protocol addressed the limitations of ad-hoc or proprietary solutions, ensuring interoperability between different vendors' PoC clients and servers. Its design within the OMA and subsequent adoption by 3GPP for Mission Critical Services (MCS) was motivated by the public safety community's need for reliable, instant group communication. TBCP provides the deterministic, network-controlled arbitration necessary to prevent chaotic collisions of audio from multiple speakers, which is crucial in high-stakes scenarios. It enables features like prioritized talkers, which allow dispatchers or incident commanders to pre-empt others, directly addressing operational requirements that previous consumer-grade voice services could not meet.

Key Features

• Manages floor control state for half-duplex group communication
• Uses RTCP or SIP for transport of control messages
• Defines messages for Request, Grant, Deny, Release, and Take of talk bursts
• Supports priority-based and queued floor control for mission-critical use
• Integrated into 3GPP Mission Critical Push To Talk (MCPTT) service
• Provides notifications to all participants about floor state changes

Evolution Across Releases

Defining Specifications