Wi-Fi & 802.11 · Study deck

Wi-Fi Power Consumption

An access point is the network unit that a Wi-Fi device joins.

Radio Remi is your guide for this deck.

wifi-powerpower-budgetsleep-wake

Radio Remi, the module guide, in a scene from this chapter.

After studying this chapter

Learning objectives

You will be able to:

describe the Wi-Fi power states that matter in IoT reviews
explain why connection, service, retry, and maintenance work can dominate a power budget
separate data-sheet current values from measured device evidence
review sleep, wake, downlink, and AP-coordination behavior without universal battery-life claims

Major section

Start With the Wireless Story

An access point is the network unit that a Wi-Fi device joins.

Its timing and traffic can change how long the device must stay awake.
Most of its energy may still be spent finding the network, joining it, waiting for a reply, or staying awake for downlink traffic.
Longer sleep can delay commands.

Major section

Start With the Wireless Story (continued)

A tiny sleep-current value does not prove long battery life.

More retries can improve delivery while using more energy.
The access point's wake schedule can change both results.
The Practitioner section explains beacon timing and practical power settings.
Under the Hood shows how newer wake schedules change the old beacon rhythm.

Major section

Start With the Wireless Story (continued)

A daily budget needs both send and receive work.

A short high peak can reset the board.
A long low wait can use more energy than the brief send.
A sleeping device cannot hear all the time.
It may wake for a network notice or at a set time.

Major section

Start With the Wireless Story (continued)

Longer sleep can save energy but delay a command.

Many devices may wake after a power cut or at the same clock time.
That burst can cause waits and retries.
Fix the model when the two do not agree.
Recheck after any of them changes.

Major section

Comparing Wi-Fi With Other Networks

A technology comparison is useful only when it starts from the requirement.

Wi-Fi may be a strong fit for powered, IP-heavy, local-dashboard, media, gateway, update, or diagnostic workflows.
A lower-power technology may be a better fit for tiny, infrequent, long-life battery telemetry.
A gateway-assisted design may be better when Wi-Fi is useful for the gateway but not for each leaf device.

Major section

Wi-Fi Sleeps Between Beacons

A Wi-Fi radio left fully on is a battery killer, so 802.11 lets a station sleep and wake only when needed.

For an IoT review, the question is not whether power save exists.
A missing AP, buffered command, credential change, or update prompt can keep the radio awake far longer than the nominal telemetry path.

Use the route to keep power-save claims tied to evidence: the review starts with the requirement, then checks states, measurement, communication timing, recovery, and the final tune-or-redesign decision.

Major section

DTIM, PS-Poll, and U-APSD

The DTIM period is a key knob: a station may sleep through ordinary beacons and only must wake at the DTIM beacon.

Worked example: A battery sensor rarely receives commands.
A voice handset would keep DTIM = 1 for responsiveness.
The knob is set per use case.
Practitioner evidence should separate the knob from the outcome.

Major section

Target Wake Time Breaks the Beacon Cadence

Worked example: Suppose a building has 300 Wi-Fi sensors reporting every 30 seconds.

Legacy power save uses beacon and DTIM timing to learn about buffered downlink traffic, although a client need not wake for every beacon.
Target Wake Time (TWT) appeared in 802.11ah and is also available in 802.11ax (Wi-Fi 6).
If their legacy power-save wakeups cluster, they may contend in bursts.

Major section

Target Wake Time Breaks the Beacon Cadence (continued)

The schedule may smooth channel load; it does not guarantee an uncontended slot or maximum battery life.

A capable station and AP can negotiate a schedule — a wake time and a service-period duration — so the station may sleep between agreed service periods when its traffic and latency requirements allow.
For a large fleet of Wi-Fi sensors, that scheduling can avoid a burst of simultaneous wakeups; actual airtime, retries, and battery life still need measurement.
The under-the-hood evidence is the negotiated schedule, not the marketing label.

Major section

Target Wake Time Breaks the Beacon Cadence (continued)

A compatible AP could negotiate staggered TWT service periods; a sensor may sleep for much of each 30-second interval, but its own reporting duration, downlink deadlines, and retries shorten that sleep.

TWT can improve a fleet only when the station, AP, firmware, and application timing all honor the same contract.
A release record should also say what invalidates the claim: AP replacement, firmware change, new command-latency requirement, different traffic cadence, roaming profile change, or a site with mixed AP support.
Without those retest triggers, a good lab TWT result becomes a fragile deployment assumption.

Deck summary

Key takeaways

An access point is the network unit that a Wi-Fi device joins.

