Description
The MC client is a logical entity defined in 3GPP TS 23.280 that represents and aggregates a set of specialized clients residing on a Mission Critical (MC) capable User Equipment (UE). Rather than treating each MC function as an isolated client, the MC client provides a unified framework that encompasses the Group management client, Configuration management client, Identity management client, Key management client, Location management client, and the MC service client itself. This aggregation model allows the UE to interact with the MC system through a coherent set of interfaces while still maintaining the functional separation required by each MC service.
Architecturally, the MC client sits at the application layer of the UE and interfaces with the MC service servers over the network. The Group management client handles the creation, modification, and deletion of MC groups, communicating with the Group Management Server. The Configuration management client retrieves and manages user and service configuration data from the Configuration Management Server. The Identity management client is responsible for user authentication and identity provisioning, interacting with the Identity Management Server. The Key management client manages cryptographic keys used for media and signalling protection, working with the Key Management Server. The Location management client provides location information to the MC system, interfacing with the Location Management Server. Finally, the MC service client implements the actual mission critical push-to-talk (MCPTT), video (MCVideo), or data (MCData) service logic.
The MC client concept was introduced to streamline the UE-side architecture for MC services. In earlier releases, each functional client was described separately, which could lead to ambiguity in how they interact and share resources. By defining an aggregating MC client, 3GPP provides a clear reference point for conformance testing and implementation, ensuring that all constituent clients are present and properly coordinated. This is particularly important for interoperability, as different vendors may implement the individual clients differently, but the aggregated MC client must behave consistently.
The MC client also plays a role in service continuity and resource management. For example, when a UE is shared among multiple MC service clients (as in the MC gateway UE scenario), the MC client framework helps manage the sharing of underlying resources such as network connections, security contexts, and location data. The MC client can coordinate between the different service clients to avoid conflicts and ensure that priority services (e.g., emergency calls) are handled appropriately.
In terms of protocol, the MC client communicates with the MC system using SIP for session control, HTTP for configuration and group management, and various media protocols for user plane data. The interfaces are defined in 3GPP TS 23.280 and related specifications. The MC client must support security mechanisms such as authentication, authorization, and encryption, which are handled by the identity and key management clients. The location management client may use 3GPP location services (e.g., LCS) or other positioning methods to provide location updates.
Overall, the MC client is a foundational concept in the MC architecture, enabling a modular yet integrated approach to delivering mission critical services over 3GPP networks. Its introduction in Rel-18 reflects the maturity of the MC specifications and the need for a consolidated client model as MC services expand to new domains and deployment scenarios.
Purpose & Motivation
The MC client exists to provide a unified, standardized representation of all client-side functionality required for Mission Critical services. Before its introduction, the various MC clients (group management, configuration management, identity management, key management, location management, and MC service clients) were specified as separate entities without a single aggregating concept. This could lead to implementation divergence and interoperability issues, especially when multiple MC services are used on the same UE. The MC client solves this by defining a clear aggregation point that ensures all necessary clients are present and can be managed cohesively.
Another motivation is the need to support complex scenarios such as UE sharing and multi-service operation. As MC services evolve to include MCVideo and MCData alongside MCPTT, the number of clients on a UE grows. The MC client provides a framework to coordinate these clients, manage shared resources (e.g., security keys, location data), and ensure consistent behavior. This is particularly important for MC gateway UEs, which may serve multiple MC service clients simultaneously.
Finally, the MC client concept aids in conformance and testing. By specifying a single entity that encompasses all clients, 3GPP makes it easier for vendors and operators to verify that a UE supports the complete set of MC functionalities. It also simplifies the description of interactions between the UE and the MC system, as the MC client can be treated as a single logical endpoint for certain procedures.
What changed in its specifications
The latest release-to-release comparison of specifications that define MC client. Each summary describes the whole specification, not only this term.
Rel-19 adds Enhanced Mission Critical Architecture changes, including location reporting trigger cancel and override indication. It also adds location reporting and location information request procedures for mission critical clients on non-3GPP devices behind a UE or 5G-RG.
Full comparison in TS 23.280 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (4 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference MC client, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.280 vk51 | Mission Critical Services Architecture | Rel-20 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |