49  Wi-Fi: Comprehensive Review

In 60 Seconds

Wi-Fi for IoT is about trade-offs: selecting the right 802.11 standard, frequency band, and power mode determines whether a device lasts days or years. Wi-Fi 6 (802.11ax) introduces Target Wake Time for scheduled sleep and OFDMA for simultaneous small-payload transmission. Channel planning (only 3 non-overlapping 2.4 GHz channels) and WPA3 security are non-negotiable for IoT.

Minimum Viable Understanding

If you take away only three things from this chapter:

  1. Wi-Fi for IoT is about trade-offs, not throughput – selecting the right 802.11 standard (Wi-Fi 4/5/6), frequency band (2.4 GHz vs 5 GHz vs 6 GHz), and power mode (TWT, light sleep, modem sleep) determines whether your IoT device lasts days or years on a battery.
  2. Wi-Fi 6 (802.11ax) is a game-changer for IoT – Target Wake Time (TWT) lets devices negotiate exact wake schedules with the AP, and OFDMA subdivides channels into Resource Units so dozens of small IoT payloads transmit simultaneously without contention overhead.
  3. Channel planning and security are non-negotiable – overlapping channels in the 2.4 GHz band (only 3 non-overlapping: 1, 6, 11) cause hidden-node interference that devastates low-power sensors, and WPA3-Personal with SAE replaces the vulnerable PSK handshake that exposed earlier IoT deployments to offline dictionary attacks.

Hey Sensor Squad! Imagine Sammy, Lila, Max, and Bella are at a huge school party where EVERYONE is trying to talk at once using walkie-talkies!

The Problem: There are only 3 walkie-talkie channels that do not interfere with each other (just like Wi-Fi’s 2.4 GHz channels 1, 6, and 11). If too many kids use the same channel, their voices get all jumbled up and nobody can hear anything!

Sammy’s Discovery: Sammy notices that some kids are SHOUTING entire stories into the walkie-talkie, while sensors like him only need to whisper a tiny temperature reading. “Why do I have to wait for someone to finish their whole story before I can say ‘72 degrees’?” he asks.

Lila’s Smart Solution – “Take Turns Sleeping!” (That is TWT!): Lila figures out a brilliant plan. She tells the teacher (the Access Point): “I only need to talk for 1 second every 5 minutes. Can I nap the rest of the time?” The teacher says YES and gives Lila a schedule card. Now Lila’s walkie-talkie battery lasts ALL WEEK instead of just one day!

Max’s Channel Trick – “Share the Lane!” (That is OFDMA!): Max discovers that one walkie-talkie channel is actually wide enough to carry FOUR tiny whispers at the same time! Instead of one kid talking at a time, Max, Sammy, Bella, and Lila each get a mini-lane. All four send their sensor readings simultaneously – no waiting!

Bella’s Security Rule – “Secret Handshake!” (That is WPA3!): Bella makes everyone do a special secret handshake before joining the channel. Even if a sneaky kid overhears one handshake, they STILL cannot figure out other kids’ secrets. That is way better than the old system where knowing ONE password let you snoop on everyone!

Real-world version: Smart home sensors (thermostats, door locks, cameras) use Wi-Fi 6 with TWT to save battery, OFDMA to share the channel efficiently, and WPA3 to keep your home network secure – even with 50+ devices connected!


The simple explanation: This chapter brings together everything you need to know about using Wi-Fi for IoT projects. Wi-Fi is the same wireless technology your phone uses to connect to the internet, but when IoT devices use it, there are special challenges – mainly around battery life, handling lots of devices, and security.

An analogy: Think of a Wi-Fi network like a busy highway. Regular computers and phones are like cars and trucks that use the highway all day. IoT sensors are like delivery scooters that only need to get on the highway briefly to drop off a small package (a sensor reading). This review teaches you how to design the highway so the scooters can get on and off quickly without wasting fuel.

Why does Wi-Fi matter for IoT? Unlike Zigbee or LoRa, Wi-Fi connects directly to your existing network and the internet – no special gateway needed. This makes it perfect for IoT devices that need higher data rates (like cameras) or that live near a power outlet (like smart plugs).

