Description
MC service is a generic name used in 3GPP specifications to refer to any one of the three mission critical services: Mission Critical Push-To-Talk (MCPTT), Mission Critical Video (MCVideo), or Mission Critical Data (MCData). These services are designed to meet the stringent requirements of public safety, security, and other critical communications users, including low latency, high reliability, priority handling, and group communication. The term is defined in 3GPP TS 23.280 (Common functional architecture to support mission critical services) and TS 23.783 (Mission Critical (MC) services over 5G System).
The MC service architecture is built on a common set of enablers that are shared across all three services. These include group management, configuration management, identity management, key management, and location management. Each specific service (MCPTT, MCVideo, MCData) then adds its own service-specific functionality. For example, MCPTT includes call control for group voice calls, push-to-talk floor control, and talker identification. MCVideo includes video streaming and sharing, while MCData includes short messaging, file distribution, and location sharing. The common architecture ensures consistency and interoperability across services.
MC services are delivered over 3GPP networks, primarily LTE (EPS) and 5G (5GS). They use IP-based protocols such as SIP for session control, HTTP for configuration and group management, and RTP for media transport. The services support both unicast and multicast/broadcast delivery (via MBMS), allowing efficient group communication. Quality of Service (QoS) is a critical aspect: MC services use prioritized bearers to ensure that critical users get the necessary resources even during network congestion. The architecture also includes mechanisms for service continuity, security (authentication, encryption, integrity protection), and location reporting.
The MC service concept was introduced in Release 14, building on the earlier work on MCPTT in Release 13. Release 14 added MCVideo and MCData, and the generic term was adopted to refer to all three. Since then, the term has been used consistently across releases, with the definition text remaining unchanged through Release 20. This stability reflects the maturity of the mission critical services framework. However, the underlying specifications have continued to evolve, adding features such as 5G support, network slicing, and enhanced security.
MC services are a key part of the 3GPP roadmap for critical communications. They are designed to replace legacy narrowband systems like TETRA and P25, offering higher data rates, multimedia capabilities, and integration with commercial networks. The term MC service is used in specifications, test specifications, and industry forums to collectively refer to MCPTT, MCVideo, and MCData. It is an essential concept for engineers and students working on public safety and critical communications.
Purpose & Motivation
The MC service term was created to provide a common label for the three mission critical services defined by 3GPP. Before its introduction, each service was specified separately, and there was no convenient way to refer to them collectively. As the mission critical portfolio expanded from MCPTT to include MCVideo and MCData, the need for a generic term became apparent. The MC service term solves this by providing a single name that encompasses all three, simplifying communication and specification references.
The motivation for mission critical services themselves is to enable critical communications users (police, fire, ambulance, etc.) to leverage commercial LTE and 5G networks instead of dedicated narrowband systems. Legacy systems like TETRA provide excellent group voice but limited data capabilities. 3GPP MC services offer voice, video, and data over broadband, with the reliability and priority needed for critical use. The generic term MC service helps in describing the common architecture and enablers that support all three services, promoting reuse and interoperability.
Historically, MCPTT was the first mission critical service, standardized in Release 13. Release 14 added MCVideo and MCData, and the term MC service was introduced to refer to the set. Since then, the term has been used consistently, with the definition unchanged through Release 20. This stability indicates that the concept is well-established and serves its purpose. The MC service framework continues to evolve with new releases, adding features like 5G support, but the core definition remains the same.
What changed in its specifications
The latest release-to-release comparison of specifications that define MC service. 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 (50 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- Request for network resources at session establishment from the MC service server TS 23.280CR0278
- Introduction of MC service UE label for location reporting TS 23.280CR0283
- Functional alias for private call interworking between an MC service system and an LMR system TS 23.783CR0036
- Functional alias for floor control interworking between MC service system and LMR system TS 23.783CR0037
- MC service emergency alert clarifications TS 23.280CR0275
- Introducing descriptive text describing the urgency handling in the MC service system TS 23.280CR0221
+ 3 more changes
- Private call towards a migrated MC service user TS 23.280CR0353
- Partner MC service server stores necessary information for communication redirection TS 23.280CR0355
- Migration service de-authorization procedure initiated by MC service server TS 23.280CR0363
- Updating the MC service user ID list within preconfigured user regroup TS 23.280CR0364
- MC gateway UE association with one MC service TS 23.280CR0341
- Corrections to the use of MC service system TS 23.280CR0319
+ 5 more changes
- Corrections to MC service emergency alert cancel request information flow TS 23.280CR0469
- ACM providing interconnection MC service group ID TS 23.280CR0506
- ACM updating MC service UE initial configuration for migration TS 23.280CR0508
- ACM updating MC service user profiles assigned from partner MC system TS 23.280CR0509
- Functional architecture for MC service logging, recording and replay TS 23.280CR0567
- Ad hoc group call procedure towards a migrated MC service user TS 23.280CR0579
+ 9 more changes
- Functional model for MC service UE disable and enable TS 23.280CR0709
- Reference point descriptions for MC service UE disable and re-enable TS 23.280CR0725
- Unique MC service UE identifier handling TS 23.280CR0729
- MC service UE Disable Procedure TS 23.280CR0730
- MC service UE re-enable Procedure TS 23.280CR0731
- Provide User Info ID during MC service user authentication procedure TS 23.280CR0708
+ 2 more changes
Defining Specifications
3GPP specifications that define or reference MC service, 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 |