56  Wi-Fi 6 for IoT

In 60 Seconds

This review analyzes Wi-Fi 6 for a 500-device smart factory (200 vibration sensors, 150 temperature sensors, 100 cameras, 50 AGVs). Total throughput is only 260 Mbps (3.7% of Wi-Fi 5 capacity), but airtime utilization reaches 42.6% due to per-packet overhead from CSMA/CA – approaching the 50% degradation threshold. Wi-Fi 6 OFDMA divides 80 MHz channels into Resource Units (26-tone to 996-tone), enabling parallel transmission of 4+ devices per TXOP. This reduces airtime from 42.6% to 15.4% (2.77x improvement). Even the smallest 26-tone RU (2 MHz) provides roughly 37,500 times more bandwidth than a temperature sensor needs. TWT eliminates beacon listening (99% of energy for periodic sensors), potentially extending battery life from 62 days to years. Channel planning uses measurement-driven iteration with non-overlapping 5 GHz channels in a checkerboard pattern.

“Our factory has 500 devices and Wi-Fi 5 is struggling!” said Max the Microcontroller. “Even though we only use 3.7% of the bandwidth, the AIRTIME is 42.6% full!”

“That is because of OVERHEAD,” explained Sammy the Sensor. “Every tiny packet needs the full channel access ceremony – wait for silence, back off, transmit, get ACK. It is like making every student walk to the front of the class just to say one word!”

“Wi-Fi 6 OFDMA fixes this!” said Lila the LED. “It divides the channel into RESOURCE UNITS. Now four students can speak at the SAME TIME, each using their own slice of the channel. Even the smallest slice (26-tone, 2 MHz) gives a temperature sensor over 37,000 times more bandwidth than it needs!”

“And Target Wake Time helps ME!” cheered Bella the Battery. “Instead of waking up every 100 milliseconds to check for beacons – which wastes 99% of my energy – I only wake up at my scheduled time. My battery could last YEARS instead of two months!”

56.1 Learning Objectives

By the end of this section, you will be able to:

  • Calculate Throughput Requirements: Aggregate device traffic across heterogeneous IoT workloads and compare totals against AP capacity limits
  • Distinguish Airtime from Throughput: Explain why low throughput utilization can mask high airtime contention and predict when per-packet overhead causes performance degradation
  • Allocate OFDMA Resource Units: Assign 26-tone through 996-tone RUs to mixed IoT traffic types and justify each allocation based on device data rates
  • Evaluate TWT Power Savings: Calculate energy budgets with and without Target Wake Time scheduling to quantify battery life improvements for periodic sensors
  • Design Dense Deployment Plans: Configure channel assignments and AP density for industrial IoT facilities using measurement-driven iteration

Wi-Fi 6 was specifically designed to handle environments with many connected devices – smart offices, stadiums, and IoT-heavy buildings. This review covers how OFDMA, BSS Coloring, and Target Wake Time work together to support hundreds of IoT devices on a single access point without performance degradation.

56.2 Prerequisites

Before working through this analysis, ensure you understand:

Key Concepts

  • Dense Deployment: High-density IoT environments with 50-500+ devices per AP coverage area; requires Wi-Fi 6 features for efficiency
  • OFDMA for Small Packets: Wi-Fi 6 allocates Resource Units (RUs) to multiple clients simultaneously; ideal for small IoT sensor packets
  • MU-MIMO Uplink: Wi-Fi 6 adds uplink multi-user MIMO enabling simultaneous uplink from multiple clients; improves IoT sensor polling
  • BSS Coloring Efficiency: Reduces spatial reuse waste; colored BSS allows overlapping transmissions that do not interfere
  • TWT for Dense IoT: Scheduling hundreds of IoT devices with non-overlapping TWT windows eliminates contention for sensor networks
  • Channel Reuse Factor: In dense 802.11ax deployments, BSS Coloring allows reuse factor approaching 1 vs legacy 1/3 or 1/4
  • OFDMA vs OFDM: OFDM assigns entire channel to one client per slot; OFDMA divides channel into resource units for simultaneous multi-user access
  • Wi-Fi 6 AP Capacity: Wi-Fi 6 APs handle 4-8x more devices efficiently vs Wi-Fi 5 APs in dense environments