Key terms to know:

Term Meaning
802.11ax (Wi-Fi 6) The latest Wi-Fi standard, optimized for many simultaneous devices
TWT (Target Wake Time) A Wi-Fi 6 feature that lets devices sleep on a schedule to save battery
OFDMA Divides a Wi-Fi channel into smaller sub-channels so multiple devices transmit at once
WPA3 The newest Wi-Fi security protocol, replacing WPA2
RSSI Received Signal Strength Indicator – how strong the signal is at a device
Channel Planning Assigning non-overlapping channels to avoid interference

Where is Wi-Fi used in IoT? Smart home devices (thermostats, speakers, cameras), industrial monitoring dashboards, point-of-sale systems, asset tracking in warehouses, and any IoT application needing high bandwidth or seamless IP connectivity.


49.1 Wi-Fi IoT Architecture Overview

The following diagram shows how Wi-Fi connects IoT devices from the physical radio layer through to cloud services, highlighting the key protocol layers an IoT architect must understand.

Layered architecture diagram of Wi-Fi for IoT showing five layers from bottom to top. Physical layer with IEEE 802.11 radio operating at 2.4 GHz, 5 GHz, and 6 GHz bands. MAC layer with CSMA/CA channel access, OFDMA resource allocation, and TWT power scheduling. Network layer with IPv4 and IPv6 addressing and DHCP. Transport and application layer with TCP, UDP, MQTT, HTTP, and CoAP protocols. Cloud and edge layer with data ingestion, analytics, and device management services. Arrows show data flowing upward from sensors through each layer to the cloud.

49.2 Wi-Fi Standards Evolution for IoT

Understanding which Wi-Fi generation to choose is critical for IoT. Each generation brought specific improvements relevant to constrained devices.

Timeline diagram showing Wi-Fi standards evolution from Wi-Fi 4 through Wi-Fi 7 with IoT-relevant features. Wi-Fi 4 (802.11n, 2009) introduced MIMO and 2.4 plus 5 GHz dual-band support with up to 600 Mbps. Wi-Fi 5 (802.11ac, 2014) added wider 80 and 160 MHz channels, MU-MIMO downlink, and up to 3.5 Gbps. Wi-Fi 6 (802.11ax, 2020) introduced OFDMA for multi-user uplink, TWT for power savings, BSS Coloring for interference management, and up to 9.6 Gbps. Wi-Fi 6E (2021) extended Wi-Fi 6 into the 6 GHz band with 1200 MHz of new spectrum. Wi-Fi 7 (802.11be, 2024) added Multi-Link Operation, 320 MHz channels, and 4096-QAM for up to 46 Gbps. The IoT sweet spot is highlighted at Wi-Fi 6 and Wi-Fi 6E.

49.3 Wi-Fi 6 IoT Power Management with TWT

Target Wake Time (TWT) is the single most important Wi-Fi 6 feature for battery-powered IoT. This diagram shows how a TWT session works between an IoT device and the Access Point.

Sequence diagram showing the Target Wake Time (TWT) negotiation and operation between an IoT sensor device and a Wi-Fi 6 Access Point. Step 1: the device sends a TWT Request frame specifying a wake interval of 300 seconds and a wake duration of 10 milliseconds. Step 2: the AP responds with a TWT Response accepting the schedule. Step 3: the device enters deep sleep for 300 seconds consuming only 10 microamps. Step 4: the device wakes at the scheduled TWT Service Period, transmits a 50-byte sensor reading in 2 milliseconds, and receives an acknowledgment. Step 5: the device returns to deep sleep for another 300 seconds. The cycle repeats, achieving over 99 percent sleep time and dramatically extending battery life compared to legacy power save mode.

49.4 OFDMA Resource Allocation for IoT

OFDMA allows the Access Point to subdivide a channel into smaller Resource Units (RUs), enabling multiple IoT devices to transmit simultaneously within a single OFDM symbol period.

