PCCB

Private Call Call-Back

Services
Introduced in Rel-14
PCCB is a supplementary service for Mission Critical Push-To-Talk (MCPTT) that enables a user to request a callback from a busy or unavailable user in a private call. It stores the callback request and automatically establishes the call when both parties become available. This feature is vital for ensuring reliable and guaranteed communication in public safety and professional mobile radio scenarios.

Description

Private Call Call-Back (PCCB) is a standardized supplementary service within the 3GPP Mission Critical Services (MCS) framework, specifically defined for Mission Critical Push-To-Talk (MCPTT). It operates within the IP Multimedia Subsystem (IMS) layer of the network. The service allows an MCPTT user (the originator) who attempts to establish a private call (a one-to-one call) with another user (the destination) but finds them busy, unreachable, or not answering, to invoke a PCCB request. The network then stores this request in a PCCB state.

Architecturally, the PCCB service logic resides within the MCPTT application server (AS), which is an IMS application server enhanced for critical communications. When a private call setup fails due to the destination's status, the originating MCPTT client can send a SIP INVITE request with a specific indication for PCCB, or a subsequent SIP request like MESSAGE. The MCPTT AS, acting as the PCCB service provider, acknowledges the request and monitors the availability status of the destination user. This monitoring leverages registration and presence information from the IMS core. Once the MCPTT AS detects that the destination user is registered and available for MCPTT service (e.g., not in another MCPTT session and has service coverage), it automatically initiates a new private call setup between the two parties, fulfilling the callback.

Key components involved include the MCPTT client on the User Equipment (UE), the MCPTT AS hosting the PCCB service logic, and the underlying IMS core providing registration, session control, and presence capabilities. The service works by maintaining a PCCB record containing the identities of the originator and destination, the timestamp of the request, and its state (e.g., pending, being processed). The MCPTT AS manages the lifecycle of this record, including expiration timers to prevent indefinite pending states. Its role is to enhance the reliability and success rate of critical one-to-one communications by automating retry logic, ensuring that important calls are not missed due to temporary unavailability.

Purpose & Motivation

PCCB was created to address a critical operational gap in push-to-talk communications for public safety and mission-critical workforce users. In high-stakes environments like emergency response, it is imperative that communication attempts succeed. Traditional cellular calls or basic PTT services simply return a busy signal or go to voicemail if the recipient is unavailable, which is unacceptable when urgent instructions or status updates need to be delivered. PCCB provides a guaranteed delivery mechanism for private call attempts.

The problem it solves is the inefficiency and potential failure of manual retry. Without PCCB, a user who encounters a busy colleague must repeatedly attempt to call, wasting time and attention during critical incidents. PCCB automates this process, offloading the retry task to the network. This was motivated by the requirements defined by professional mobile radio users and standard bodies like TCCA, which were integrated into 3GPP's MCPTT specifications starting in Release 13. It addresses the limitation of previous PTT systems, which often lacked intelligent, network-managed supplementary services.

Furthermore, PCCB increases the effectiveness of team coordination. By ensuring that a callback request is queued and executed automatically, it allows the originator to continue other tasks with confidence that the connection will be established. This aligns with the broader 3GPP mission to provide carrier-grade, feature-rich critical communications over LTE and 5G networks, replacing or complementing legacy systems like TETRA or P25 with more flexible and IP-based services.

Key Features

  • Automated callback initiation for failed private MCPTT call attempts
  • Network-based storage and management of callback requests
  • Integration with IMS registration and presence for availability monitoring
  • Support for configurable expiration timers on pending callback requests
  • Notification to users about the invocation and completion of PCCB
  • Ensures reliable one-to-one communication in mission-critical scenarios

Evolution Across Releases

Rel-14 Initial

Introduced the Private Call Call-Back (PCCB) service as part of the Phase 2 enhancements for Mission Critical Push-To-Talk (MCPTT). Defined the basic procedures, SIP signaling flows, and service logic within the MCPTT Application Server for handling and fulfilling callback requests for private calls.

Enhanced PCCB to interoperate with other MCPTT supplementary services like pre-established sessions. Improved the handling of priority levels, ensuring that high-priority PCCB requests are processed appropriately within the MCPTT service hierarchy.

Extended PCCB support for Mission Critical Data and Mission Critical Video services, allowing callback-like functionality for data session initiation. Refined the interaction with proximity services (ProSe) for off-network scenarios.

Introduced enhancements for 5G integration, optimizing PCCB signaling for 5G Core Network and leveraging network exposure for improved availability detection. Added support for PCCB in conjunction with MCPTT group merge scenarios.

Further optimizations for latency and reliability in 5G-Advanced networks. Enhanced the service logic to better handle user mobility and transitions between network slices dedicated to mission-critical services.

Continued maintenance and feature refinement, focusing on interoperability with AI/ML-based predictive availability status and integration with advanced mission-critical communication frameworks.

Defining Specifications

SpecificationTitle
TS 24.281 3GPP TS 24.281
TS 24.379 3GPP TS 24.379
TS 37.579 3GPP TR 37.579