Radio trunking is a system that automatically shares a pool of radio frequencies among many user groups, instead of giving each group its own dedicated channel. Think of it like a phone system: rather than reserving one phone line per department, a central computer assigns an open line the moment someone needs to talk, then frees it up when they’re done. This lets hundreds or thousands of users communicate efficiently on far fewer channels than they’d need otherwise.
How Trunking Differs From Conventional Radio
On a conventional radio system, each group of users gets a fixed frequency. A city’s fire department might be assigned Channel 1, police dispatch Channel 2, and public works Channel 3. If the fire department isn’t talking, that channel sits idle, wasted. Meanwhile, if police need a second channel for a major incident, they’re out of luck.
A trunked system flips this model. Instead of permanently pairing groups with frequencies, it puts all available frequencies into a shared pool. Users are organized into logical groups called talkgroups, which function like virtual channels. When a firefighter keys their radio, a central computer instantly finds an open frequency, directs every radio in that talkgroup to switch to it, and the conversation happens. The moment the transmission ends, the frequency goes back into the pool. The whole process takes a fraction of a second and is invisible to the user.
The Role of the Control Channel
The system’s brain is a dedicated frequency called the control channel. It doesn’t carry voice traffic. Instead, it constantly exchanges small data packets between every radio on the network and a central computer. When you power on a trunked radio, it immediately registers with the control channel, telling the system which talkgroup you’re on and which radio site you’re near.
When you press the transmit button, your radio sends a request to the control channel computer. The computer picks an available frequency, then signals every radio monitoring your talkgroup to jump to that frequency. Once you release the button, all those radios return to listening on the control channel for the next instruction. This constant back-and-forth coordination is what makes trunking work, and it happens so quickly that users experience it the same way they’d experience turning a channel knob on a conventional radio.
Infrastructure Behind the System
A trunked network requires more hardware than a simple repeater setup. Each radio site is equipped with several base repeaters, managed by a site controller computer. The site controller designates one of those repeaters as the control channel and dynamically assigns the rest to active talkgroup conversations. Above the individual sites, a system core computer ties everything together, tracking which users are on which sites and coordinating channels across the entire network.
If a site doesn’t have a free repeater when someone tries to talk, the system sends the requesting radio a busy tone, similar to a busy signal on a landline. Larger systems reduce this problem by having more repeaters per site and spreading traffic across multiple tower locations.
What Happens When the System Fails
Because trunking depends on a central controller, there are built-in fallback modes. If the trunking system fails entirely, radios automatically switch to “failsoft” mode, operating on a single predetermined frequency in conventional (non-trunked) fashion. It’s a degraded experience, but communication doesn’t stop completely. Once the system recovers, radios return to trunked operation on their own.
A more limited failure is when an individual site loses contact with the central controller. In that case, the site enters “site trunking” mode: radios at that location can still trunk among themselves, but they lose the ability to communicate with users on other sites. The radio displays a notification so users know their reach is limited.
Talkgroups Replace Channels
For the person holding the radio, talkgroups feel almost identical to channels on a conventional system. You scroll to “Fire Dispatch” or “North Patrol” and talk. The difference is entirely behind the scenes. Switching talkgroups doesn’t change your frequency. It sends a message to the control channel saying you now belong to a different logical group. The system controller then includes your radio in whatever frequency assignments that talkgroup receives.
This is a powerful advantage for large organizations. A police department can have dozens of talkgroups for different precincts, detective units, and tactical operations, all sharing the same set of physical frequencies. During a major event, dispatchers can merge talkgroups or patch them together without rewiring anything.
Major Trunking Standards
Two digital standards dominate the public safety world. Project 25 (P25), maintained by the Telecommunications Industry Association, is the primary standard in the United States. It uses narrower channels (12.5 kHz in its first phase) and was designed from the ground up for police, fire, and EMS agencies. TETRA (Terrestrial Trunked Radio), developed by the European Telecommunications Standards Institute, is the standard across most of Europe, Asia, and other regions. TETRA uses wider 25 kHz channels but fits four simultaneous communication slots into each one, giving it higher per-channel capacity.
The practical difference for users is minimal. Both deliver encrypted digital voice, data messaging, and GPS location. The choice between them is largely geographic and regulatory: if you’re building a public safety network in the U.S., you’re almost certainly using P25. In Europe or much of the rest of the world, it’s TETRA.
Licensing and Spectrum Rules
In the United States, the FCC requires trunked systems to demonstrate real usage to justify their spectrum. The standard threshold is 100 mobile radios per channel. A licensee requesting new trunked channels must certify that at least 70 radios per channel will be active within five years. To expand an existing system with additional channels, the current system must already be loaded at 70 radios per channel. Rural areas get some flexibility, with licensees allowed to add up to five extra channels without meeting those loading thresholds.
Construction deadlines are tight. Licensees must build out their system within one year, and a base station isn’t considered operational unless at least two mobile radios (or one mobile and one control station) are also active. If the deadline passes without permanent operation, the license cancels automatically.
Connecting Trunked Radio to Broadband Networks
Modern trunked systems increasingly need to exchange voice and data with LTE and 5G cellular networks. The 3GPP standards body has defined an Interworking Function (IWF) that bridges the gap between traditional narrowband trunked radio and broadband mission-critical services. This lets a P25 radio user talk to someone on a broadband push-to-talk app, or lets dispatchers on a cellular network reach field units on TETRA.
The U.S. public safety broadband network, FirstNet, has announced IWF support specifically for connecting local P25 systems to its nationwide LTE network. The European rail industry is using the same framework to migrate from its legacy rail radio system to a next-generation broadband platform. The catch is bandwidth: trunked radio systems are inherently narrowband, so interworking is generally limited to voice, short messages, and location data rather than video or large file transfers.