Diagram showing OFDMA resource allocation in a 20 MHz Wi-Fi 6 channel. The channel is divided into Resource Units of different sizes: one 106-tone RU allocated to a security camera sending video at 20 Mbps, one 52-tone RU allocated to a smart thermostat sending a 100-byte status update, one 26-tone RU allocated to a door sensor sending a 20-byte alert, and another 26-tone RU allocated to a motion sensor sending a 15-byte detection event. All four devices transmit simultaneously in the same time slot, compared to legacy Wi-Fi where each device would contend separately and wait its turn, wasting airtime for small IoT payloads.

49.5 Wi-Fi Frequency Band Decision Framework

Choosing the right frequency band is one of the most consequential decisions in Wi-Fi IoT deployment. This decision tree helps you select the optimal band.

Decision tree flowchart for selecting Wi-Fi frequency band for IoT deployments. Start with the question: Does the device need to penetrate walls or operate at long range? If yes, choose 2.4 GHz band offering 3 non-overlapping channels, maximum 150 meter indoor range, and best wall penetration but with crowded spectrum and microwave interference risk. If no, ask: Does the deployment have more than 50 devices per AP? If yes, consider Wi-Fi 6E at 6 GHz with 59 non-overlapping 20 MHz channels and minimal interference but requiring line-of-sight and newer hardware. If no, choose 5 GHz offering 25 non-overlapping 20 MHz channels, good throughput, moderate range, and less interference than 2.4 GHz. Each path shows data rate, range, and interference characteristics.


Chapter Organization

This comprehensive Wi-Fi review has been organized into focused sections for better navigation:

49.5.1 Chapter Sections

  1. Introduction - Learning objectives, prerequisites, key concepts, and interactive visualizations
  2. Knowledge Checks - Scenario-based quiz questions testing Wi-Fi deployment, channel selection, and power optimization
  3. Wi-Fi 6 Features - In-depth exploration of Target Wake Time (TWT), OFDMA, BSS Coloring, and advanced IoT capabilities
  4. Summary and Visual Gallery - Comprehensive chapter summary, visual reference gallery, and final assessment

49.5.2 Case Study Deep Dives

  1. Channel Selection Analysis - Site survey interpretation, path loss calculations, band selection, and battery life estimation
  2. Power Optimization - Energy budgeting, optimization strategies, anti-patterns, and Wi-Fi vs LoRaWAN comparison
  3. Wi-Fi 6 High-Density - Throughput vs airtime analysis, OFDMA resource allocation, TWT savings, channel planning

49.7 Prerequisites

Before starting this comprehensive review, ensure you have completed:

49.8 Learning Objectives

By completing this comprehensive review, you will be able to:

  • Trace the evolution from Wi-Fi 4 through Wi-Fi 7 and classify each generation’s IoT-relevant features
  • Evaluate 2.4 GHz vs 5 GHz vs 6 GHz frequency band trade-offs and justify a band selection for a given IoT deployment scenario
  • Apply Wi-Fi 6 TWT and OFDMA mechanisms to design efficient communication schedules for battery-powered IoT devices
  • Implement WPA3-Personal with SAE and defend the choice over WPA2-PSK for IoT-only SSIDs
  • Construct a channel allocation plan using only non-overlapping channels (1, 6, 11) and predict interference outcomes when overlapping channels are used
  • Calculate average current draw and battery life for a Wi-Fi IoT device using TWT sleep scheduling

49.9 What This Review Covers

This comprehensive review synthesizes Wi-Fi knowledge for IoT applications through:

  • Interactive Visualizations: Mermaid diagrams showing network architecture, protocol stacks, and Wi-Fi 6 features
  • Scenario-Based Questions: Real-world deployment challenges testing channel selection, power optimization, and security
  • Wi-Fi 6 Analysis: Detailed exploration of game-changing IoT features (TWT, OFDMA, BSS Coloring)
  • Visual Gallery: AI-generated figures summarizing key Wi-Fi concepts
  • Inline Knowledge Checks: 12+ interactive assessments throughout the chapter

