MCVideo Emergency State

Description

MCVideo Emergency State (MVES) is a logical and functional state entered by a user's Mission Critical Service Client (e.g., an MCVideo application) and recognized by the network's Mission Critical Server. It is triggered by an explicit user action to initiate an emergency service, most commonly the start of an MCVideo Emergency Private Call (MVEPC). Entering MVES is a pivotal event that alters the operational parameters and network handling for all communications from that user for the duration of the emergency incident.

Architecturally, the state transition is managed collaboratively between the MC Client and the MCVideo Server. When a user triggers an emergency video call, the client application sends a specific service request (e.g., an emergency session initiation request as per TS 24.281) to the MCVideo server. Upon validating the request and beginning call setup, the server acknowledges and confirms the activation of MVES for that user. This state is then maintained in both the client and the server. The client's user interface may change (e.g., displaying a prominent 'EMERGENCY' indicator), and its behavior is modified—for instance, it may automatically accept incoming emergency-related communications or restrict non-emergency actions.

From a network perspective, the declaration of MVES has significant implications. It informs the MCVideo server and, by extension, the core network policies that this user's traffic should be treated with the highest priority, not just for the initial call but for any follow-on communication. This means that even if the initial MVEPC session ends, the user might remain in MVES, and any new video call or data session they initiate could continue to receive emergency-priority QoS (governed by mechanisms like MVEPP) until an authorized person (the user or a dispatcher) explicitly cancels the emergency state. The server manages this state, potentially broadcasting the user's emergency status to other authorized users (like a dispatcher group) and logging all activities for post-incident analysis. Clearing the MVES involves a specific deactivation procedure, returning the user and their services to normal priority levels.

Purpose & Motivation

MVES exists to provide context and persistence to emergency operations beyond a single call session. The problem it solves is the potential fragmentation of emergency response; without a persistent state, a first responder might establish a high-priority MVEPC, but once that call ends, their next communication (e.g., sending a vital image or starting a new call) could inadvertently revert to normal priority, causing dangerous delays. MVES ensures continuity of priority treatment throughout the entire emergency incident.

This concept was motivated by operational protocols from traditional land mobile radio systems, where an 'emergency mode' or 'man-down' state persists until cleared. Translating this to IP-based broadband systems required a standardized, service-layer state machine. MVES addresses the limitation of a purely session-centric QoS model by tying priority to the user's operational status. It provides a clear, unambiguous signal to the entire mission-critical system that a particular user is engaged in a life-critical situation, allowing for coordinated and prioritized support from both the network and other human operators until the situation is formally resolved. It is a key feature for making MCVideo services robust and operationally practical for real-world public safety use.

Key Features

• A persistent service-layer state activated by an emergency user action
• Modifies client application behavior and UI during emergency incidents
• Ensures continuity of high-priority QoS for all user communications while active
• Managed and coordinated by the MCVideo Server
• Requires an explicit user or dispatcher action to deactivate
• Can be indicated to other authorized users within the mission-critical system

Evolution Across Releases

Defining Specifications