A tiny sleep-current value does not prove long battery life.
A daily budget needs both send and receive work.
Longer sleep can save energy but delay a command.
A technology comparison is useful only when it starts from the requirement.

Retrieval practice

Recall check 1 of 6

Radio Remi says: answer from memory, then check your reasoning.

Q1A team estimates Wi-Fi battery life using only active transmit current and payload size. How should the team assess this Wi-Fi battery-life estimate for its actual workflow?

ARequire a state-based power record for the actual device workflow, including connection, service, retry, sleep, and maintenance.

BAccept it because transmitting draws the highest instantaneous current.

CAccept it, since payload size sets the total battery life

DSwitch to BLE based on its lower quoted radio current.

Show answer

Answer: A Wi-Fi battery life needs a state-based model covering connect, service, retry, sleep, and maintenance, not just transmit current.

Retrieval practice

Recall check 2 of 6

Radio Remi says: answer from memory, then check your reasoning.

Q2A Wi-Fi maintenance tool keeps its local dashboard session open after the technician leaves. Which power review action fits that workflow?

ATreat the idle session as sleep because no payload is being sent.

BCompare transmit-current tables only and ignore service-session duration.

CChoose a different radio before measuring how the support session closes.

DMeasure active and idle session duration, set an idle timeout, and verify the session closes cleanly.

Show answer

Answer: D Maintenance power includes the live session and its idle timeout, not only transmit current.

Retrieval practice

Recall check 3 of 6

Radio Remi says: answer from memory, then check your reasoning.

Q3A device can save energy by sleeping longer, but it also needs occasional downlink commands. What should the reviewer require?

AAlways choose the longest sleep interval because energy is the only goal.

BDisable downlink commands merely to improve the power budget.

CRequire wake schedule, command latency and AP buffering evidence.

DAssume the access point buffers commands correctly because its connection queue preserves them during device sleep.

Show answer

Answer: C Sleep and wake behavior must be reviewed against freshness, command, AP, retry, and support requirements.

Retrieval practice

Recall check 4 of 6

Radio Remi says: answer from memory, then check your reasoning.

Q4In Wi-Fi power-save mode, how does a sleeping station learn it has downlink traffic waiting?

AIt sends a cellular query and asks the cloud whether the AP buffered traffic.

BIt stays awake for all downlink frames so AP-side buffering is not required.

CIt wakes for a beacon and reads the TIM bitmap that marks buffered frames for that station.

DIt receives a vendor phone-app alert whenever a frame arrives at the AP.

Show answer

Answer: C The AP buffers a sleeping station's frames and signals them via the TIM bitmap in each beacon.

Retrieval practice

Recall check 5 of 6

Radio Remi says: answer from memory, then check your reasoning.

Q5An AP increases its DTIM period from 1 to 3 (beacon interval ~102.4 ms), and a power-save sensor is configured to wake at each DTIM and sleep between them. What is the effect?

AIt triples the PHY data rate because each beacon advertises three delivery windows.

BIt can sleep about 307 ms between required wakeups, trading power savings for downlink delay.

CIt disables AP buffering, so commands are sent only while the sensor is already awake.

DIt forces continuous awake mode because DTIM beacons become too far apart.

Show answer

Answer: B A larger DTIM period lengthens sleep and delays buffered delivery - a good trade for latency-tolerant sensors.

Retrieval practice

Recall check 6 of 6

Radio Remi says: answer from memory, then check your reasoning.

Q6How does Target Wake Time (TWT) improve on legacy Wi-Fi power save for a large sensor fleet?

AIt keeps every station awake during a shared service period to prevent missed frames.

BIt removes 802.11 acknowledgments so each report uses fewer MAC exchanges.

CIt restricts sensor scheduling to 6 GHz channels where beacons are less frequent.

DIt lets stations negotiate separate wake slots, extending sleep and reducing wakeup contention.

Show answer

Answer: D TWT both extends sleep and spreads stations' wake times, avoiding the thundering-herd contention of synchronized wakeups.

Print reference

Answers 1 of 2

Answer key.

A · Wi-Fi battery life needs a state-based model covering connect, service, retry, sleep, and maintenance, not just transmit current.
D · Maintenance power includes the live session and its idle timeout, not only transmit current.
C · Sleep and wake behavior must be reviewed against freshness, command, AP, retry, and support requirements.
C · The AP buffers a sleeping station's frames and signals them via the TIM bitmap in each beacon.

Print reference

Answers 2 of 2

Answer key.

B · A larger DTIM period lengthens sleep and delays buffered delivery - a good trade for latency-tolerant sensors.
D · TWT both extends sleep and spreads stations' wake times, avoiding the thundering-herd contention of synchronized wakeups.