9  NB-IoT Power Optimization

PSM, eDRX, and Battery Life Engineering

In 60 Seconds

NB-IoT achieves 10+ year battery life through two complementary power modes: PSM (Power Saving Mode) turns the radio completely off (3-10 uA sleep current) controlled by T3412 and T3324 timers, while eDRX (Extended Discontinuous Reception) maintains periodic paging windows for downlink reachability at the cost of slightly higher idle power (~15 uA).

Key Concepts
  • RAI (Release Assistance Indicator): NB-IoT feature allowing device to signal to the network that no further data is expected, triggering immediate connection release vs waiting for inactivity timer
  • Early Data Transmission (EDT): NB-IoT Release 15 feature allowing small payloads to be sent during the RACH procedure (before full connection establishment), reducing connection overhead
  • WUS (Wake-Up Signal): NB-IoT Release 15 feature where the base station sends a short signal before paging, allowing devices to skip paging decoding if no WUS is received — saving significant RX energy
  • PSM Timer Negotiation: Device requests T3412/T3324 values via AT+CPSMS; network may grant different values; device must use granted values (check via AT+CPSMS? after request)
  • Energy per Transmission Equation: E = (I_TX × t_TX + I_RX × t_RX + I_idle × t_connection) × V_supply; minimize by reducing t_connection overhead via RAI and EDT
  • IoT Power Profiler: Nordic Semiconductor Power Profiler Kit 2 (PPK2) — hardware tool for µA-resolution current measurement; essential for NB-IoT power budget validation
  • Active Timer Optimization: Minimize T3324 (Active Timer) to the shortest duration that allows pending downlink data to be delivered; typical: 5–15 seconds; each extra second costs ~30–100 µAs
  • Antenna Efficiency Impact: A poorly matched PCB trace antenna adding 3 dB insertion loss requires the modem to transmit at 3 dB higher power to maintain link quality, doubling TX energy

9.1 Learning Objectives

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

  • Configure PSM timers: Determine optimal T3412 and T3324 values for a given application’s reporting interval and downlink requirements
  • Design eDRX cycles: Justify eDRX cycle length and PTW duration that balance power savings with downlink responsiveness for specific use cases
  • Evaluate power mode trade-offs: Compare PSM-only, eDRX-only, and hybrid mode strategies and recommend the best fit for a given deployment scenario
  • Calculate battery life budgets: Quantify daily energy consumption accounting for sleep current, TX duration, CE repetitions, and environmental derating factors

NB-IoT devices achieve multi-year battery life through two key features: PSM (Power Saving Mode) lets devices sleep deeply between transmissions, and eDRX (Extended Discontinuous Reception) reduces how often devices check for incoming messages. This chapter shows how to configure these features for maximum battery life.

“How do you make a battery last ten years?” Bella the Battery asked. “The secret is PSM – Power Saving Mode. When Sammy finishes sending his data, I tell the radio to completely shut off. My power drops from 15 milliamps all the way down to 5 microamps – that is three thousand times less power! I barely use any energy while sleeping.”

“Two timers control the whole thing,” Max the Microcontroller explained. “T3412 is the big timer – it tells me how long I can sleep before I need to check in with the network. I usually set it to 24 hours for a water meter. T3324 is the small timer – it tells me how long to stay awake after sending data, usually just 30 seconds to wait for a reply.”

Sammy the Sensor jumped in. “eDRX is for when I need to be reachable sometimes. Instead of sleeping completely like PSM, I set an alarm to wake up every few minutes and check if the server has a message for me. It uses more power than PSM, but at least the server can send me a firmware update or a new configuration command.”

“Here is a real example,” Lila the LED said. “A smart water meter with a 5 amp-hour battery, sending one 100-byte reading per day with PSM enabled: sleep current is 5 microamps for 23 hours and 59 minutes, active current is 200 milliamps for about 5 seconds. That math works out to over ten years of battery life. That is the power of proper power optimization!”

9.2 Power Saving Mode (PSM) Deep Dive

PSM is the foundation of NB-IoT’s 10+ year battery life promise. When in PSM, the device’s radio is completely off, reducing current consumption to 3-10 uA.

9.2.1 PSM Timer Configuration

Two timers control PSM behavior:

T3412 (TAU Timer - Extended Periodic Tracking Area Update)

  • Determines how long the device can sleep while remaining registered
  • Range: 2 seconds to 310 hours (configurable in 3GPP Release 13+)
  • Device must send TAU before T3412 expires or be de-registered
  • Typical values: 24-72 hours for smart metering

T3324 (Active Timer)

  • Determines how long device stays in active mode after data transfer
  • Range: 2 seconds to 186 minutes
  • Device enters PSM when T3324 expires
  • Typical values: 10-60 seconds (just long enough for ACK)

NB-IoT PSM mode 24-hour timeline showing device wake-up, data transmission at 200 mA for 1-2 seconds, T3324 active timer countdown of 30 seconds at idle power, then deep PSM sleep at 3-5 microamps until T3412 periodic TAU timer expires after 24 hours, triggering brief re-registration before returning to sleep.

NB-IoT PSM timeline
Figure 9.1: NB-IoT PSM Mode 24-Hour Sleep Timeline with T3412/T3324 Timers

9.2.2 PSM Power Consumption

State Current Duration Notes
PSM Sleep 3-10 uA Hours/days Radio completely off
Waking 50 mA ~100 ms Restoring context
RRC Connected 40-80 mA 0.5-2 s Signaling exchange
TX Active 200-300 mA 0.2-2 s Data transmission

Consider a water meter reporting once daily with T3412=24h and T3324=30s. With a 6,000 mAh battery:

Daily energy budget: \[E_{\text{sleep}} = 5 \text{ µA} \times 23.99 \text{ h} = 120 \text{ µAh} = 0.120 \text{ mAh}\] \[E_{\text{wake}} = 50 \text{ mA} \times 0.1 \text{ s} = 5 \text{ mAs} = 0.0014 \text{ mAh}\] \[E_{\text{TX}} = 220 \text{ mA} \times 1.5 \text{ s} = 330 \text{ mAs} = 0.092 \text{ mAh}\] \[E_{\text{total}} = 0.120 + 0.0014 + 0.092 = 0.213 \text{ mAh/day}\]

Battery life: \[\text{Life} = \frac{6{,}000 \text{ mAh}}{0.213 \text{ mAh/day}} = 28{,}169 \text{ days} \approx 77 \text{ years (theoretical)}\]

With 40% derating for temperature and self-discharge: ~46 years realistic, far exceeding the 10-year target. Sleep current dominates, confirming that PSM mode is remarkably efficient for daily-reporting meters.

9.2.3 PSM Limitations

Important: During PSM, the device is completely unreachable.

  • Network cannot page the device
  • Downlink messages are queued until device wakes
  • Emergency commands cannot be delivered
  • Firmware updates must wait for scheduled wake-up

This is why PSM is ideal for uplink-only applications (metering, environmental monitoring) but problematic for applications requiring downlink responsiveness.

9.3 Extended Discontinuous Reception (eDRX)

eDRX provides a middle ground between always-connected (high power) and PSM (unreachable). The device periodically wakes to check for paging messages.

9.3.1 eDRX Configuration

eDRX Cycle: How long between paging windows

  • Range: 5.12 seconds to 2.91 hours (NB-IoT specific)
  • Longer cycles = better battery life, slower downlink response

Paging Time Window (PTW): How long device listens during each cycle

  • Range: 2.56 seconds to 40.96 seconds
  • Longer PTW = better downlink reception, higher power

9.3.2 eDRX Power Consumption

eDRX Cycle (20.48 seconds example):

|----Sleep period-----|--PTW--|----Sleep...
|     (0.5 mA avg)    | 2.5s  |
|                     |       |
|<--- 20.48s -------->|       |
|                     |       |
|  Cannot receive     | Check |
|  downlink           | page  |

Average current during eDRX:

Sleep current: 0.5 mA (light sleep, maintaining timing)
Active during PTW: 40 mA
PTW duration: 2.56 seconds every 20.48 seconds

Average current = (17.92s x 0.5mA + 2.56s x 40mA) / 20.48s
                = (8.96 + 102.4) / 20.48
                = 5.4 mA average

Compare to:
- PSM: 0.003 mA (1800x lower!)
- Always connected: 40 mA (7x higher)

9.4 PSM vs eDRX: Mode Selection

Comparison chart of PSM and eDRX power modes. PSM offers 3-10 microamp sleep current with no downlink reachability, ideal for uplink-only sensors. eDRX offers 15 microamp average with periodic paging windows for downlink, suitable for devices needing occasional commands. Decision flow: if downlink needed, choose eDRX; if uplink-only, choose PSM.

