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

Glossary term · Services

Manual commencement mode

Manual Commencement Mode

Services →

Manual commencement mode is a mode for MCPTT private calls where the receiving user must manually accept or reject the call setup before communication begins to ensure callee consent.

Introduced
Rel-13
Where
Services
Specifications
2 specs
Manual commencement mode Description Purpose What changed Neighbours Specifications

Description

Manual commencement mode is a call setup behavior defined for Mission Critical Push To Talk (MCPTT) services within 3GPP. In this mode, when an MCPTT user initiates a private call to another user, the call does not connect automatically. Instead, the receiving MCPTT user is alerted and must perform an explicit action—such as pressing a button or selecting an on-screen option—to accept or reject the incoming call. This contrasts with automatic commencement mode, where the call is established without callee intervention. The mode is specified in 3GPP TS 23.179 and TS 23.379, which define the functional architecture, procedures, and information flows for MCPTT.

The need for manual commencement arises from the operational requirements of mission-critical communications. In many public safety scenarios, users must have control over which calls they accept, especially when they are engaged in other activities or when the call may interrupt critical tasks. Manual commencement provides a mechanism for the callee to screen calls, ensuring that only authorized or desired communications are established. It also supports privacy and prioritization, as users can reject calls from unknown or lower-priority sources.

From an architectural perspective, manual commencement mode involves several MCPTT entities. The originating MCPTT client sends a call setup request to the MCPTT server. The server, upon determining that the target user is configured for manual commencement, forwards the call invitation to the terminating MCPTT client. The terminating client then alerts the user and waits for a response. If the user accepts, the client sends an acceptance message back to the server, which then completes the call setup and grants the floor to the originator. If the user rejects, the server notifies the originator of the rejection and the call attempt is terminated. This process is governed by the MCPTT service configuration, which may define timers for user response and fallback behaviors.

Manual commencement mode is particularly relevant in off-network and isolated E-UTRAN scenarios, where direct communication between UEs may be used. In such cases, the mode ensures that the callee is not forced into a call without consent. The mode can be configured per user or per group, and it may be overridden by emergency or imminent peril calls, which typically use automatic commencement to ensure immediate communication.

The feature has been part of MCPTT since its introduction in Release 13 and has remained stable across subsequent releases. Its definition has not undergone substantive changes, reflecting its fundamental role in mission-critical call control. As MCPTT evolves towards MCX (Mission Critical Services) encompassing video and data, manual commencement remains a key building block for user-centric call handling.

Purpose & Motivation

Manual commencement mode exists to give MCPTT users control over incoming private calls, ensuring that they can accept or reject call setups based on their current situation. This is critical in public safety and mission-critical environments where interruptions can have serious consequences. The mode addresses the need for callee consent, privacy, and prioritization, which are not adequately handled by automatic call setup mechanisms.

Before the introduction of MCPTT, mission-critical push-to-talk systems often used automatic call setup, which could lead to unwanted interruptions. Manual commencement provides a standardized way to implement call screening and user-controlled acceptance, aligning with the operational needs of first responders. It also supports regulatory and privacy requirements by allowing users to decline calls. The feature was introduced in Release 13 as part of the initial MCPTT specifications and has been maintained without significant changes, demonstrating its enduring relevance.

What changed in its specifications

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

TS 23.379Rel-18 → Rel-19

Rel-19 adds clauses for ad hoc group call release, leave and criteria modification. It also covers emergency private call and floor remote triggers, floor revoke, and extended ad hoc group call setup.

Full comparison in TS 23.379 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-13 Initial

Introduced as part of the initial MCPTT specifications. Defined manual commencement mode as a mode where the receiving MCPTT user must perform an action to accept or reject the private call setup.

Definition carried over unchanged from Rel-13.

Definition carried over unchanged from Rel-13.

Definition carried over unchanged from Rel-13.

Definition carried over unchanged from Rel-13.

Definition carried over unchanged from Rel-13.

Definition carried over unchanged from Rel-13.

Definition carried over unchanged from Rel-13.

Defining Specifications

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

SpecificationTitleRelease
TS 23.179 vd50 MCPTT Functional Architecture Rel-13 read
TS 23.379 vk40 Mission Critical Push-to-Talk Architecture Rel-20 read