Project 25

Description

Project 25 (P25) is a set of standards developed by the Telecommunications Industry Association (TIA) for digital land mobile radio (LMR) communications, widely adopted by public safety agencies (police, fire, emergency medical) in the United States, Canada, and other countries. Within the 3GPP context, P25 is not a 3GPP-defined technology itself; instead, 3GPP specifications define the architecture, interfaces, and procedures for interworking between 3GPP-defined broadband networks (LTE and 5G NR) and legacy P25 narrowband LMR systems. This interworking enables mission-critical services (MCS) like push-to-talk (PTT) voice, short data services, and status messaging to span both network types.

The 3GPP architecture for P25 interworking involves several key functional entities. The central component is the Interworking Function (IWF), which acts as a gateway between the 3GPP core network (e.g., 5G Core or EPC) and the P25 system. The IWF performs protocol translation between 3GPP protocols (like HTTP, SIP, or mission-critical specific protocols) and the P25-specific signaling and media protocols (such as P25 CAI - Common Air Interface). It also handles media transcoding between audio codecs used in 3GPP (e.g., EVS, AMR) and those used in P25 (e.g., IMBE, AMBE). The IWF is typically deployed as part of the Mission Critical Services (MCS) architecture, interfacing with the Mission Critical Push-To-Talk (MCPTT) server.

From a procedural standpoint, a UE (such as a public safety radio) capable of both 3GPP broadband access and P25 access can operate in a dual-system mode. The 3GPP network provides the control and management plane for mission-critical services, utilizing the MCPTT application server. When a user initiates a group call, the MCPTT server, via the IWF, can set up the call leg to the P25 network. This allows a user on a 3GPP device to communicate with users on traditional P25 handheld radios, and vice versa. The IWF manages subscriber identity mapping between 3GPP identities (like SUCI or SUPI) and P25 identities (like Radio ID), and handles group management across the domains.

The role of P25 interworking in the 3GPP ecosystem is to facilitate the transition from legacy LMR systems to 3GPP-based broadband mission-critical networks (like FirstNet in the US). It ensures service continuity and interoperability during this long migration period. 3GPP specifications such as TS 23.283 define the stage 2 architecture, while TS 24.883 details the stage 3 protocol details for the interworking. This allows network operators and public safety agencies to leverage the high bandwidth, low latency, and rich data services of LTE/5G while maintaining connectivity to the reliable, wide-area voice-centric P25 networks.

Purpose & Motivation

The integration of P25 with 3GPP networks was motivated by the critical need for interoperability during the evolution of public safety communications. Legacy P25 networks represent a massive, long-term investment by public safety agencies and provide robust, dedicated voice communications, often with superior coverage in rural or disaster-stricken areas. However, they lack the high-speed data capabilities needed for modern applications like live video, data analytics, and location sharing. 3GPP-based LTE and 5G networks offer these broadband capabilities and are the foundation for next-generation mission-critical networks.

The problem solved by 3GPP-defined P25 interworking is the creation of a seamless communication fabric that bridges these two worlds. Without such interworking, public safety agencies would face a costly and disruptive "forklift" upgrade, replacing all P25 devices and infrastructure simultaneously. More importantly, it would create dangerous communication silos where first responders using new broadband devices could not talk to those still on the legacy system. The interworking standards allow for a gradual, phased migration, protecting existing investments and ensuring all personnel can communicate regardless of their device.

Historically, this work began in 3GPP around Release 13, aligning with the broader push for mission-critical communications over LTE (MC-LTE). The limitations of previous approaches were proprietary, vendor-specific gateways that were expensive and limited in scale. 3GPP standardization aimed to create a unified, open interface for interworking, fostering multi-vendor ecosystems and reducing costs for public safety organizations. It addresses the fundamental requirement for mission-critical services: reliable, interoperable, and instantaneous communication, which is literally a matter of life and death.

Key Features

• Defines an Interworking Function (IWF) for protocol and media translation between 3GPP and P25 systems
• Supports interoperability for Mission Critical Push-To-Talk (MCPTT) voice group calls
• Handles subscriber identity mapping between 3GPP identities (SUPI) and P25 Radio IDs
• Manages transcoding between 3GPP audio codecs (EVS, AMR) and P25 codecs (IMBE, AMBE)
• Enables service continuity and roaming between broadband and narrowband networks for public safety users
• Provides standardized interfaces (e.g., MCx, MI) for integration into the 3GPP Mission Critical Services architecture

Evolution Across Releases

Defining Specifications