PSM vs eDRX comparison
Figure 9.2: Comparison of PSM and eDRX power modes showing key characteristics and trade-offs

9.4.1 Mode Selection Guide

Use Case Uplink Frequency Downlink Needed? Recommended Mode
Smart meter Daily Rare (monthly firmware) PSM + scheduled wake
Asset tracker Hourly Yes (change reporting interval) eDRX (wake every 20 min)
Smart parking Continuous (occupancy change) No PSM (wake on sensor trigger)
Remote control Low Yes (real-time commands) eDRX or RRC Connected

9.5 Worked Example: PSM vs eDRX for Fleet Tracker

Scenario: A fleet management company deploys NB-IoT trackers in delivery vehicles. The vehicles operate 10 hours per day (7 AM - 5 PM) with varying requirements.

Given:

  • Vehicle operation: 10 hours/day active, 14 hours/day parked
  • Active tracking: Location every 5 minutes
  • Parked mode: Location every 2 hours + instant wake on motion
  • Downlink requirements:
    • During operation: Route updates every 30 minutes
    • Parked: Theft alerts (immediate delivery required)
  • Battery: 10,000 mAh (replaceable annually)
  • Target battery life: 12 months minimum

9.5.1 Design: Mode Transitions

Vehicle tracker state machine with three modes: PARKED state using PSM at 3 microamps with 2-hour position updates and accelerometer wake for theft, DRIVING state using eDRX with 5-minute position updates and 20-second paging cycle for route updates, and THEFT ALERT state in connected mode at 200 mA for immediate reporting. Transitions triggered by accelerometer motion detection and time-of-day scheduling.

Vehicle tracker state machine
Figure 9.3: Vehicle tracker state machine showing transitions between PARKED (PSM), DRIVING (eDRX), and THEFT ALERT (Connected) modes

9.5.2 Calculation: DRIVING Mode Power

Active hours: 10 hours/day = 36,000 seconds

Position updates:
- Frequency: Every 5 minutes = 120 per day (active)
- GPS fix: 1 second at 30 mA = 30 mAs
- NB-IoT TX: 0.5 second at 200 mA = 100 mAs
- Total per update: 130 mAs

eDRX listening:
- eDRX cycle: 20.48 seconds
- Paging windows per hour: 176
- Listen duration: 10 ms at 40 mA = 0.4 mAs each
- Per hour: 176 x 0.4 = 70.4 mAs
- 10 hours: 704 mAs

Sleep between eDRX:
- Duration: ~35,802 seconds
- Current: 10 uA
- Energy: 358 mAs

Daily DRIVING consumption:
- Position TX: 120 x 130 = 15,600 mAs = 4.33 mAh
- eDRX listening: 704 mAs = 0.20 mAh
- Sleep: 358 mAs = 0.10 mAh
- Total DRIVING: 4.63 mAh/day

9.5.3 Calculation: PARKED Mode Power

Parked hours: 14 hours/day = 50,400 seconds

Position updates (every 2 hours):
- Updates: 7 per day (parked period)
- GPS + TX: 130 mAs each
- Total: 910 mAs = 0.25 mAh

PSM sleep:
- Duration: ~50,390 seconds
- Current: 3 uA
- Energy: 151 mAs = 0.04 mAh

Accelerometer (always-on for theft detection):
- Current: 5 uA continuous
- 24 hours: 432 mAs = 0.12 mAh

Daily PARKED consumption:
- Position TX: 0.25 mAh
- PSM sleep: 0.04 mAh
- Accelerometer: 0.12 mAh
- Total PARKED: 0.41 mAh/day

9.5.4 Calculation: Total Battery Life

Total daily: 4.63 + 0.41 = 5.04 mAh

With 10,000 mAh battery:
Theoretical life = 10,000 / 5.04 = 1,984 days = 5.4 years

Apply derating:
- Usable capacity (80%): 8,000 mAh
- Temperature factor (90%): 7,200 mAh
- Aging over 1 year (85%): 6,120 mAh

Practical life = 6,120 / 5.04 = 1,214 days = 3.3 years

RESULT: 12-month target easily met with 2+ years margin!

