AODV - Khan BMS Battlefield Management System
AODV — Ad-Hoc On-Demand Distance Vector — is one of the unglamorous primitives modern BMS lives or dies on. Here is how Khan BMS engineers it.
The first time AODV matters is the first time the link goes brown. It stops being an acronym on a wiring diagram and starts being the reason a formation still functions.
Strip the marketing and AODV is exactly what the standard says: Ad-Hoc On-Demand Distance Vector. Reactive routing protocol that builds routes on demand. AODV (RFC 3561) builds routes only when a source needs to send traffic, using route-request and route-reply broadcasts. It minimizes routing overhead in sparse-traffic networks but pays a setup latency cost on first use. AODV is a common reference design for low-overhead tactical and IoT mesh networks.
AODV earns its full keep at the Tumen — ten thousand nodes under a single human Khan. Span of control stays at ten because the hierarchy is fractal; AODV state aggregates upward through Minghan and Zuun before it ever reaches the Khan's console.
AODV is one of perhaps a dozen primitives that decide whether a modern force can fight through denial. Khan BMS is built on the premise that all of them deserve the same treatment.