Description
MCVideo Emergency Alert (MVEA) is a standardized service defined by 3GPP for public safety communications, specifically within the Mission Critical Services (MCS) framework. It operates as part of the MCVideo architecture, which is an evolution of Mission Critical Push-to-Talk (MCPTT) to include video capabilities. MVEA enables an authorized user, typically a dispatcher or incident commander, to initiate an emergency alert that includes video content. This alert is then broadcast to a predefined or dynamically formed group of MCVideo users, such as emergency personnel in a specific geographic area. The service leverages the underlying LTE or 5G network infrastructure, utilizing IP Multimedia Subsystem (IMS) for session control and the MCVideo application server for service logic and group management.
The architecture of MVEA involves several key components. The MCVideo client on user equipment (UE) supports the capability to send and receive emergency alerts. The MCVideo application server, which may be part of a dedicated public safety network or a commercial network with MCS support, handles the authorization, routing, and distribution of the alert. It interfaces with the Group Management System to determine the target recipients, often based on group membership (like an emergency response team) or location. The alert initiation typically involves the user activating an emergency function, which triggers a session establishment procedure via IMS. The video content, which could be pre-recorded or live streamed, is then transmitted using Real-time Transport Protocol (RTP) over the established bearer, with Quality of Service (QoS) mechanisms ensuring priority and low latency.
MVEA works by integrating with the core network's emergency services enhancements. When an MVEA is initiated, the MCVideo server validates the requestor's credentials and the emergency context. It then establishes a one-to-many communication session. The alert may include metadata such as urgency level, location, and text description alongside the video. The system ensures reliable delivery, often using mechanisms like confirmation receipts. Its role in the network is to provide a standardized, interoperable method for emergency video broadcasting, which is essential for coordinated responses in disasters, terrorist attacks, or large-scale accidents, where visual information can significantly improve situational awareness and decision-making.
Purpose & Motivation
MVEA was created to address the critical need for rapid, reliable, and rich-media emergency communication in public safety scenarios. Prior to its standardization, emergency alerts were largely limited to voice (e.g., sirens, radio broadcasts) or text (e.g., SMS, Cell Broadcast), which lack the contextual depth of live video. The limitations of these approaches included delayed comprehension, ambiguity in describing complex scenes, and an inability to provide real-time visual updates to distributed teams. The motivation for MVEA stemmed from lessons learned in major incidents where first responders lacked shared visual awareness, leading to inefficient resource deployment and increased risk.
Historically, public safety communications relied on legacy Land Mobile Radio (LMR) systems, which are voice-centric and have limited data capabilities. The transition to broadband LTE and 5G networks under the 3GPP Mission Critical Services umbrella enabled multimedia services. MVEA specifically solves the problem of disseminating urgent visual information—such as live footage from a fire, a suspect's image, or a hazardous material leak—to all relevant personnel simultaneously. It ensures that commanders can convey complex situations more effectively than with voice alone, potentially saving lives and property.
The creation of MVEA was driven by requirements from public safety agencies worldwide, coordinated through standards bodies like 3GPP. It integrates with other MCS components like MCPTT and MCData to provide a comprehensive mission-critical ecosystem. By standardizing MVEA, 3GPP ensures interoperability across different vendors and networks, which is vital for cross-border emergencies and multi-agency responses. It represents a significant evolution from traditional alerting systems by leveraging modern IP-based networks to enhance emergency preparedness and response capabilities.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (125 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 MVEA (MCVideo Emergency Alert) function was introduced, enabling the initiation of emergency alerts through mechanisms like implicit transmission requests when joining an MCVideo chat group. The release also defined specific triggering criteria for MCVideo emergency location and established distinct internal client states to manage emergency alerts, such as the "MCVideo emergency alert state" and "MCVideo private emergency alert state." These additions provided the foundational call control and state management protocols necessary to support emergency alerting within the MCVideo service architecture.
- MCVideo ambient viewing client procedures TS 24.281CR0033
- MCVideo ambient viewing participating MCVideo function procedures and controlling MCVideo function procedures TS 24.281CR0034
- MCVideo ambient viewing general description TS 24.281CR0035
- Usage of MBMS for MCVideo - signaling control TS 24.281CR0037
- Correction to session-type in XML schema for MCVideo Information TS 24.281CR0039
- Fix issues with encoding of IEs in MONP messages for MCVideo TS 24.281CR0046
+ 8 more changes
In Release 16, the MVEA function was enhanced to support off-network operations, allowing emergency alerts to function without cellular network infrastructure. The release also included corrections and fixes to core alerting parameters, the alert element structure, and the location data schema to ensure reliability. Furthermore, it completed the necessary IANA registrations for the MCVideo protocol to standardize its identifiers.
In Release 17, the MVEA (MCVideo Emergency Alert) function was enhanced with new **emergency alert area notification functionalities**, including specific handling for client-side operations. Furthermore, the protocols were extended to support **interconnect procedures for MCVideo Emergency Alerts**, enabling alerting across different MCVideo systems. These updates were complemented by general improvements to location reporting, such as adding **altitude and accuracy to the MCVideo location XML schema**.
- Functional Alias usage in MCVideo Call TS 24.281CR0093
- Add altitude, timestamp to MCVideo location XML schema TS 24.281CR0095
- Add preconfigured regroup to MCVideo TS 24.281CR0096
- Control per service authorizations limit for MCVideo service TS 24.281CR0100
- Call control - Restricting MCVideo private communications TS 24.281CR0105
- Emergency alert area notification functionalities handling for MCVideo TS 24.281CR0106
+ 33 more changes
In Release 18, key enhancements for the MCVideo Emergency Alert (MVEA) function included the specific procedure to handle clients affiliating to a group that is already in an emergency alert state. Furthermore, the release introduced support for emergency adhoc group calls and imminent peril adhoc group calls within the MCVideo service, expanding the scenarios for emergency communications. These updates built upon the existing architectural procedures for MCVideo emergency alerts and imminent-peril calls as specified in the stage 2 document.
- Use of 5G MBS transmission in MCVideo signalling plane TS 24.281CR0199
- Add the description of 5MBS in MCVideo TS 24.281CR0220
- MCVideo support of multiplexing - SDP offers and answers TS 24.281CR0215
- Support MCVideo over 5G ProSe TS 24.281CR0225
- General adhoc group call procedures in single system - Protoc impl for MCVideo TS 24.281CR0221
- Adhoc group call participants modify procedures in single system - protoc impl MCVideo TS 24.281CR0226
+ 43 more changes
In Release 19, the MVEA (MCVideo Emergency Alert) function was enhanced for ad hoc group scenarios by modifying the criteria for determining the list of participants during an ongoing alert. This included adding specific criteria to the SIP message containing the participant lists sent to authorized users. These changes were accompanied by corrections to the procedures and XML schemas for ad hoc group emergency alerts to ensure proper functionality.
- Modify list of participants by changing the criteria during an ongoing MCVideo ad hoc group call TS 24.281CR0278
- Adhoc group emergency alert add criteria to the SIP message containing the participant lists sent to the authorised users TS 24.281CR0279
- MCVideo adhoc group call to migrated user TS 24.281CR0280
- Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert TS 24.281CR0282
- FRMCS_Ph5 Adding reason to leave a session in MCVideo TS 24.281CR0290
- Enhance handling of criteria for ad hoc group communication (MCVideo) TS 24.281CR0267
+ 11 more changes
Explore further
Broader topics and technologies where MVEA plays a role.
Defining Specifications
3GPP specifications that define or reference MVEA, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.281 vj40 | MCVideo Signalling Control Specification | Rel-19 |
| TS 37.579 vi40 | Mission Critical services conformance testing | Rel-18 |