NB-IoT theft alert optimization flowchart showing accelerometer interrupt triggering immediate PSM exit, followed by GPS fix acquisition in 1 second, NB-IoT transmission in 0.5 seconds, achieving total alert latency under 5 seconds compared to 2-hour delay with pure periodic PSM wake, with minimal battery impact since accelerometer draws only 5 microamps continuously.

Theft alert optimization
Figure 9.4: NB-IoT theft alert optimization: accelerometer-triggered wake achieves less than 5-second alert latency vs 2-hour delay with pure PSM, with minimal battery impact

Result: Use hybrid PSM/eDRX mode with accelerometer wake. During driving (7 AM - 5 PM): eDRX with 20.48s cycle for route updates. While parked (5 PM - 7 AM): PSM with 2-hour T3412, accelerometer-triggered immediate wake for theft alerts. This achieves 5-minute tracking during operation, <5 second theft alerts when parked, and 3.3-year battery life.

Key Insight: PSM and eDRX are not mutually exclusive - design a state machine that transitions between modes based on operational context. The accelerometer is critical - it enables instant theft detection while allowing PSM’s ultra-low power sleep.

9.6 Interactive: PSM vs eDRX Battery Life Calculator

9.7 Knowledge Check

Question: Power Saving Modes - PSM vs eDRX

You’re deploying 50,000 smart water meters using NB-IoT. Meters report water usage once per day at midnight. Utility company wants to occasionally send firmware update commands to meters (approximately once per month).

Which power-saving mode should you use?

  1. PSM only (deep sleep, wake up to send data, no downlink listening)
  2. eDRX only (periodic wake-ups to check for downlink messages)
  3. PSM + eDRX combination (deep sleep, but brief wake-ups for downlink)
  4. No power saving (always connected for instant downlink)
Answer and Detailed Explanation

Correct Answer: C) PSM + eDRX combination

9.7.1 Understanding the Trade-offs

Mode Sleep Current Downlink Capability Battery Life Use Case
No power saving 100mA Instant (always listening) 20 hours Not viable for battery devices
eDRX only 1-5uA Periodic (every 2.91 hours max) 2-5 years Fair compromise
PSM only 3-10uA None (device unavailable) 10-15 years No downlink possible
PSM + eDRX 5-15uA Periodic during wake-ups 5-10 years Best balance

9.7.2 Why PSM + eDRX Combination is Optimal

Hybrid Approach:

Normal operation (29 days/month):
- PSM sleep at 10 uA
- Daily wake for meter reading
- No eDRX overhead

Firmware update month (1 day):
- Enable eDRX for 24 hours
- Device wakes every 2.91 hours to check for downlink
- Download firmware in chunks
- Return to PSM after successful update

Battery Life with Hybrid:

Normal month: 55.4 mAh
Firmware update month: 74 mAh
Annual total: 683 mAh

Battery life with 8,000 mAh battery:
8,000 / 683 = 11.7 years

9.7.3 Why Other Options Fall Short

A) PSM Only: Cannot receive firmware updates (device unreachable) B) eDRX Only: Higher power consumption (wakes even when no downlink needed) D) No Power Saving: 20-hour battery life (completely unusable)

Real-World Example: Kamstrup Water Meters

  • Default mode: PSM only (10-15 year battery life)
  • Firmware update mode: Enable eDRX temporarily
  • Update success rate: 99.2% (no technician visits needed)

9.8 AT Command Configuration

Configuring PSM with eDRX on Quectel BG96:

// Step 1: Enable PSM with eDRX
AT+CPSMS=1,"00000001","00000001","00100001","00000001"
// T3412 (TAU timer): 24 hours
// T3324 (Active timer): 30 seconds

// Step 2: Configure eDRX (only when firmware update pending)
AT+CEDRXS=2,5,"0101"
// Mode 2: Enable eDRX
// AcT 5: E-UTRAN (NB-IoT)
// eDRX cycle: 2.91 hours (configurable 20.48s - 2.91 hours)

// Step 3: Normal operation - disable eDRX
AT+CEDRXS=3,5
// Disable eDRX, rely on PSM only

9.9 Environmental Factors That Erode Battery Life

Datasheet battery life calculations assume laboratory conditions. Real deployments encounter environmental stresses that can cut predicted battery life by 30-60%. The following table captures the most common derating factors.

9.9.1 Temperature Derating

Battery chemistry is the dominant factor. Most NB-IoT devices use lithium thionyl chloride (LiSOCl2) primary cells, which suffer significant capacity loss at temperature extremes.

