85 802.15.4 Quiz: Power
- Power State Transitions: TX (20 mA) → RX (18 mA) → idle (1 mA) → sleep (5 µA); energy is dominated by time in TX/RX
- Reporting Interval: Time between sensor transmissions; longer intervals dramatically reduce duty cycle and extend battery life
- Retransmission Overhead: Failed transmissions due to interference increase energy per successful delivery by the retry factor
- CSMA/CA Energy Cost: CCA (receive mode during sensing) plus random backoff (idle or RX) adds to transmission energy
- Multi-hop Energy: Each relay hop adds radio energy at the forwarding node; deeply nested devices drain relay node batteries faster
- Sleep Wake Pattern: Periodic sleep-wake cycles must be shorter than reporting interval; wake-up time adds to effective duty cycle
- Receive Window: Time RFD listens after waking; must be long enough to receive any pending messages from parent
- Throughput vs Duty Cycle: Lower duty cycle saves power but reduces maximum sustainable data rate
85.1 Minimum Viable Understanding
This quiz covers four power and performance calculations: (1) battery life using weighted average current where sleep current dominates at sub-0.001% duty cycles; (2) superframe GTS allocation with SO/BO parameters controlling the 16-slot active period; (3) variant selection where 802.15.4g’s sub-GHz range creates 40x infrastructure savings; and (4) MAC retransmission reliability where 3 retries convert 85% per-attempt success to 99.95% delivery probability.
85.2 Learning Objectives
After completing this quiz section, you should be able to:
- Derive battery life estimates for IEEE 802.15.4 devices by applying weighted-average current formulas to duty cycle and current consumption parameters
- Determine superframe timing and GTS (Guaranteed Time Slots) allocation from SO/BO parameters using the exponential relationship
- Justify IEEE 802.15.4 variant selection (standard vs 802.15.4g) by quantifying range, cost, and latency trade-offs for a given deployment scenario
- Assess MAC retransmission reliability using geometric probability models and explain the layer-separation rationale against TCP-style retransmission
This quiz focuses on power management in 802.15.4 networks. Battery life is critical for IoT sensors, and 802.15.4 provides several mechanisms to save energy – sleep modes, indirect transmissions, and beacon scheduling. Test your understanding of how these mechanisms work together.
Return to: Quiz Bank Part 1 Overview
Other Quiz Sections:
- Addressing and Network Structure
- Power and Performance Calculations (Current)
- Device Types and Security
Study Materials:
- 802.15.4 Fundamentals - Core concepts
- 802.15.4 Topic Review - Quick reference
85.3 Quiz: Battery Life Calculation
Step 1: Calculate active time per cycle
Transmission interval: 15 minutes = 900 seconds
Transmit duration: 1.6 ms per packet
Active time percentage: (1.6 ms / 900,000 ms) x 100 = 0.00018%
Step 2: Calculate average current consumption
Active current: 10 mA (transmitting)
Sleep current: 5 uA = 0.005 mA (sleeping)
Time active per hour: (60 min / 15 min) x 1.6 ms = 6.4 ms/hour
Time sleeping per hour: 3,600,000 ms - 6.4 ms = 3,600,000 ms
Average current calculation:
I_avg = (I_tx x T_tx + I_sleep x T_sleep) / T_total
Per hour (3,600,000 ms):
I_avg = (10 mA x 6.4 ms + 0.005 mA x 3,599,993.6 ms) / 3,600,000 ms
I_avg = (64 mA-ms + 17,999.97 mA-ms) / 3,600,000 ms
I_avg = 18,063.97 mA-ms / 3,600,000 ms
I_avg = 0.00502 mA = 5.02 uA
Step 3: Calculate battery life
Battery capacity: 2000 mAh
Average current: 0.00502 mA
Battery life = 2000 mAh / 0.00502 mA
Battery life = 398,406 hours
Battery life = 398,406 / 24 = 16,600 days
Battery life = 45.5 years (theoretical)
Why is the answer 8.7 years, not 45 years?
Realistic Factors:
In practice, battery capacity degrades and other factors reduce lifetime:
- Self-discharge: Coin cells lose ~2-3% capacity/year even unused
- Temperature effects: Warehouse temperature swings reduce capacity
- Voltage drop: Effective capacity ~70% when considering voltage cutoff
- Microcontroller overhead: Periodic wake-ups for RTC, housekeeping add ~0.5 uA
Revised calculation with realistic factors:
Effective capacity: 2000 mAh x 0.7 (voltage drop) = 1400 mAh
Additional overhead: 0.005 mA + 0.0005 mA (MCU) = 0.0055 mA
Self-discharge equivalent: ~1% capacity loss/year
Battery life = 1400 mAh / 0.0055 mA
Battery life = 254,545 hours = 10,606 days = 29 years
With 3% self-discharge/year:
Effective life = 29 years / 3.3 = ~8.8 years = 8.7 years
Comparison with Alternative Scenarios:
| Scenario | Interval | TX Time | Battery Life |
|---|---|---|---|
| Warehouse sensor (15 min) | 15 min | 1.6 ms | 8.7 years |
| Smart meter (60 min) | 60 min | 2.0 ms | 29.4 years |
| Fire sensor (alarm only) | 24 hr | 0.5 ms | 47.3 years |
| Industrial monitor (1 min) | 1 min | 1.6 ms | 1.5 years |
| Asset tracker (5 min) | 5 min | 1.6 ms | 2.8 years |
Key Insight:
IEEE 802.15.4’s ultra-low duty cycle (<< 1%) enables multi-year operation: - Transmission takes 1.6 ms every 900,000 ms (0.00018% duty cycle) - Sleep current (5 uA) dominates total power consumption - Transmission power (10 mA) is 2000x higher but occurs 0.00018% of time - Result: Average current = sleep current, enabling 8.7-year lifetime
85.3.1 Knowledge Check: Duty Cycle Impact on Average Current
85.4 Quiz: Superframe Structure and GTS
85.4.1 Knowledge Check: Superframe Duty Cycle
85.5 Quiz: Variant Selection for Industrial Deployment
85.5.1 Knowledge Check: Variant Selection
85.6 Quiz: MAC Retransmission and Reliability
85.6.1 Knowledge Check: Battery Life Estimation
The Mistake:
When calculating IEEE 802.15.4 sensor battery life, students typically account for transmit current (10-30 mA) and sleep current (1-10 uA) but forget the MCU wake-up and processing overhead that occurs before and after every transmission. This leads to overly optimistic battery life estimates that fail in real deployments.
Example Calculation (Incomplete):
“A sensor transmits every 15 minutes. Transmit current = 15 mA, duration = 2 ms, sleep current = 5 uA.”
Average current = (15 mA x 2 ms + 0.005 mA x 899,998 ms) / 900,000 ms
= (30 + 4,500) / 900,000
= 0.005 mA = 5 uA
Battery life (2000 mAh) = 2000 / 0.005 = 400,000 hours = 45.6 years
Why This Is Wrong:
The calculation assumes the MCU instantly wakes, samples sensors, builds the frame, and transmits – with zero overhead. In reality:
Real MCU Wake-Up Sequence (Texas Instruments CC2652R example):
| Phase | Duration | Current | Description |
|---|---|---|---|
| 1. Deep sleep | 899,990 ms | 1.2 uA | RTC running, RAM retained |
| 2. Wake from sleep | 150 us | 3 mA | Oscillator startup, voltage regulator stabilization |
| 3. MCU boot | 500 us | 6 mA | Restore CPU state, peripheral initialization |
| 4. Sensor sampling | 800 us | 2 mA | I2C/SPI transaction (temperature sensor) |
| 5. Frame construction | 300 us | 4 mA | Build 802.15.4 frame, copy to radio buffer |
| 6. Radio startup | 200 us | 8 mA | PLL lock, calibration |
| 7. CSMA-CA backoff | 1,000 us (avg) | 20 mA | Listen (CCA) during backoff |
| 8. Transmission | 2,000 us | 15 mA | TX frame + wait for ACK (192 us turnaround) |
| 9. Radio shutdown | 50 us | 3 mA | Power down RF front-end |
| 10. Return to sleep | 100 us | 2 mA | Store state to RAM, enter deep sleep |
Corrected Calculation:
| Phase | Duration (us) | Current (mA) | Charge (uA-ms) |
|---|---|---|---|
| Deep sleep | 899,990,000 | 0.0012 | 1,080,000 |
| Wake + boot | 650 | 4.5 | 2.93 |
| Sensor sample | 800 | 2.0 | 1.60 |
| Frame build | 300 | 4.0 | 1.20 |
| Radio startup | 200 | 8.0 | 1.60 |
| CSMA-CA | 1,000 | 20.0 | 20.00 |
| TX + ACK | 2,000 | 15.0 | 30.00 |
| Radio shutdown | 50 | 3.0 | 0.15 |
| Sleep entry | 100 | 2.0 | 0.20 |
| Total | 900,000,000 | - | 1,080,057 |
Average current = 1,080,057 uA-ms / 900,000 ms = 1.20 mA = 1,200 uA
Corrected Calculation (consistent units in mA-ms, with 5 uA sleep current):
| Phase | Duration (ms) | Current (mA) | Charge (mA-ms) |
|---|---|---|---|
| Deep sleep | 899,990 | 0.005 | 4,499.95 |
| Wake + boot | 0.65 | 4.5 | 2.93 |
| Sensor sample | 0.80 | 2.0 | 1.60 |
| Frame build | 0.30 | 4.0 | 1.20 |
| Radio startup | 0.20 | 8.0 | 1.60 |
| CSMA-CA | 1.00 | 20.0 | 20.00 |
| TX + ACK | 2.00 | 15.0 | 30.00 |
| Radio shutdown | 0.05 | 3.0 | 0.15 |
| Sleep entry | 0.10 | 2.0 | 0.20 |
| Total | 900,000.00 | - | 4,557.63 |
With the correct sleep current of 5 uA = 0.005 mA:
Sleep charge = 0.005 mA x 899,990 ms = 4,499.95 mA-ms
Total charge = 4,499.95 + 57.68 = 4,557.63 mA-ms
Average current = 4,557.63 / 900,000 = 0.00506 mA = 5.06 uA
Overhead contribution: 57.68 / 4,557.63 = 1.3% additional current
Impact on battery life:
Naive estimate (ignoring overhead): 2000 mAh / 0.005 mA = 400,000 hours = 45.6 years
Corrected estimate (with overhead): 2000 mAh / 0.00506 mA = 395,257 hours = 45.1 years
Difference: 0.5 years (1.2% error)
So why does this matter if the error is only 1.2%?
Because the error scales with transmission frequency:
| Transmit Interval | Naive I_avg | Corrected I_avg | Error | Impact |
|---|---|---|---|---|
| 15 minutes | 5.00 uA | 5.06 uA | 1.2% | Negligible |
| 5 minutes | 5.00 uA | 5.19 uA | 3.8% | Minor |
| 1 minute | 5.03 uA | 5.96 uA | 18.5% | Significant |
| 10 seconds | 5.50 uA | 11.26 uA | 105% | CRITICAL |
For event-driven sensors (fire alarms, motion detectors), the overhead becomes dominant:
Fire alarm scenario (1 transmission per day, but MCU wakes every 10 seconds to check sensor):
Wakeups per day: 86,400 / 10 = 8,640 wakeups
Most wakeups: sensor check only (no transmission)
Wake -> Sample -> Sleep: 650 us + 800 us + 100 us = 1.55 ms @ avg 3 mA
Overhead per wakeup: 3 mA x 1.55 ms = 4.65 mA-ms
Daily overhead: 8,640 x 4.65 = 40,176 mA-ms
Sleep (remaining time): 86,400,000 ms - (8,640 x 1.55 ms) = 86,386,608 ms @ 5 uA
Sleep charge: 0.005 mA x 86,386,608 ms = 431,933 mA-ms
Total daily charge: 40,176 + 431,933 = 472,109 mA-ms
Average current: 472,109 / 86,400,000 = 0.00546 mA = 5.46 uA
Battery life: 2000 mAh / 0.00546 mA = 366,300 hours = 41.8 years
Naive estimate (ignoring wake-up overhead): 45.6 years
Corrected estimate: 41.8 years
Error: 3.8 years (8.3%)
Why This Matters in Practice:
- Deployment planning: 8% error means 96 out of 1,000 sensors die before expected replacement
- Warranty liability: If you guarantee 10-year battery life but 8% fail at year 9.2, you face costly replacements
- User trust: Early battery failures undermine product reputation
How to Avoid This Mistake:
Best practice 1: Measure real current profiles Use a power profiler (e.g., Nordic PPK2, Joulescope) to capture actual current draw during wake-sleep cycles. You’ll see current spikes during wake-up that naive calculations miss.
Best practice 2: Use vendor-provided current budgets TI, Nordic, STMicro provide detailed current consumption tables for each MCU state. Don’t assume “sleep = 5 uA” – check datasheet for: - Deep sleep with RTC - Light sleep with RAM retention - Active mode (CPU @ various MHz) - Peripheral current (I2C, SPI, ADC)
Best practice 3: Add 20% margin to all battery calculations Real-world deployments have: - Temperature variations (current increases at high temp) - Component aging (sleep current drifts upward over years) - Firmware updates (new features add wake-up overhead) - User behavior (unexpected sensor polling)
Battery capacity with derating:
Usable capacity = Nominal x 0.70 (voltage drop) x 0.70 (self-discharge) x 0.80 (aging reserve)
Effective capacity = 40% of nominal capacity
Real-World Example: nRF52840 (Nordic Semiconductor)
Advertised sleep current: 1.9 uA (System OFF mode with RTC)
Real deployment current:
- System OFF with RTC: 1.9 uA (datasheet)
- RAM retention (64 KB): +1.4 uA (ignored in naive calculations)
- GPIO leak current (10 pins): +0.3 uA (forgotten)
- Actual measured: 3.6 uA (90% higher than advertised!)
Wake-up sequence (measured with PPK2):
- Deep sleep -> Active: 150 us @ 4 mA (oscillator start)
- Active processing: 2 ms @ 6 mA (sensor + frame build)
- Radio TX: 2 ms @ 9 mA (0 dBm output power)
- Active -> Deep sleep: 100 us @ 3 mA (RAM flush)
Overhead per transmission: 4.65 ms average @ 5.5 mA = 25.6 uA-ms
For 1-minute transmission interval:
Average current = (3.6 uA x 60,000 ms + 25,600 uA-ms) / 60,000 ms
= (216,000 + 25,600) / 60,000
= 4.03 uA (12% higher than naive 3.6 uA sleep current estimate)
Battery life impact: 12% reduction in actual runtime
Key Takeaway:
Always measure or model the complete wake-sleep-transmit cycle. The overhead is small for infrequent transmissions (< 5% for 15-minute intervals) but becomes dominant for frequent or event-driven applications (> 50% for sub-minute intervals). Ignoring MCU overhead is the single most common battery life estimation error in 802.15.4 deployments.
| Core Concept | Root Physics | Design Consequence | Real-World Trade-off |
|---|---|---|---|
| Ultra-low duty cycle | Sleep current dominates at < 1% duty | Average current = sleep current | 8.7-year battery life, but need MCU overhead awareness |
| Superframe timing | SO/BO exponential relationship | Duty cycle = 2^(SO-BO) | Higher SO = more capacity but 2x power per increment |
| Sub-GHz advantage | Free-space path loss proportional to frequency squared | 915 MHz has 10x better range than 2.4 GHz | 40x infrastructure savings, but 5x latency penalty |
| GTS allocation | Guaranteed bandwidth vs shared capacity | CAP% = (16 - GTS_slots) / 16 | 87.5% contention access with 2 GTS, but only 7 slots max |
| MAC retransmission | Link-layer vs end-to-end reliability | 99.95% single-hop success is not a multi-hop guarantee | Masks interference locally, but routing adds per-hop failures |
85.7 See Also
- 802.15.4 Review: Power Management - Sleep modes and duty cycle analysis
- 802.15.4 Review: Beacon Networks - Superframe structure and GTS
- 802.15.4 Fundamentals - Core standard concepts
- Device Types and Security Quiz - FFD/RFD and AES-128
- Addressing and Network Structure Quiz - Addressing modes and Cskip
Common Pitfalls
Multi-hop networks require router (FFD) nodes to forward packets for leaf devices. Routers must stay awake longer to relay messages. Optimizing leaf device power while leaving routers continuously powered wastes overall system energy. Size router battery separately from leaf device battery.
Clear Channel Assessment requires the radio receiver to be active for at least 8 symbol periods per CSMA/CA attempt. For high traffic networks with multiple backoff attempts, CCA energy accumulates significantly and must be included in power calculations.
Real IoT devices often burst-report (many readings at startup, then settle to steady rate). Power budgets based on steady-state averages underestimate peak energy draw during burst periods. Always model worst-case reporting rates and their impact on battery lifetime.
Neighbor tables, routing tables, and security counters consume RAM. In low-memory devices (2-8 KB RAM), these tables can fill after days or weeks of operation. Devices then fail to route or associate new nodes. Test long-running behavior, not just initial operation.
85.8 Summary
This quiz section covered IEEE 802.15.4 power management and performance calculations:
| Topic | Key Calculation | Practical Result |
|---|---|---|
| Battery Life | Duty cycle = TX time / interval | 8.7 years on coin cell |
| Superframe/GTS | CAP = (16 - beacon - GTS) / 16 | 87.5% for contention access |
| Variant Selection | Coverage = pi x range^2 | 40x cost savings with sub-GHz |
| MAC Reliability | P(success) = 1 - P(fail)^retries | 99.95% with 3 retries |
85.8.1 Key Formulas
Battery Life:
I_avg = (I_tx x T_tx + I_sleep x T_sleep) / T_total
Battery_life = Capacity / I_avg (with derating factors)
Superframe Structure:
Active Period = Base x 2^SO
Beacon Interval = Base x 2^BO
Duty Cycle = 2^(SO-BO)
Retransmission Reliability:
P(success) = 1 - P(single_fail)^(retries + 1)
With 15% loss, 3 retries: 1 - 0.15^4 = 99.95%
85.9 What’s Next
| Chapter | Description |
|---|---|
| Device Types and Security | FFD/RFD role distinctions, AES-128 encryption, and channel-hopping mechanisms |
| Addressing and Network Structure | 16-bit short vs 64-bit extended addressing modes and the Cskip tree-routing algorithm |
| Quiz Bank Part 1 Overview | Return to the main quiz navigation page for all 802.15.4 quiz sections |
| 802.15.4 Fundamentals | Review core PHY/MAC concepts, frame formats, and protocol stack architecture |
| 802.15.4 Review: Power Management | Deep dive into sleep modes, indirect transmission, and duty-cycle analysis |