Experiment 2: Mobility and Handover
Experiment 2: Mobility and Handover
Experiment 2: Mobility and Handover
LTE-M is often chosen for devices that move across cells. Do not reduce that to a single speed number. The real question is whether the device can keep its service behavior within the application’s tolerance while signal quality, cell selection, and network policy change.
Step 2: Log movement and delivery on your own modem
- In the modem terminal, start a timestamped log of serving cell, signal quality, registration state, sent payload ID, and acknowledgement.
- Move along a route with a known weak segment while the tracker sends numbered test messages; keep the antenna and enclosure fixed.
- Mark the point where the serving cell changes and compare it with buffered messages and their eventual server receipts.
- Record whether alerts met their deadline and whether old positions were discarded instead of replayed as current.
- This example used no cellular modem or operator account, so no handover or delivery result was measured here; the fields above are the required on-hardware evidence.
Serving-cell quality
Track signal strength and quality trends, not only a one-time signal reading.
Neighbor-cell measurements
Record whether the modem can see stronger candidate cells before the serving cell becomes unusable.
Application continuity
Check whether payload delivery, buffering, and retry behavior stay within the service requirement during movement.
Mobility Lab Questions
Start by which payloads can be delayed until the device reaches a stable cell? Then which alerts must be sent immediately while moving? Next how will the device behave when the network does not permit the expected mobility behavior? Finally what local buffering rule prevents stale location data from being sent later as if it were current?