Readiness checklist
Readiness checklist
Readiness Checklist
Use this checklist before accepting a FANET-VANET design:
Mobility
- Are vehicle and UAV motion modeled separately? Vehicles follow road constraints, while UAVs follow mission paths in three dimensions. Separate position and motion records help assess whether both sides can sustain a useful contact.
- Are stale position records expired? Record observation times for each side. Movement can make a recent path stale quickly, so an old position should not continue to imply that a contact is available.
- Is the contact useful for the message priority? Judge freshness and available paths against how long the message may wait. Urgent alerts need a current useful path; delayed records may be carried when the mission permits waiting.
Links
- Is air-to-ground quality measured recently? Record signal quality, packet delivery history, and observation time together. Vehicle and UAV movement can make an earlier contact stale, so judge freshness against the current message priority.
- Is roadside or gateway reachability known? Compare current exits to determine whether data can leave the local contact area through a useful path.
- Is line-of-sight risk recorded when relevant? Include this risk in the link record so a handoff decision can be reviewed alongside measurement freshness and the selected or rejected paths.
Traffic
- Are safety alerts separated from delayed records? Different priorities need different forwarding rules. Urgent alerts should use the freshest useful contact, while delayed records may wait for a more trustworthy path when permitted.
- Is buffer permission explicit? Record whether the data may wait, how long it may wait, and why it was carried instead of forwarded. Retain its original time so its age remains visible.
- Are lower-priority flows prevented from blocking urgent traffic? Carrying bulk records until a stable gateway contact appears can protect scarce link capacity for urgent messages.
Handoff log
- Are selected and rejected paths logged? Record the chosen contact or buffering decision and why alternatives were not used. Include record freshness and priority class so the choice can be understood in its original conditions.
- Are handoff outcomes visible? Distinguish delivered, buffered, retried, expired, and failed outcomes, with a reason for failure. A selected path alone does not show whether delivery occurred.
- Can a delivery gap be explained after the mission? Connect the outcome to contact conditions and buffer reasons. These records help distinguish a design problem from a temporary partition.