10  NB-IoT Power Saving (PSM/eDRX)

In 60 Seconds

PSM (Power Saving Mode) and eDRX (Extended Discontinuous Reception) are NB-IoT’s two power-saving mechanisms: PSM provides the lowest power (~5 uA) by turning off the radio entirely but makes devices unreachable for downlink, while eDRX maintains periodic paging windows (up to 2.91 hours) for downlink reachability at higher idle power (~15 uA), with timer selection (T3412, T3324) critical to battery life calculations.

Key Concepts
  • PSM Periodic TAU (T3412): Timer defining the periodic tracking area update interval while in PSM; device is unreachable (except emergency) between TAUs; range 2 s to 413 days
  • PSM Active Timer (T3324): Duration the device remains in idle mode (reachable) after completing data session before entering PSM deep sleep; range 2 s to 310 s
  • eDRX Cycle: The total sleep+listen cycle duration in eDRX mode; NB-IoT supported values: 20.48 s, 40.96 s, 81.92 s, 163.84 s, 327.68 s, 655.36 s, 1310.72 s, 2621.44 s
  • PTW (Paging Time Window): Active window within each eDRX cycle where device listens for network pages; duration determines downlink responsiveness; trade-off: longer PTW = more power use
  • eDRX vs PSM Trade-off: PSM: maximum power savings, hours to days of downlink unreachability; eDRX: moderate power savings, periodic reachability (seconds to hours between windows)
  • T3412/T3324 AT Commands: Request via AT+CPSMS=1,,,,; verify granted values via AT+CPSMS?; device must use network-granted values even if different from requested
  • NB-IoT eDRX AT Command: Enable via AT+CEDRXS=1,5,; access technology type=5 for NB-IoT; verify via AT+CEDRXS? and +CEDRXP URC
  • PSM State Machine: Device states: RRC Connected (active radio) → RRC Idle/eDRX (periodic paging) → PSM (deep sleep, no paging) → wakeup → RRC Connected (data transmission cycle)

10.1 Learning Objectives

By the end of this chapter, you will be able to:

  • Compare PSM and eDRX mechanisms: Differentiate Power Saving Mode and Extended Discontinuous Reception in terms of sleep current, reachability, and state transitions
  • Calculate battery life from power profiles: Compute device lifetime by combining active, idle, and sleep current consumption across daily duty cycles
  • Configure PSM/eDRX timers: Select and justify appropriate T3412 and T3324 timer values for specific application latency and battery requirements
  • Evaluate hybrid power strategies: Assess trade-offs between PSM-only, eDRX-only, and combined PSM+eDRX configurations for real-world deployment scenarios

10.2 Prerequisites

Before diving into this chapter, you should be familiar with:

  • NB-IoT Fundamentals: Understanding basic NB-IoT concepts, deployment modes, and system architecture provides the foundation for advanced power management topics
  • Cellular IoT Fundamentals: Knowledge of cellular network protocols and 3GPP standards helps you understand power-saving mechanisms in the context of LTE architecture
  • LPWAN Fundamentals: Understanding LPWAN power optimization strategies provides context for comparing NB-IoT’s PSM/eDRX with other technologies

Deep Dives:

Comparisons:

Related Topics:

Quick Reference: Acronyms and Timers
  • PSM (Power Saving Mode): Deep sleep with the radio off; device stays registered but is unreachable for downlink.
  • eDRX (extended Discontinuous Reception): Periodic paging windows; device is reachable for downlink, but with higher idle power than PSM.
  • TAU (Tracking Area Update): Brief wake-up to refresh network registration and location context.
  • T3412 (Periodic TAU timer): How long the device can stay in PSM before performing a TAU (hours to days).
  • T3324 (Active timer): How long the device stays reachable after an uplink (seconds to minutes) before entering PSM.

“PSM and eDRX are the ultimate power-saving superpowers!” Bella the Battery declared. “With PSM, the radio shuts off completely. Imagine unplugging your TV instead of putting it on standby – that is the difference. Sleep current drops to just 5 microamps, which means I can keep Sammy running for over ten years!”

