LwM2M Lifecycle Workbench
LwM2M Lifecycle Workbench
LwM2M lifecycle narrated tour
Play silently with captions on provisional storyboard timing; narration audio is pending. Production pacing is not protocol time. Choose Reduced motion for a complete still at each beat.
Play the tour to open the workbench. Pause, replay a beat, or read the full transcript below. Unsupported processes keep the existing frame and provide captions only.
Full transcript — LwM2M lifecycle (8 beats)
B1 — Battery sensor lifecycle
You operate a battery sensor that reports temperature to a remote service. Stale readings make its health uncertain, and a retired sensor that keeps reconnecting leaves unfinished work. Your job follows the sensor through its working life, including a firmware change and its eventual removal.
Model caption: Your battery sensor needs a managed working life, including updates and retirement.
B2 — Identity and firmware states
A device lifecycle connects identity, operation, and retirement. Joining the service is a transition within that life. Firmware also has distinct states: the image requested can differ from the image downloaded or the image actually running. Keeping those states distinct makes an update easier to understand.
Model caption: Lifecycle state includes identity, operation, and retirement. Requested, downloaded, and running firmware may differ.
B3 — Bootstrap and register
Bootstrap prepares the sensor to join. The client, meaning the device, obtains security settings and management server settings. Missing or mismatched credentials prevent registration. Then the client registers with the management server, announcing its endpoint name and supported objects. Objects group the resources the server can address.
Model caption: Bootstrap supplies Security and Server settings; Register announces the endpoint and its supported objects.
B4 — Observe, Notify, Write, Execute
During operation, the server observes a temperature resource. The client sends notifications when its value changes or reporting settings require an update. For management, a write operation changes a resource value, such as a threshold. Execute requests an action, such as rebooting the sensor.
Model caption: Observe sets up reporting; Notify sends values. Write changes a value; Execute requests an action.
B5 — Pull firmware delivery
Take a firmware delivery example from the workbench. With pull delivery, the server supplies a package address for the client to fetch. It writes to five slash zero slash one: firmware object five, instance zero, resource one. The update action has a different address: five slash zero slash two, ending in resource two.
Model caption: Pull delivery writes the package address to /5/0/1. The update action uses /5/0/2.
B6 — Deferred installation
Suppose the package has downloaded, but the user has postponed installation. Firmware Download is stage seven of the ten stage model. Advance once: seven plus one gives stage eight, Firmware Update. The firmware status says downloaded, deferred, and the server says awaiting approval. The package has arrived, while installation waits for policy or user approval to allow the update action.
Model caption: Stage 7 + one advance = stage 8. Firmware: downloaded, deferred. Server: awaiting approval.
B7 — Request versus outcome
The misconception is that an update request means installation succeeded. A request asks for an action; the deferred example leaves the package waiting. The firmware State and Update Result tell the operator what happened. An Execute response alone cannot establish the outcome.
Model caption: An update request is not an installation outcome. Read firmware State and Update Result.
B8 — Update and retire
After an update, the client can refresh its registration. At retirement, it deregisters so the server removes its endpoint. Retirement also removes account links, revokes credentials, and wipes local data. Follow the device by its state, from joining the service to leaving it cleanly.
Model caption: Endpoint removed. Retirement also removes account links, revokes credentials, and wipes local data. Follow the device by its state, from joining the service to leaving it cleanly.