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

Glossary term · Services

Private call

MCVideo Private Call

Services →

Private call is a fundamental one-to-one mission-critical video service between two users, optionally initiated as an emergency call, as defined in 3GPP specifications.

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

Description

A private call is a mission-critical video (MCVideo) service primitive in which one user initiates a call towards exactly one other user, with the intention of establishing a one-to-one video session. Unlike a group call, which distributes media to many recipients, a private call is point-to-point in nature and is therefore suited to dispatcher-to-field-user conversations, supervisor consultations, or direct user-to-user communications. The call may be a normal private call or an MCVideo emergency private call, the latter carrying elevated priority and pre-emption treatment. The concept is defined in 3GPP TS 24.281 (MCVideo call control protocol) and referenced in TS 24.379 (mission-critical push-to-talk over LTE/5G, MCPTT) for the analogous voice service.

Architecturally, a private call is established through the MCVideo application server (MCVideo AS), which acts as the central call-control entity. The calling user's MCVideo client sends a session initiation request (typically SIP-based) to the MCVideo AS, which authorizes the request against the user's service profile, checks group and user affiliation, and then invites the called party. The called user's client may auto-answer or require manual acceptance depending on configuration. Once both parties are connected, media flows over the bearer plane, which in 3GPP mission-critical deployments is typically a dedicated EPS bearer or a 5G QoS flow with guaranteed bit rate and appropriate 5QI (e.g., 5QI for conversational video or mission-critical video).

The private call is one of several MCVideo call types, alongside group calls, broadcast calls, and emergency calls. Its distinguishing property is the one-to-one relationship between caller and callee. This has implications for floor control: in a private call, floor control is typically implicit or simplified because only two parties contend for the transmission opportunity, whereas group calls require a centralized floor control server to arbitrate among many participants. Nevertheless, MCVideo private calls still use the MCVideo floor control protocol to manage who transmits video at any moment, particularly in half-duplex or push-to-video modes.

Emergency private calls are a special variant. When a user initiates an emergency private call, the request is marked with an emergency indication, which triggers priority handling in the network: the call may pre-empt lower-priority sessions, receive elevated QoS, and be routed to a designated emergency dispatcher. This is critical for public safety and first-responder use cases, where a user may need to reach a specific supervisor or dispatcher immediately even under network congestion.

In terms of protocol layering, the private call control sits above the transport layer and relies on SIP for session establishment, with MCVideo-specific extensions for floor control, media negotiation, and emergency handling. The MCVideo AS maintains call state, performs authorization, and can record or log the call for auditing. Interworking with legacy systems (e.g., LMR) may be supported through gateways. The private call concept was introduced in Release 14 as part of the initial MCVideo specification and has been carried forward essentially unchanged through Release 19, reflecting its stability as a core service primitive.

Purpose & Motivation

The private call exists to provide a standardized, interoperable mechanism for one-to-one video communication in mission-critical environments. Before 3GPP defined MCVideo, public safety and critical-communications users relied on proprietary or narrowband systems (such as TETRA or P25) that offered limited or no video capability. As broadband networks (LTE, later 5G) became available to first responders, there was a need to define a common service layer that could deliver video with the same reliability, priority, and security guarantees as voice. The private call fills the gap for direct, targeted video communication between two users, complementing group calls that serve broader teams.

The motivation for a distinct private call concept, rather than treating all calls as group calls with a single member, is twofold. First, it simplifies call setup and floor control when only two parties are involved, reducing signaling overhead and latency. Second, it enables specific features such as emergency private calls that must reach a particular individual (e.g., a dispatcher or commander) rather than a group. This is essential in situations where a user needs to escalate to a specific authority figure without broadcasting to an entire talkgroup.

Historically, the private call concept in MCVideo mirrors the private call in MCPTT (Mission-Critical Push-To-Talk), which was defined earlier in Release 13. The success of MCPTT private calls demonstrated the value of one-to-one communication in mission-critical voice, and this was naturally extended to video in Release 14. The definition has remained stable across Releases 14 through 19, indicating that the fundamental semantics of a private call are well understood and that subsequent work has focused on enhancements elsewhere (e.g., interworking, QoS, security) rather than redefining the core concept.

What changed in its specifications

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

TS 24.281Rel-17 → Rel-18

Added MBS session management and XML schema types. Added MCVideo emergency and imminent peril adhoc group call procedures. Added MCVideo gateway UE function for non-3GPP access. Added 5G ProSe support to MCVideo. Added migration service authorization for MCVideo clients.

Full comparison in TS 24.281 →
TS 24.379Rel-18 → Rel-19

Rel-19 adds participant-criteria handling for ad hoc group emergency alerts, a Reason header with cause 200 on session-leaving messages, and SIP 302 rejection for migrated MCPTT IDs. It also adds location-information conditions for INVITE and REFER requests, removes implicit floor grants from such requests, and changes prearranged group call and emergency alert authorisation rules.

Full comparison in TS 24.379 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (32 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 4 changes
  • Remotely initiated private call client procedures TS 24.379CR0356
  • Remotely initiated private call server procedures TS 24.379CR0357
  • Adding audio media level section in SDP body for offnetwork MCVideo group and private call TS 24.281CR0072
  • Off-network corrections to off-network private call type control TS 24.379CR0449
Rel-16 3 changes
  • Cancellation of a Private Call (without Floor Control) prior the setup TS 24.379CR0565
  • Corrections to off-network private call control state machine TS 24.379CR0533
  • Corrections to Off-network private call type control state machine TS 24.379CR0537
Rel-17 13 changes
  • Interconnect - MCVideo Private call procedures TS 24.281CR0157
  • FA as a target user for MCVideo private call TS 24.281CR0177
  • Call transfer for MCPTT private call, call control part TS 24.379CR0673
  • Call forwarding for MCPTT private call, call control part TS 24.379CR0709
  • Interconnect - MCPTT Private call procedures TS 24.379CR0757
  • Additional private call rejection reasons TS 24.379CR0780

+ 7 more changes

Rel-18 9 changes
  • Private call to user that is migrated to a partner system TS 24.379CR0913
  • Corrections for MCPTT private call transfer TS 24.379CR0898
  • Corrections to MCPTT emergency private call response handling in participating function TS 24.379CR0948
  • Corrections for MCPTT private call forwarding TS 24.379CR0951
  • Corrections for MCPTT private call forwarding TS 24.379CR0844
  • Corrections and enhancements for MCPTT private call forwarding TS 24.379CR0868

+ 3 more changes

Rel-19 3 changes
  • Corrections for MCPTT private call transfer TS 24.379CR0982
  • Clarifications for MCPTT private call forwarding TS 24.379CR0995
  • Clarifications on MCPTT private call transfer TS 24.379CR1023

Defining Specifications

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

SpecificationTitleRelease
TS 24.281 vk10 MCVideo Signalling Control Rel-20 read
TS 24.379 vk10 MCPTT Call Control Protocol Rel-20 read