“The two timers are like alarm clocks,” Max the Microcontroller explained. “T3412 is the big alarm that wakes me up to check in with the network – I set it to 24 hours for most sensors. T3324 is the snooze timer that keeps me awake briefly after sending data, just long enough to receive a reply. Then I go right back to my deep sleep.”

Sammy the Sensor added, “eDRX is for when I need to be somewhat reachable. Instead of sleeping for a full day like PSM, I set periodic wake-up windows. Every 2 to 43 minutes, I briefly open my ears to listen for incoming messages. It uses more power than PSM but lets the server send me commands without waiting a whole day.”

“Here is the key decision,” Lila the LED summarized. “If your device only sends data and never needs to receive urgent commands, use PSM for maximum battery life. If the server sometimes needs to reach the device – like sending a firmware update or changing a configuration – use eDRX so the device checks for messages periodically. Some devices even combine both modes!”

10.3 Getting Started (For Beginners)

If you’re new to NB-IoT power management, this section will help you understand how NB-IoT devices achieve 10+ year battery life.

10.3.1 What is NB-IoT Power Management? (Simple Explanation)

Analogy: Think of NB-IoT power modes like your smartphone’s power settings, but WAY more extreme:

  • Your smartphone: “Sleep mode” saves battery, but the phone still checks for notifications every few seconds - battery lasts 1-2 days
  • NB-IoT PSM mode: “Deep sleep” - the device completely turns off the radio and sleeps for hours or days - battery lasts 10-15 years!

The key difference: NB-IoT devices don’t need to be instantly reachable (unlike your phone). They wake up, send data, and go back to deep sleep.

10.3.2 Real-World Examples

Example 1: Smart Water Meter (PSM Mode)

