How Repeaters Work, Part 3: DMR Tier III Trunking vs Analog Type II Systems

Independence notice: RunBoard is an independent operations platform and is not affiliated with, endorsed by, or sponsored by any company, product, network, or agency named in this article. Names are used only for identification and education.

What trunking actually is

Start with the problem trunking solves. On a conventional system, every talkgroup or user group is tied to a fixed channel. Dispatch is on one channel, a fireground on another, public works on a third. If your dispatch channel is quiet at 2 a.m., that channel still sits there doing nothing. Meanwhile, if two groups both need the busy channel at once, one of them waits even though other channels are idle. Conventional radio wastes capacity because assignments are permanent.

Trunking breaks that fixed link. Instead of owning a channel, each talkgroup shares a common pool of channels managed by a controller. When someone keys up, the system finds a free channel in the pool, tells every affected radio to move to it for the duration of that transmission, carries the call, and then releases the channel back into the pool. Radios do this automatically and almost instantly, so users never see it. The effect is that a handful of physical channels can serve many talkgroups, because no two of them are likely to be busy at the exact same moment. Trunking is, at heart, statistical sharing of scarce spectrum.

Most trunked systems reserve one path as a control channel, a continuous data stream that coordinates the whole thing. Radios listen to the control channel constantly, receive channel-grant messages, and follow those instructions to the traffic channels. Some designs distribute that control function differently, but the principle holds: a coordinating signal moves radios around a shared pool. Part 2 of this series described how P25 does exactly this on the public-safety standard side. DMR Tier III and analog Type II are two other ways to reach the same result.

DMR Tier III: the ETSI digital trunking standard

DMR stands for Digital Mobile Radio, a standard published by ETSI, the European Telecommunications Standards Institute. DMR is defined in tiers. Tier I covers unlicensed low-power use. Tier II covers licensed conventional digital repeater operation, which is where a lot of business and public-safety DMR lives. Tier III is the trunking tier. When people say DMR trunking, they mean Tier III.

Tier III applies the trunking concept described above to a digital DMR system. It defines how the control channel signals radios, how talkgroups and individual calls are set up, how the system handles registration and roaming across multiple sites, and how data services are carried. Because it is an open published standard rather than one company's design, multiple manufacturers can build to it. Hytera and Motorola both offer DMR Tier III infrastructure and subscriber equipment, and other vendors participate in the DMR ecosystem as well. That multi-vendor character is one of the reasons DMR became attractive to organizations that wanted digital trunking without being locked into a single supplier's proprietary architecture.

DMR uses a two-slot TDMA scheme, meaning each 12.5 kHz channel is divided into two time slots that can carry separate traffic. In a Tier III system that time-slot structure combines with trunking to squeeze more simultaneous conversations out of the same licensed spectrum than a comparable analog channel count would allow. That efficiency, paired with generally lower equipment and licensing costs than full public-safety P25 systems, is a big part of why DMR Tier III has been adopted well beyond small users. Large regional deployments and even nationwide networks have been built on DMR Tier III, covering utilities, transportation, commercial operations, and some government users who did not require a P25 mandate. It scales up further than many people assume.

Where does DMR Tier III fit for a public-safety decision-maker? Think of it as the digital, standards-based, lower-cost trunked option. It gives you clear digital audio, spectrum efficiency, individual and group calling, text and data services, and multisite roaming, at a price point that often undercuts P25. Whether that fits depends on whether your interoperability and standards obligations allow it, which we will come back to.

Analog Type II: the older trunked family

Long before digital trunking existed, agencies were already trunking with analog technology. The most widespread family is sometimes called Type II, a term that comes from the Motorola SmartNet and SmartZone line of trunked systems. Type II describes how those systems format their control-channel signaling and identify radios and talkgroups. It is worth stating plainly that this is analog trunking. The control channel is digital signaling, but the voice traffic itself is conventional analog FM. Type II is not DMR, does not use the DMR standard, and predates DMR by many years.

