Also known as: P25, Project 25, APCO-25, APCO P25
Project 25 (P25, also APCO-25) is a suite of open standards for digital land-mobile radio developed for public-safety and government users in North America. It defines how radios, repeaters, and trunked systems carry digital voice and data, with the explicit goal of interoperability between equipment from different manufacturers.1 The standards are published by the TIA as the TIA-102 series and were driven by the requirements of APCO International, the association of public-safety communications officials.2
Overview
P25 was created so that police, fire, and emergency-medical agencies could replace incompatible analog and proprietary systems with a common, openly documented digital standard. Rather than a single document, P25 is a suite: it specifies the Common Air Interface (how bits travel over the radio link), the vocoder used for voice, the trunking control signalling, inter-RF-subsystem interfaces (ISSI), console and network interfaces, and encryption. Because every layer is published, radios from Motorola, L3Harris, Tait, Kenwood, and others can interoperate on the same system.
P25 comes in two air-interface generations that share the same signalling and addressing: Phase 1, which uses FDMA with one call per 12.5 kHz channel, and Phase 2, which uses two-slot TDMA to carry two calls in the same 12.5 kHz for doubled spectrum efficiency. A single system often mixes both: a Phase 1 C4FM control channel directs traffic to Phase 2 voice channels.
Technical characteristics
| Property | Phase 1 | Phase 2 |
|---|---|---|
| Access | FDMA | TDMA (2 slots) |
| Channel | 12.5 kHz | 12.5 kHz / 2 = 6.25 kHz equiv. |
| Modulation | C4FM / CQPSK | H-CPM / H-DQPSK |
| Vocoder | IMBE | AMBE+2 |
| Symbol rate | 4800 baud (9600 bps) | 6000 symbols/s per slot |
| Voice FEC | Golay, Hamming, Reed–Solomon, trellis | as Phase 2 profile |
| Control signalling | TSBK on the control channel | Phase 1 control channel |
Every P25 unit and system carries a layered set of identifiers that the control channel broadcasts and the decoder reads: the Network Access Code (NAC), a 12-bit “digital squelch” that separates co-channel systems; the WACN and System ID, which together uniquely name a network worldwide; the RFSS and site number, which locate a specific RF subsystem; and per-call fields such as source radio ID and destination talkgroup. Both phases can be deployed conventionally (fixed frequency) or as a trunked system coordinated by a control channel.
History
P25 standardisation began in the late 1980s under APCO, which set user requirements, with the TIA drafting the TIA-102 documents; Phase 1 was published from the mid-1990s.1 The suite deliberately reused the IMBE vocoder and a spectrally efficient 4-level FSK (C4FM) modulation so that legacy 12.5 kHz channel plans could be kept. Phase 2 followed in the 2000s to meet FCC narrowbanding and spectrum-efficiency mandates, adopting two-slot TDMA and the half-rate AMBE+2 vocoder so that two conversations could share one 12.5 kHz channel.2
Deployment
P25 is the dominant digital standard for U.S. state, county, and federal public safety, and is used by many large metropolitan systems as well as by users in Australia, Canada, and elsewhere. Statewide interoperability networks (for example large state radio systems serving thousands of agencies) are typically P25 trunked systems with dozens of sites tied together by a wide-area network. Systems are catalogued in databases such as RadioReference, which list their control-channel frequencies, NACs, System IDs, and talkgroups. Much public-safety traffic is now encrypted (commonly AES-256), which is audible to a scanner only as the system metadata, not as clear voice.
Decoding it with GopherTrunk
GopherTrunk decodes both P25 Phase 1 and Phase 2. It locks the control channel, reads the TSBK grants and the NAC / WACN / System ID / RFSS identity broadcasts, follows channel grants to the assigned voice channel (and, in Phase 2, the assigned slot), and runs the matching IMBE or AMBE+2 vocoder to produce audio. It renders clear and (with a known key) some scrambled traffic, but it does not defeat keyed encryption such as AES or DES — encrypted calls are logged with their metadata only. See the protocol landscape lesson for how P25 compares with other systems, and the Status page for current coverage.
Sources
-
Project 25 — Wikipedia, for P25 history, the Phase 1/Phase 2 air interfaces, the identifier hierarchy, and the TIA/APCO standardisation. ↩ ↩2
-
P25 (Project 25) — CISA SAFECOM, for the public-safety interoperability rationale, the TIA-102 standards suite, and the Phase 1 to Phase 2 spectrum-efficiency progression. ↩ ↩2