Scenario: Municipal water meter in basement
- Reports water usage once per day (midnight)
- No downlink needed (utility company doesn't send commands)
- Must last 15 years (replacing battery costs $50 labor + truck roll)

Power profile (24 hours):
├─ Sleep (PSM): 23 hours 59 minutes (radio OFF, 5 μA)
├─ Wake up at midnight: 1 second
├─ Send water reading (50 bytes): 5 seconds (200 mA)
├─ Receive ACK: 1 second (50 mA)
└─ Return to PSM: immediate

Daily energy consumption:
- Sleep: 23.98 hours × 5 μA = 120 μAh = 0.12 mAh
- Transmit: 7 seconds × 150 mA (average) = 0.29 mAh
Total per day: 0.41 mAh

Battery life with 6,000 mAh battery (2× AA lithium):
6,000 mAh ÷ 0.41 mAh/day = 14,634 days = **40 years**!
(In practice: 15 years due to battery self-discharge)

Why PSM works here:

  • Device doesn’t need to receive commands (uplink-only)
  • Reporting schedule is predictable (midnight daily)
  • Deep sleep maximizes battery life

Example 2: Smart Parking Sensor (eDRX Mode)

Scenario: Street parking sensor
- Reports occupancy changes immediately (car arrives/leaves)
- Must receive commands from cloud (e.g., "enable maintenance mode")
- Battery replacement every 5 years is acceptable

Power profile (typical day):
├─ Sleep with eDRX listening: 23 hours (15 μA average)
│   └─ Wake every 2.91 hours to check for downlink (100 ms)
├─ Occupancy change events: 4× per day (car in/out)
│   └─ Each transmission: 5 seconds (200 mA)
└─ Total active time: 20 seconds/day

Daily energy consumption:
- eDRX sleep: 23 hours × 15 μA = 345 μAh = 0.345 mAh
- Transmissions: 4 × 5s × 200mA = 1.11 mAh
Total per day: 1.46 mAh

Battery life with 6,000 mAh battery:
6,000 ÷ 1.46 = 4,110 days = **11.3 years** ✅

Why eDRX is needed here:

  • Device must be reachable for cloud commands (downlink required)
  • Still achieves 10+ year battery life
  • Slightly higher power consumption than PSM (15 μA vs 5 μA)

10.3.3 The Two Essential Power Saving Modes

NB-IoT offers two main power-saving modes. Here’s how to choose:

Power Mode Sleep Current Can Receive Messages? Wake-up Time Battery Life Use Case
PSM (Power Saving Mode) 3-5 μA No (radio OFF) Hours to days 15+ years Uplink-only sensors (meters, trackers)
eDRX (Extended DRX) 15 μA Yes (wakes periodically) Seconds to minutes 5-10 years Devices needing downlink (actuators, remote config)

Key insight: The difference between 5 μA (PSM) and 15 μA (eDRX) seems tiny, but over 10 years: - PSM: 5 μA × 87,600 hours = 438 mAh - eDRX: 15 μA × 87,600 hours = 1,314 mAh - Difference: 876 mAh (can double battery size requirements!)

10.3.4 Why PSM and eDRX Exist When Cellular Networks Already Have DRX

Standard LTE devices already use Discontinuous Reception (DRX) to save power – a smartphone checks for paging messages every 1.28 seconds during idle mode. So why did 3GPP invent two entirely new power-saving mechanisms (PSM in Release 12, eDRX in Release 13) specifically for IoT?

Standard DRX wastes 97% of an IoT device’s energy budget on unnecessary listening. A smart water meter that reports once per day spends 86,398 seconds idle and 2 seconds transmitting. With standard LTE DRX (1.28s paging cycle), the radio wakes up 67,498 times per day to check for paging messages that almost never arrive. Each wake-up draws 30-50 mA for 5-10 ms, consuming roughly 5-9 mAh per day just for paging reception. The actual data transmission uses only 0.08-0.15 mAh. The paging overhead alone would drain a 6,000 mAh battery in under 3 years.

PSM eliminates paging entirely. By telling the network “do not page me until I contact you,” the device avoids all 67,498 daily wake-ups. Sleep current drops from the DRX average of 1-2 mA to the PSM floor of 3-5 uA (set by the voltage regulator leakage, not the radio). This is a 200-400x reduction in idle power, extending battery life from 2-3 years to 15+ years.

eDRX is the compromise for bidirectional devices. Some IoT devices need occasional downlink messages (firmware updates, configuration changes, actuator commands) but not with smartphone-like immediacy. eDRX extends the paging cycle from 1.28 seconds to values ranging from 5.12 seconds up to 2.91 hours. At 40-minute eDRX cycles, a device wakes 36 times per day instead of 67,498 times, reducing paging energy by 99.95% while remaining reachable within 40 minutes.

The three modes form a clear decision hierarchy:

Mode Paging wakeups/day Idle power Reachability Best for
Standard DRX 67,500 1-2 mA < 2 seconds Smartphones
eDRX (40 min) 36 15 uA < 40 minutes Parking sensors, fleet trackers
PSM 0 3-5 uA Only when device wakes Water meters, soil sensors

10.3.5 Common Beginner Questions

Q1: What’s the difference between PSM and “turning the device off”?

A: PSM keeps network registration, “off” loses it:

PSM (Power Saving Mode):
1. Device tells network: "I'm going to sleep for 24 hours"
2. Network says: "OK, I won't page you until then"
3. Device sleeps (5 μA)
4. Wake up → immediate connection (already registered)
   └─ No handshake needed, just send data (fast!)

Fully OFF (not registered):
1. Device powers off completely (0 μA)
2. Wake up → must re-register with network
   ├─ Cell search: 5-10 seconds
   ├─ Attach procedure: 10-20 seconds
   └─ Finally send data: 5 seconds
   Total: 20-35 seconds active (vs 5 seconds with PSM)

Battery impact:
- PSM: 5 seconds active (0.28 mAh)
- Full OFF/ON: 25 seconds active (1.39 mAh)
→ PSM uses 80% less energy per transmission!

Q2: Can I use Wi-Fi-style “sleep mode” with NB-IoT to save power?

A: No, NB-IoT requires PSM or eDRX for long battery life:

Wi-Fi sleep (like ESP32 light sleep):
- Radio stays synchronized with access point
- Must wake every 100 ms to receive beacon
- Sleep current: 800 μA - 15 mA (depending on implementation)
- Battery life: weeks to months

NB-IoT PSM (deep sleep):
- Radio completely OFF (loses synchronization)
- No periodic wake-ups required
- Sleep current: 3-5 μA
- Battery life: 10-15 years

Why 100× difference?
- Wi-Fi: Designed for high-speed, always-on communication
- NB-IoT: Designed for infrequent, scheduled communication

Q3: How do I choose between PSM and eDRX?

A: Ask: “Does the cloud need to send commands to the device?”

Decision flowchart for NB-IoT power mode selection. Start: Does cloud need to send commands to device? If No, use PSM (3-5 microamp sleep, 10-15 year battery, device unreachable during sleep). If Yes, is near-real-time response needed? If Yes, use eDRX with short cycle (20 seconds, 5-10 year battery). If No, use eDRX with long cycle (10-40 minutes, 8-12 year battery) or hybrid PSM plus scheduled eDRX windows.
Figure 10.1: Decision flowchart for choosing between PSM and eDRX power modes based on downlink requirements

10.4 Power Saving Mode (PSM)

PSM allows devices to enter deep sleep while remaining registered to the network:

NB-IoT Power Saving Mode state transition sequence showing device sending uplink data at 200 milliamps, entering idle mode for T3324 timer duration when downlink can be received, then transitioning to deep PSM sleep at 3 to 5 microamps until T3412 periodic TAU timer expires for network re-registration
Figure 10.2: NB-IoT Power Saving Mode state transitions and timers

NB-IoT Power Saving Mode sequence diagram showing device sending uplink data using 200mA for 5 seconds, entering idle mode for T3324 duration (30 seconds at 50mA) when downlink can be received, then entering deep PSM sleep at 3-5 µA for hours to days until T3412 periodic TAU timer expires, when device briefly wakes to re-register with network before returning to PSM.

This state machine diagram shows NB-IoT power states: devices cycle through Connected, Active (TX/RX), Idle, and deep PSM Sleep modes based on timers and events.

PSM characteristics:

  • Device remains registered but unreachable
  • No paging monitoring (radio off)
  • Wakes up periodically or on application trigger
  • Current consumption: < 5 µA (comparable to powered off)
  • Wake-up triggers: Timer expiry, application event

Configurable timers:

  • T3324 (Active Timer): Time in idle mode after data transfer before entering PSM
  • T3412 (Periodic TAU): Time between tracking area updates (can be hours to days)

10.5 Extended Discontinuous Reception (eDRX)

eDRX extends the sleep period while remaining reachable for mobile-terminated data:

NB-IoT Extended Discontinuous Reception sequence diagram showing device in eDRX sleep mode at 15 µA, periodically waking (up to 2.91 hour cycles) to check for paging. First wake finds no downlink and device returns to sleep. Second wake receives downlink command, device processes it at 200mA for 10 seconds, acknowledges, then returns to eDRX sleep maintaining reachability while conserving power.
Figure 10.3: Extended Discontinuous Reception cycle with paging windows

eDRX characteristics:

  • Device remains reachable (can receive downlink)
  • Periodically wakes to listen for paging
  • eDRX cycle: up to 2.91 hours (10,485 seconds) in NB-IoT
  • Sleep current: ~15 µA (slightly higher than PSM)
  • Trade-off: Reachability vs power consumption

The difference between PSM’s 5 µA and eDRX’s 15 µA seems small, but the weighted average power depends on how frequently the device wakes to check for paging.

For a 10.24-minute eDRX cycle:

Each paging check: 50 mA × 100 ms = 5 mAs = 0.00139 mAh

Paging checks per day: \(\frac{24 \times 60}{10.24} = 141 \text{ checks/day}\)

Paging energy: \(141 \times 0.00139 \text{ mAh} = 0.196 \text{ mAh/day}\)

Sleep energy: \(15 \text{ µA} \times 23.99 \text{ h} = 0.360 \text{ mAh/day}\)

Total eDRX: 0.556 mAh/day (vs 0.120 mAh/day for PSM sleep only)

This 4.6× difference compounds over 10 years: eDRX consumes ~2,000 mAh more than PSM, enough to require a 50% larger battery or reduce device life from 15 years to 10 years.

10.6 Power Mode Comparison

Mode Current Reachable Latency Use Case
Active/Connected 50-300 mA Yes < 1s Data transfer
Idle (normal DRX) 1-5 mA Yes < 10s Frequent communication
Idle (eDRX) 15 µA Yes seconds-minutes Occasional downlink
PSM <5 µA No hours-days Uplink-only, scheduled
NB-IoT power mode state machine showing transitions between Active/Connected (50-300mA, <1s latency), Idle DRX (1-5mA, <10s), eDRX (15µA, seconds-minutes), and PSM (< 5µA, hours-days). After data transfer, device enters Idle, then eDRX light sleep, then PSM deep sleep for maximum power savings. PSM can only wake on TAU timer or uplink trigger (radio OFF, cannot receive downlink). eDRX can wake on paging for downlink reception while maintaining low power.
Figure 10.4: NB-IoT power mode transitions from active to deep sleep

Pitfall: Ignoring Initial Attach Power Cost in Battery Calculations

The Mistake: Developers calculate battery life based only on daily transmission energy (e.g., “50 bytes × 4 times/day = 0.5 mAh/day”), then are shocked when field devices die 40% faster than predicted.

Why It Happens: NB-IoT initial attach after PSM wake-up requires a complete RRC connection establishment, authentication, and security mode command exchange. This signaling overhead consumes 220-300 mA for 5-10 seconds BEFORE any user data is transmitted, adding 0.3-0.8 mAh per attach cycle that’s often omitted from calculations.

The Fix: Include full attach sequence in power budget: 1. RACH preamble: 50ms @ 200mA = 0.003 mAh 2. RRC setup + NAS signaling: 3-5 seconds @ 220mA = 0.18-0.30 mAh 3. Authentication: 1-2 seconds @ 150mA = 0.04-0.08 mAh 4. Security mode: 0.5-1 second @ 150mA = 0.02-0.04 mAh 5. Bearer setup: 0.5-1 second @ 150mA = 0.02-0.04 mAh Total attach overhead: 0.27-0.48 mAh per wake cycle (typically exceeds user data transmission cost for small payloads). For devices waking 4 times/day: attach overhead = 1.1-1.9 mAh/day. Compare to 50-byte TX: only 0.07 mAh. Attach is 15-27x more expensive than data!


10.7 Knowledge Check

Test your understanding of NB-IoT power modes:

Question 1: PSM Timer Configuration for Smart Parking

You’re configuring 10,000 street parking sensors using NB-IoT. Each sensor: - Reports occupancy changes immediately (car arrives/leaves) - Average turnover: 4 events per day per spot - Must last 10 years on battery - City needs to send occasional firmware updates (once per year)

You’re configuring the T3412 (TAU timer) and T3324 (Active timer) for PSM mode.

Answer & Detailed Explanation

Correct Answer: B) T3412 = 24 hours, T3324 = 30 seconds