56.3 Wi-Fi 6 for High-Density IoT Deployments

Scenario:

A smart factory is deploying 500 Wi-Fi-connected IoT devices across a 10,000 m2 facility:

  • 200 vibration sensors (25 KB/s continuous monitoring, latency <50 ms)
  • 150 temperature sensors (100 bytes every 10 seconds, latency <5 seconds)
  • 100 cameras (2 Mbps video stream, latency <100 ms)
  • 50 AGV robots (Automated Guided Vehicles, 50 KB/s telemetry + control, latency <20 ms)

The facility currently has 10x Wi-Fi 5 (802.11ac) access points providing coverage. Each AP supports:

  • Wi-Fi 5 specs: 80 MHz channels, 256-QAM, 4 spatial streams, theoretical 1.73 Gbps
  • Typical real-world throughput: 600-800 Mbps per AP
  • Frequency: 5 GHz band (channels 36, 40, 44, 48, 52, 56, 60, 64, 100, 104)

Network architect proposes upgrading to Wi-Fi 6 (802.11ax) APs with:

  • Wi-Fi 6 specs: 80 MHz channels, 1024-QAM, 4 spatial streams, OFDMA, TWT
  • Theoretical: 2.4 Gbps
  • Typical real-world: 1.2-1.5 Gbps per AP

Analysis Questions:

  1. Calculate the total required throughput and determine if Wi-Fi 5 infrastructure can support the deployment
  2. Analyze how Wi-Fi 6 OFDMA improves efficiency for mixed IoT traffic (calculate resource units needed)
  3. Estimate power savings using Wi-Fi 6 TWT (Target Wake Time) for the 150 temperature sensors
  4. Recommend channel planning and AP density for optimal performance

56.4 Total Throughput Requirements and Wi-Fi 5 Capacity Analysis

56.4.1 Device Traffic Calculation

Device Type Count Per-Device Rate Total Throughput
Vibration sensors 200 25 KB/s (200 kbps) 40 Mbps
Temperature sensors 150 100 bytes/10s (80 bps) 0.012 Mbps
Cameras 100 2 Mbps 200 Mbps
AGV robots 50 50 KB/s (400 kbps) 20 Mbps
TOTAL 500 260 Mbps

56.4.2 Wi-Fi 5 Capacity Analysis

Metric Value Calculation
Number of APs 10 Existing deployment
Throughput per AP 700 Mbps Real-world (midpoint 600-800 range)
Total capacity 7,000 Mbps (7 Gbps) 10 x 700
Required throughput 260 Mbps From table above
Throughput utilization 3.71% 260 / 7,000

Initial Verdict: Wi-Fi 5 CAN support deployment - only 3.71% throughput utilization

But wait… This analysis is misleading!

It only considers throughput, not airtime efficiency.

56.4.3 Per-AP Device Distribution (even distribution)

Device Type Devices per AP Throughput per AP
Vibration sensors 20 4 Mbps
Temperature sensors 15 0.001 Mbps
Cameras 10 20 Mbps
AGV robots 5 2 Mbps
Total 50 devices 26 Mbps (3.7%)

56.5 Hidden Problem: Airtime Efficiency and Latency

Wi-Fi 5 uses OFDM (not OFDMA), meaning only one device transmits at a time. Each transmission requires overhead:

56.5.1 Wi-Fi 5 Packet Overhead Components

  • DIFS (Distributed Inter-Frame Space): 28 us
  • Backoff (average): 67.5 us
  • Payload transmission: Variable (depends on PHY rate)
  • SIFS + ACK: 24 us
  • Total overhead per packet: ~120 us + transmission time

56.5.2 Airtime Analysis (per AP)