49.10 Worked Example: Wi-Fi IoT Power Budget Calculation

Worked Example: Estimating Battery Life for a Wi-Fi 6 Temperature Sensor

Scenario: You are deploying a battery-powered Wi-Fi 6 temperature sensor in a warehouse. The sensor must report every 5 minutes (300 seconds) and run on a 3000 mAh coin cell battery. The sensor uses an ESP32-C6 with Wi-Fi 6 support.

Given:

  • Battery capacity: 3000 mAh at 3.3V
  • TWT wake interval: 300 seconds (5 minutes)
  • Active transmit current: 240 mA for 15 ms (association + data TX + ACK)
  • Active receive current: 100 mA for 5 ms (waiting for ACK)
  • Deep sleep current: 5 uA
  • Sensor reading current: 2 mA for 10 ms

Step 1 – Calculate charge consumed per wake cycle:

  • Transmit: 240 mA x 15 ms = 240 mA x 0.015 s = 3.6 mAs = 0.001 mAh
  • Receive: 100 mA x 5 ms = 100 mA x 0.005 s = 0.5 mAs = 0.000139 mAh
  • Sensor read: 2 mA x 10 ms = 2 mA x 0.01 s = 0.02 mAs = 0.0000056 mAh
  • Total active per cycle: 4.12 mAs = 0.00114 mAh

Step 2 – Calculate charge consumed during sleep:

  • Sleep duration: 300 s - 0.030 s (active) = 299.97 s
  • Sleep charge: 5 uA x 299.97 s = 0.005 mA x 299.97 s = 1.5 mAs = 0.000417 mAh

Step 3 – Calculate total charge per cycle:

  • Per cycle: 0.00114 + 0.000417 = 0.001557 mAh

Step 4 – Calculate average current:

  • Average current: 0.001557 mAh / (300s / 3600s) = 0.001557 / 0.0833 = 0.0187 mA = 18.7 uA

Step 5 – Calculate battery life:

  • Battery life: 3000 mAh / 0.0187 mA = 160,428 hours = 18.3 years (theoretical)
  • With 70% battery efficiency: 160,428 x 0.70 = 112,300 hours = 12.8 years

Key Insight: Wi-Fi 6 TWT makes battery-powered Wi-Fi feasible for the first time. Without TWT, the device would need to wake for every DTIM beacon (typically every 300 ms), consuming approximately 0.5 mA average – reducing battery life to about 250 days. TWT provides a 19x improvement in battery life for this scenario.

Practical caveat: Real-world Wi-Fi reconnection after deep sleep may take 50-200 ms (not just 15 ms) due to scanning, authentication, and reassociation. Always measure actual current profiles with an oscilloscope or power analyzer before finalizing battery sizing.


Common Pitfalls in Wi-Fi IoT Deployments

Pitfall 1 – Using 2.4 GHz Channel 4 (or any overlapping channel): The 2.4 GHz band has only 3 non-overlapping channels: 1, 6, and 11. Deploying APs on channels 2-5 or 7-10 causes partial overlap with adjacent channels, which is WORSE than full co-channel interference because the CSMA/CA mechanism cannot detect partially overlapping transmissions. Devices on channel 3 will not defer to transmissions on channel 1 (they cannot hear them cleanly), but the signals still interfere at the receiver. Always use only channels 1, 6, and 11 in 2.4 GHz deployments.

Pitfall 2 – Assuming Wi-Fi Range Equals Throughput Range: A Wi-Fi signal may be detectable (RSSI > -90 dBm) at 50 meters, but the usable data rate at that distance could be as low as 1 Mbps with 30%+ packet loss. IoT devices that rely on successful packet delivery should target RSSI > -67 dBm for reliable operation. Design for coverage at -67 dBm, not at the theoretical maximum range. A site survey with actual measurements is essential.

Pitfall 3 – Disabling DTIM or Setting Overly Long DTIM Intervals: Setting the DTIM interval too high (e.g., DTIM=10 with 100 ms beacon interval = 1 second) saves power but causes multicast/broadcast frames (including ARP and DHCP) to be delayed. IoT devices may fail to renew DHCP leases or respond to mDNS discovery. Keep DTIM at 1-3 for IoT networks, and use TWT instead for power savings.