10.7.1 Understanding PSM Timers

T3412 (Periodic Tracking Area Update timer):

  • How often device wakes from PSM to register with network
  • Tells network: “I’m still alive and in your coverage area”
  • Longer period = better battery life (fewer wake-ups)
  • Shorter period = network knows device is reachable more often

T3324 (Active Timer):

  • How long device stays in “idle” mode after data transfer before entering PSM
  • During this time, device can receive downlink messages
  • Longer period = more opportunity for downlink, but higher power consumption
  • Shorter period = faster sleep, better battery life

10.7.2 Why Option B is Optimal

Option B: T3412 = 24 hours, T3324 = 30 seconds

Power consumption breakdown:

PSM TAU wake-ups:
- 1 wake-up per day (daily)
- Duration: 5 seconds connection + 30 seconds idle = 35 seconds
- Energy: 35s × 50mA = 0.49 mAh/day

Occupancy event reports:
- 4 events per day
- Each event: 5 seconds transmit + 30 seconds idle = 35 seconds
- Energy: 4 × 35s × 50mA = 140s × 50mA = 1.94 mAh/day

PSM sleep:
- Sleep time: 24h - (35s + 140s) = 24h - 2.9 minutes ≈ 23.95 hours
- Energy: 23.95h × 5μA = 0.12 mAh/day