These systems were the workhorses of trunked public-safety and business radio for a long era, and a great many are still in service. Naming any specific system would be pointing at a real agency, so we will keep it general, but the pattern is common: an organization built a Type II or SmartZone system years ago, invested heavily in sites, radios, and training, and that system still does its job every day. Ripping it out is expensive and disruptive, so it keeps running.

Agencies stay on analog trunking for reasons that are usually practical rather than technical superiority. The installed base is enormous, so replacement radios and used equipment are available and understood. Neighboring agencies may run compatible systems, which makes cross-agency talkgroups and mutual aid easy to keep working. Certain features, roaming behaviors, or fleet-mapping arrangements are configured exactly the way operations wants them, and there is no appetite to relearn a new platform. Some run a hybrid, keeping analog trunking for legacy fleets while adding digital sites or channels alongside. None of that means analog Type II is chosen because it is DMR or because it is better. It is chosen because it already exists, it works, and change costs money.

Digital versus analog audio and spectrum

The most audible difference between DMR Tier III and analog Type II is what the voice sounds like at the edges. Analog FM degrades gracefully. As a radio moves away from the site or into interference, the audio gets progressively noisier, hissing and picket-fencing, but a trained ear can often still pull words out of a weak signal. Digital systems, including DMR, sound clean across most of their coverage because a vocoder reconstructs the voice and rejects background noise. But digital has a cliff. When the signal quality drops below the threshold the decoder needs, audio does not fade, it garbles or drops. Some crews prefer the analog fade because they can judge how bad their signal is by ear; others prefer clean digital audio that stays intelligible right up to the edge.

Spectrum efficiency clearly favors the digital side. DMR's two time slots per 12.5 kHz channel let one channel carry two conversations, effectively doubling capacity in the same bandwidth compared to a single analog channel of the same width. Combined with trunking, that multiplies how much traffic a licensed allocation can support. For an agency fighting for channels in a crowded band, or trying to add capacity without acquiring new frequencies, that efficiency is a concrete advantage. Analog Type II, being one voice path per channel, simply does not pack traffic as tightly.

Digital also brings data services that analog trunking handles poorly or not at all: text messaging, GPS location reporting, telemetry, and radio management over the air. If your operation wants unit location on a map or short data alongside voice, the digital platforms are built for it. Consider the list below when you weigh the two.

• Audio character: analog degrades gradually and noisily; digital stays clean, then hits a threshold and garbles.
• Capacity per channel: DMR carries two time slots per 12.5 kHz; analog carries one voice path per channel.
• Data features: digital supports text, location, and telemetry natively; analog trunking largely does not.
• Noise handling: digital vocoders reject background noise well; analog passes engine and scene noise through.
• Familiarity: long-time users often have strong instincts for reading analog signal quality by ear.

Cost, feature sets, and migration

Cost is where DMR Tier III earns much of its reputation. As a general pattern, DMR infrastructure and subscriber radios tend to cost less than P25 equipment of comparable scale, and the multi-vendor nature of the standard puts competitive pressure on pricing. For an organization that needs digital trunking but is not bound to the public-safety standard, that gap can be the deciding factor across a fleet of hundreds of radios. Analog Type II costs live mostly in the sunk investment already made and in the shrinking pool of new equipment, since manufacturers have steadily shifted focus to digital.

Feature sets differ in ways that matter operationally. Both DMR Tier III and analog Type II offer the trunking fundamentals: talkgroups, individual calls, priority handling, multisite roaming, and emergency signaling. The digital platforms layer on the data and management capabilities noted above. Legacy analog systems sometimes carry very specific configurations, fleet maps, and interoperability arrangements that an agency has depended on for years, and reproducing those exactly on a new platform takes deliberate planning.

Migration is rarely a single flip of a switch. Realistic paths tend to be phased. An agency may stand up a digital system alongside the analog one, run both during a transition, move fleets over group by group, and keep a bridge or gateway so the two can still talk during the overlap. That bridging period is where a lot of hidden cost and complexity lives, because you are maintaining two systems and the connection between them at the same time. Planning the sequence, the interoperability during transition, and the training load is as important as choosing the destination technology.

Interoperability and where P25 fits

