// reference · wi-fi 8
Wi-Fi 8 - IEEE 802.11bn Ultra-High Reliability
802.11bn (Wi-Fi 8) shifts the design objective from peak throughput to deterministic reliability - sub-millisecond latency, 25% less packet loss, coordinated multi-AP operation, and mandatory WPA3. The standard targets finalisation in 2028; draft D1.x is active now.
Sources: IEEE TGbn official updates (2026), Samsung Research, Rohde & Schwarz Wi-Fi 8 whitepaper, arXiv 802.11bn tutorial (2025), Extreme Networks ExtremeConnect 2026 presentation.
What is Wi-Fi 8?
Wi-Fi 8 (IEEE 802.11bn) is the Ultra-High Reliability (UHR) amendment to 802.11. Unlike every prior generation - which competed on peak throughput (11 Mbps → 54 Mbps → 300 Mbps → 600 Mbps → 3.5 Gbps → 9.6 Gbps → 46 Gbps) - 802.11bn targets consistent, deterministic, worst-case performance. The standard is currently at Draft 1.x (TGbn D1.4, March 2026 plenary). Final publication: March/May 2028.
One-sentence summary per domain
| Domain | What it addresses | Key features | How it works |
|---|---|---|---|
| Spectrum Efficiency | Better use of available channels - primary channel bottleneck removed | NPCA, DSO, DBE | AP can temporarily use a non-primary 20 MHz channel; dynamically shifts STAs to different subbands |
| Multi-AP Coordination MAPC | APs working together - inter-AP interference eliminated | Co-TDMA, Co-BF, Co-SR, Co-RTWT | Inter-AP coordination agreements; APs share TXOPs and null out interference for each other |
| Mobility | Seamless roaming - security context never dropped | SMD Roaming, Bounded ESS | STAs stay associated while moving between APs in the same Seamless Mobility Domain |
| Reliability | Smoother performance - finer rate steps, better power management | New MCS, IDC/DUO, DPS, TWT, P-EDCA | Sub-10 ms latency guarantee for critical traffic via Defer Signal; finer rate adaptation |
| Uplink / Range | Stronger uplink signal at distance - link budget imbalance fixed | DRU, ELR | Distributed tone allocation overcomes 6 GHz PSD limits; ELR covers edge users at BPSK/QPSK |
| Security | Protecting all planes - data, control, and coordination | WPA3, RSNO, Secure Control Frames, 802.11bi | WPA3 mandatory with no legacy fallback; RSNO maintains security across AP transitions |
Technical targets vs Wi-Fi 7 (IEEE TGbn PAR)
25%
Throughput increase at a given SINR
25% faster at the same distance and interference level (rate-vs-range improvement)
25%
Reduction in 95th percentile latency
25% fewer worst-case lag spikes - the tail latency that kills XR, gaming, and industrial apps
25%
Reduction in MPDU loss
25% fewer dropped packets and retransmissions - the metric that matters for real-time control systems
Wi-Fi generation comparison
| Generation | Amendment | Year | Design goal | Peak rate | Key additions over prior gen |
|---|---|---|---|---|---|
| Wi-Fi 4 | 802.11n (HT) | 2009 | Higher throughput | 600 Mbps | MIMO, 40 MHz channels, A-MPDU aggregation |
| Wi-Fi 5 | 802.11ac (VHT) | 2013 | Very high throughput | 6.9 Gbps | 256-QAM, 80/160 MHz, DL MU-MIMO, beamforming |
| Wi-Fi 6 / 6E | 802.11ax (HE) | 2021 | High efficiency | 9.6 Gbps | OFDMA, UL MU-MIMO, TWT, BSS Color, 6 GHz band |
| Wi-Fi 7 | 802.11be (EHT) | 2024 | Extremely high throughput | 46 Gbps | 320 MHz, 4096-QAM, MLO, 16 spatial streams, preamble puncturing |
| Wi-Fi 8 | 802.11bn (UHR) | 2028 (est.) | Ultra-high reliability | ~23 Gbps (same as Wi-Fi 7) | DRU, ELR, UEQM, MAPC, NPCA, DSO, SMD, RSNO, P-EDCA, 802.11bi, NPU-ready APs |
What Wi-Fi 8 does NOT change
802.11bn retains the same physical foundation as Wi-Fi 7: 2.4 GHz / 5 GHz / 6 GHz bands (1–7.25 GHz), maximum 320 MHz channel bandwidth, 4096-QAM modulation, up to 8 spatial streams per link, and ~23 Gbps theoretical peak. The peak rate does not increase. The mission is making every percentile of performance better - not raising the ceiling, but raising the floor.
PHY Layer Enhancements
Wi-Fi 8 introduces five PHY-layer improvements. Three address uplink range and reliability (DRU, ELR, UEQM). Two address finer link adaptation (new MCS, 2xLDPC). Together they close the link budget gap between AP and STA that has plagued every prior generation.
DRU - Distributed-tone Resource Units
Problem: In Wi-Fi 6/7, OFDMA Resource Units are contiguous subcarrier blocks. In the 6 GHz band under LPI rules, the AP can transmit at up to 30 dBm EIRP - but a phone using a small contiguous 26-tone RU is PSD-limited to much lower power per tone, capping its uplink range.
Solution (DRU): Scatter the same number of subcarriers across the entire available distribution bandwidth instead of in a contiguous block. Each subcarrier can now transmit at the PSD limit independently. Net effect: the same information content transmitted with dramatically higher total power - doubling or tripling the reliable uplink range for the same device in the 6 GHz band.
Solution (DRU): Scatter the same number of subcarriers across the entire available distribution bandwidth instead of in a contiguous block. Each subcarrier can now transmit at the PSD limit independently. Net effect: the same information content transmitted with dramatically higher total power - doubling or tripling the reliable uplink range for the same device in the 6 GHz band.
| Parameter | Regular RU (Wi-Fi 6/7) | DRU (Wi-Fi 8) |
|---|---|---|
| Subcarrier arrangement | Contiguous block (e.g., 26 adjacent tones) | Distributed across full bandwidth (e.g., 26 tones spread across 320 MHz) |
| 6 GHz uplink range | Limited by PSD constraint on contiguous RU | 2–3x improved range by maximising per-tone power |
| Best for | High-throughput short-range links | Low-power devices: IoT, wearables, AR glasses, edge sensors |
| 802.11bn reference | Introduced in 802.11ax §26.3.2 | 802.11bn dRU - see TGbn D1.x §26.x (DRU subcarrier allocation) |
ELR - Enhanced Long Range PPDU
Problem (link budget imbalance): An AP can transmit at up to 23 dBm (indoors) or 36 dBm (outdoors with AFC). A phone transmits at ~20 dBm. That 10+ dB asymmetry means the AP can hear the phone from 50 m away, but the phone cannot reliably respond - uplink fails before downlink. This is the fundamental range problem for all Wi-Fi deployments.
Solution (ELR): A dedicated 20 MHz-only PPDU format with BPSK and QPSK at two coding rates - 1.67 Mbps and 3.33 Mbps - that sacrifices throughput for extreme link robustness. ELR uses 2xLDPC and extended preamble for additional coding gain. The ELR-MARK field in the preamble carries BSS Color for early OBSS filtering.
Solution (ELR): A dedicated 20 MHz-only PPDU format with BPSK and QPSK at two coding rates - 1.67 Mbps and 3.33 Mbps - that sacrifices throughput for extreme link robustness. ELR uses 2xLDPC and extended preamble for additional coding gain. The ELR-MARK field in the preamble carries BSS Color for early OBSS filtering.
| Parameter | Value |
|---|---|
| Channel bandwidth | 20 MHz only |
| Supported modulation | BPSK, QPSK |
| PHY data rates | 1.67 Mbps (BPSK) and 3.33 Mbps (QPSK) |
| Uplink support | 2.4 GHz (UL + DL), 5 GHz (UL only), 6 GHz (UL only) |
| Preamble | Backward-compatible legacy preamble + ELR-MARK (2 symbols, carries BSS Color) |
| Error correction | 2x LDPC code rate (two passes for additional coding gain) |
| Use cases | Outdoor cameras, IoT edge sensors, AR glasses, wearables, industrial endpoints |
UEQM - Unequal Modulation
Prior Wi-Fi: all spatial streams in a MU-MIMO or beamforming transmission use the same MCS (e.g., all 4 streams at MCS 11 1024-QAM). UEQM (Unequal Modulation) allows each spatial stream to use a different modulation order based on that stream's specific channel quality. A beam pointing toward a client through a concrete wall uses QPSK on its weakest stream while using 1024-QAM on its strongest. Net effect: significantly better beamforming performance in complex multi-antenna environments with heterogeneous link qualities.
New MCS Levels
802.11bn introduces additional MCS levels to close the SNR gaps between existing MCS indices. In Wi-Fi 6/7, there are step jumps at certain SNR values where the link could theoretically support a higher rate but no MCS index exists for that operating point. New MCS fill these gaps, enabling finer-grained link adaptation and better throughput at intermediate SNR values. Result: smoother rate-vs-range curves and fewer retransmissions at SNR boundary conditions.
2xLDPC - Enhanced Error Correction
Low-Density Parity Check (LDPC) has been in 802.11 since 802.11n as an optional coding scheme. 802.11bn upgrades LDPC to a two-pass (2x) implementation that provides additional coding gain - particularly useful for ELR frames and for critical-reliability data streams where even a 1 dB improvement in effective SNR matters. 2xLDPC is the error correction equivalent of what ELR is to the PHY format: sacrificing some overhead for measurable reliability gains at the receiver.
MAC Layer Enhancements
Wi-Fi 8 MAC enhancements address three separate problems: the primary channel bottleneck (NPCA, DSO), the latency tail (P-EDCA, preemption), and power management for dense IoT (DPS, TWT enhancements). These are independent mechanisms that can operate simultaneously.
NPCA - Non-Primary Channel Access
Problem: In all prior 802.11 standards, the primary 20 MHz channel carries all MAC signalling - beacons, probe requests, trigger frames, channel announcements. When this channel is busy (often due to OBSS activity), the entire 80/160/320 MHz channel is blocked even if the other 14 non-primary 20 MHz sub-channels are clear.
Solution: NPCA allows an AP or STA to temporarily designate a different 20 MHz channel as the primary channel (the "NPCA primary channel") when the original primary is occupied. The AP broadcasts NPCA parameters including the candidate NPCA primary channel, switching delays, and the conditions under which NPCA is permitted. The STA also declares its own switching delay. The result: congested primary channels no longer block the full wideband operation.
Solution: NPCA allows an AP or STA to temporarily designate a different 20 MHz channel as the primary channel (the "NPCA primary channel") when the original primary is occupied. The AP broadcasts NPCA parameters including the candidate NPCA primary channel, switching delays, and the conditions under which NPCA is permitted. The STA also declares its own switching delay. The result: congested primary channels no longer block the full wideband operation.
| Parameter | Detail |
|---|---|
| Trigger condition | Primary 20 MHz channel busy - typically from OBSS transmissions |
| Switching mechanism | AP indicates NPCA primary channel, switching conditions, and per-device switching delay parameters |
| Scope | Temporary primary channel reassignment; reverts when original primary clears |
| Combined benefit | Works alongside DSO - NPCA for primary channel bottleneck, DSO for bandwidth mismatch |
| Impact | Turns underutilised non-primary channels into on-demand transmission opportunities |
DSO - Dynamic Subband Operation
Problem: A 320 MHz AP serving a 160 MHz client wastes 160 MHz. A 160 MHz AP serving an 80 MHz client wastes 80 MHz. There was previously no mechanism to dynamically shift a STA's operating bandwidth to better utilise the AP's wider channel. Under-utilised spectrum in one part of the band while another part is congested.
Solution: DSO allows the AP to dynamically allocate frequency resources to a STA operating outside the STA's normal bandwidth. For example: move an 80 MHz STA into a different 80 MHz slice of the AP's 320 MHz channel to reduce congestion in the primary slice. Works in conjunction with NPCA for comprehensive spectrum flexibility.
Solution: DSO allows the AP to dynamically allocate frequency resources to a STA operating outside the STA's normal bandwidth. For example: move an 80 MHz STA into a different 80 MHz slice of the AP's 320 MHz channel to reduce congestion in the primary slice. Works in conjunction with NPCA for comprehensive spectrum flexibility.
DBE - Dynamic Bandwidth Expansion
Related to DSO. DBE allows the AP to expand a STA's operating bandwidth when spectrum becomes available - the inverse of DSO. A STA negotiated at 80 MHz can be temporarily expanded to 160 MHz during periods of low channel load, then returned to 80 MHz when congestion increases. This maximises throughput during favourable conditions without sacrificing compatibility.
P-EDCA and Preemption - Sub-10ms Latency Guarantee
P-EDCA (Prioritised EDCA): A STA with an urgent frame sends a Defer Signal (DS-CTS) - a new control frame type - that temporarily excludes all STAs with non-urgent traffic from channel contention. This clears the airwaves for one high-priority TXOP. The DS-CTS is the Wi-Fi 8 equivalent of a 5G QoS priority class - it carves out a guaranteed transmission slot.
Preemption: If an urgent frame arrives during an ongoing transmission of lower priority, 802.11bn allows stopping that transmission and starting the urgent one. The interrupted transmission resumes after the high-priority frame is acknowledged. This is conceptually borrowed from 5G pre-emptive scheduling and is new to 802.11.
Combined latency target: P-EDCA + preemption target sub-10 ms worst-case latency for AR/VR, industrial control, and mission-critical signalling.
Preemption: If an urgent frame arrives during an ongoing transmission of lower priority, 802.11bn allows stopping that transmission and starting the urgent one. The interrupted transmission resumes after the high-priority frame is acknowledged. This is conceptually borrowed from 5G pre-emptive scheduling and is new to 802.11.
Combined latency target: P-EDCA + preemption target sub-10 ms worst-case latency for AR/VR, industrial control, and mission-critical signalling.
DPS - Dynamic Power Save
DPS reduces power consumption during link listening periods. An AP in DPS mode can reduce its antenna activity and receiver sensitivity during intervals when no associated STA is expected to transmit (based on TWT schedules and traffic patterns). Designed for APs in battery-powered or energy-constrained deployments. Complements TWT at the STA side - when the STA is asleep (TWT), the AP side can also save power rather than maintaining full receive readiness.
MAPC - Multi-AP Coordination Protocol
MAPC is the most architecturally significant feature of Wi-Fi 8. It enables multiple APs that share the same primary channel to coordinate their transmissions - sharing TXOPs, beamforming nulls, and timing - rather than competing independently via CSMA/CA. MAPC transforms a collection of competing APs into a cooperative network. IEEE 802.11bn D1.x defines a common framework for AP coordination, with four specific coordination schemes.
MAPC coordination schemes
| Scheme | Full name | How it works | Primary benefit |
|---|---|---|---|
| Co-TDMA | Coordinated Time-Division Multiple Access | APs share TXOPs in time - AP 1 transmits during slots 1–3, AP 2 during slots 4–6, coordinated via Initial Control Frame (ICF). Eliminates inter-AP collisions by schedule rather than by backoff. | Deterministic channel access - predictable, collision-free airtime allocation across multiple APs. Directly enables sub-millisecond latency guarantees for industrial Wi-Fi. |
| Co-BF | Coordinated Beamforming | Two or more APs beam to their respective clients simultaneously on the same channel. Each AP uses its remaining spatial degrees of freedom to create radiation nulls (interference-free zones) toward the other AP's client. Requires NDP sounding and compressed V-matrix exchange between coordinating APs. | Multiple APs transmit simultaneously on the same channel without causing interference. Dramatically increases spatial reuse - effectively treating a multi-AP deployment as a distributed MIMO system. |
| Co-SR | Coordinated Spatial Reuse | OBSS Spatial Reuse from 802.11ax extended to multi-AP context. Coordinating APs negotiate OBSS_PD thresholds jointly so that both can transmit concurrently under the OBSS_PD rule without causing harmful interference. More aggressive than BSS Color-based SR because APs actively coordinate rather than independently applying thresholds. | Higher aggregate throughput in overlapping BSS scenarios. More spectrum reuse in dense deployments than BSS Color alone. |
| Co-RTWT | Coordinated Restricted TWT | Multiple APs in a MAPC group coordinate TWT service periods - all coordinated APs align their IoT wake windows to the same time slots. During these slots, coordinated APs can serve their respective IoT clients simultaneously without interference (using Co-BF or Co-SR) rather than sequentially. | Scales IoT TWT efficiency from single-AP to multi-AP environments. Enables synchronised IoT wake-up across an entire floor or building segment. |
MAPC protocol flow (Co-BF example)
| Step | Frame / Action | What happens |
|---|---|---|
| 1 | ICF - Initial Control Frame | Sharing AP (the MAPC coordinator) sends ICF to the Shared AP, indicating coordination parameters: target STA, duration, coordination type (Co-BF) |
| 2 | ICR - Initial Control Response | Shared AP responds with ICR confirming participation and its own STA target |
| 3 | NDP Announcement + NDP | Both APs exchange NDP sounding to learn cross-AP channel state - required for interference null calculation |
| 4 | Compressed V-matrix exchange | Each AP provides its beamforming feedback to the other so both can compute interference-cancelling steering matrices |
| 5 | Simultaneous DL transmission | Both APs transmit to their respective clients simultaneously on the same channel using the computed null-steering beamforming weights |
| 6 | Block ACK from both clients | Each client ACKs to its own AP. Coordination TXOP ends. |
MAPC vs legacy CSMA/CA
| Aspect | Legacy CSMA/CA (Wi-Fi 6/7) | MAPC (Wi-Fi 8) |
|---|---|---|
| AP coordination | None - each AP competes independently for the channel | Explicit - APs exchange ICF/ICR, sounding, and beamforming feedback before transmitting |
| Simultaneous transmission | Only if STAs are far enough apart for BSS Color-based SR (opportunistic) | Guaranteed via Co-BF null steering (interference-managed) |
| Latency guarantee | None - EDCA provides priority, not determinism | Co-TDMA provides time-slotted deterministic access per AP |
| Infrastructure requirement | Independent AP firmware | Coordinating APs must share sounding data - requires controller or direct AP-to-AP communication |
| Wired equivalent | Multiple independent Ethernet switches on same collision domain | Coordinated Ethernet switch fabric with explicit time-division scheduling |
Seamless Mobility - SMD and Bounded ESS
Wi-Fi 8 mobility is a step beyond 802.11k/v/r. Rather than optimising the transition between APs, SMD (Seamless Mobility Domain) makes the transition invisible by keeping the STA associated during the move. The STA never fully disassociates - it transitions link-by-link using MLO-aware mechanisms while maintaining security context.
SMD - Seamless Mobility Domain
What it solves: Even with 802.11r Fast Transition, there is a handover latency - the STA disassociates from AP1 before completing reassociation on AP2. In a 50 ms window, a voice call drops a packet, an XR frame is missed, or an industrial control message is delayed. SMD eliminates this by redefining the roaming event as a link transition within a maintained association rather than a disassociation and new association.
How it works: STAs in a Seamless Mobility Domain maintain association with multiple APs simultaneously via MLO (from 802.11be). When a STA moves from AP1 to AP2, it uses a dedicated link on AP2 to complete key re-establishment before dropping the link to AP1. The data path moves from AP1 to AP2 with zero packet loss and zero latency interruption. Security context (PMK, PTK) is maintained throughout - there is no EAPOL 4-Way Handshake re-run. SMD roaming is measured in microseconds, not milliseconds.
How it works: STAs in a Seamless Mobility Domain maintain association with multiple APs simultaneously via MLO (from 802.11be). When a STA moves from AP1 to AP2, it uses a dedicated link on AP2 to complete key re-establishment before dropping the link to AP1. The data path moves from AP1 to AP2 with zero packet loss and zero latency interruption. Security context (PMK, PTK) is maintained throughout - there is no EAPOL 4-Way Handshake re-run. SMD roaming is measured in microseconds, not milliseconds.
| Comparison | 802.11r FT (Wi-Fi 6/7) | SMD (Wi-Fi 8) |
|---|---|---|
| Association state during transition | Disassociated from AP1 before reassociation completes on AP2 - brief gap | Associated with both APs via MLO links simultaneously - no gap |
| Security context during transition | PMK-R1 pre-distributed; PTK re-derived on new AP via FT Auth frames | Security context maintained throughout - no new key derivation required |
| Transition latency | 35–50 ms (well-configured 802.11r) | Sub-millisecond (link transition, not re-association) |
| Packet loss during handover | 0–2 packets with 802.11r; more without | Zero - data path moves before old path drops |
| Infrastructure requirement | Controller with PMK-R1 pre-distribution to candidate APs | Coordinated APs in the same SMD (MLO-aware, MAPC-enabled) |
| Best for | VoIP, video calls in enterprise | XR/VR, industrial control, autonomous robots, AR glasses with real-time compute |
Bounded ESS
A Bounded ESS is a defined set of APs that form a single coordinated wireless domain with strict membership rules. Within a Bounded ESS, MAPC, SMD, RSNO (secure roaming), and coordinated resource allocation all operate under a unified policy. The boundary is administratively defined - only APs within the Bounded ESS participate in coordination. STAs inside a Bounded ESS get full Wi-Fi 8 benefits; STAs outside get standard 802.11 treatment. This is the architectural unit of Wi-Fi 8 deployment - analogous to a 5G cell cluster or a coordinated RAN cluster.
Wi-Fi 8 Security Architecture
Wi-Fi 8 extends security from the data plane to the control plane. For the first time, the frames that coordinate AP behaviour - MAPC coordination messages, timing signals, and roaming triggers - are cryptographically protected. WPA3 with no legacy fallback is mandatory. Security is not optional or an SSID configuration - it is baked into the 802.11bn amendment itself.
Four security pillars
1
WPA3 Required
Strong encryption by default. No legacy WPA2 fallback.
✓ WPA3-Personal (SAE) and WPA3-Enterprise mandatory
✓ SAE Dragonfly handshake - forward secrecy, offline dictionary attack resistant
✓ 192-bit security mode for government/industrial: AKM 12, GCMP-256, BIP-GMAC-256
✓ PMF (802.11w) mandatory - all management frames encrypted post-association
✓ WPA3-Personal (SAE) and WPA3-Enterprise mandatory
✓ SAE Dragonfly handshake - forward secrecy, offline dictionary attack resistant
✓ 192-bit security mode for government/industrial: AKM 12, GCMP-256, BIP-GMAC-256
✓ PMF (802.11w) mandatory - all management frames encrypted post-association
2
RSNO - Secure Roaming
RSN Overriding (RSNO) - consistent security context across AP transitions.
✓ RSNO mandatory for all STAs operating in a Bounded ESS
✓ PMK and PTK context maintained across SMD transitions - no re-authentication
✓ Security level cannot be downgraded between APs in the same MAPC group
✓ Seamless, secure roaming - the STA's encryption state never lapses
✓ RSNO mandatory for all STAs operating in a Bounded ESS
✓ PMK and PTK context maintained across SMD transitions - no re-authentication
✓ Security level cannot be downgraded between APs in the same MAPC group
✓ Seamless, secure roaming - the STA's encryption state never lapses
3
Secure Control Plane
Protects coordination and control signalling - new in Wi-Fi 8.
✓ Secure Control Frames protect MAPC coordination messages (ICF/ICR, Co-TDMA scheduling, Co-BF sounding)
✓ Built on 802.11ml (Protected Management Frames framework extended to coordination)
✓ Protects against rogue AP injecting false MAPC coordination messages
✓ P-EDCA Defer Signal also requires cryptographic binding to prevent DoS via fake DS-CTS injection
✓ Secure Control Frames protect MAPC coordination messages (ICF/ICR, Co-TDMA scheduling, Co-BF sounding)
✓ Built on 802.11ml (Protected Management Frames framework extended to coordination)
✓ Protects against rogue AP injecting false MAPC coordination messages
✓ P-EDCA Defer Signal also requires cryptographic binding to prevent DoS via fake DS-CTS injection
4
802.11bi - Enhanced Privacy
Improved device privacy and identity protection.
✓ Enhanced MAC Address Randomisation - more aggressive rotation policy than 802.11ax
✓ Randomised Device Identity (RDI) - stable within an AP session but unlinkable across sessions
✓ Identity Concealment - IE content in probe frames cannot be used to fingerprint device type
✓ Reduces tracking exposure in retail, transportation, and public space deployments
✓ Enhanced MAC Address Randomisation - more aggressive rotation policy than 802.11ax
✓ Randomised Device Identity (RDI) - stable within an AP session but unlinkable across sessions
✓ Identity Concealment - IE content in probe frames cannot be used to fingerprint device type
✓ Reduces tracking exposure in retail, transportation, and public space deployments
Security comparison: Wi-Fi 6 vs Wi-Fi 7 vs Wi-Fi 8
| Feature | Wi-Fi 6 (802.11ax) | Wi-Fi 7 (802.11be) | Wi-Fi 8 (802.11bn) |
|---|---|---|---|
| WPA3 | Required on 6 GHz; optional on 2.4/5 GHz | Required on 6 GHz; optional on 2.4/5 GHz | Required on all bands - no WPA2 fallback |
| PMF (802.11w) | Mandatory for WPA3; optional for WPA2 | Mandatory for WPA3; optional for WPA2 | Mandatory for all associations |
| Control plane security | Not protected | Not protected | Secure Control Frames - MAPC messages signed |
| Roaming security | 802.11r PMKR1 - brief security gap during FT | 802.11r PMKR1 - brief security gap during FT | RSNO - security context continuous during SMD |
| Device privacy | Basic MAC randomisation (802.11aq) | Basic MAC randomisation | 802.11bi - enhanced RDI + identity concealment |
| Legacy fallback | WPA2 allowed on 2.4/5 GHz | WPA2 allowed on 2.4/5 GHz | No legacy fallback permitted in UHR BSS |
Beyond Connectivity - APs as Edge AI Platforms
Wi-Fi 8 is designed for APs that contain Neural Processing Units (NPUs) - dedicated AI inference silicon that offloads complex ML tasks from the main CPU. This is not a feature of the 802.11bn standard itself, but a design direction that Wi-Fi 8's reliability and latency properties enable. APs are already in every room, always powered, and always connected - the most distributed compute infrastructure any organisation already owns.
NPU-enabled AP applications
Video & Visual Analytics
Occupancy counting, queue detection, safety compliance - all processed locally. No video stream leaves the premise. Inference latency: sub-50 ms at the AP.
Healthcare Monitoring
Asset tracking, patient flow, environmental sensing - acted on at the edge. No PII in the cloud. PHI never leaves the clinical network boundary.
Industrial & Logistics
Proximity alerts, workflow optimisation, predictive maintenance - sub-second response. Does not depend on cloud round trip. Works even during WAN outage.
Retail Intelligence
Foot traffic, dwell time, dynamic signage - no PII leaves the premises. Enables personalisation without cloud dependency or GDPR exposure.
Smart Building Operations
HVAC, lighting, space utilisation - driven by real-time occupancy inference at the AP. Reduces energy consumption by 20–40% in pilot deployments vs cloud-controlled systems.
Security & Threat Detection
Rogue AP detection, behavioural anomaly, automated containment - no cloud latency. The AP sees all RF traffic and can act on anomalies in under 100 ms, before cloud-based systems even receive the alert.
Edge AI deployment timeline
Near-term
Network Optimisation & Telemetry
AP uses NPU to process RF measurements, interference patterns, and client behaviour locally. Feeds optimisation decisions back to the controller in real time without raw data upload.
Mid-term
Lightweight Edge Inference
AP runs quantised ML models for specific vertical applications: occupancy detection, asset tracking, anomaly detection. Models deployed over-the-air by the controller. No dedicated edge server required.
Long-term
Customer Business Applications
Third-party application marketplace for AP firmware. Retailers, hospitals, and manufacturers deploy custom inference models on AP infrastructure they already own. The AP becomes a compute node, not just a radio.
Key insight from David Coleman (Extreme Networks, ExtremeConnect 2026): "Your Wi-Fi infrastructure is the most distributed compute platform you already own - edge AI turns it into a business application platform." The 802.11bn reliability improvements (sub-millisecond latency, 25% less packet loss, MAPC coordination) are what make this viable - AI inference results are only useful if the network can act on them in real time.
IEEE 802.11bn Standardisation Timeline
802.11bn follows a single-release standardisation cycle from TGbn formation (Nov 2023) to final publication (~2028). The Wi-Fi Alliance certification programme is on a parallel track targeting devices in market by early 2028. As of May 2026, TGbn is at Draft 1.4 (D1.4) - resolving ~1,800 comments from Letter Ballot 291 across all feature domains.
Key milestones
| Date | Milestone | Status |
|---|---|---|
| Jul 2022 | UHR Study Group established - defined objectives and scope for new 802.11 amendment | Done |
| Nov 2023 | TGbn (UHR Task Group) formally established - standardisation work begins | Done |
| Feb 2025 | Draft 0.1 completed - initial technical scope and feature set | Done |
| Jun–Jul 2025 | Draft 1.0 finalised - defines the technical scope of 802.11bn | Done |
| Sep–Nov 2025 | Draft 1.1 / 1.2 - ~700 LB291 comments resolved; D1.2 generated | Done |
| Mar 2026 | D1.4 - ~1,800 LB291 comments resolved in 11-session plenary (11 topics including Co-TDMA, Co-BF, NPCA, ELR, DRU, MAPC, roaming, security) | Done |
| Jul 2026 | TGbn MAC ad-hoc (mixed mode) meeting - North America | Scheduled |
| May 2026 | Draft 2.0 expected | In progress |
| Jan 2027 | Draft 3.0 expected | Pending |
| May 2027 | Final draft submitted for Sponsor Ballot | Pending |
| Jun 2027 | Wi-Fi Alliance certification test plan finalised | Pending |
| Dec 2027 | Wi-Fi Alliance Wi-Fi 8 certification programme launches | Pending |
| Mar–May 2028 | IEEE 802.11bn standard published | Pending |
| 2027–2028 | First Wi-Fi 8 certified devices enter market (MediaTek Filogic 8000, Qualcomm, Intel) | Pending |
Chipset development status (as of May 2026)
| Vendor | Platform | Known Wi-Fi 8 features |
|---|---|---|
| MediaTek | Filogic 8000 | Full 802.11bn feature set + Single-MAC MLO, zero-wait DFS, 5th receive antenna configuration (+20% performance), enhanced DPD+ power efficiency |
| Qualcomm | FastConnect 8000 series | Active TGbn contributor. FastConnect 7800 for Wi-Fi 7 (current); 802.11bn next-gen platform in development |
| Intel | BE series follow-on | Intel BE200 (Wi-Fi 7 current). 802.11bn client platform in development for laptop integration |
| Broadcom | Wi-Fi 8 SoC | Active TGbn contributor. Enterprise AP silicon with MAPC hardware acceleration reported in roadmap |
What to watch
The three features most likely to define Wi-Fi 8 adoption in practice are: (1) MAPC / Co-TDMA - this is the feature that enables industrial and mission-critical wireless for the first time; (2) SMD seamless roaming - this is what XR and autonomous mobile devices need; (3) DRU uplink - this solves the IoT uplink range problem that TWT alone cannot address. WPA3 mandatory is not a headline feature but is the most operationally disruptive change for organisations still running WPA2-only infrastructure.