WiFi & Mobile Networks · Study deck
Wi-Fi Bands: Channels, DFS, and 6 GHz
More channels do not remove local rules or radar events.
Radio Remi is your guide for this deck.
After studying this chapter
Learning objectives
You will be able to:
- Explain: If you only need the intuition, this layer is enough: use Wi-Fi when the device requirement benefits from IP connectivity and the installed network, power source, security model, and support workflow can be proven.
- Explain: The review should not stop at "connected." It should record the AP owner, network policy, local API boundary, command authorization, reconnection behavior, and retest trigger for AP replacement, firmware update, credential rotation, or enclosure change.
- Explain: The best width is the narrowest one that meets the service objective while leaving enough clean reuse for the installed cell pattern.
Major section
Three Bands, Many Channels, Several Widths
Wi-Fi operates across three unlicensed bands, and each behaves differently for IoT.
- 2.4 GHz reaches farthest and penetrates walls best but is crowded and offers only three non-overlapping 20 MHz channels (1, 6, 11).
- 5 GHz has far more channels and less congestion but shorter range.
Major section
Three Bands, Many Channels, Several Widths (continued)
A 5 GHz plan may be better for powered tools or cameras because it offers more reuse options, yet final mounting points and DFS recovery still need proof.
- 6 GHz (Wi-Fi 6E/7) adds ~1200 MHz of clean spectrum with the most wide-channel room, at the shortest range.
- Channel width is the second half of the decision.
- The approval record should name the band, width, client group, AP profile, and retest trigger together.
Major section
The 5 GHz UNII Sub-Bands and Channel Count
The best width is the narrowest one that meets the service objective while leaving enough clean reuse for the installed cell pattern.
- The 5 GHz band is organised into UNII sub-bands, each with its own rules.
- Channel width consumes these channels fast.
- A useful field test has two views.
Major section
The 5 GHz UNII Sub-Bands and Channel Count (continued)
In a dense site that means far less reuse and more co-channel contention.
- Worked example.: An installer wants maximum per-link speed and sets every AP to 80 MHz — then finds only two or three non-DFS 80 MHz channels exist, so adjacent APs collide.
- The spectrum view shows neighbouring Wi-Fi, partial overlap, non-Wi-Fi interference, and channel changes over time.
- The service view shows association, retries, missing telemetry, video stalls, command latency, and update success for the client class.
Major section
DFS Mechanics and the 6 GHz Power Classes
The hidden implementation detail is that a channel move is not just a radio event.
- This unlocks many extra channels but risks a mid-service channel change.
- UNII-2C offers many channels but they are DFS, so a passing weather radar could force a camera's AP to vacate mid-stream.
- For 6 GHz, the equivalent review is compatibility and operating scope.
- Standard-power operation adds a location-aware coordination dependency.
Major section
DFS Mechanics and the 6 GHz Power Classes (continued)
LPI can be attractive indoors, but old clients, setup phones, gateways, and battery sensors may not support the band.
- The planner reserves non-DFS UNII-1/UNII-3 channels for the cameras' critical links and uses DFS channels for tolerant bulk traffic — a design driven directly by the band's regulatory mechanics.
- Clients must hear the change, reassociate or follow the AP, refresh security state if needed, and rebuild the application path before the service timeout expires.
- Without those limits, a clean spectrum label can turn into an operations problem.
Major section
Wi-Fi Fundamentals for IoT
The radio link is only one step between the freezer and the person who must act.
- An access point is the local unit that lets wireless devices join a wired or wider network.
- This first path test cannot predict every shared-air or roaming effect.
- Practitioner builds the fit record.
Major section
Wi-Fi Fundamentals for IoT (continued)
The record should let another reviewer see why Wi-Fi is a fit, where the evidence came from, and what change would require retest.
- Firmware is the built-in software that controls a device.: Record its version with the access point setup, time, signal result, message delay, loss, and recovery.
- Wi-Fi is a family of IEEE 802.11 wireless LAN technologies.
- Wi-Fi review is easier when each symptom is routed to the right layer.
Major section
Wi-Fi Fundamentals for IoT (continued)
It may need local infrastructure, IP access, high bursts, simple commissioning, or existing security controls, but the choice only works if power, coverage, airtime, and ownership evidence match the device job.
- That promise is valuable when the device needs local services, cloud services, web APIs, dashboards, diagnostics, firmware updates, or richer data than a small sensor message.
- The first design mistake is treating "the device connected" as the same thing as "Wi-Fi fits." Association to an access point is only one checkpoint.
- A practical Wi-Fi review starts with the device workflow, not with a standards table.
Major section
Wi-Fi Fundamentals for IoT (continued)
The difference is the amount of evidence available: early design may record assumptions and required tests, while a pilot should record installed observations and logs.
- If the requirement is vague, stop before arguing about standards; if infrastructure is unknown, route the work to coverage planning; if traffic, power, or security is weakest, follow that branch before accepting the pilot.
- This ordered read connects a familiar network label to the chapter's real promise: Wi-Fi fits only within the evidence boundary recorded for the intended device and site.
- Wi-Fi may still be possible, but it is no longer a low-evidence choice.
Major section
Wi-Fi Fundamentals for IoT (continued)
If you only need the intuition, this layer is enough: use Wi-Fi when the device requirement benefits from IP connectivity and the installed network, power source, security model, and support workflow can be proven.
- A powered building controller needs a local dashboard for maintenance and a cloud path for status reports.
- The review should not stop at "connected." It should record the AP owner, network policy, local API boundary, command authorization, reconnection behavior, and retest trigger for AP replacement, firmware update, credential rotation, or enclosure change.
- Treating all of those as "Wi-Fi is broken" slows diagnosis.
Major section
Wi-Fi Fundamentals for IoT (continued)
The overview decision should separate the layers enough that a future failure has a first place to look.
- A small room sensor sends one short reading occasionally and is expected to run for a long maintenance interval.
- The review must measure wake, association, service, retry, sleep, failure recovery, support mode, and update behavior on representative hardware.
- It requires a clear evidence boundary between the radio link, the LAN service, the application path, and the product workflow.
Deck summary
Key takeaways
Wi-Fi operates across three unlicensed bands, and each behaves differently for IoT.
- A 5 GHz plan may be better for powered tools or cameras because it offers more reuse options, yet final mounting points and DFS recovery still need proof.
- The best width is the narrowest one that meets the service objective while leaving enough clean reuse for the installed cell pattern.
- In a dense site that means far less reuse and more co-channel contention.
- The hidden implementation detail is that a channel move is not just a radio event.
Retrieval practice
Recall check 1 of 6
Radio Remi says: answer from memory, then check your reasoning.
Q1For a long-range, wall-penetrating IoT sensor link, which Wi-Fi band is generally the best fit, and why?
Show answer
Answer: B Its longer wavelength trades channel count for range and penetration, which suits reach-limited sensors.
Retrieval practice
Recall check 2 of 6
Radio Remi says: answer from memory, then check your reasoning.
Q2Why does using 80 MHz channels reduce the number of independent channels available for reuse?
Show answer
Answer: A Wider channels consume more spectrum each, leaving fewer independent channels for neighbouring APs to reuse.
Retrieval practice
Recall check 3 of 6
Radio Remi says: answer from memory, then check your reasoning.
Q3What must an AP do before and during use of a DFS channel in 5 GHz UNII-2?
Show answer
Answer: A DFS protects radar: check first, monitor continuously, and move off the channel on detection.
Retrieval practice
Recall check 4 of 6
Radio Remi says: answer from memory, then check your reasoning.
Q4A prototype joins Wi-Fi once beside a lab router. What does that prove?
Show answer
Answer: B A single connection is useful evidence, but it does not prove installed coverage, service reachability, traffic behavior, power, security, provisioning, or recovery.
Retrieval practice
Recall check 5 of 6
Radio Remi says: answer from memory, then check your reasoning.
Q5A powered IoT controller needs a technician dashboard and cloud status reports. Which Wi-Fi review record is strongest?
Show answer
Answer: C This ties Wi-Fi to the installed workflow and the evidence needed to support it.
Retrieval practice
Recall check 6 of 6
Radio Remi says: answer from memory, then check your reasoning.
Q6A device associates to Wi-Fi and receives an IP address, but its local dashboard cannot be opened. Which boundary should be reviewed next?
Show answer
Answer: D Association and IP service are already partially proven; the next boundary is whether the intended local service is reachable and authorized.
Print reference
Answers 1 of 2
Answer key.
- B · Its longer wavelength trades channel count for range and penetration, which suits reach-limited sensors.
- A · Wider channels consume more spectrum each, leaving fewer independent channels for neighbouring APs to reuse.
- A · DFS protects radar: check first, monitor continuously, and move off the channel on detection.
- B · A single connection is useful evidence, but it does not prove installed coverage, service reachability, traffic behavior, power, security, provisioning, or recovery.
Print reference
Answers 2 of 2
Answer key.
- C · This ties Wi-Fi to the installed workflow and the evidence needed to support it.
- D · Association and IP service are already partially proven; the next boundary is whether the intended local service is reachable and authorized.