Wi-Fi 7 MLO Deployment: Modes, Channels and Cabling Reality

Wi-Fi 7 marketing leads with 46 Gbps. Enterprise planning should lead with three unglamorous facts: most client devices are still Wi-Fi 6 or older, 6 GHz has only three non-overlapping 320 MHz channels, and multi-link operation needs more backhaul and more power than the AP it replaces. This article covers what MLO actually changes, how to choose an operating mode, and the infrastructure prerequisites that decide whether the upgrade pays off.

What MLO changes

Instead of associating to one band at a time, a Wi-Fi 7 client (a multi-link device) forms links on 2.4, 5 and 6 GHz simultaneously. The upper MAC handles security and the logical connection; the lower MAC drives the radios. The practical outcome is not peak throughput but resilience: when one link degrades, traffic shifts without a re-association, which eliminates the roaming gap that applications experience today.

The three MLO modes

• EMLSR (enhanced multi-link single radio) — the client listens on several links and switches its single active radio to whichever link gets a transmit opportunity first. Best latency behaviour per watt, and the mode you can actually deploy in 2026 because it is what client chipsets implement.
• NSTR (non-simultaneous transmit and receive) — multiple links, but transmission and reception cannot overlap. A hardware compromise that still improves throughput over single-link.
• STR (simultaneous transmit and receive) — true parallel operation, requiring strong RF isolation to avoid self-interference. Rare on client devices today; expected with newer chipset generations.

Deployment translation: enable MLO in EMLSR mode, keep 2.4 GHz out of the MLO group (5 GHz + 6 GHz only), and treat STR as a future optimisation rather than an enabler of the project.

Channel planning is the real constraint

# Three non-overlapping 320 MHz channels exist in 6 GHz (US):
# 5955-6235 MHz | 6275-6555 MHz | 6595-6875 MHz
# In dense deployments use 160 MHz, not 320 MHz - co-channel
# interference negates the wider channel.

If you have more than a handful of APs per floor, a 320 MHz channel means every AP shares the same channel and the MLO gain evaporates. The sane enterprise configuration in 2026 is 160 MHz on 6 GHz, 80 MHz on 5 GHz, and 20 MHz on 2.4 GHz left for IoT and legacy clients.

Infrastructure prerequisites people miss

• Uplinks. Dual-radio MLO at 160 MHz needs 2.5 GbE minimum; tri-radio 320 MHz needs 5–10 GbE. A 1 GbE port caps the AP no matter what the radio does.
• PoE budget. Wi-Fi 7 APs draw 30 W and more, which means 802.3bt (PoE++) ports, not the 802.3at ports from a typical Wi-Fi 6 deployment. Audit your switch budget before ordering APs.
• Switch port density. Multi-gig copper at scale is often the missing component — a 48-port switch with 2.5 GbE on every port also needs the stacking bandwidth to match.

A staged rollout that survives the CFO

1. Upgrade the areas with the worst user complaints (dense meeting rooms, warehouse/AR use cases) and measure uplink throughput and latency before and after.
2. Keep MLO enabled only where clients support it; Wi-Fi 6 clients fall back to single-link, so there is no risk to legacy devices.
3. Plan the wired refresh together with the wireless one — multi-gig ports and PoE++ budgets are the same project as the AP replacement.
4. Re-measure with real devices; published MLO field trials show large gains under interference (uplink throughput improvements of well over 100 % and up to two-thirds lower uplink latency in trial conditions), but those numbers assume a Wi-Fi 7 client on the other end.

Related reading: 802.11k/v/r fast roaming configuration, PoE standards explained and 802.1X and MAB configuration.

原文链接：https://calmops.com/network/wifi-7-80211be-complete-guide