Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

MCVideo

Mission Critical Video

Services →

MCVideo is a 3GPP mission-critical service introduced in Release-14 that provides reliable, low-latency, and prioritized real-time video communication over cellular networks for public safety and emergency response scenarios.

Introduced
Rel-14
Where
Services › IMS
Specifications
2 specs
MCVideo Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

Mission Critical Video (MCVideo) is a standardized service within the 3GPP framework that enables real-time video communication for mission-critical operations, such as those conducted by public safety agencies, first responders, and industrial teams. It works by establishing video sessions between users or groups over LTE or 5G networks, leveraging the Mission Critical Services (MCS) architecture to ensure high reliability, low latency, and prioritized access. The architecture includes key components like the MCVideo client on user equipment, which captures and encodes video streams, and the MCVideo server in the network, which manages session control, media distribution, and interoperability with other mission-critical services like MCPTT and MCData. The service operates in conjunction with core network functions such as the Policy and Charging Rules Function (PCRF) to enforce QoS policies, ensuring that video traffic receives higher priority over commercial traffic during emergencies. Its role in the network is to provide a secure and resilient video communication platform that supports features like group video calls, video push-to-talk, and integration with location services, enabling enhanced situational awareness. MCVideo utilizes protocols like SIP for signaling and RTP for media transport, with extensions for mission-specific requirements such as fallback to narrowband networks or operation in isolated environments. By standardizing this service, 3GPP facilitates interoperability across different vendors and networks, which is crucial for effective cross-agency collaboration during critical incidents.

Purpose & Motivation

MCVideo was created in Rel-14 to address the gap in standardized video communication for mission-critical scenarios, where existing consumer video services lacked the reliability, security, and prioritization needed for emergency response. Prior to its introduction, public safety organizations often relied on proprietary video systems or adapted commercial solutions, which suffered from interoperability issues, inconsistent performance under network congestion, and insufficient integration with voice and data services. The development of MCVideo was motivated by the increasing use of video in fields like law enforcement, firefighting, and disaster management, where real-time visual information can significantly improve decision-making and coordination. It solves problems related to network resilience by incorporating features like QoS prioritization, service continuity during handovers, and support for degraded network conditions. Historically, as 3GPP expanded its mission-critical portfolio from MCPTT (voice) in Rel-13 to include data and video, MCVideo represented a natural evolution to provide a comprehensive communication suite. It addresses limitations of previous approaches by ensuring that video services are built on the same robust architecture as other mission-critical components, enabling seamless interoperability and enhanced safety for users in high-stakes environments.

What changed in its specifications

The latest release-to-release comparison of specifications that define MCVideo. Each summary describes the whole specification, not only this term.

TS 23.281Rel-18 → Rel-19

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 →

Technology family

Mission-critical services · Services

  1. Rel-12 GCS AS, GCSE_LTE, ProSe
  2. Rel-13 IOPS, MCPTT, ProSe UE-to-Network Relay
  3. Rel-14 MCData, MCVideo, MCX common functional architecture
  • MCVideo builds on MCX common functional architecture
    “The MCVideo architecture is based on the functional architecture for mission critical communication services defined in 3GPP TS 23.280 [6].” TS 23.281
  • MCVideo coexists with MCPTT
    “MC service: A generic name for any one of the three mission critical services: either MCPTT, or MCVideo, or MCData.” TS 23.280
  • MCVideo coexists with MCData
    “MC service: A generic name for any one of the three mission critical services: either MCPTT, or MCVideo, or MCData.” TS 23.280

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 7 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-14 introduced

MCVideo service is first specified in Rel-14, with stage 2 architecture (TS 23.281), call control signalling (TS 24.281) and media plane control (TS 24.581) defining its entities, procedures and definitions.

  • “This document specifies the functional model, procedures and information flows needed for the mission critical video (MCVideo) service.” TS 23.281 v14.7.0
  • “The present document specifies the signalling control needed to support Mission Critical Video (MCVideo) service.” TS 24.281 v14.16.0
  • “MCVideo service: A video communication service supporting applications for mission critical organizations and mission critical applications for other businesses and organizations” TS 23.281 v14.7.0
Rel-15 specification text

MCVideo gained new capabilities in Rel-15: ambient viewing calls, MC gateway server interconnection with new reference points, and MBMS bearer use for downlink media and transmission control.

  • “Ambient viewing call: a call type allowing an authorized MCVideo user to cause an MCVideo client to initiate a communication” TS 24.281 v15.16.0
  • “The MCVideo-3 reference point exists between the MCVideo server and another MCVideo server and between the MCVideo server and the MC gateway server” TS 23.281 v15.6.0
  • “The participating MCVideo function can use an MBMS bearer for the DL transmission of the media and the media control plane.” TS 24.581 v15.9.0
Rel-16 1 CR

MCVideo gained new Rel-16 behaviour: functional alias support, a group call leave procedure, a server limit on simultaneous service authorizations, and reworked emergency alert configuration handling.

  • “shall check if the number of maximum simultaneous authorizations supported for the MCVideo user as specified in the <max-simultaneous-authorizations> element” TS 24.281 v16.12.0
  • “functional alias activation, deactivation, take over and interrogation support for MCVideo user.” TS 23.281 v16.4.0
  • Add functional alias to MCVideo group calls TS 23.281CR0127
Rel-17 1 CR

MCVideo gained functional alias support (states, usage by users, configuration) plus restricted private communications, application priority and revised MCVideo-5 reference point handling in Rel-17.

  • “the "take-over-possible" state indicating that the MCVideo user is interested in using the functional alias but the functional alias is already activated” TS 24.281 v17.13.0
  • “- use a functional alias to identify the MCVideo user.” TS 24.281 v17.13.0
  • Enhancing MCVideo communication requests with application priority capabilities in on-network mode TS 23.281CR0139
Rel-18 1 CR

MCVideo gained ad hoc group call and emergency alert support, location information in group calls, functional alias private calls, and multiplexing with SSRC handling in Rel-18.

  • “The ad hoc group calls can use the participants list provided by either an initiator of the call or MCVideo server.” TS 23.281 v18.12.0
  • Ad hoc group call feature for MCVideo TS 23.281CR0173
  • “If the group join request includes a request to transmit media it may also include location information.” TS 23.281 v18.12.0
Rel-19 2 CRs

Rel-19 changes MCVideo itself: ad hoc group call participant criteria can be modified during a call, migrated users are handled, and a transmission idle message is introduced.

  • “Such requests are known as "SIP MESSAGE request to modify participant criteria for ad hoc group emergency alert to participating MCVideo function"” TS 24.281 v19.7.0
  • Modify list of participants by changing the criteria during an ongoing MCVideo ad hoc group call (single MC system) TS 23.281CR0185
  • Introducing transmission idle message for MCVideo TS 23.281CR0195
Rel-20 1 CR

MCVideo specs changed behaviour: server-to-server ad hoc group call request/response flows were added, and group member targeting and affiliation status procedures were clarified, including excluding the call initiator from invitations.

  • “The MCVideo server shall only invite affiliated group members to a group session, excluding the member that initiated the call.” TS 24.281 v20.1.0
  • “7.19.2.3a Ad hoc group call request (MCVideo server – MCVideo server)” TS 23.281 v20.5.1
  • Correction on server-server information flows (MCVideo) TS 23.281CR0264

Defining Specifications

3GPP specifications that define or reference MCVideo, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.281 vk51 Mission Critical Video Service Rel-20 read
TS 37.579 vi50 Mission Critical (MC) services Rel-18 read