Pitfall 4 – Neglecting WPA3 Transition Mode Security: When deploying WPA3, many administrators enable “WPA3 Transition Mode” (WPA2/WPA3 mixed) for backward compatibility. This allows downgrade attacks where an attacker forces devices to connect using WPA2-PSK, defeating the security improvements of SAE. For IoT-only SSIDs where all devices support WPA3, use WPA3-only mode.

Pitfall 5 – Overloading a Single AP with Too Many IoT Devices: Even though a Wi-Fi 6 AP can theoretically associate 200+ clients, the management frame overhead (beacons, probe responses, authentication) grows linearly with client count. Beyond 75-100 devices per AP, the management overhead can consume 15-20% of airtime. Use dedicated IoT SSIDs with lower beacon rates and consider multiple APs with lower transmit power for high-density IoT.


49.11 Knowledge Check: Wi-Fi IoT Fundamentals


OFDMA resource allocation math

A 20 MHz Wi-Fi 6 channel has 234 usable subcarriers. The smallest Resource Unit (RU) is 26 tones.

Simultaneous devices: \(\lfloor 234 / 26 \rfloor = 9\) devices can transmit in parallel

Each 26-tone RU delivers: - Data subcarriers: 24 (2 are pilots) - Bit rate at MCS 7 (64-QAM, rate 5/6): \(24 × 6 \text{ bits/symbol} × (5/6) \times 250k \text{ symbols/s} = 6\) Mbps

For 40-byte IoT packets: \(40 × 8 = 320\) bits at 6 Mbps = 53 μs transmission time

Efficiency gain vs Wi-Fi 5 sequential: - Wi-Fi 5: 9 sensors × 53 μs + CSMA overhead = ~800 μs total - Wi-Fi 6: All 9 sensors in one 53 μs slot = 15× faster for small IoT payloads

This is why OFDMA is transformative for sensor networks: the contention overhead elimination, not just the raw throughput.

Scenario: A factory floor deploys 80 vibration sensors monitoring motor health. Each sensor sends a 40-byte status packet every second. The existing Wi-Fi 5 (802.11ac) AP experiences 35% packet loss during peak hours due to airtime contention. Can Wi-Fi 6 OFDMA solve this?

Given:

  • 80 sensors, each transmitting 40 bytes every 1 second
  • Wi-Fi 5 AP: 20 MHz channel, OFDM (sequential transmission)
  • Wi-Fi 6 AP candidate: 20 MHz channel, OFDMA (parallel transmission)
  • 802.11 MAC overhead: 34 bytes (header) + 20 bytes (ACK + SIFS + DIFS) = 54 bytes
  • PHY rate: 52 Mbps (MCS 7, 20 MHz, 1 spatial stream)
  • OFDM symbol duration: 4 µs

Step 1: Calculate Wi-Fi 5 Sequential Airtime

Each sensor transmits independently, requiring full MAC overhead:

  • Frame size: 40 bytes (payload) + 34 bytes (header) = 74 bytes
  • ACK + interframe spacing: 20 bytes equivalent
  • Total per transmission: 94 bytes = 752 bits
  • Transmission time: 752 bits ÷ 52 Mbps = 14.5 µs per sensor
  • 80 sensors: 14.5 µs × 80 = 1,160 µs (1.16 ms) per cycle
  • Per second: 1.16 ms = 11.6% airtime utilization

But this assumes zero collisions. With 80 contending devices: - CSMA/CA backoff overhead: ~40% additional airtime - Actual utilization: 11.6% × 1.4 = 16.2% airtime

Step 2: Add Collision Impact

With 80 devices and 1-second intervals: - Average collision probability (simplified): 1 - (1 - 1/1000)^80 ≈ 7.7% per slot - Collisions require retransmissions (exponential backoff) - Effective airtime with retransmissions: 16.2% × 1.15 = 18.6% airtime