Device Type Devices Packets/s PHY Rate Packet Time Airtime %
Vibration sensors 20 2,000 200 Mbps 132 us 26.4%
Temperature sensors 15 1.5 200 Mbps 132 us 0.02%
Cameras 10 600 400 Mbps 151 us 9.05%
AGV robots 5 500 200 Mbps 142 us 7.11%
TOTAL 50 3,101 42.58%
Revised Verdict: Wi-Fi 5 experiences 42.6% airtime utilization per AP

This is approaching the 50% threshold where Wi-Fi performance degrades significantly:

  • Increased collision probability
  • Higher latency (devices queue longer for transmission)
  • Reduced effective throughput
  • Little headroom for growth

56.5.3 Latency Impact

Using M/M/1 queuing model with 42.6% utilization (rho = 0.426):

Component Latency Notes
Queue delay 0.11 ms rho/(1-rho) x service_time
Service time 0.14 ms Average packet transmission
Processing 2.0 ms AP routing/switching
Total latency 2.25 ms Meets all requirements (barely)

Wi-Fi 5 Verdict: Can technically support deployment but operates at 42.6% airtime utilization with minimal headroom.

56.6 Wi-Fi 6 OFDMA Efficiency Improvement

56.6.1 OFDMA Overview

Wi-Fi 6 divides the 80 MHz channel into smaller Resource Units (RUs) that can be allocated to multiple devices simultaneously:

RU Size Bandwidth Data Subcarriers Typical Use Case
26-tone 2 MHz 24 Ultra-low data rate (sensors)
52-tone 4 MHz 48 Low data rate (IoT devices)
106-tone 8 MHz 102 Medium data rate
242-tone 20 MHz 234 High data rate
484-tone 40 MHz 468 Very high data rate (cameras)
996-tone 80 MHz 980 Maximum throughput

80 MHz channel can be divided into:

  • Up to 37x 26-tone RUs, OR
  • Up to 18x 52-tone RUs, OR
  • Up to 9x 106-tone RUs, OR
  • Mix of different sizes

56.6.2 RU Allocation for Factory Devices

Device Type Data Rate Assigned RU RU Bandwidth Provided Rate Efficiency
Temperature sensors 80 bps 26-tone 2 MHz ~3 Mbps 0.0027%
Vibration sensors 200 kbps 52-tone 4 MHz ~6 Mbps 3.3%
AGV robots 400 kbps 106-tone 8 MHz ~14 Mbps 2.9%
Cameras 2 Mbps 242-tone 20 MHz ~60 Mbps 3.3%
Key Insight

Even the smallest 26-tone RU provides roughly 37,500 times more bandwidth than needed for temperature sensors (3 Mbps vs 80 bps), making OFDMA extremely efficient for low-rate IoT devices.

A temperature sensor needs 80 bps but gets a 26-tone RU providing ~3 Mbps bandwidth. The efficiency ratio is: \(\text{Overkill Factor} = \frac{3,000,000 \text{ bps}}{80 \text{ bps}} = 37,500\). Worked example: A 52-tone RU provides 6 Mbps for a vibration sensor needing 200 kbps: \(\frac{6,000,000}{200,000} = 30\) times more bandwidth than needed. Despite the “waste,” OFDMA is efficient because multiple sensors transmit simultaneously, avoiding the 120+ μs overhead per packet that Wi-Fi 5 CSMA/CA requires.

56.6.3 RU Requirements per AP

80 MHz channel = 9x 106-tone RUs (baseline). Converting all RU sizes to 106-tone equivalent:

RU Size Equivalent Factor Devices per AP Peak Load (30%) RUs Needed
26-tone (temp) 0.24x 15 4.5 active 1.08 RUs
52-tone (vibration) 0.5x 20 6 active 3.0 RUs
106-tone (AGV) 1.0x 5 1.5 active 1.5 RUs
242-tone (camera) 2.3x 10 3 active 6.9 RUs
TOTAL 50 15 active 12.48 RUs

Analysis: 12.48 RUs needed vs 9 RUs available = 1.39x oversubscribed