Total daily: 0.49 + 1.94 + 0.12 = 2.55 mAh/day

Battery life: 10,000 ÷ 2.55 = 3,922 days = **10.7 years** ✅

Perfect! Exceeds 10-year target.

10.7.3 Comparison Summary

Configuration TAU Frequency Active Window Daily Consumption Battery Life
Option A Hourly (24×) 10s 5.95 mAh 4.6 years
Option B Daily (1×) 30s 2.55 mAh 10.7 years
Option C Weekly (0.14×) 2min 7.18 mAh 3.8 years
Option D N/A Always 1,200 mAh 8 days
Question 2: eDRX Cycle Optimization

You’re deploying 5,000 smart streetlight controllers using NB-IoT. Each controller: - Reports status and energy consumption every hour - Must receive commands from city management system (dim/brighten, maintenance mode) - Commands are typically sent during business hours (8 AM - 6 PM, Monday-Friday) - Battery backup must last 72 hours (in case of power failure)

You’re configuring eDRX (Extended Discontinuous Reception) mode to balance reachability and power consumption.

Answer & Detailed Explanation

Correct Answer: C) 10.24 minutes (~141 paging checks per day)


10.7.4 What the eDRX cycle controls

The eDRX cycle largely determines downlink latency:

  • Shorter cycle → device checks paging more often → faster command delivery, higher energy use
  • Longer cycle → fewer paging checks → lower energy use, slower command delivery

