5 MAC Protocols: Sharing the Channel
5.1 Start With Who Gets to Talk
A shared channel is like a narrow doorway: if every device talks whenever it wants, useful messages collide or waste battery waiting. MAC protocols are the rules that decide who may transmit, who must listen, and how the network recovers when two devices choose the same moment.
For IoT design, the question is practical before it is theoretical. Decide whether the workload is periodic, alarm-driven, mobile, sleepy, or dense, then choose the channel-sharing rule that can survive that behavior.
5.2 MAC Rules Decide Who Transmits
Medium Access Control, or MAC, is the data-link responsibility that controls access to a shared medium. In an IoT network the medium might be a Wi-Fi channel, an IEEE 802.15.4 channel, a sub-GHz LPWAN channel, or a wired bus. The MAC decision is local and immediate: listen, wait, transmit, acknowledge, retry, or sleep.
A good MAC choice is not simply a protocol name. It is a fit between traffic timing, node density, radio reachability, power budget, and failure behavior. CSMA/CA shares a channel by listening and backing off. TDMA shares a channel by assigning time. ALOHA-style access transmits with minimal coordination and accepts collisions when traffic is sparse enough.
The review question is therefore operational: what does the device do when another device wants the medium at the same time? A door sensor sending a rare alarm can tolerate a different access rule from a motor controller that must report in a bounded time window. A battery node that wakes for a few milliseconds cannot afford long idle listening, while a powered gateway can coordinate schedules, acknowledgements, and retries.
MAC evidence is local but it shapes the whole system. Lost frames become transport retries, stale dashboard values, missed alarms, and unnecessary battery drain. A defensible design names the local contention rule, the expected traffic shape, the devices that cannot hear one another, and the field metric that tells operators when the assumption has changed.
That metric might be retry rate, missed slot count, tail latency, receive-window miss rate, or battery current during contention.
Contention
Devices compete for the same medium. Carrier sensing, random backoff, acknowledgements, and retries keep moderate traffic fair without a central schedule.
Scheduling
A coordinator or network service assigns time, frequency, or link opportunities. This can bound latency and energy use when synchronization is worth the cost.
Random Access
Devices transmit with little coordination. This is attractive for sparse long-range telemetry, but capacity falls quickly as offered load rises.
5.3 Choose MAC Rules from Evidence
Start with the workload instead of the protocol. Record whether messages are periodic, event-driven, alarm-first, bulk, or interactive. Then test whether devices can hear one another, whether a gateway can coordinate them, how long a battery device may listen, and what happens when a frame is missed.
That record should be tied to a physical layout, because shelves, machinery, walls, and antenna height can change who hears whom even when every node reports the same configured channel.
Warehouse Sensor Example
A warehouse has periodic inventory sensors behind metal shelving. The average channel load is low, but sensors on opposite aisles cannot hear each other and both can reach the gateway. Pure CSMA/CA may still lose frames because each hidden sensor believes the channel is idle. There are three defensible responses.
Improve Visibility
Move gateways, add gateways, or adjust antennas so more nodes can hear each other and the coordinator has cleaner reception.
Add Handshakes
Use RTS/CTS when control-frame overhead costs less than hidden-terminal retransmissions.
Schedule Traffic
Use slots when reports are predictable and deterministic delivery matters more than immediate unscheduled access.
In 802.11, the RTS/CTS reservation is the practical version of the MACA for Wireless (MACA(W)) idea: a sender asks to transmit, the receiver grants the medium, and nearby stations that hear either control frame defer for the advertised duration. That duration feeds virtual carrier sensing, often called the Network Allocation Vector (NAV), so hidden stations can stay quiet even when they did not hear the original data sender.
Decision record: include the traffic class, contender count, hidden-terminal evidence, latency target, energy budget, chosen MAC behavior, fallback behavior, and the field metric that will trigger retesting.
5.4 MAC Collision and Timing Bounds
Under the hood, a MAC protocol is a set of timing and state rules. A contender may sense the channel, choose a random backoff, reserve the medium with control frames, send a data frame, wait for an acknowledgement, expand a retry window, or sleep until a scheduled slot. Each rule affects latency, energy, and how failures appear in logs.
Do not treat theoretical utilization as production proof. Pure ALOHA has an ideal maximum near 18% channel throughput and slotted ALOHA near 37% under simplified assumptions. CSMA/CA can perform much better at moderate load, but hidden terminals, exposed terminals, capture effects, noisy receivers, and acknowledgement loss change the field result.
Failure mode: reporting only channel utilization. A network can show low utilization and still drop critical frames if the radio geometry creates hidden terminals or if sleeping nodes miss their receive window.
Review Checklist
Collision Boundary
Name which collisions the design prevents, which it merely retries, and which it cannot observe directly.
Timing Boundary
Record worst-case access delay, retry delay, sleep window, and any synchronization dependency.
Energy Boundary
Separate transmit time, receive listening, overhearing, control frames, retry behavior, and resynchronization cost.
Retest Trigger
Retest after gateway moves, density changes, firmware alters backoff, or field logs show rising retries.
5.6 Summary
- MAC protocols decide when a local device may use a shared medium.
- CSMA/CA fits moderate contention when carrier sensing sees enough of the local channel.
- TDMA or scheduled access fits predictable traffic, bounded timing, and duty-cycled devices that can follow a schedule.
- ALOHA-style access can be acceptable for sparse telemetry but degrades quickly as offered load increases.
- Hidden terminals cause receiver-side collisions; exposed terminals waste spatial reuse.
- Production MAC decisions need evidence about traffic, reachability, timing, energy, retries, and retest triggers.
5.7 Key Takeaway
Choose a MAC protocol from measured channel behavior, not from a protocol label. The defensible design states what the channel-access rule prevents, what it retries, what it cannot see, and when operators must retest the assumption.