Description
Transmission control is a core function of the Mission Critical Video (MCVideo) service defined in 3GPP TS 23.281 (Functional architecture and information flows to support Mission Critical Video) and related specifications such as TS 23.282 and TS 23.783. MCVideo is part of the broader Mission Critical Services (MCX) family, which also includes MCPTT (push-to-talk) and MCData. These services are designed for public safety, railway, utility, and other mission-critical users who require reliable, prioritized communication.
In MCVideo, transmission control governs who is allowed to send video at any given time and how that video is distributed to other participants. Unlike a conventional video conference where multiple participants may stream simultaneously, MCVideo typically uses a controlled, arbitrated model similar to push-to-talk: a participant requests the floor (permission to transmit), and the transmission control function grants or denies that request based on configured policy, priority, and current usage. This prevents network congestion and ensures that the most important video stream gets through.
The transmission control function is implemented in the MCVideo server, which is part of the MCVideo service layer. It interacts with the group management, identity management, and configuration management functions to determine authority. When a participant is granted transmission authority, the server also determines the onward downlink transmission — that is, how the video is forwarded to other participants, including which recipients receive it and over which bearers. This may involve unicast or multicast distribution, and it must respect QoS and priority requirements.
The mechanism also handles pre-emption and revocation. A higher-priority user may pre-empt an ongoing transmission, and the server must manage the transition cleanly. Transmission control is therefore tightly coupled with QoS, security, and group communication functions. It ensures that video communication is orderly, fair, and aligned with operational priorities.
Since its introduction in Rel-14, the definition has remained essentially stable, with only minor editorial corrections (such as changing "an video call" to "a video call" in Rel-19). This stability reflects the maturity of the MCVideo service concept and its alignment with the well-established MCPTT floor control model.
Purpose & Motivation
Transmission control exists to bring order and priority to video communication in mission-critical environments. In public safety and railway operations, bandwidth is limited and the stakes are high; uncontrolled video streaming could congest the network and prevent critical information from getting through. The transmission control mechanism solves this by arbitrating who may transmit and ensuring that the most important video is delivered first.
The concept builds on the floor control model developed for MCPTT, extending it to video. Previous voice-only systems did not need to manage video bandwidth or multiple simultaneous streams. As mission-critical services evolved to include video, a new control mechanism was needed to handle the unique characteristics of video: higher bandwidth, different latency tolerances, and the need for onward distribution decisions.
Transmission control also supports interoperability and policy enforcement. By centralizing the decision in the MCVideo server, operators can apply consistent policies across users and groups, integrate with priority and pre-emption schemes, and ensure that video communication complies with operational rules.
What changed in its specifications
The latest release-to-release comparison of specifications that define Transmission control. Each summary describes the whole specification, not only this term.
Enhanced Mission Critical Architecture adds MCVideo procedures for ad hoc group call release, leave, and criteria modification, plus call handling during group regroup.
Full comparison in TS 23.281 →Adds ad hoc group data session leave, standalone data/FD, criteria modification procedures, and new information elements.
Full comparison in TS 23.282 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (4 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference Transmission control, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.281 vk51 | Mission Critical Video Service | Rel-20 read |
| TS 23.282 vk31 | Mission Critical Data Architecture | Rel-20 read |
| TR 23.783 vi00 | Technical Report on Mission Critical Services over 5GS | Rel-18 read |