Lab Scenario: Fleet Tracker
Lab Scenario: Fleet Tracker
animation
cellular-iot
ltem
lab
Lab Scenario: Fleet Tracker
Assume a fleet tracker sends a compact heartbeat while moving, stores richer diagnostic events locally, and raises immediate alerts for theft, crash, or route deviation.
Step 6: Turn the fleet scenario into a test record
- In the scenario table below, assign a payload ID and deadline to one heartbeat, one immediate alert, and one diagnostic upload.
- Set the heartbeat’s stale-data rule, the alert’s retry ceiling, and the diagnostic upload’s acceptable maintenance window.
- In the local state model, confirm that an accepted registration reaches
DATA_READYbefore the selected transfer state is considered. - On your own device, compare each modem send log with a cloud receipt and flag any late heartbeat that arrives after a newer location.
- The table is a worked design record; no fleet route or cloud receipt was generated for this example.
Requirement
Observe
Change
Explain
Heartbeat
Small payload, frequent enough for route visibility, but not every sensor sample.
Batch or suppress unchanged fields when movement is predictable.
Use compact payloads and bounded retries so the tracker does not spend energy on stale positions.
Immediate alert
Alert must be sent while the device may be moving or in weak coverage.
Prefer a more reachable mode during active journeys.
Do not hide emergency behavior behind a deep sleep interval unless the service accepts that delay.
Diagnostics
Larger payloads happen after faults, service visits, or scheduled maintenance windows.
Use a normal data session and upload when radio conditions are acceptable.
Separate normal telemetry budget from diagnostic and update budget.