← Back to the chapter · Previous detail

Technical detail · Fleet Device Management

State Reports and Recovery Evidence

A watchdog is a timer that can reset a stalled device; its state or last reset reason helps support staff see whether it has fired.

The device state machine is a key contract. Firmware must report the boot slot, package and settings versions, install attempt count, last contact, power, free storage, network type, reset reason, watchdog state, and whether rollback is possible. A device that reports only “online” may still lack power or space for an update. The platform needs those facts to decide whether to proceed, pause, or ask for help.

Update safety depends on more than sending a package. A spare boot slot, a signed manifest, a way to resume a transfer, and power and link checks can help recovery. MCUboot, RAUC, SWUpdate, Uptane, and TUF offer different pieces of this path. Record which parts the trial actually uses, which it mocks, and which it leaves for later. A single lab update does not prove the whole fleet can recover.

Support needs clear access rules. Keep secrets and personal data out of logs, limit commands by role, and record key changes and isolation actions. A retired device should not reconnect with its old identity. LwM2M is a protocol for managing constrained devices. It groups related device data and actions into objects, such as firmware update and connectivity objects. The trial must show which objects the device actually supports.

A reviewer should be able to trace one device through enrollment, settings, updates, support, replacement, and retirement using the records.

← Back to the chapter · Previous detail