Interoperability is often the quiet deciding factor. Radio systems do not exist in isolation. You share incidents with neighboring agencies, mutual-aid partners, and sometimes state or regional networks. The technology your neighbors run, and the technology any shared or mandated system requires, constrains your choices more than any spec sheet.

This is where P25 has a distinct role. P25 is the digital standard developed specifically for public safety, and in many jurisdictions the regional or statewide interoperability network is P25. If your mutual-aid framework or a grant condition or a shared system requires P25, then DMR Tier III and analog Type II are not substitutes for it, no matter how good they are on their own. You might still run DMR for internal fleets and interface to a P25 system for interoperability, but the P25 obligation drives the architecture. Part 2 covered how those P25 multisite systems are built.

Bridging between families is possible. Gateways and consoles can patch a DMR talkgroup, an analog Type II talkgroup, and a P25 talkgroup together so crews on different systems can hear each other. That works and is done routinely, but each patch is a piece of equipment to buy, configure, and maintain, and a patched call is never quite as seamless as native operation on a shared system. The more you rely on cross-system patching for day-to-day interoperability, the more you should question whether a shared standard would serve you better. Weigh these interoperability realities:

• What your neighbors run shapes how easily you share incidents with them.
• Mandates and grant conditions may require P25 regardless of internal preferences.
• Regional and statewide networks often set the standard you must interface to.
• Gateways and patches bridge families but add equipment and are less seamless than native shared operation.

Choosing: it depends on your situation

There is no universal winner among these technologies, and anyone who tells you otherwise is selling something. Each fits a different set of constraints. DMR Tier III is a strong candidate when you want digital audio, spectrum efficiency, and data features at a lower cost than P25, and when no mandate forces you onto the public-safety standard. Analog Type II can be the sensible answer when you already own a working system, your partners are compatible with it, and the case for replacement does not yet justify the disruption. P25 is the answer when interoperability requirements or mandates point there, even if it costs more.

The honest framing is that the right choice falls out of four things: your budget, your existing infrastructure, your interoperability needs, and any standards requirements you are bound to. A well-funded agency inside a P25 region has a different correct answer than a budget-constrained operation with a healthy analog system and neighbors who run the same thing. Both can be making a good decision. What matters is that the decision follows from your actual constraints rather than from a general belief that newer or digital or cheaper is always better.

It also helps to separate the internal question from the external one. Internally, what do your own crews need for daily operations, coverage, capacity, and features? Externally, what must you connect to, and on whose terms? Sometimes those two answers point to one technology. Sometimes they point to a hybrid, where you run one platform internally and interface to another for interoperability. Naming those two questions clearly keeps a procurement conversation honest.

Questions to ask before you commit

Before signing anything, work through a short list with your radio vendor, your neighboring agencies, and your own operations staff. The goal is to surface constraints early, while they are still cheap to design around.

• What must we interoperate with, and on what technology? Identify every partner, regional network, and mandate that constrains the choice before you compare products.
• Are we bound to a standard? Check grant conditions, state or regional requirements, and mutual-aid agreements for a P25 or other obligation.
• What is the total cost, including the transition? Count infrastructure, subscriber radios, licensing, programming, training, and the cost of running two systems during migration.
• What do we own now, and what is its remaining useful life? A healthy analog system may have years left; a failing one may force the decision.
• What capacity and coverage do we actually need? Match channel count, sites, and talkgroups to real traffic, not to a vendor's default package.
• Which data and feature capabilities are must-haves versus nice-to-haves? Text, location, and telemetry can justify digital, or may be irrelevant to your operation.
• Is the platform multi-vendor or single-source, and what does support look like long term? Open standards give procurement leverage; assess parts, service, and lifecycle either way.
• What is the migration sequence and the interoperability plan during the overlap? Know how old and new will coexist before you commit to the destination.

Answer those honestly and the technology tends to choose itself. DMR Tier III, analog Type II, and P25 are each the right answer for some agency somewhere, and the point of the exercise is to figure out which agency you are.

Independence notice: RunBoard is an independent operations platform and is not affiliated with, endorsed by, or sponsored by any company, product, network, or agency named in this article. Names are used only for identification and education.