Condition Capacity Derating Effective Battery Life (from 11.7-year baseline) Typical Deployment
20-25C (lab conditions) 0% (baseline) 11.7 years Indoor, climate-controlled
0C to -10C -15 to -25% 8.8-10.0 years Northern Europe, unheated outdoor
-20C to -30C -30 to -50% 5.9-8.2 years Nordic winter, freezer rooms
+50C to +60C -10 to -20% 9.4-10.5 years Desert, rooftop, engine compartment

9.9.2 Signal Quality Impact

Poor RF conditions force more retransmissions and longer active periods, both of which drain the battery faster than any power-saving mode can compensate.

RSRP (signal strength) Typical Retransmissions Active Time per Message Battery Impact
> -100 dBm (good) 0-1 1-2 seconds Baseline
-110 to -120 dBm (fair) 2-4 3-8 seconds 2-4x per message
-120 to -130 dBm (poor, CE1) 8-32 10-30 seconds 10-15x per message
< -130 dBm (marginal, CE2) 64-128 30-120 seconds 30-60x per message

Real-world example: A parking sensor deployed in an underground garage with -128 dBm signal uses Coverage Enhancement Level 2. Each 24-byte uplink requires 64 repetitions, consuming 45 seconds of active time instead of 1.5 seconds at street level. Predicted battery life drops from 11.7 years to approximately 2.1 years – an 82% reduction solely from RF conditions.

Design guideline: Always perform an RF survey before deployment. If RSRP is consistently below -120 dBm, either improve antenna placement (external antenna, higher mounting) or consider adding a small cell / repeater. The cost of a $200 repeater is trivial compared to replacing 500 devices with dead batteries 8 years early.

9.10 Summary

9.11 Concept Relationships

Power optimization in NB-IoT involves multiple interacting design decisions:

The key insight is that power optimization is a system-level design problem, not just a configuration checkbox - achieving 10+ year battery life requires coordinated decisions across power modes, timers, coverage class, and application messaging patterns.

9.12 See Also

Related NB-IoT Topics:

Practical Application:

Design Resources:

Common Pitfalls

Setting T3324 (Active Timer) to 30 seconds “to ensure all downlink data arrives” costs 30 seconds of 3–10 mA idle-mode current after every uplink transmission. For a device transmitting hourly, this adds 30 µAh per hour vs 0.5 µAh with a 2-second T3324. On a 10 Ah battery, the difference is 5 months vs 3 years of battery life. Keep T3324 at the minimum time needed to receive expected downlink responses (typically 5–10 seconds for cloud acknowledgments).

NB-IoT Release 13+ supports RAI (Release Assistance Indicator) set to “no further uplink/downlink” in the last uplink data PDU. This signals the network to immediately release the RRC connection after receiving the data, rather than waiting for the inactivity timer (typically 10–20 s). Not using RAI wastes 10–20 seconds of idle-mode current (~5 mA × 15 s = 75 µAh) after every transmission. Set RAI=2 (no further uplink or downlink expected) in AT+NSOSTF command for one-way telemetry applications.

Power budgets that calculate energy per transmission based on a single HARQ round underestimate real-world energy by 2–50× in poor coverage areas. Each failed HARQ round requires re-transmission of the entire transport block. In CE Mode B with 2048 repetitions, a single uplink message may require 200–2000 ms of continuous transmission. Build coverage-weighted energy models: 70% devices at CE Level 0 (nominal), 20% at CE Level 1, 10% at CE Level 2, to estimate fleet-average battery life.

NB-IoT module power optimization often focuses on modem sleep current but ignores host MCU, sensors, and peripherals. An nRF9160 in PSM uses 2.5 µA, but a connected accelerometer in continuous mode may consume 100–300 µA, dominating total system power by 40–120×. Build a full system power audit: list every powered component, document their sleep and active currents, and verify that all peripherals enter their lowest power state when the NB-IoT modem enters PSM.

9.13 What’s Next

Next Topic Description
NB-IoT Practical Guide Common deployment mistakes and real-world pitfalls in power mode configuration
NB-IoT Lab Simulation Hands-on ESP32 simulation of PSM and eDRX concepts with AT commands
NB-IoT Power and Channel Channel access mechanisms and how power modes interact with uplink configuration
NB-IoT Coverage Enhancement How coverage enhancement levels multiply energy consumption per message