Private Communication (MCX)

Description

Private Communication is a generic mission-critical service (MCX) concept that denotes a one-to-one communication session between exactly two users. Unlike a private call, which is specific to MCVideo, Private Communication is service-agnostic and applies across the MCX family: MCPTT (voice), MCVideo (video), and MCData (data). It is defined in 3GPP TS 22.280 (Mission Critical Services Common Requirements) and referenced in TS 23.501 (System Architecture for the 5G System). The term captures the common semantics of point-to-point communication that underpin private calls, private data exchanges, and other one-to-one interactions.

Architecturally, Private Communication is realized through the respective MCX application servers (MCPTT AS, MCVideo AS, MCData AS) and the common functional architecture defined for mission-critical services. When a user initiates a private communication, the request is routed to the appropriate MCX AS, which authorizes the session based on the user's profile and the target user's availability. The AS then establishes a session between the two clients, managing signaling, media, and floor control as needed. In 5G, the underlying transport may use QoS flows with appropriate 5QI values to guarantee the required performance, and the session may be anchored at the AS for policy enforcement and recording.

The concept of Private Communication is important because it provides a unified abstraction for one-to-one services across different media types. This allows common procedures for authorization, security, and priority handling to be defined once and reused. For example, the emergency handling for a private communication is similar whether it is voice, video, or data: the request is marked as emergency, receives elevated priority, and may pre-empt other traffic. This consistency simplifies implementation and interoperability across vendors and agencies.

In terms of protocol, Private Communication relies on SIP for session establishment in MCPTT and MCVideo, while MCData may use HTTP-based protocols or SIP depending on the specific service. The MCX AS acts as a back-to-back user agent or application server, maintaining state and enforcing policies. Floor control is applicable to MCPTT and MCVideo private communications, ensuring that only one party transmits at a time in half-duplex mode, while MCData private communications may be full-duplex or transactional.

Private Communication was introduced in Release 14 as part of the broader mission-critical services framework, and its definition has remained essentially unchanged through Release 20. This stability reflects the maturity of the concept and its role as a foundational building block for MCX services. The term is often used in requirements specifications to describe the general capability, while more specific terms like private call are used in protocol specifications for individual services.

Purpose & Motivation

Private Communication exists to provide a standardized, media-agnostic definition of one-to-one communication within the mission-critical services framework. Before this concept was formalized, one-to-one communication was described separately for each service (e.g., private call for MCPTT, private call for MCVideo), leading to duplication and potential inconsistency. By defining a common term, 3GPP enables a unified approach to requirements, architecture, and procedures that apply across all MCX services.

The motivation is both technical and operational. Technically, a common abstraction reduces specification complexity and ensures that features like emergency handling, priority, and security are treated consistently. Operationally, end users and administrators benefit from a uniform experience: a private communication is understood as a direct interaction between two individuals, regardless of whether it involves voice, video, or data. This is particularly important in public safety, where a user may need to switch between media types seamlessly during an incident.

Historically, the term emerged from the need to generalize the private call concept beyond voice. Release 13 introduced MCPTT with private calls; Release 14 expanded to MCVideo and MCData, and the common requirements in TS 22.280 introduced Private Communication as the umbrella term. Since then, the definition has been carried forward unchanged, indicating that the abstraction has proven robust and sufficient for subsequent releases, including the integration with 5G in Release 15 and beyond.