NEXEDGE Trunking: Type-C and Type-D
Kenwood NEXEDGE systems built on the NXDN digital standard (see NXDN Digital Standard and Kenwood NEXEDGE Overview) can operate as trunked radio systems, where a pool of repeater channels is shared automatically among many talkgroups instead of each group being tied to one physical channel. The NXDN standard defines two distinct trunking architectures — Type-C (centralized) and Type-D (distributed) — and NEXEDGE implements both. Choosing between them is one of the first design decisions in a NEXEDGE trunked deployment.
Type-D: Distributed Trunking
Type-D trunking has no dedicated control channel. It is the FB6-based, LTR-derived protocol specified by the NXDN Forum, and its defining characteristic is that trunking is controlled by the "home repeater" assigned to each radio — not by a central controller, and not by radios hunting across channels. Each subscriber is associated with a home repeater that manages its access, exactly as in analog LTR.
Two consequences follow directly:
- No registration. Like LTR, Type-D has no unit-registration step. The system does not maintain a picture of which radios are present.
- Every channel carries voice. No channel is consumed full-time for control, so a two- or three-channel system gets voice capacity out of every repeater it owns.
That economy is Type-D's appeal — attractive for small businesses and single-site systems. The trade-offs are lower total capacity, limited scalability, and the absence of the system-level features that registration enables. Type-D is generally a single-site or small-system architecture.
Type-C: Centralized Trunking
Type-C trunking uses a dedicated control channel, like most large trunked architectures (including P25 trunking). Idle radios sit on the control channel; when a user presses push-to-talk, the radio sends a call request on the control channel and the system's trunking controller instantly assigns a voice channel and directs all members of the talkgroup to it.
This yields fast, deterministic call setup, higher traffic capacity, and — critically — support for multi-site systems: several repeater sites can be linked over an IP (Internet Protocol) network so a talkgroup spans a city, campus, or region, with radios registering at whichever site hears them best and roaming between sites. Type-C systems also support richer system-level features such as unit registration, individual (private) calls across sites, and centralized management. The cost is that one channel per site is dedicated to control duty, so the smallest practical Type-C site has at least two channels.
Generation 1 vs Generation 2 NEXEDGE Systems
Kenwood's NEXEDGE trunking has gone through two broad system generations, and the differences are architectural rather than protocol-level (both speak NXDN over the air):
- Generation 1 systems were built around the first-generation NXR-710/NXR-810 repeaters (see Kenwood NXR Repeaters), with trunking logic residing largely in the repeaters themselves and multi-site networking done by linking repeaters over IP. This kept systems simple and affordable but bounded their scale.
- Generation 2 systems, associated with the later NX-5000-era infrastructure, expanded multi-site IP networking capacity substantially — more sites, more channels per site, and more subscriber units — and added stronger centralized system management. Qualitatively, generation 2 moved NEXEDGE Type-C from "a handful of linked sites" territory toward genuinely wide-area regional networks.
Type-C vs Type-D at a Glance
| Aspect | Type-C (centralized) | Type-D (distributed) |
|---|---|---|
| Protocol lineage | FB8-based, full-featured NXDN Forum protocol | FB6-based, digital LTR-derived protocol |
| Control channel | Dedicated, continuously transmitting/receiving | None — the radio's assigned home repeater controls trunking |
| Unit registration | Required | None (as with LTR) |
| Call setup speed | Fast, controller-directed | Slower |
| Minimum practical size | 2+ channels per site | Works even on very small systems |
| Channel efficiency at small scale | One channel lost to control duty | All channels carry voice |
| Capacity and scalability | High; large systems | Modest; small systems |
| Multi-site wide-area operation | Yes, via IP site links | Not the intended use case |
| Typical buyer | Utilities, large campuses, regional operators | Small businesses, single sites |
Rule of Thumb
If the system is a single site with only a few channels and a modest user count, Type-D keeps every repeater earning its keep. If the system needs fast access, many users, private calling at scale, or more than one site, Type-C is the architecture to specify.
Related Pages
- Kenwood NEXEDGE Overview
- NXDN Digital Standard
- Trunked Radio Systems
- Kenwood NXR Repeaters
- Talkgroups and Fleet Mapping
References
- NXDN Trunking — NXDN Forum — the standards body's own description: Type-C is FB8-based with a dedicated, continuously active control channel and required registration; Type-D is the FB6-based digital LTR protocol with no control channel, trunking controlled by each radio's home repeater, and no registration.
- NXDN TRKG (Type-C) — Kenwood · NXDN TRKG (Type-D) — Kenwood
- System type and scale — Kenwood — for current site/channel/subscriber limits, which this page deliberately does not quote.
- JVCKENWOOD NXDN systems — CommTech
- NXDN(C) and NXDN(D) — RadioReference
Verified August 2026. Correction applied: an earlier revision described Type-D as radios "hunting across the system's channels for a free one," guided by status bursts from idle channels. That is not how Type-D works — it is LTR-derived, with each radio's assigned home repeater controlling trunking. The FB6/FB8 lineage and the registration difference (required on Type-C, absent on Type-D) were also missing and have been added, since registration is the cleanest discriminator between the two.
This article is part of the CTI Products Knowledge Base. Questions about RadioPro or MCN products? Call +1 (513) 595-5900 or email info@ctiproducts.com.
Informational only. This article is general background and is not engineering, safety, legal or regulatory advice. Verify requirements with the equipment manufacturer and the applicable authority before relying on it. Product names and trademarks belong to their respective owners.