35 Wi-Fi Access: Standards and Link Budget
35.1 Overview
This first route develops Wi-Fi standards, band choices, link margins, and device power constraints.
This is part 1 of 2. Continue with Wi-Fi Access: Scanning and Deployment for the second focused route.
35.4 Prerequisites
Before diving into this chapter, you should be familiar with:
- Network Access and Physical Layer Overview: Understanding the role of physical and network access layers
- Wired Network Access: Ethernet: Comparing wired vs wireless connectivity options
Wi-Fi is how devices connect to the internet wirelessly - like invisible cables made of radio waves! When your phone connects to your home router without a cable, that’s Wi-Fi.
Wi-Fi uses radio frequencies (like a radio station) to send data through the air. The 2.4 GHz frequency travels farther through walls but is slower and more crowded. The 5 GHz frequency is faster but doesn’t travel as far.
| Term | Simple Explanation |
|---|---|
| Wi-Fi | Wireless connection using radio waves (no cables needed) |
| Access Point (AP) | The device that creates the Wi-Fi network (often built into router) |
| 2.4 GHz | Radio frequency that travels far but is slow and crowded |
| 5 GHz | Radio frequency that’s fast but doesn’t go through walls well |
| SSID | The name of a Wi-Fi network (like “Home_WiFi”) |
| RSSI | Signal strength - how strong the Wi-Fi signal is |
“Wi-Fi keeps getting faster and smarter!” said the microcontroller. “The original 802.11b from 1999 was only 11 Mbps. Now Wi-Fi 6 can do over 9 Gbps — that is nearly 900 times faster!”
“But speed is not the only improvement for IoT,” noted Temperature Terry. “Wi-Fi 6 has two features I love. First, OFDMA lets the router talk to many devices at the same time instead of one at a time. With hundreds of IoT devices in a smart building, that is essential.”
“Second is Target Wake Time,” added the battery with a smile. “TWT lets me negotiate a sleeping schedule with the access point. I tell it ‘wake me up in 4 hours,’ and I sleep the whole time. Before TWT, Wi-Fi devices had to wake up constantly to check for messages. TWT makes Wi-Fi actually practical for battery-powered sensors!”
the LED brought up the frequency choice. “2.4 GHz goes through walls better but is crowded — every microwave, baby monitor, and Bluetooth device uses it. 5 GHz is faster and less crowded, but does not travel as far. And Wi-Fi HaLow at sub-1 GHz can reach a whole kilometer — perfect for outdoor IoT!”
35.5 IEEE 802.11 Wi-Fi Overview
Start with the standards history, because each generation solves a different design problem.
IEEE 802.11, commonly known as Wi-Fi, is a protocol replacing wired Ethernet for wireless communications. It uses the unlicensed radio band for data transmission.
In a Wi-Fi network, the Wireless Access Point (WAP) is responsible for translating digital signals from the wired network to radio signals, and vice versa, for communications between mobile devices in the WAP range and the Internet.
Inspect Figure 35.1 before this decision: Wi-Fi Evolution from 802.11 to Wi-Fi 7 must be judged beside 802.11b/g. Together Wi-Fi Evolution from 802.11 to Wi-Fi 7 and 802.11b/g bound this claim.
Wi-Fi Evolution from 802.11 to Wi-Fi 7 begins the diagram in Figure 35.1; locate Wi-Fi Evolution from 802.11 to Wi-Fi 7, compare 802.11b/g, and verify 2.4 GHz. Wi-Fi Evolution from 802.11 to Wi-Fi 7 states the starting condition; 802.11b/g supplies its counterpart; 2.4 GHz limits the conclusion; retain its labelled boundary.
Compare that 2.4 GHz starting point with the later HaLow, OFDMA, and Target Wake Time milestones before choosing a generation for an IoT workload.
35.6 Wi-Fi Protocol Comparison
| Standard | Year | Frequency | Max Speed | Range | IoT Suitability |
|---|---|---|---|---|---|
| 802.11b | 1999 | 2.4 GHz | 11 Mbps | ~100m | Low (legacy) |
| 802.11g | 2003 | 2.4 GHz | 54 Mbps | ~100m | Medium |
| 802.11n | 2009 | 2.4/5 GHz | 600 Mbps | ~200m | Good |
| 802.11ac | 2013 | 5 GHz | 3.5 Gbps | ~100m | Good (high bandwidth) |
| 802.11ah | 2016 | Sub-1 GHz | 347 Mbps | ~1 km | Excellent (low power) |
| 802.11ax | 2021 | 2.4/5 GHz | 9.6 Gbps | ~200m | Excellent (dense) |
35.7 IoT-Specific Wi-Fi Standards
The 802.11ah (Wi-Fi HaLow) and 802.11ax (Wi-Fi 6) protocols specifically address shortcomings in IoT-constrained environments.
35.7.1 802.11ah (Wi-Fi HaLow)
Before 802.11ah (wi-fi halow), inspect Figure 35.2: Wi-Fi HaLow Features for IoT must be considered with Sub-GHz. That visual pairing grounds wi-fi halow features and iot applications in named evidence.
At Wi-Fi HaLow Features for IoT in Figure 35.2, compare the diagram with Sub-GHz; then locate better wall penetration. That labelled check bounds wi-fi halow features and iot applications. For 802.11ah (wi-fi halow), retain better wall penetration as evidence for the resulting choice.
The same record must verify the labelled one-kilometre range and 8,191-device ceiling against the deployment’s actual link and capacity budgets.
Key Features:
- Operates in sub-1 GHz frequency bands (better penetration through walls and obstacles)
- Longer range (up to 1 km vs 100m for traditional Wi-Fi)
- Lower power consumption (suitable for battery devices)
- Supports large number of devices (up to 8,191 per access point)
- Use cases: Smart city sensors, agricultural monitoring, industrial IoT
35.7.2 802.11ax (Wi-Fi 6)
Figure 35.3 makes 802.11ax (wi-fi 6) inspectable through Wi-Fi 6 Features and IoT Applications and OFDMA. Those diagram labels establish the scope of wi-fi 6 features and iot applications.
Use OFDMA to test Wi-Fi 6 Features and IoT Applications in the diagram at Figure 35.3. Then inspect serves many small devices as the final qualifier on wi-fi 6 features and iot applications. That sequence keeps 802.11ax (wi-fi 6) tied to what is visibly labelled.
Check OFDMA resource units alongside the Target Wake Time schedule; neither the stated power reduction nor latency follows from the Wi-Fi 6 label alone.
Key Features:
- OFDMA (Orthogonal Frequency Division Multiple Access) for better multi-device handling
- Target Wake Time (TWT) for power savings - devices sleep longer, wake only when needed
- Higher capacity in dense environments (stadiums, offices, warehouses)
- Lower latency (8 ms typical vs 30 ms for Wi-Fi 5)
- Use cases: Smart buildings, dense sensor deployments, industrial automation
Core Concept: TWT allows IoT devices to negotiate specific wake-up times with the access point, sleeping for extended periods rather than constantly listening for beacons - reducing power consumption by up to 90% for infrequent data transmission.
Why It Matters: Traditional Wi-Fi devices wake every 100 ms to check for data, consuming significant power even when idle. TWT lets a sensor wake once per minute (or less), dramatically extending battery life from days to months.
Key Takeaway: When deploying battery-powered Wi-Fi sensors, require Wi-Fi 6 (802.11ax) support to leverage TWT. Configure appropriate wake intervals based on data reporting frequency - a sensor reporting hourly can sleep for 59 minutes between transmissions.
Checkpoint: Standards and IoT Fit
You now know:
- Wi-Fi spans from 802.11b at 11 Mbps to Wi-Fi 6 at 9.6 Gbps and beyond.
- HaLow trades speed for sub-1 GHz coverage, 1 km range, and up to 8,191 devices per AP.
- Wi-Fi 6 adds OFDMA and TWT, which matter more to dense IoT fleets than headline speed alone.
35.8 Frequency Band Trade-offs
Option A (2.4 GHz):
- Range: 100-150m indoor
- Channels: 3 non-overlapping (1, 6, 11)
- Interference: Crowded spectrum with Bluetooth/Zigbee/microwave
- Wall penetration: -4 dB per drywall, -6 dB per concrete
- Max 802.11n: 150 Mbps
Option B (5 GHz):
- Range: 50-75m indoor
- Channels: up to 24 non-overlapping (region-dependent)
- Interference: Less interference from IoT devices
- Wall penetration: -5 dB per drywall, -12 dB per concrete
- Max 802.11ac: 1.3 Gbps
Decision Factors: Choose 2.4 GHz for IoT gateways requiring maximum range through walls, legacy device compatibility, or outdoor deployments. Choose 5 GHz for high-bandwidth applications (video cameras, AR/VR), dense urban environments with heavy 2.4 GHz congestion, or when gateway and devices are in the same room with minimal obstacles.
Walls are not the only obstacle worth budgeting for. Water absorbs 2.4 GHz strongly enough to matter for IoT placement: a straight path through pure water loses most of its usable signal within roughly 8 km, through ordinary drinking water within about 45 m, but through sea water in under a centimeter. Human tissue behaves close to sea water for this purpose, with higher body-fat content absorbing somewhat more, which is one reason a cell that measures strong on an empty test bench can degrade once a room fills with people. A gateway mounted near an aquarium, a water tank, or dense plumbing needs its own site survey rather than trusting the drywall numbers above, and foliage or rain add a comparable penalty outdoors.
The band choice narrows the problem; modulation margin decides whether that choice remains reliable when the air gets busy.
35.9 Select Wi-Fi Modulation
Scenario: Designing a Wi-Fi-connected IoT gateway that aggregates data from 50 BLE sensors. The gateway sends 10 kB data bursts to the cloud every 30 seconds. Building has 8 competing Wi-Fi networks causing channel congestion.
Given:
- Data requirement: 10 kB every 30 seconds = 2.73 kbps average
- Wi-Fi options: 802.11b/g/n/ac at various modulation schemes
- Interference: 8 neighboring networks on overlapping channels
- Power: Mains-powered (no battery constraint)
- Distance to AP: 25 meters through 2 drywall partitions
Steps:
-
Calculate minimum required data rate:
- 10 kB x 1024 x 8 = 81,920 bits per burst
- At 1 Mbps: ~82 ms transmission time
- At 54 Mbps: ~1.5 ms transmission time
- Faster = less airtime = less collision probability
-
Evaluate modulation schemes by robustness:
Modulation Protocol Max Rate Min SNR Required Range BPSK 1/2 802.11a/g 6 Mbps 4 dB Excellent QPSK 1/2 802.11a/g 12 Mbps 7 dB Very Good 16-QAM 1/2 802.11a/g 24 Mbps 12 dB Good 64-QAM 3/4 802.11a/g 54 Mbps 25 dB Fair 256-QAM 5/6 802.11ac 400+ Mbps 32 dB Poor -
Estimate link quality:
- TX power: 20 dBm
- Path loss: free space at 25 m is 68 dB, plus 2 interior walls at 4 dB each = 76 dB
- Received power: 20 - 76 = -56 dBm
- Noise floor: -95 dBm
- SNR: -56 - (-95) = 39 dB (very good)
-
Select appropriate MCS (Modulation and Coding Scheme):
- With 39 dB SNR, 256-QAM (32 dB) is theoretically possible
- However, interference from 8 networks fluctuates the SNR; budget a 10 dB swing (the margin rule below)
- Worst-case SNR: 39 - 10 = 29 dB
- Select 64-QAM 3/4 (requires 25 dB SNR) — 4 dB of margin even in the worst case. Note how close this is: budgeting a 15 dB swing instead would push the safe choice down to 16-QAM 1/2. Margins, not peak SNR, decide the MCS.
Result: Configure the gateway for 802.11n with MCS 7 (64-QAM, 72.2 Mbps). This provides 4 dB margin above minimum SNR in worst-case interference, ensures sub-2 ms burst transmission to minimize collision window, and far exceeds the 2.73 kbps requirement.
Key Insight: For IoT gateways in congested Wi-Fi environments, do NOT select the highest modulation scheme your SNR supports. Leave 5-10 dB margin for interference variability. A reliable 54 Mbps link beats an intermittent 300 Mbps link for IoT applications.
Wi-Fi link budget calculations determine the achievable data rate and modulation scheme based on signal strength and noise. For the IoT gateway scenario with interfering networks:
Received signal strength (RSS):
Signal-to-noise ratio (SNR):
SNR with interference:
Selecting modulation and coding scheme (MCS) requires margin:
This selects 64-QAM with rate 3/4 coding (MCS 7), providing 4 dB fade margin. Using 256-QAM (requires 32 dB SNR) would fall short by 3 dB, causing frequent link failures during interference spikes.
Transmission time for 10 kB burst at 72.2 Mbps:
Sub-2 ms transmission minimizes collision probability in the congested 2.4 GHz band.
Checkpoint: Band and Link Margin
You now know:
- 2.4 GHz offers about 100-150 m indoor reach but only three non-overlapping channels.
- The gateway example starts with 20 dBm transmit power, 25 m distance, two drywall partitions, and 8 competing networks.
- Margin changes the MCS decision: 64-QAM 3/4 works with a 25 dB gate only if interference still leaves enough SNR headroom.
35.10 Continue to Part 2
Continue with Wi-Fi Access: Scanning and Deployment.
