Networking: Unicast, Broadcast, and Multicast
The Delivery Models
These are the basic ways IP traffic can be addressed to one or more recipients:
Unicast
Unicast is one sender to one specific receiver, addressed to that single device's own unique IP address — a direct, point-to-point conversation between exactly two endpoints. It is the overwhelming majority of ordinary network traffic (a web request, a TCP connection, a single dispatch console pulling one specific radio's audio) and, conceptually, the default/foundational addressing mode IP networking is built around — broadcast and multicast exist as deliberate extensions on top of a network that is otherwise unicast by default.
Broadcast
Broadcast is one sender to every device on the local network segment, with no opt-in required — every device receives it whether it's relevant to them or not. Broadcast is inherently inefficient at scale (every device has to process every broadcast packet) and does not cross router boundaries by default, which is part of why subnetting exists — smaller subnets mean smaller broadcast domains. Notably, broadcast does not exist in IPv6 at all — IPv6 replaces every use case broadcast historically served in IPv4 (like ARP-based local address resolution) with multicast instead, sent to a narrowly-scoped multicast group rather than to every device on the segment; see Networking IPv6 for NDP, the multicast-based mechanism that replaces ARP there.
Multicast
Multicast is one sender to a group of interested receivers, but unlike broadcast, only devices that have explicitly joined that multicast group receive the traffic. This gets much of broadcast's one-to-many efficiency (the sender only transmits once, regardless of how many receivers there are) without broadcast's "everyone gets it whether they want it or not" downside — at the cost of needing multicast-aware network infrastructure (see below) to actually deliver that efficiency.
Why This Matters for Radio-System Networks
- DHCP's Discover step is a broadcast — a new device on the network doesn't know a DHCP server's address yet, so it has to broadcast its request to the whole local segment.
- ARS and similar registration/presence messages are typically unicast or narrowly-targeted UDP between a specific radio and its Presence Notifier/gateway, not broadcast to the whole network.
- Simulcast audio distribution is a natural fit for multicast in principle — the same audio needs to reach every transmitter site simultaneously — though the specific mechanism a given vendor's simulcast implementation uses (multicast vs. point-to-point unicast to each site) depends on that system's architecture; see Simulcast and GPS for how site timing/sync is handled regardless of which delivery model carries the audio.
Common Misunderstandings
- "Unicast can't scale, so multicast is always the 'better' choice for one-to-many traffic" — not automatically; multicast's efficiency advantage only matters once there are enough simultaneous receivers on the same managed network to make the extra multicast-routing complexity worth it, and it doesn't work at all across most WAN/internet paths. For the very common case of "one specific radio talking to one specific dispatch console" — ordinary unicast, not multicast, is already the right and simplest answer, and is exactly what most RoIP client connections use by default (see RoIP (Radio over IP)).
- "Unicast is somehow the 'weaker'/legacy option compared to multicast" — the opposite in terms of universal compatibility: unicast is the one delivery model guaranteed to work across any IP path, including the public internet, with zero special network configuration, which is precisely why it's the default choice absent a specific reason to use something else.
- "Anycast is just a fancy name for multicast" — they're different: multicast delivers to every group member; anycast delivers to exactly one (whichever the routing infrastructure considers nearest/best).
Related Pages
- Networking: IPv4
- Networking: IPv6
- Networking: DHCP
- IP Networking in Two-Way Radio Systems
- RoIP (Radio over IP)
- Simulcast
- ACL (Access Control List)
References
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.