Description
The MC system is the top-level architectural concept in the 3GPP mission critical services framework, defined in TS 23.280 and reused in TS 23.783 for MC services over 5G. It encompasses all the applications, services, and enabling capabilities needed to deliver one or more mission critical services — MCPTT, MCVideo, and MCData — to one or more mission critical organizations. Rather than denoting a single network element, the MC system is a collection that spans service enablers, common functional entities, and the interfaces that connect them.
Architecturally, the MC system comprises several layers. The service enablers provide the specific mission critical services: the MCPTT server and related functions, the MCVideo server, and the MCData server. The common functional architecture provides shared capabilities used by all enablers, including identity management, group management, configuration management, key management, location management, and the MC service user database. The MC system also includes the interfaces to the underlying 3GPP network (EPS or 5GS) that provide connectivity, policy and charging control, and network-level services. The MC service UE sits at the edge, connecting to the MC system through the network.
The MC system is designed to serve one or more mission critical organizations. An organization is an administrative entity — such as a police department, fire service, or ambulance service — that owns or subscribes to MC services. A single MC system may serve multiple organizations, with appropriate isolation and policy enforcement between them, or an organization may be served by multiple MC systems that interoperate. This multi-organization capability is essential for cross-agency incident response, where responders from different organizations must communicate seamlessly.
Operationally, the MC system provides the functions needed for service delivery: authentication and authorization of users, configuration of UEs, management of groups and affiliations, handling of calls and data sessions, location reporting, and security key distribution. It also provides interfaces for administration and provisioning, and for interconnection with other MC systems. The MC system relies on the underlying 3GPP network for transport, QoS, and policy enforcement, using mechanisms such as dedicated bearers or 5G QoS flows to meet mission critical performance requirements.
The MC system concept was introduced in Rel-15, building on the Rel-14 work that defined the individual MC service enablers and the common architecture. Its introduction reflected the need for a holistic architectural view that spans services and organizations, rather than treating each enabler in isolation. The definition has remained unchanged from Rel-15 through Rel-20, indicating a stable architectural abstraction.
Purpose & Motivation
The MC system concept exists to provide a holistic, standardized architectural view of mission critical communications. In the initial Rel-14 work, 3GPP defined individual MC service enablers (MCPTT first, followed by MCVideo and MCData) and a common functional architecture. As the framework matured, it became clear that a top-level concept was needed to describe the complete collection of applications, services, and enabling capabilities that together deliver mission critical services to organizations. This avoids treating each enabler as an isolated system and supports the reality that organizations deploy and operate integrated mission critical communications.
The concept also addresses the multi-organization nature of mission critical operations. Incident response routinely involves multiple agencies, and the MC system abstraction explicitly supports serving one or more mission critical organizations, enabling cross-agency communication and shared infrastructure. This was difficult to express with service-specific terminology alone.
Introduced in Rel-15, the MC system concept provided the architectural umbrella under which subsequent enhancements — including MC services over 5G in TS 23.783 — could be described consistently. Its unchanged definition through Rel-20 reflects its role as a stable reference point for the evolving MC services ecosystem.
What changed in its specifications
The latest release-to-release comparison of specifications that define MC system. 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 (13 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- Modify list of participants by changing the criteria during an ongoing ad hoc group emergency alert (single MC system) TS 23.280CR0413
- ACM updating MC service user profiles assigned from partner MC system TS 23.280CR0509
- Including UE capabilities towards the partner MC system during migration TS 23.280CR0622
- Preconfigured Group Regroup formation in a single MC system alignment in 10.15.3.2.1 TS 23.280CR0438
- Update Preconfigured User Regroup formation in a single MC system in 10.15.3.2.2 TS 23.280CR0439
- Corrections on modifying the criteria during an ad hoc group alert (single MC system) TS 23.280CR0474
+ 1 more changes
Defining Specifications
3GPP specifications that define or reference MC system, 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 |
| TR 23.783 vi00 | Technical Report on Mission Critical Services over 5GS | Rel-18 read |