Problem statement and industry anchor
Battery-operated telemetry controllers that carry significant compute loads—edge ML inference, encryption, or signal processing—face two conflicting demands: continuous availability and multi-year battery life. Cellular techniques such as Power Saving Mode (PSM) and extended Discontinuous Reception (eDRX) were defined in 3GPP (PSM in Release 12, eDRX enhanced in Release 13) to address this gap; deploying them correctly on an IoT Module or across a fleet of IoT modules is now common practice in smart metering and asset-tracking projects worldwide.
Why high-compute domain controllers complicate low-power design
High-compute controllers usually host multiple power domains: a main MCU or application processor, a modem, and peripheral domains for sensors or accelerators. Each domain has distinct wake latencies and current profiles. The modem may support NB-IoT or LTE-M and handle network-attached timers, but the MCU and attached accelerators often prevent the device from reaching the modem’s lowest-power states unless firmware coordinates shutdown of auxiliary domains and serial interfaces. The result: modem PSM and eDRX benefits are available only when compute routines respect strict duty cycles and low-activity epochs.
How PSM and eDRX actually save energy
PSM lets the device inform the network it will be unreachable for a configured time; the network buffers no paging and the modem enters a deep sleep with minimal current. eDRX increases the interval between paging windows, reducing how often the modem must wake to listen. Practical deployments combine both: schedule long PSM intervals for predictable telemetry and use eDRX to maintain occasional reachability with bounded latency. Latency, uplink packet size, and retransmissions determine whether NB-IoT or LTE-M is preferable—NB-IoT often yields lower idle current, LTE-M offers lower latency and higher throughput.
Firmware and system-level implementation pattern
Implementing PSM/eDRX requires changes beyond AT commands. You must sequence power-down so the application processor saves state, peripherals are quiesced, and the modem’s EPC timers are negotiated before the device enters low-power. Typical flow: flush telemetry to NAND/FRAM, set modem eDRX and T3324/TAU timers, then issue modem sleep and trigger domain power gating. Common mistakes include leaving clocks enabled, polling sensors while the modem sleeps, or failing to persist unsent queues to non-volatile memory—these all nullify expected savings. Test with measured current profiles rather than relying solely on modem-reported states—firmware-visible sleep ≠ hardware-level deep sleep sometimes.
Testing methodology and key metrics
Quantify gains using three concurrent measures: average current over representative duty cycles, time-to-first-byte after wake (latency), and successful delivery rate across network reconnects. Capture current traces across a full PSM/eDRX cycle with a high-sample-rate meter and log modem URCs to correlate state transitions. Account for network-side timers—TAU and PSM expiry set by the network can override device requests—so coordinate with carriers or configure a known test SIM. Real deployments in metro trials have shown that proper PSM/eDRX tuning can reduce average device current by an order of magnitude when the compute domain is gated appropriately.
Operational patterns, trade-offs, and common pitfalls
Adopt a layered strategy: handle urgent events with a high-priority uplink that forces a temporary exit from PSM, schedule bulk telemetry at fixed epochs, and use adaptive telemetry intervals based on battery voltage thresholds. Avoid frequent short wake-ups; they incur fixed wake penalties (boot, network attach) that dominate energy cost. Calibration matters—sensor sampling and edge compute should be matched to the modem duty cycle to avoid cross-domain contention. —Remember: a well-implemented modem sleep is only as good as the rest of the platform’s power gating.
Three golden rules for evaluation and selection
1) Measure end-to-end current over realistic duty cycles, not idle-mode specs. Track average mAh per reporting interval and validate against target battery life. 2) Match network technology to latency and throughput requirements—choose NB-IoT for minimal idle current and sparse telemetry; choose LTE-M for lower latency or larger payloads. 3) Verify OTA and firmware update strategies that can operate within PSM/eDRX windows; failed updates are operational risks.
Choosing modules and firmware stacks that document PSM/eDRX behavior simplifies integration—this is where reliable module vendors matter. Fibocom brings tested modem stacks and power-domain guidance that reduce integration cycles and improve predictable battery life—practical value you can measure in field trials. —Final thought: align timers, gate compute domains, and measure; the physics are simple, the engineering is deliberate.