Note: 30% peak load factor assumes not all devices transmit simultaneously (realistic for IoT workloads with staggered reporting).

56.6.4 OFDMA Airtime Improvement

Wi-Fi 6 OFDMA enables simultaneous transmissions - multiple devices share each transmission opportunity (TXOP). Assuming 4 devices per TXOP scheduled via Target Wake Time:

Device Type Devices TXOPs/sec TX Time Wi-Fi 6 Airtime Wi-Fi 5 Airtime Improvement
Vibration sensors 20 500 170.38 us 8.52% 26.4% 3.1x better
Temperature sensors 15 0.4 170.38 us 0.02% 0.02% Same
Cameras 10 200 170.38 us 3.41% 9.05% 2.7x better
AGV robots 5 200 170.38 us 3.41% 7.11% 2.1x better
TOTAL 50 15.36% 42.58% 2.77x better

56.6.5 OFDMA Transmission Time Breakdown

  • DIFS: 28 us
  • Backoff: 67.5 us
  • Parallel TX (4 devices): 50.88 us (vs 528.88 us sequential in Wi-Fi 5)
  • SIFS + ACK: 24 us
  • Total: 170.38 us per multi-user transmission
Wi-Fi 6 OFDMA Result: 15.4% airtime utilization (vs 42.6% Wi-Fi 5)

Improvement: 2.77x better airtime efficiency

Benefits:

  1. Lower Latency: Less queue delay (15% vs 43% utilization)
  2. Higher Capacity: Can support 2.77x more devices
  3. Better Coexistence: More airtime available for non-IoT traffic (laptops, phones)

56.6.6 Interactive Airtime Comparison

56.7 Wi-Fi 6 TWT (Target Wake Time) Power Savings

56.7.1 TWT Overview

Wi-Fi 6 introduces Target Wake Time (TWT), allowing AP to schedule when devices wake up and transmit. This eliminates:

  • Random backoff contention (saves power waiting for transmission opportunity)
  • Frequent beacon listening (wake only at scheduled time)

56.7.2 Temperature Sensor Power Analysis

Without TWT (Wi-Fi 5):

Device wakes every 10 seconds to transmit 100 bytes. Energy components:

Component Duration Current Energy Notes
Beacon listening 100 ms 100 mA 0.00278 mAh Must maintain association
Channel contention 67.5 us 100 mA 0.0000019 mAh Random backoff
Transmit 4 us 240 mA 0.00000027 mAh 100 bytes @ 200 Mbps
ACK wait 24 us 100 mA 0.00000067 mAh Frame acknowledgment
Sleep 9.9 s 10 uA 0.0000275 mAh Deep sleep mode
Total per cycle 10 s 0.00281 mAh Beacon dominates (99%)

Daily Energy (Without TWT):

  • Cycles per day: 8,640 (every 10 seconds)
  • Daily energy: 0.00281 x 8,640 = 24.28 mAh/day
  • Battery life (CR123A 1500 mAh): 61.8 days

56.7.3 With TWT (Wi-Fi 6)

AP schedules device to wake at exact 10-second intervals. Device wakes, transmits immediately, returns to sleep:

Component Duration Current Energy Notes
Beacon listening 0 0 0 Eliminated - scheduled wake
Channel contention 0 0 0 Eliminated - scheduled TX
Transmit 4 us 240 mA 0.00000027 mAh Same as Wi-Fi 5
ACK wait 24 us 100 mA 0.00000067 mAh Same as Wi-Fi 5
Sleep 10 s 10 uA 0.0000278 mAh Deep sleep mode
Total per cycle 10 s 0.00002874 mAh 97.9x less than Wi-Fi 5
TWT Takeaway for IoT

Target Wake Time (TWT) can let compatible clients sleep longer by aligning wake windows, which can reduce idle listening and contention for scheduled, low-duty-cycle sensors. The actual battery-life impact depends on DTIM/beacon settings, whether the device stays associated, retry rate, and the module’s true sleep current. Treat large “x improvement” claims as workload/device dependent - validate with datasheet currents and a bench measurement.

