Description
The On-network MCPTT service is defined in the 3GPP mission-critical specifications (TS 23.179, TS 23.379, TS 23.779, and TS 23.783) as the collection of functions and capabilities required to provide Mission Critical Push To Talk (MCPTT) via EPS bearers using E-UTRAN to provide the last hop radio bearers. In simpler terms, it is the mode of MCPTT operation in which the service is hosted and controlled by the network, and the user's device connects to the service through the cellular radio access network rather than through a direct device-to-device link.
Architecturally, the On-network MCPTT service relies on the EPS (Evolved Packet System) as the underlying connectivity layer, with E-UTRAN providing the last-hop radio bearers between the user equipment and the network. On top of this connectivity, the MCPTT service layer provides the functional entities needed for push-to-talk operation: the MCPTT server, the group management functions, the participating and controlling functions, and the interfaces to the EPS for bearer and policy control. The service supports one-to-one calls, group calls, and broadcast calls, and it integrates with the EPS bearer model to obtain the QoS treatment required for mission-critical voice.
The On-network MCPTT service is distinguished from the off-network MCPTT service, which operates without network coverage using direct communication between devices. The on-network mode is the primary mode of operation when coverage is available, because it allows the network to manage group membership, enforce authorization and priority, provide location information, and support dispatch and recording functions. These capabilities are essential for public safety and mission-critical users who need reliable, managed communication.
Because MCPTT is a mission-critical service, the On-network MCPTT service must support priority and pre-emption, including the ability to prioritize MCPTT traffic over other traffic and to pre-empt lower-priority sessions when resources are scarce. It also supports security functions such as authentication and encryption, and it can interoperate with other mission-critical services such as MCData and MCVideo through shared architectural elements.
The definition of the On-network MCPTT service has evolved slightly across releases. In Rel-17, the wording was expanded to include the use of 5GS access based on the 5G System architecture to provide the last hop radio bearers, reflecting the migration of mission-critical services toward 5G. In Rel-18, the wording reverted to the EPS/E-UTRAN-only formulation. The term remains central to the MCPTT architecture and is used consistently alongside related concepts such as off-network MCPTT, MCPTT server, and MCPTT group.
Purpose & Motivation
The On-network MCPTT service exists to provide a managed, network-hosted push-to-talk capability for mission-critical users such as public safety personnel. Unlike consumer push-to-talk applications, mission-critical communication requires guaranteed priority, pre-emption, group management, and security, all of which are best provided when the service is hosted in and controlled by the network.
The concept was created to clearly separate the network-hosted mode of MCPTT from the off-network mode, which relies on direct device-to-device communication when network coverage is unavailable. This separation allows the specifications to define distinct functional architectures, procedures, and requirements for each mode while ensuring interoperability between them.
Historically, mission-critical voice was provided by narrowband technologies such as TETRA and P25. The On-network MCPTT service brings these capabilities to broadband LTE and, later, 5G networks, enabling richer services and integration with data and video applications. The Rel-17 wording change reflects the industry's move toward 5G-based mission-critical services.
What changed in its specifications
The latest release-to-release comparison of specifications that define On-network MCPTT service. Each summary describes the whole specification, not only this term.
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.
Defining Specifications
3GPP specifications that define or reference On-network MCPTT service, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.179 vd50 | MCPTT Functional Architecture | Rel-13 read |
| TS 23.379 vk40 | Mission Critical Push-to-Talk Architecture | Rel-20 read |
| TS 23.779 vd00 | MCPTT over LTE Stage 2 Study | Rel-13 read |
| TR 23.783 vi00 | Technical Report on Mission Critical Services over 5GS | Rel-18 read |