10.7.5 Compare the options

A) 20.48 seconds

  • Worst-case command latency: ~20 seconds (very responsive)
  • Paging checks: ~4,200/day (very frequent wake-ups)
  • Only worth it if the application truly needs near-real-time control

B) 2.91 hours

  • Worst-case command latency: ~3 hours
  • Too slow for typical streetlight operational commands (dim/brighten/maintenance workflows)

D) PSM only

  • If the controller only listens after its hourly report, worst-case command latency is ~60 minutes
  • That often fails usability expectations for interactive city control

C) 10.24 minutes ✅ - Worst-case command latency: ~10 minutes (good trade-off for city operations) - Paging checks: ~141/day (moderate overhead)


10.7.6 Battery-backup sanity check (order-of-magnitude)

Using the same assumption as earlier in this chapter (paging check ≈ 100 ms @ 50 mA):

Energy per paging check:
50 mA × 0.1 s = 5 mAs = 0.00139 mAh

Paging energy per day:
A) 4,200 × 0.00139 mAh ≈ 5.8 mAh/day
B) 8 × 0.00139 mAh ≈ 0.01 mAh/day
C) 141 × 0.00139 mAh ≈ 0.20 mAh/day

Over a 72-hour outage, option C adds well under 1 mAh from paging while keeping command latency in the ~10-minute range.


10.8 Worked Example: PSM/eDRX Configuration for Smart Gas Meter

Worked Example: PSM/eDRX Configuration for Smart Gas Meter

Scenario: A utility company is deploying 25,000 NB-IoT gas meters across a metropolitan area. The meters must report daily consumption, support monthly firmware updates, and achieve 12+ year battery life on a 14.5Ah lithium-thionyl chloride (LTC) cell.

