← Back to the chapter · Next detail →
Technical detail · NB-IoT Fundamentals
Measure the complete transaction
Build the energy tradeoff from phases. A real transaction includes search or resume, random access, security and context handling where needed, payload transfer, acknowledgement or application response, active timer behavior, paging windows when eDRX is used, retries, logging, host work and return to sleep. Poor coverage and recovery can make the radio-active phases expensive even when sleep current is very low.
Payload shape matters as much as size. A compact binary reading with a stable acknowledgement path behaves differently from verbose JSON, a TLS session that renegotiates too often, or a firmware workflow that repeatedly wakes the radio. Frequent acknowledgements and large updates can erase a promising low-power design. Measure the protocol stack the product will ship, including certificate handling, DNS or APN behavior, duplicate handling and the application’s response to a late record.
Timer behavior is negotiated. Firmware requests PSM and eDRX values; the network grants the values the device must use. Store granted timers and adapt scheduling from measured grants rather than configuration intent alone. If a grant changes after a network or SIM-profile update, reopen the fit record instead of retaining stale battery assumptions. Coverage-enhancement repetitions, repeated access attempts and retries can dominate energy and latency, so compare traces from good, marginal and failed sites.