Prioritization is not reservation.
QoS marking changes the odds on a shared channel; only separation comes close to guaranteeing control traffic its airtime.
Prioritization is not reservation.
QoS is the first answer most network engineers reach for when control traffic shares the air with everything else. Mark the control traffic, map it to a high-priority queue, move on. I get why. On a wired switch, strict priority queuing can keep that promise.
On Wi-Fi it can’t. Every station contends for the same half-duplex channel, and the 802.11 access categories change the odds, not the outcome. RFC 83251 is blunt about it: contention has a random element, so 802.11 cannot assure strict priority between access categories or a minimum bandwidth for any of them. Higher categories get statistically better service. “Statistically” is the word that should worry a controls engineer.
Prioritization improves the odds; it does not reserve the channel
Each access category waits a fixed time, then a random one. The ranges overlap, so a lower category sometimes goes first.
Drawn to scale
Default parameters for the first attempt, drawn to scale. A best-effort frame that draws a short backoff (from 3 slots) can beat a video frame that draws a long one (up to 9), which is why 802.11 cannot promise strict priority or a minimum bandwidth to any category. Each failed attempt doubles the window, up to its maximum.
Source: RFC 8325, Figures 3 and 4, which reproduce the IEEE 802.11-2016 defaults.
It gets worse upstream. The access point marks what it sends. What the client sends is marked by the client’s own operating system (RFC 8325). If the robot doesn’t mark its traffic, your QoS policy doesn’t exist in that direction.
None of this makes QoS useless. Mark every class correctly and keep the marking intact end to end. It improves the odds, and odds matter. It is just the weaker lever.
The stronger lever is separation. Keep bulk transfers off the radios that carry control and safety traffic. On a vehicle, that can be literal: two radios, one for control traffic and one for everything else. The control radio can be Wi-Fi on its own band, or private 5G. What matters is that nothing else rides on it. Schedule map pushes, firmware updates, and log uploads outside production. And you can’t separate what you haven’t listed. You have to know everything on the air so control and safety traffic are prioritized over large transfers and updates. NIST’s guide to industrial wireless deployments makes the same call in its own terms: survey and inventory every network and emitter in the plant.
Two radios, two jobs
A map download on the second radio cannot queue in front of an I/O packet on the first.
Schematic, not to scale
On one shared channel, 802.11 cannot promise strict priority between access categories or a minimum bandwidth to any of them, so prioritization improves the odds and reserves nothing. Two radios separate the traffic instead. Conceptual: no products, timings, or throughput implied.
Source: RFC 8325.
The pressure only goes one way. Bot and AGV density is rising across industries and is saturating channels. 6 GHz is being deployed to relieve utilization, and the FCC opened 1,200 megahertz2 for it. More spectrum buys room. It doesn’t change the rule.
Start with the list: every traffic class, its marking, its radio, and its schedule window. Airtime is finite walks through it.
A marking asks for priority. Separation is as close to a reservation as Wi-Fi gets.
About this page
Built from 3 sources: 2 standards bodies and labs and 1 regulator or government source. Researched and drafted with AI assistance, then reviewed and approved by Ben Rutter on . How pages are made
- First published
- Last updated
Change history (1)
- First published
Cite this page
Plain
Ben Rutter. "Prioritization is not reservation.." OT Wireless, published October 5, 2026. https://otwireless.com/perspectives/prioritization-is-not-reservation/
APA 7
Rutter, B. (2026, October 5). Prioritization is not reservation.. OT Wireless. https://otwireless.com/perspectives/prioritization-is-not-reservation/
BibTeX
@misc{rutter2026prioritizationisnotreservation,
author = {Rutter, Ben},
title = {{Prioritization is not reservation.}},
year = {2026},
howpublished = {\url{https://otwireless.com/perspectives/prioritization-is-not-reservation/}},
organization = {OT Wireless},
}