โ† Back to the chapter

Technical detail ยท Practice: NB-IoT Modem Bring-Up

Under the Hood: Requested Timers Are Not Granted Behavior

Under the Hood: Requested Timers Are Not Granted Behavior

NB-IoT power behavior depends on both the device request and the network response. The modem can request PSM or eDRX, but the operator network decides what it grants, and the whole board still has to enter the expected low-power state.

Recovery also has hidden state. A modem reset, weak-coverage attach loop, cloud outage, or low-battery restart can turn a successful demo into a battery drain or duplicate-message problem. That is why the lab pairs modem logs with current traces, cloud receipts, retry limits, and owner actions. The application has to know whether a reading was created before or after a reconnect, whether a payload was acknowledged, and whether retrying it would create a duplicate event.

The timer problem has two layers. First, the network may grant different active-time, periodic-update, PSM, or eDRX behavior than the firmware requested. Second, the board may fail to reach the expected low-power state even when the modem does. Regulators, sensors, level shifters, pull-ups, debug interfaces, and host firmware can keep consuming current. A credible power result therefore needs both modem readback and whole-board measurement.

Coverage enhancement and retry behavior are another reason to test the full sequence. In poor conditions, a device may spend more time searching, registering, repeating transmissions, or waiting for a response. That can erase the energy advantage expected from long sleep intervals. The under-the-hood lesson is simple: NB-IoT bring-up is not a single attach command. It is a state machine whose states must be logged, measured, bounded, and tied to product behavior.

That state machine also needs owner rules. Firmware should cap retry loops, label queued payloads with their original measurement time, and expose enough diagnostics for support to know whether the failure was radio, identity, packet context, cloud, or power related. Without those rules, a device can look healthy after recovery while quietly spending too much energy or uploading data with the wrong operational meaning.

โ† Back to the chapter