Step 3: Calculate Wi-Fi 6 OFDMA Parallel Airtime

OFDMA divides the 20 MHz channel into Resource Units (RUs): - 20 MHz = 234 usable subcarriers (52 data + 4 pilot per OFDM symbol) - Smallest RU: 26 tones (24 data + 2 pilot subcarriers) - Available RUs: 234 ÷ 26 = 9 RUs (can serve 9 sensors simultaneously)

Per OFDMA transmission: - 9 sensors transmit in parallel using 26-tone RUs - Payload per RU: 40 bytes = 320 bits - MCS 7 (26-tone RU): ~6 Mbps effective - Transmission time: 320 bits ÷ 6 Mbps = 53.3 µs for 9 sensors - Multi-user ACK (Block ACK): 60 µs - Total per batch: 53.3 + 60 = 113.3 µs for 9 sensors

For 80 sensors: - Batches needed: 80 ÷ 9 = 8.89 → 9 batches - Total time: 113.3 µs × 9 = 1,020 µs (1.02 ms) per cycle - Per second: 1.02 ms = 10.2% airtime utilization

Step 4: Calculate Efficiency Gain

Metric Wi-Fi 5 (OFDM) Wi-Fi 6 (OFDMA) Improvement
Airtime per cycle 1.16 ms (ideal) 1.02 ms 12% reduction
Airtime with overhead 1.86 ms (realistic) 1.02 ms 45% reduction
Collision rate 7.7% (80 contending) <1% (9 at a time) 8x reduction
Effective capacity 53 sensors (before 35% loss) 95+ sensors (headroom for 2x growth) 1.8x increase

Step 5: Real-World Validation

After deploying Wi-Fi 6 AP with OFDMA: - Packet loss: 35% → 2% (within acceptable range) - Latency: 85 ms avg → 22 ms avg (4x improvement due to reduced queueing) - Jitter: ±45 ms → ±8 ms (predictable scheduling) - Battery life: +18% (fewer retransmissions = less TX energy)

Key Insight: OFDMA’s efficiency gain comes from eliminating CSMA/CA contention overhead for small IoT packets. Wi-Fi 5 forces 80 devices to compete for channel access using random backoff, wasting airtime on collisions and retries. Wi-Fi 6 OFDMA batches 9 devices per transmission, reducing contention domain from 80 → 9 and cutting collision probability by 8x. The real-world benefit is not just 12% faster transmission, but 45% lower airtime due to eliminated backoff overhead. For IoT with 100+ small-payload devices, OFDMA can provide 2-3x capacity increase over Wi-Fi 5 on the same spectrum.

Design Rule: OFDMA benefits scale with device count and inversely with packet size. For 10 devices sending 1 KB payloads, the gain is minimal. For 100 devices sending 50-byte payloads, OFDMA can double effective capacity.

How It Works: Wi-Fi IoT Stack

Wi-Fi for IoT operates across multiple layers. At the Physical (PHY) layer, radio signals are modulated using OFDM at 2.4, 5, or 6 GHz bands. The MAC layer implements CSMA/CA to coordinate channel access - devices sense if the channel is busy before transmitting to avoid collisions.

For power management, Wi-Fi 6 Target Wake Time (TWT) allows IoT devices to negotiate specific wake schedules with the Access Point. A sensor can tell the AP “I’ll wake up every 5 minutes for 10 milliseconds,” then enter deep sleep the rest of the time. This achieves 99.9%+ sleep ratios.

OFDMA subdivides the channel into smaller Resource Units (RUs). Instead of sequential transmission where 80 sensors wait their turn, the AP allocates 9 simultaneous 26-tone RUs so multiple sensors transmit in parallel - dramatically reducing contention overhead.

WPA3 security uses SAE (Simultaneous Authentication of Equals) with ephemeral Diffie-Hellman key exchange. Even if an attacker captures the authentication handshake and later learns the password, they cannot decrypt past traffic because each session uses unique keys derived from random nonces.

Goal: Measure actual ESP32 Wi-Fi power consumption to understand the impact of sleep modes.