56.8 Channel Planning and AP Density Recommendation

Treat Wi-Fi 6 planning as a measurement-driven loop rather than a single “coverage radius” calculation:

56.8.1 Planning Process

  1. Define requirements: device count, traffic model (bursty vs periodic), latency/jitter, roaming, and power constraints

  2. Choose band and channel width:

    • Prefer narrower channels when you need many APs and reuse (reduces co-channel contention)
    • Account for regional channel availability and DFS behavior when planning 5 GHz (and 6 GHz if available)

  3. AP density and transmit power:

    • More APs at lower transmit power can improve spatial reuse and reduce contention, but increases deployment complexity

  4. Backhaul strategy:

    • Prefer wired uplinks; if using mesh, minimize wireless hops and avoid sharing client/backhaul radios where possible

  5. Wi-Fi 6 features:

    • OFDMA can help under contention when APs and clients support it
    • TWT can reduce idle listening for scheduled sensors, but savings are workload/device dependent

56.8.2 Validation Checklist

  • Measure airtime utilization, retries, and latency/jitter under realistic load
  • Verify roaming behavior (802.11r/k/v) if devices move
  • Run a pilot, then iterate placement, channel plan, and power settings
Wi-Fi 6 channel planning diagram showing 10,000 square meter factory floor divided into 6 zones, each served by a Wi-Fi 6 AP. APs use non-overlapping 5 GHz channels (36, 44, 52, 60, 100, 108) in a checkerboard pattern to minimize interference. Each zone covers approximately 40x40 meters with 15-20% overlap for seamless roaming.
Figure 56.1: Channel planning for 10,000 m2 factory with 6 Wi-Fi 6 APs using non-overlapping 5 GHz channels in checkerboard pattern.

Scenario: A 40,000-seat stadium needs Wi-Fi for 500 IoT devices (cameras, sensors, digital signage) PLUS spectator access. Peak load: 25,000 concurrent spectator devices during sold-out games.

Challenge: Spectator devices generate 20-50 Mbps each (video streaming, social media uploads), but IoT devices need guaranteed low-latency operation for security cameras and real-time scoreboard updates.

Constraint: Cannot separate IoT onto dedicated APs due to facility layout - IoT cameras mounted on light poles that also serve spectator areas.

Design Goal: Ensure IoT devices maintain <100 ms latency and >99% reliability even when spectators max out bandwidth.

Step 1: Calculate Total Throughput Requirements

Spectators (worst case - halftime):

  • 25,000 devices × 30 Mbps average = 750 Gbps total
  • Distributed across 500 Wi-Fi 6 APs = 1.5 Gbps per AP

IoT Devices (per AP average):

  • 5 security cameras @ 4 Mbps = 20 Mbps
  • 3 temperature sensors @ 100 bps = 300 bps
  • 2 digital signs @ 2 Mbps = 4 Mbps
  • 1 VIP section door controller @ 10 Kbps = 10 Kbps
  • Total IoT per AP: 24 Mbps

Combined per-AP load: 1.5 Gbps (spectators) + 24 Mbps (IoT) = 1.524 Gbps

Wi-Fi 6 AP capacity:

  • Theoretical: 9.6 Gbps (160 MHz, 8 spatial streams)
  • Practical (80 MHz, 4 streams, real-world): 2.4 Gbps
  • Result: 1.524 / 2.4 = 63% utilization → Throughput is manageable

But throughput is NOT the problem…

Step 2: Analyze Airtime Without OFDMA (Wi-Fi 5 Baseline)

Spectator traffic pattern:

  • Small packets (ACKs, pings): 40% of packets
  • Medium packets (web, social): 40% of packets
  • Large packets (video): 20% of packets

IoT traffic pattern:

  • Camera H.264 frames: 1500-byte packets @ 30 fps
  • Sensor reports: 200-byte packets every 5 seconds
  • Door controller: 100-byte packets on events (bursty)

Wi-Fi 5 OFDM (one device transmits at a time):