Given:

  • Battery: 3.6V 14.5Ah LTC cell (52.2 Wh capacity)
  • Carrier: T-Mobile NB-IoT (Band 12, 700 MHz)
  • Module: u-blox SARA-R410M
  • Reporting: Once daily at 3 AM (50 bytes payload)
  • Firmware updates: Monthly OTA (max 64 KB, during 4-hour maintenance window)
  • Coverage: Mixed urban/suburban (80% normal coverage, 20% extended coverage CE1)
  • Module specifications:
    • Active TX current (CE0): 180 mA @ +23 dBm, 3 seconds
    • Active TX current (CE1): 220 mA @ +23 dBm, 8 seconds (32 repetitions)
    • Active RX current: 40 mA
    • PSM sleep current: 2.7 µA (T-Mobile optimized)
    • eDRX sleep current: 12 µA
    • Network attach: 250 mA, 6 seconds

Steps:

  1. Design PSM configuration for normal operation (daily reporting):

    PSM Parameters:
    T3412 (Periodic TAU): 24 hours = 86,400 seconds
    T3324 (Active Timer): 20 seconds (sufficient for ACK)
    
    AT Commands:
    AT+CPSMS=1,"","","01000100","00000101"
    // T3412 extended value: 01000100 = 24 hours (unit: 10 hours, value: 4 x 6 = 24h)
    // T3324: 00000101 = 20 seconds (unit: 2 seconds, value: 10 x 2 = 20s)
  2. Calculate daily energy consumption (normal coverage - 80% of meters):

    Wake + Attach: 250 mA × 6 s = 1,500 mAs = 0.417 mAh
    TX (CE0): 180 mA × 3 s = 540 mAs = 0.150 mAh
    RX (ACK): 40 mA × 2 s = 80 mAs = 0.022 mAh
    Active Timer (T3324): 40 mA × 20 s = 800 mAs = 0.222 mAh
    PSM Sleep: 2.7 µA × 23.99 h = 64.77 µAh = 0.065 mAh
    
    Daily total (CE0): 0.876 mAh/day
  3. Design eDRX configuration for firmware update window:

    Monthly maintenance window: 4 hours (midnight to 4 AM)
    eDRX cycle: 2.56 seconds (PTW = 1.28s, eDRX = 2.56s)
    
    AT Commands (enable during maintenance):
    AT+CEDRXS=2,5,"0010"
    // WB-S1 mode: 5
    // Requested eDRX: 0010 = 2.56 seconds
    
    Energy during 4-hour eDRX window:
    eDRX Sleep: 12 µA × 4 h = 48 µAh = 0.048 mAh
    Paging checks: 5,625 cycles × 40 mA × 5 ms = 1,125 mAs = 0.313 mAh
    Firmware download (if available): 64 KB @ 20 kbps = 25.6 s active
      TX/RX: 150 mA × 26 s = 3,900 mAs = 1.083 mAh
    
    Monthly firmware update total: 0.048 + 0.313 + 1.083 = 1.444 mAh/month
    Daily average (firmware): 1.444 / 30 = 0.048 mAh/day
  4. Calculate battery life with safety margins:

    Weighted daily consumption:
    CE0 meters (80%): 0.876 mAh/day
    CE1 meters (20%): 1.820 mAh/day
    Firmware overhead: 0.048 mAh/day
    Fleet average: (0.8 × 0.876) + (0.2 × 1.820) + 0.048 = 1.113 mAh/day
    
    Battery capacity: 14,500 mAh
    Derating factors:
    - Temperature cycling (-30°C to +60°C outdoor): -18%
    - Self-discharge 12 years: -12%
    - End-of-life reserve: -15%
    - Safety margin: -10%
    Usable capacity: 14,500 × 0.82 × 0.88 × 0.85 × 0.90 = 8,001 mAh
    
    Battery life: 8,001 / 1.113 = 7,189 days = 19.7 years ✓