Materials Needed:

  • ESP32 development board
  • USB power analyzer or multimeter with current measurement
  • Arduino IDE with ESP32 board support

Exercise Steps:

  1. Baseline Measurement - Upload a sketch that connects to Wi-Fi and stays awake continuously. Measure average current (typically 80-120 mA active).

  2. Add Deep Sleep - Modify the sketch to enter deep sleep for 10 seconds between Wi-Fi transmissions:

    esp_sleep_enable_timer_wakeup(10 * 1000000);  // 10 seconds
    esp_deep_sleep_start();

    Measure average current (should drop to 5-10 mA average).

  3. Optimize Connection - Use WiFi.persistent(false) and WiFi.setAutoReconnect(true) to reduce reconnection overhead. Measure the time from wake to successful transmission (target < 100 ms).

  4. Calculate Battery Life - For a 3000 mAh battery at 3.3V:

    • Continuous mode: 3000 mAh / 100 mA = 30 hours
    • Deep sleep mode: 3000 mAh / 10 mA = 300 hours (12.5 days)
    • With TWT (if available): 3000 mAh / 0.02 mA = 150,000 hours (6 years theoretical)

Expected Observations:

  • Deep sleep reduces average current by 10-20x
  • Reconnection after deep sleep takes 50-200 ms
  • Battery life improvement matches sleep ratio (time asleep / total time)

Extension: Implement “connection reuse” where the device stays connected for multiple transmissions before sleeping, trading power for reduced latency.

49.12 Enhanced Summary: Wi-Fi for IoT – Key Takeaways

49.12.1 Core Concepts

Concept Key Takeaway IoT Impact
Wi-Fi 6 (802.11ax) OFDMA + TWT + BSS Coloring Enables battery-powered Wi-Fi IoT for the first time
TWT (Target Wake Time) Devices negotiate exact wake schedules 10-20x battery life improvement over legacy power save
OFDMA Channel subdivided into Resource Units Multiple small IoT payloads transmit simultaneously
Frequency Bands 2.4 GHz (range) vs 5 GHz (capacity) vs 6 GHz (density) Band choice determines range, interference, and device count
Channel Planning Only 1, 6, 11 in 2.4 GHz; 25+ in 5 GHz Prevents partial-overlap interference that breaks CSMA/CA
WPA3 (SAE) Replaces vulnerable PSK handshake Prevents offline dictionary attacks on IoT credentials
RSSI Threshold Target > -67 dBm for reliable operation Determines AP placement density and coverage design
Power Modes Deep sleep (5-10 uA) vs active TX (200-350 mA) Sleep ratio determines battery life; TWT maximizes sleep

49.12.2 Decision Quick Reference

  • Need IP connectivity and high bandwidth? – Wi-Fi is the right choice
  • Battery-powered with small payloads? – Use Wi-Fi 6 with TWT, or consider BLE/Zigbee/LoRa
  • Dense deployment (50+ devices)? – Wi-Fi 6 with OFDMA on 5 GHz or 6 GHz
  • Security-critical? – WPA3-only mode (no Transition Mode)
  • Range through walls? – 2.4 GHz band, but plan for only 3 channels
  • High data rate (video/audio)? – 5 GHz with wide channels (80/160 MHz)

49.12.3 What to Review Next

  1. Introduction Section – Deep dive into 802.11 architecture and protocol stack
  2. Knowledge Checks – Test yourself with scenario-based questions
  3. Wi-Fi 6 Features – Detailed TWT, OFDMA, and BSS Coloring analysis
  4. Channel Selection Case Study – Work through path loss and RSSI calculations
  5. Power Optimization Case Study – Energy budgeting with real numbers

49.14 What’s Next

If you want to… Read this
Review Wi-Fi 6 features specifically Wi-Fi 6 Features
Study Wi-Fi review summary Wi-Fi Review Summary
Practice implementation labs Wi-Fi Hands-On Labs and Exercises
Learn Wi-Fi power optimization Wi-Fi Power Optimization
Explore Wi-Fi channel analysis Wi-Fi Channel Analysis