MCVideo Emergency Private Priority

Description

MCVideo Emergency Private Priority (MVEPP) is not a standalone service but a critical quality of service (QoS) attribute and procedural framework defined within the 3GPP MCVideo specifications. It represents the highest priority tier for MCVideo private calls, specifically engineered to guarantee the performance of MCVideo Emergency Private Call (MVEPC) sessions. MVEPP governs how the network reserves, allocates, and protects the necessary bandwidth, latency, and reliability for these life-critical video streams from end to end.

Technically, MVEPP is implemented through a combination of standardized QoS parameters and network policies. In LTE, it maps to specific QoS Class Identifiers (QCIs) with characteristics suitable for real-time conversational video, but with the additional attribute of being allocated for 'Mission Critical' use. In 5G systems, it maps to standardized 5G QoS Indicators (5QIs) that define similar packet delay budget, packet error rate, and priority level. The key differentiator of MVEPP is its priority level, which is set higher than that of any commercial service and even higher than other non-emergency mission-critical traffic. This priority is signaled during the session establishment procedure (defined in TS 24.281) from the MC client to the MCVideo server, which then interacts with the core network's Policy and Charging Control (PCC) architecture.

The PCC framework, comprising the Policy Control Function (PCF) and Session Management Function (SMF), translates the MVEPP service requirement into concrete network rules. These rules are enforced at the User Plane Function (UPF) in 5GC or the PGW in EPC for packet filtering and QoS marking, and crucially, at the Radio Access Network (RAN). The RAN uses these rules for uplink and downlink scheduling, ensuring packets for an MVEPP session are served before others. Furthermore, MVEPP enables pre-emption capabilities. In severely congested scenarios, the network may be authorized to pre-empt (i.e., downgrade or disconnect) resources from lower-priority existing sessions (like a commercial video stream) to admit or maintain an incoming MVEPP-based MVEPC session. This end-to-end enforcement chain—from service-level signaling to core network policy to RAN scheduling—is what defines and implements MVEPP.

Purpose & Motivation

The purpose of MVEPP is to provide the technical 'teeth' to the MCVideo Emergency Private Call service. Defining a service like MVEPC is insufficient if the network treats its data packets with the same best-effort priority as a social media video. MVEPP exists to solve the fundamental problem of resource scarcity and contention during emergency situations, ensuring that critical video communication is not degraded or blocked by network congestion.

Historically, public safety networks used dedicated, narrowband spectrum which inherently prioritized their traffic but lacked high-bandwidth capabilities like video. As public safety migrated to broadband LTE and 5G, sharing infrastructure with commercial users, a mechanism was needed to replicate and exceed the guaranteed access of traditional systems. MVEPP was created to be that mechanism within the 3GPP standards. It addresses the limitation of earlier priority schemes which were not specifically tailored or guaranteed for the unique requirements of emergency private video—requirements that include not just high priority, but also strict latency bounds for interactivity and reliability for situational awareness. It ensures that the promise of 'mission-critical' over commercial-grade networks is technically enforceable and reliable.

Key Features

• Defines the highest QoS priority level for MCVideo private sessions
• Maps to standardized high-priority QCIs (LTE) and 5QIs (5G) for mission-critical video
• Integrated with 3GPP PCC architecture for dynamic policy enforcement
• Enables resource pre-emption over lower-priority sessions during congestion
• Signaled as part of the MCVideo session establishment procedure
• Ensures end-to-end network resource guarantee from core to RAN

Evolution Across Releases

Defining Specifications