Result:

Parameter Configuration
T3412 (TAU interval) 24 hours
T3324 (Active timer) 20 seconds
eDRX cycle (maintenance) 2.56 seconds
Daily consumption (fleet avg) 1.113 mAh
Usable battery capacity 8,001 mAh
Battery life (calculated) 19.7 years
Battery life (target) 12 years ✓

Key Insight: The hybrid PSM + scheduled eDRX approach enables both ultra-long battery life (19+ years) and monthly firmware update capability. The key design principle is using PSM (2.7 µA) for 99.5% of the time and only enabling eDRX (12 µA) during predictable maintenance windows.

10.9 Interactive: eDRX Cycle Energy Calculator

10.10 Practice Exercises

  1. Pick a use case (metering, asset tracking, smart parking) and write the uplink schedule (payload bytes and messages/day).
  2. Decide whether you need downlink and choose PSM, eDRX, or a hybrid (PSM normally + eDRX during maintenance windows).
  3. Choose initial timers (T3324 and T3412) and justify them in one sentence each (latency vs battery trade-off).
  4. Estimate daily energy: mAh/day = I_sleep×t_sleep + I_tx×t_tx + I_rx×t_rx (use typical module currents from your modem datasheet).
  5. Stress-test the design for worst case (deep indoor): assume higher repetitions and longer transmit time; re-check the 10-year target.

If you want to validate the configuration on real hardware, continue with NB-IoT Labs and Implementation.

10.11 Summary

10.12 Concept Relationships

PSM and eDRX form the foundation of NB-IoT’s power optimization system:

The key insight is that PSM and eDRX are not competing options but complementary tools - optimal designs often use both, switching between modes based on application state and downlink urgency.

10.13 See Also

Related Power Topics:

Hands-On Application:

Comparison:

Design Tools:

Common Pitfalls

The network may grant different T3412/T3324 values than requested due to operator policy or network capacity management. An operator may cap T3412 at 24 hours regardless of requested values, or enforce minimum T3324 of 30 seconds. Firmware that uses requested timer values without reading granted values from the +CPSMS? response will have incorrect timing expectations. Always read granted values after setting PSM parameters and adapt application duty cycle accordingly.

PSM makes the device unreachable for downlink until the next TAU (T3412 expiry) or the device initiates an uplink connection. Using PSM for a device that needs to receive cloud-triggered alerts within 10 seconds is fundamentally incompatible: PSM T3412 minimum useful duration is ~1 minute, and the device wakes to transmit, then immediately re-enters PSM. Use eDRX for applications requiring <10 minute downlink latency, and PSM only for devices that initiate all communications themselves.

Some NB-IoT implementations wake from PSM, immediately transmit data, and re-enter PSM in <1 second. This does not allow time for: pending downlink data delivery, device management commands (firmware update triggers), or configuration updates. Implement a configurable “active window” after each uplink transmission: transmit data → wait T3324 seconds for downlink → check for pending commands → enter PSM. Set T3324 to 15–30 seconds for applications that may receive occasional downlink commands.

eDRX support varies by NB-IoT deployment: some operators have deployed eDRX, others have not. Configuring eDRX on an operator that does not support it results in the modem ignoring the eDRX request and falling back to standard DRX, consuming more power than expected. Query eDRX support by checking the +CEDRXP URC after connection — if the URC is absent, the operator does not support eDRX. Test on the actual carrier in the target deployment region, not in a lab with a different operator.

10.14 What’s Next

Topic Chapter Description
Channel Access NB-IoT Channel Access Uplink/downlink channel structure and single-tone vs multi-tone optimization
Coverage Enhancement NB-IoT Coverage Enhancement Repetition mechanisms and MCL calculations for deep indoor coverage
Labs and Implementation NB-IoT Labs and Implementation Configure PSM and eDRX timers with AT commands on real hardware
Practical Guide NB-IoT Practical Guide Common PSM/eDRX configuration mistakes and how to avoid them