Mission library · Defence & security

Convoy and escort communications on the move.

A column on the move crosses towns with good cellular, valleys with none, and stretches where only the radio between vehicles holds. This mission is about making the column its own network — every vehicle a mesh node, the mix re-scored continuously, and nobody stopping to reconfigure anything.

Who runs it

Security forces, escort operations and the operators of critical transports — any column that must stay linked while it rolls.

What breaks

The route decides which link works. No single transport survives the whole road, and manual switching at speed is a liability.

What Atlas contributes

Every vehicle a mesh node bonding its own modems with inter-vehicle radio; the column carries its own network, reweighted continuously.

Runs on

Compute the vehicles already carry — a small board per vehicle, a workstation at the rear command post. One Linux binary, one configuration file.

The mission

An escort moves a critical transport a hundred kilometres across mixed country: out through the city, down a river valley, over a saddle, into the receiving site. The rear command post needs the picture for the whole move — position and status from every vehicle, voice with the escort commander, and video from the camera vehicle whenever something on the road needs looking at. The column’s one absolute rule is that it keeps rolling; stopping on the verge to sort out communications is precisely the exposure the escort exists to prevent.

What breaks

Coverage follows population, and the route does not. The city end is dense with cells; the valley has a strip of coverage that follows the villages and dies between them; the saddle has nothing at all. Worse, the column is not one radio experience but many: at any given minute the lead vehicle may be in a live cell while the tail is in shadow, and five minutes later the situation has inverted. A link that is perfect at sixty kilometres per hour at kilometre twelve is gone at kilometre nineteen — and it fails during the handover between cells, at speed, which is exactly when a human cannot be reassigning links by hand.

The classical answers each fall short of the moving case. A satellite terminal on every vehicle is expensive, and terrain and antenna masking interrupt it anyway. A convoy voice net holds the column together but carries no data picture rearward. And any architecture built around one transport — pick your favourite — inherits that transport’s dead stretches as its own.

The architecture on this mission

Convoy mesh geometry on the route A three-vehicle column rolls from a town with cellular coverage toward a valley with none; the vehicles link to each other in a chain, and whichever vehicle still sees a cell carries the whole column’s traffic back to the rear command post. the route — a town with cellular, a valley with none TOWN CELL NO COVERAGE AHEAD THE COLUMN CARRIES ITS OWN NETWORK Rear command post reachback Tail Mid Lead
The scene: the lead vehicle is already entering dead ground (crossed), but the chain of inter-vehicle links holds the column together, and the tail — still in the town cell’s footprint — carries everyone’s traffic back to the rear command post. As the column rolls, the gateway role simply moves to whichever vehicle currently has coverage.

Every vehicle runs the same node, bonding what that vehicle has: its own cellular modems, and an inter-vehicle radio that links it to its neighbours in the order of march. The vehicles form one encrypted mesh — up to eight hops of it — so lead and tail stay connected through the middle even when the column stretches over kilometres of dead ground. There is no designated gateway vehicle: whichever node currently sees a live cell carries the column’s rearward traffic, and that role migrates along the column, automatically, as coverage comes and goes.

The reweighting is continuous, not event-driven. Every link is probed several times a second; degradation is detected and traffic moved within roughly half to three-quarters of a second — and the system is predictive as well as reactive, using each vehicle’s shared position and velocity to walk traffic off a fading cell before the handover fails rather than after. At speed, that difference is the difference between a seamless move and a minute-long hole at every cell boundary.

Traffic is classed. The commander’s voice and the vehicles’ position reports hold reserved floors that video can never crowd out; the camera feed rides the elastic video class and sheds quality as the column narrows onto thinner links. The rear command post sees one column, on one encrypted connection, whatever mixture of physics is carrying it this minute.

How the move unfolds

  1. Staging. Engines running, nodes up. The vehicles authenticate by key and form the mesh in the yard; the rear command post’s dashboard shows every vehicle and every link’s measured state before the column moves a metre.
  2. Through the town. Cellular is everywhere and every vehicle is its own gateway. Traffic spreads across carriers and vehicles; the camera feed runs at full quality; nobody is thinking about communications, which is the point.
  3. Into the valley. Cells fall away one by one. Position and velocity trends shift traffic off each fading cell before it drops; the column’s rearward path consolidates onto the vehicles still in coverage — first three of them, then one.
  4. The dead stretch. Over the saddle nothing reaches the outside at all. The inter-vehicle chain holds the column together — voice, positions, the commander’s picture — while rearward reports queue on the tail vehicle in priority order, waiting for the next cell.
  5. Out the far side. The lead vehicle catches the first cell of the descent and becomes the column’s gateway; queued reports drain, oldest and most important first; video quality climbs back as capacity returns.
  6. The debrief. The journal holds a per-vehicle, per-kilometre record of what every link did along the route — where coverage held, where it died, how long the gaps ran. The next move over the same road is planned from measurement, not memory.

What each mechanism contributes

  • Vehicle-to-vehicle mesh with per-hop encryption — the column as one fabric, lead to tail through up to eight hops, indifferent to speed and order of march. Shipped.
  • Per-vehicle bonding with a migrating gateway — whichever vehicle has coverage carries the column; no designated link vehicle to lose. Shipped.
  • Predictive handover — position and velocity move traffic off a fading cell before the drop, not after it. Shipped.
  • Class floors and ordered degradation — voice and positions reserved, video elastic; enforced, not hoped for. Shipped, opt-in.
  • Store-carry-forward and the journal — reports queue through dead stretches and deliver on the next contact; the route’s coverage record accumulates for free. Shipped.

The honest boundary: Atlas contributes the network layer. The vehicles, the radios’ RF performance, the route selection and the escort doctrine are the force’s — and where the route genuinely offers no coverage and no line of sight, the guarantee is the intact column mesh plus queued delivery, not a live rearward feed. A plain statement for careful readers: the mechanisms here address terrain, motion and single-carrier fragility, and they degrade in an ordered way whatever the cause of loss — but resilience against deliberate interference is not a field-validated claim we make; our field record is controlled link-degradation trials.

What a pilot should prove

  • Voice and position continuity from every vehicle across one real route’s measured dead stretches, with the per-link record showing which physics carried each segment.
  • Gateway migration on the move: the rearward path demonstrably shifting between vehicles as coverage changes, with no operator action and no session reset.
  • Handover behaviour at speed: reweighting ahead of cell boundaries, compared against a single-carrier control run over the same road.
  • The debrief artefact: a per-kilometre journal of the route good enough to brief the next escort from.

One route, one column, one instrumented run. The evaluation format covers the structure.

Request a briefing

Escorting columns through dead ground?

Bring the route, the vehicles and the radios already in the racks — we will define what one instrumented run should prove.