Relay Path Practice
Relay Path Practice
Prove One Relay Path Before Calling It a Mesh
Picture a farm sensor that reaches the control room only while a battery relay remains awake. The direct radio link and the relayed path are different promises.
A gateway means the boundary system that joins local devices to another network or service.
Send marked packets over one hop and several hops, then remove one relay and restart the gateway. Keep node identities, route version, each next hop, time, retries, delivery, energy state, loss, and recovery result.
This test covers selected paths and faults, not the whole estate. The deeper sections compare forwarding, route repair, reliability, energy cost, gateway intake, and operating ownership.
Log both the relay path and gateway result. A drawn route cannot prove the app worked.
The worked application expires a payload after 30 seconds, so delivery alone is not enough. Sketch the end node, each relay, and the gateway, then record the role of every hop. A route observation should show which neighbor forwarded the marked packet and whether gateway intake accepted it. Test a lost neighbor or delayed relay to see when the application receives stale data or no data. Keep the route trace, gateway record, and recheck trigger together. A topology sketch tells reviewers what to test; it does not prove the route remains current at the site.
Record Template
- Purpose: What application outcome is this path supporting?
- Topology choice: Direct, relay, or mixed path, with the reason for choosing it.
- Relay role: Which nodes forward for others and what burden they accept.
- Route proof: What route behavior was observed, not only drawn.
- Gateway proof: What shows the message became accepted application data.
- Owner and trigger: Who maintains the proof, and what change reopens the decision?
Before approving a relay path, write a short route freshness record. It keeps the review anchored to message usefulness instead of hop count alone.
Message Boundary
Name the payload, freshness limit, duplicate rule, missing-data behavior, and application acknowledgement that makes delivery count.
Relay Burden
Name each relay role, queue limit, power impact, retry budget, health signal, and owner who responds when forwarding is no longer healthy.
Route Recheck
Name the link, queue, battery, mobility, gateway, or policy change that invalidates the current route proof and forces retest.
Technical boundaries. The relay-path comparison uses marked test packets on a small illustrative network; results from a real mesh depend on radio conditions, relay power and gateway behaviour.