Com Vector 4 bis – OBBDW

Principle

• Predefined point-to-point flights (“dotted way” segments) between sites B/C/D or isolated sites.
• Drones follow the same axes as the OBBHFH backbone (Bangui → Relay → Damara → Ombella), but physically.
• Payload: sealed µSD/USB containing encrypted bundles (gzip + manifest hash).
• Drop/pick in a weatherproof buffer box at each site, linked to the mini-server (K/H station).
• Direct integration with LuckyBlocks: export bundles on site A/B/C/D → copy to media → flight → import + ACK on arrival.
• Keeps “mayors’ network” messages flowing even if radio hops L1/L2/L3 are down or jammed.

Topology Bangui → Damara → Ombella (DW view)

Drone corridors reuse the same physical sites as the 5 GHz backbone.

[ Site A – Bangui (hill/house) ]
             ||
             ||  (drone corridor DW-A-B ~ 35–40 km)
             \/
[ Site B – Intermediate hill relay ]
             ||
             ||  (drone corridor DW-B-C ~ 35–40 km)
             \/
[ Site C – Damara (town hall / public building) ]
             ||
             ||  (drone corridor DW-C-D ~ 25–30 km)
             \/
[ Site D – Ombella-Bord (N12 × Ombella) ]

Possible corridors:
  • DW-A-B, DW-B-C, DW-C-D  → regular flights
  • DW-A-C, DW-B-D          → emergency flights (direct, longer)
      

• DW buffer boxes are installed right next to the backbone RPis.
• Each drone corridor is documented (distance, minimum altitude, obstacles, diversion points).

Drone fleet & performance

• 15-inch FPV drones:
  • Cruise speed: ~80 km/h easy, up to 150–200 km/h fast flight.
  • Typical range: 40–50 km per battery at brisk pace.
  • Example: Bangui → Damara (~80 km) doable in one leg at ~80 km/h.
• Drone network organization:
  • Drones prepositioned in each prefecture/town hall with charged batteries.
  • Battery charging centers around sites A/B/C/D (or small intermediate bases).
  • Drones can pick the nearest charging base based on wind, rain, etc.
• Centralized + decentralized piloting:
  • A small pilot group can cover ~300 km radius around Bangui.
  • Ready-to-fly drones are “rented” remotely: a pilot connects, runs the mission, releases the craft.
  • Local autonomous missions possible (waypoint, return home) when a town hall has a trained operator.

Network latency & FPV control via OBBHFH

The OBBHFH backbone gives ~10–20 ms typical latency, up to ~30 ms, similar to analog FPV video (~30 ms) and more responsive than some digital systems (DJI ~50–70 ms).

• Over ~100 km logical distance (several hops), latency stays near 30 ms, perfectly flyable FPV.
• Over ~300 km, may climb to ~100 ms, still flyable for planned flights.
• Pilots can stay centralized in Bangui while controlling drones within a 300 km radius (as long as video/telemetry ride the 5 GHz backbone).

This combo OBBHFH + OBBDW forms a digital aerial “defense belt” around Bangui and the mayors’ zone.

Procedures

• To do Buffer box: quick access, hash log, sealed media.
• To do Site script: global hash, signature, return ACK bundle.
• To do Operator checklist: flight plan, weather, seals, logbook.

Example full cycle for corridor DW-B-C:

1. Site B: export high-priority bundles (P0–P1) → write to µSD/USB.
2. Record global hash + signature, note in flight log.
3. Prep FPV drone (battery, mechanical check, GPS if needed).
4. Takeoff, fly to Site C per validated plan (weather OK).
5. On arrival: retrieve media, import bundles, verify hash, send ACK via backbone or next flight.
6. Cleanup/rotation: secure wipe, prep for next trip.

Security

• To do Minimal clear manifest (scope) + encrypted segments.
• To do Global hash + media signature before flight.
• To do Systematic ACK for local purge.

Extras:

• µSD/USB content is always end-to-end encrypted (mayors’ network model); the drone only carries opaque data.
• If a drone is lost, an adversary gets only a cipher blob + minimal metadata.
• Local buffers at stations A/B/C/D purge only after a signed ACK.

When to use

• Cross a river, relief, or radio-denied area.
• Maintain a regular “link” between two isolated bases.
• Complement OBBHFH when no radio window is usable.
• Crisis scenarios: Internet cut, 5 GHz jamming, relay destruction.
• Deliver media containing app updates, offline maps, encrypted logs.

Integration with mayors’ app & 56k households

• The “mayors’ network” app runs on the RPis/mini-PCs at sites A/B/C/D. Even if the backbone is partly destroyed, data can travel via OBBDW.
• A few households near town halls can connect at 56k / low-bandwidth Wi‑Fi to the local mini-server for messages, laws, municipal announcements.
• Updates (content, docs, firmware) are pushed by OBBDW, keeping the network modern without public Internet.

DW vs HFH (quick recap)

• OBBHFH: 5 GHz radio backbone, 30–40 km per hop, tens of Mbps, solar power, ~10–20 ms latency.
• OBBDW: drone corridors, 40–80 km per flight (or more with battery relay), physical bundle transport, higher latency but very resilient to radio outages.
• Together: a hybrid radio + “air mail” system that keeps running even if some relays are down.