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

Glossary term · Services

MCPTT UE

Mission Critical Push To Talk User Equipment

Services →

MCPTT UE is a User Equipment that enables an MCPTT User to participate in the MCPTT Service by providing client functionality for mission-critical push-to-talk communication.

Introduced
Rel-13
Where
Services
Specifications
2 specs
MCPTT UE Description Purpose What changed Neighbours Specifications

Description

The MCPTT UE is the user equipment (mobile device) that hosts the MCPTT Client and allows an MCPTT User to access the Mission Critical Push To Talk service. It is a specialized UE that supports the necessary protocols, codecs, and functionalities to participate in MCPTT sessions. The MCPTT UE can be a dedicated device (e.g., a ruggedized handset) or a commercial smartphone with the MCPTT Client application installed. It must support the underlying 3GPP network access (LTE/5G) and the MCPTT application protocols.

The MCPTT UE includes several key components: the MCPTT Client, which implements the MCPTT service logic, floor control, and group communication; the Configuration Management (CM) client, which retrieves user and group configuration from the CMS; the Identity Management (IdM) client, which handles authentication and authorization; and the Key Management (KM) client, which manages security keys for media and signaling. The UE also supports the necessary QoS mechanisms, such as requesting dedicated bearers with appropriate 5QI/QCI for MCPTT media, and priority handling for access and bearer establishment.

The MCPTT UE can operate in both on-network and off-network modes. In on-network mode, it communicates via the MCPTT Server using IMS and the EPS/5GS. In off-network mode, it uses ProSe direct communication (PC5 interface) to communicate directly with other UEs, without relying on network coverage. The UE must support the migration between these modes, including procedures for detecting network loss and establishing direct connections.

The UE also supports functional aliases, allowing the user to be identified by an alias (e.g., "Firefighter 1") in addition to the IMPU. It may support location reporting, providing its location to the MCPTT Server for dispatcher use. The MCPTT UE must meet specific performance requirements, such as fast call setup times (e.g., less than 300 ms for on-network, less than 1 second for off-network) and high audio quality (using AMR-WB or EVS codecs).

The MCPTT UE is defined in 3GPP TS 22.179 (service requirements) and TS 24.980 (MCPTT UE protocol conformance). It is a critical component of the MCPTT system, as it provides the user interface and the client-side implementation of the mission-critical push-to-talk service.

Purpose & Motivation

The MCPTT UE exists to provide users with a device that can access the Mission Critical Push To Talk service with the required performance, security, and reliability. Traditional commercial UEs lack the specialized features needed for mission-critical communication, such as priority handling, floor control, and direct mode operation. The MCPTT UE fills this gap by defining a standardized set of capabilities that ensure interoperability and consistent user experience across different vendors and networks.

The MCPTT UE solves the problem of enabling push-to-talk communication over cellular networks with mission-critical quality. It ensures that users can initiate and participate in group calls quickly, even in congested networks, and can continue communicating when network coverage is lost by switching to direct mode. It also provides the necessary security mechanisms to protect sensitive communications.

Historically, mission-critical users relied on LMR devices, which were proprietary and limited in data capabilities. The MCPTT UE leverages commercial cellular technology, reducing costs and enabling integration with broadband data applications. The specification of the MCPTT UE in 3GPP ensures that devices from different manufacturers can interoperate, fostering a competitive ecosystem.

What changed in its specifications

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

TS 22.179Rel-16 → Rel-17

Rel-17 added Mission Critical Push-to-talk Phase 3 to TS 22.179, covering general overview, Figure 6.15.3.1.1, and requirements. It also changed three other related items in the same release.

Full comparison in TS 22.179 →
TR 24.980Rel-15 → Rel-16

Rel-16 brings only minor changes to TS 24.980: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 24.980 →

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

Initial definition introduced the MCPTT UE as a UE that enables an MCPTT User to participate in MCPTT Service. This release established the basic requirements for the UE, including support for MCPTT client, IMS, and QoS.

The definition remained unchanged from Rel-13, with no textual modifications.

The definition remained unchanged from Rel-14, with no textual modifications.

The definition remained unchanged from Rel-15, with no textual modifications.

The definition remained unchanged from Rel-16, with no textual modifications.

The definition remained unchanged from Rel-17, with no textual modifications.

The definition remained unchanged from Rel-18, with no textual modifications.

The definition remained unchanged from Rel-19, with no textual modifications.

Defining Specifications

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

SpecificationTitleRelease
TS 22.179 vl00 MCPTT Service Requirements Rel-21 read
TR 24.980 vg00 MCPTT IMS Profile for Gm Reference Point Rel-16 read