Average packet transmission time calculation:

Small (100 bytes):  (28 + 67.5 + 27 + 24) µs = 146.5 µs
Medium (500 bytes): (28 + 67.5 + 56 + 24) µs = 175.5 µs
Large (1500 bytes): (28 + 67.5 + 121 + 24) µs = 240.5 µs

Weighted average: 0.4×146.5 + 0.4×175.5 + 0.2×240.5 = 177 µs per packet

Packets per second at 1.5 Gbps spectator load:

1.5 Gbps = 187,500,000 bytes/sec
Average packet size: 600 bytes (mixed traffic)
Packets/sec: 187,500,000 / 600 = 312,500 packets/sec

Airtime calculation:

312,500 packets × 177 µs = 55,312,500 µs/sec = 55.3 seconds per second

Wait, that’s impossible! Correct - this would require 55× more airtime than available. Result: Massive packet loss, >5 second latencies, IoT devices unable to transmit.

The problem is that calculation assumed perfect packing. Real Wi-Fi 5 behavior:

Realistic Wi-Fi 5 at 63% throughput utilization:

  • Airtime utilization: 85-95% (approaches saturation)
  • Queue delays: 200-500 ms for IoT packets waiting for transmission opportunity
  • Collision rate: 15-20% requiring retransmissions
  • IoT latency: Regularly exceeds 1 second → UNACCEPTABLE

Step 3: Wi-Fi 6 OFDMA Solution

Resource Unit (RU) allocation strategy:

Spectator devices (bulk data):

  • Allocate 242-tone RUs (20 MHz slices)
  • 80 MHz channel = 4× 242-tone RUs per TXOP
  • High throughput, tolerates 50-100 ms latency

IoT cameras (priority data):

  • Allocate dedicated 106-tone RUs (8 MHz)
  • Guaranteed low-latency slot every 33 ms (30 fps)
  • Protected from spectator congestion

IoT sensors (small periodic):

  • Share 52-tone RUs (4 MHz)
  • Scheduled via BSS Coloring (multiple sensors transmit simultaneously without collision)

OFDMA transmission example (single TXOP):

One 80 MHz TXOP (50 µs) can now transmit:
- 4 spectator devices (242-tone RUs) = 4 large video packets
- 2 camera frames (106-tone RUs) = 2× 1500-byte packets
- 8 sensor reports (26-tone RUs) = 8× 200-byte packets
Total: 14 devices transmit SIMULTANEOUSLY in same 50 µs

Airtime improvement:

Wi-Fi 5: 14 devices = 14 sequential TXOPs = 14 × 177 µs = 2,478 µs
Wi-Fi 6 OFDMA: 14 devices = 1 parallel TXOP = 170 µs (includes MU overhead)

Efficiency gain: 2,478 / 170 = 14.6× better airtime utilization

Step 4: Target Wake Time (TWT) for Battery Sensors

Non-critical IoT devices (temperature sensors):

Traditional Wi-Fi: Wake every 100 ms to check for beacons (maintain association)

100 ms wake @ 100 mA = 0.00278 mAh per cycle
Idle time: 5 seconds between reports
Wakeups: 50 per reporting cycle
Overhead: 50 × 0.00278 = 0.139 mAh per report (99% of energy!)

Wi-Fi 6 TWT: AP schedules sensor to wake only at report time (every 5 seconds)

Wake only for transmission: 0.00028 mAh per report
Reduction: 0.139 → 0.00028 = 496× improvement
Battery life: 50 days → 68 years (practical limit: 5-10 years from self-discharge)

Step 5: Deployment Results

Metrics after 6-month season:

Metric Target Achieved Wi-Fi 5 Baseline
IoT latency (p95) <100 ms 47 ms 850 ms
IoT reliability >99% 99.7% 94.3%
Camera frame drops <0.1% 0.02% 2.8%
Sensor battery life 2 years 6.5 years (projected) 42 days
Spectator complaints <5% 2.1% 15%

Cost comparison:

Item Wi-Fi 5 Approach Wi-Fi 6 Approach Savings
AP count 800 (separate IoT APs) 500 (shared) $300K
Annual battery replacement $6,000 (quarterly) $450 (every 5 years) $5,550/year
Installation complexity High (dual networks) Low (single network) $50K labor

Key Lessons:

  1. Throughput ≠ capacity - Wi-Fi 5 at 60% throughput was >90% airtime → near collapse
  2. OFDMA enables QoS - Dedicated RUs guarantee IoT latency even under spectator load
  3. TWT transforms battery life - Eliminates 99% of idle power consumption
  4. BSS Coloring reduces collisions - Overlapping APs don’t interfere like Wi-Fi 5
  5. Mixed workloads favor Wi-Fi 6 - The more diverse the devices, the greater the OFDMA advantage

When Wi-Fi 6 is NOT needed:

  • Homogeneous device types (all cameras or all sensors)
  • Low device density (<20 devices per AP)
  • Adequate airtime on Wi-Fi 5 (utilization <40%)
  • Devices already mains-powered (TWT irrelevant)

56.9 Concept Relationships

Understanding how Wi-Fi 6 features relate to high-density deployments:

Concept Depends On Enables Trade-off
OFDMA Wi-Fi 6 AP/client support Parallel transmission Scheduler complexity vs airtime efficiency
Resource Units MCS configuration Bandwidth granularity Small RU overhead vs parallelism
TWT (Target Wake Time) AP scheduling support Predictable sleep Coordination vs beacon elimination
MU-MIMO Multiple spatial streams Simultaneous clients Antenna cost vs capacity
BSS Coloring OBSS detection Spatial reuse Protocol overhead vs interference tolerance

Common Pitfalls

Wi-Fi 6 features (OFDMA, MU-MIMO uplink, TWT) require both AP and client to support 802.11ax. Legacy IoT devices (Wi-Fi 4/5) connected to a Wi-Fi 6 AP receive no OFDMA or TWT benefit. Only the improved scheduling for legacy clients (through better spatial reuse) helps. Full Wi-Fi 6 benefits require upgrading end devices.

Wide channels increase per-client throughput but reduce available non-overlapping channels. A dense IoT deployment with 160 MHz channels in 5 GHz has only 2 non-overlapping channels in many regions, causing massive co-channel interference. Use 20-40 MHz channels for dense deployments to maximize the number of reuse channels.

Wi-Fi 6 OFDMA has two modes: triggered (AP controls resource allocation) and scheduled. For dense IoT deployments, trigger-based OFDMA with the AP polling devices and assigning RUs provides far better efficiency than allowing devices to contend for RUs. Verify your AP enables triggered OFDMA mode.

Enterprise Wi-Fi 6 APs support 8x8 MU-MIMO. But IoT devices typically have 1x1 or 2x2 MIMO at most. MU-MIMO serves multiple single-stream clients simultaneously, so 8 IoT sensors can each receive one spatial stream simultaneously — but only if the AP can separate their signals, which requires sufficient antenna separation and signal diversity.

56.10 Summary

This analysis demonstrated Wi-Fi 6 advantages for high-density IoT deployments:

  • Throughput vs Airtime: Low throughput utilization (3.7%) can mask high airtime utilization (42.6%)
  • OFDMA Efficiency: Parallel transmission reduces airtime utilization from 42.6% to 15.4% (2.77x improvement)
  • Resource Units: Even smallest RUs (26-tone, 2 MHz) provide orders of magnitude more bandwidth than sensors need
  • TWT Power Savings: Eliminating beacon listening can dramatically extend battery life for scheduled sensors
  • Planning Approach: Measurement-driven iteration beats single-pass coverage calculations

56.11 See Also

For deeper exploration of related topics:

56.12 What’s Next

Chapter Focus
Wi-Fi Review: Summary and Visual Gallery Comprehensive chapter summary and visual reference gallery covering all Wi-Fi concepts
Bluetooth Fundamentals Low-power wireless technology for personal area networks and short-range IoT connectivity