Description
The Critical Communications Application (CCA) is a comprehensive framework defined by 3GPP to support mission-critical services over LTE and 5G networks. It provides the application-layer architecture, functional entities, and reference points necessary to implement professional mobile radio (PMR) capabilities, specifically targeting the evolution and replacement of legacy systems like TETRA (Terrestrial Trunked Radio). The CCA framework operates within the broader Mission Critical Services (MCS) architecture, interfacing with core network functions and client applications on user equipment to deliver secure group communications, emergency alerts, and prioritized access.
Architecturally, CCA consists of several key functional components that interact through standardized interfaces. The Mission Critical Push To Talk (MCPTT) application server handles group call setup, floor control, and media distribution for voice communications. The Mission Critical Video (MCVideo) and Mission Critical Data (MCData) servers extend these capabilities to real-time video streaming and data messaging respectively. These application servers interface with the underlying 3GPP core network (EPC or 5GC) through standardized reference points, leveraging network capabilities like quality of service (QoS), priority handling, and location services. The framework also includes management functions for configuration, subscription, and security policies.
From an operational perspective, CCA works by establishing secure sessions between user equipment and application servers, with the 3GPP network providing the transport layer with appropriate QoS guarantees. When a user initiates a critical communication (like a push-to-talk call), the CCA client on the device authenticates with the application server and requests resources from the network. The network applies priority and preemption policies based on the user's subscription and the critical nature of the communication. Media flows are then established with guaranteed bandwidth and latency characteristics, ensuring reliable communication even in congested network conditions. The framework supports both on-network and off-network (direct device-to-device) operation through Proximity Services (ProSe).
The role of CCA in the network is to provide a standardized, interoperable platform for critical communications that can be deployed alongside commercial mobile services. It enables network operators to offer dedicated critical communication services to public safety agencies, transportation companies, utilities, and industrial organizations. By leveraging commercial LTE and 5G networks, CCA provides significant advantages over legacy PMR systems including higher data rates, better spectral efficiency, and integration with broadband applications. The framework also supports regulatory requirements for emergency services and disaster response through features like priority access, group management, and location-based services.
Purpose & Motivation
CCA was created to address the growing need for modern, broadband-enabled critical communications systems that could replace aging legacy technologies like TETRA and P25. These legacy systems, while reliable for voice communications, lacked the bandwidth and flexibility needed for modern public safety and industrial applications requiring video, data, and high-speed mobility. The limitations of TETRA included narrowband capabilities (typically 25 kHz channels), limited data rates (up to 28.8 kbps), and proprietary implementations that hindered interoperability between different vendors and regions. As LTE technology matured, it became clear that commercial mobile networks could provide a more cost-effective and capable platform for critical communications if appropriate application-layer frameworks were standardized.
The primary motivation for CCA development was to enable public safety organizations and critical infrastructure operators to leverage commercial mobile network investments while maintaining the reliability, security, and functionality required for mission-critical operations. Before CCA standardization, attempts to use commercial networks for critical communications relied on proprietary solutions that lacked interoperability and couldn't guarantee the necessary performance characteristics during emergencies. The 3GPP standardization effort aimed to create a globally recognized framework that would enable equipment vendors, network operators, and application developers to build compatible solutions, driving economies of scale and fostering innovation in the critical communications market.
CCA solves several key problems: it provides a migration path from legacy PMR systems to broadband networks, enables convergence of multiple critical communication applications (voice, video, data) on a single platform, and ensures that critical communications receive appropriate priority and resources within shared commercial networks. The framework also addresses regulatory requirements for emergency services communications, including support for lawful interception, location services, and priority access during network congestion. By standardizing these capabilities, CCA enables network operators to offer critical communication services as a managed service, reducing the capital and operational expenses for public safety agencies compared to maintaining dedicated PMR networks.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (11 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, the CCA function introduced new capabilities including application layer security for the N32 interface and mechanisms for authorizing an Application Function's requests. It also added procedures for the application to report when PFDs (Packet Flow Descriptions) are removed or modified, with specific reporting defined for the TDF (Traffic Detection Function). Furthermore, a new Quality of Service Class Identifier (QCI) was standardized to support MCVideo services.
- new QCI for MCVideo TS 29.212CR1667
- Application layer security on the N32 interface TS 33.501CR0376
- Authorization of Application Function's requests TS 33.501CR0213
- Application report when the PFDs are removed or modified TS 29.212CR1670
- TDF application report when the PFDs are removed or modified TS 29.212CR1679
In Release 17, the CCA (Critical Communications Application) function was formally introduced with an official abbreviation and received clarifications regarding its intended audience. The release also provided specific technical clarifications on how CCA operates concerning FR1 band selection. These updates served to more clearly define the scope and operational parameters of the CCA within the mission critical services architecture.
In Release 18, the new capability for the Critical Communications Application (CCA) function was the ability to convey the CCA of the source Network Function service consumer. This enhancement, as indicated by the Change Request title, introduced a mechanism to signal this specific application context within service-based interactions.
- Conveying the CCA of the source NF service consumer TS 33.501CR1804
In Release 19, the new CCA work introduced specific charging principles, architecture, and information flows for the IMS Data Channel (IMS DC) application download charging function. This enhancement provides the necessary framework to support charging for downloading critical communications applications over the IMS data channel. The updates ensure this charging function is integrated within the existing mission critical services architecture.
Explore further
Broader topics and technologies where CCA plays a role.
Defining Specifications
3GPP specifications that define or reference CCA, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.782 vf00 | Interworking between LTE MC and non-LTE MC systems | Rel-15 |
| TS 29.212 vj00 | Gx/Gxx/Sd/St Diameter Protocol | Rel-19 |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 |
| TS 32.260 vj10 | IMS Charging Management | Rel-19 |
| TS 32.270 vj00 | MMS Charging Management Specification | Rel-19 |
| TS 32.271 vj20 | 3GPP LCS Charging Management Spec | Rel-19 |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 |
| TS 32.273 vj00 | MBMS Charging Management | Rel-19 |
| TS 32.276 vj00 | VCS Online Charging from Proxy Function | Rel-19 |
| TS 32.293 vj00 | Proxy Function in Domestic Service Provider | Rel-19 |
| TS 32.296 vj00 | Online Charging System (OCS) Architecture | Rel-19 |
| TS 32.299 vj00 | Diameter Charging Applications for 3GPP | Rel-19 |
| TS 32.825 va00 | Study on Rc Reference Point for ABMF | Rel-10 |
| TS 33.501 vk00 | 5G Security Architecture and Procedures | Rel-20 |
| TS 33.790 vj10 | Security for Next-Gen Real-Time Communication Phase 2 | Rel-19 |
| TR 33.876 vi01 | Technical Report on Certificate Management | Rel-18 |
| TS 38.522 vj11 | UE Conformance Test Applicability Statement | Rel-19 |
| TR 38.889 vg00 | NR-based access to unlicensed spectrum study | Rel-16 |