Rolling live coverage of road races.

The mission

A grand-tour stage, a spring classic, a national championship — or a rally, or a big-city marathon. The production convoy is a studio stretched over the road: camera motorcycles inside the race, chase cars behind it, a helicopter overhead, and a broadcast compound at the finish where the director cuts the programme the world actually sees. Every one of those platforms is streaming live video while moving, for five or six hours, along a route that was drawn for the sport. The route does not care where the coverage is good — and on air, a frozen frame is the failure that matters, because the audience sees it the instant it happens.

What breaks

The race carries its own dead zone with it. Wherever the peloton is, thousands of spectators are — and they raise their phones exactly when the camera motorcycle passes, saturating roadside cells that sat idle the rest of the year. The terrain does the rest: gorges, forest climbs and cuttings cut line of sight to towers the flat sections took for granted. And a platform at race speed crosses into a new cell every minute or two; every handover is a chance for the stream to stall, every address change a chance for a session to reset on air.

The classical answers each cost something. A dedicated RF video link to the helicopter needs spectrum coordination in every country the calendar visits, and is still one path with one failure mode. Hardware bonding modules tie every platform to one vendor’s appliance and its roadmap. And no single carrier serves every kilometre of a 180-kilometre stage — the map guarantees that before the race even starts.

The architecture on this mission

Every camera platform — motorcycle, chase car, helicopter — runs the same software node beside its encoder, bonding two or three carriers into one encrypted tunnel to the compound. The stream rides the sum of what those carriers currently offer: every link is probed several times a second, and when one cell’s uplink softens the weight shifts to the others within well under a second. Forward error correction repairs the packet loss the road inevitably produces without retransmission delay — the difference, on a live path, between a briefly softer picture and a frozen one. The encoders and cameras are untouched; Atlas sits underneath them as the network.

Because the tunnel’s addresses are stable, the endless cellular handovers and address changes of a moving platform are absorbed below the stream. Sessions roam with the motorcycle instead of resetting with each new cell — the on-air feed never has to be re-established because the platform crossed a boundary.

The relay geometry handles what bonding cannot. The platforms are mesh nodes for each other: in a gorge the motorcycle’s own carriers vanish, but the chase car two hundred metres back may still hold a cell, and the helicopter above the valley always sees more towers than the valley floor does. The motorcycle’s traffic hops through whichever platform currently has a way out — automatically, with no operator action and no switchover event. Where the production also runs a private RF link from the helicopter, it joins the bond as one more measured path. And for the traffic that must not fail — the intercom, return control — duplication across paths applies the blunt arithmetic: three independent paths each losing 2% of packets leave an effective loss of 0.0008%.

How the race day unfolds

1. Three hours before the flag. The nodes on the motorcycles, chase cars and helicopter come up with the convoy’s radios; each platform bonds its carriers into one tunnel to the compound. One dashboard shows every platform’s every link — measured state, not signal bars.
2. The rolling start. The convoy strings out along the route. Every link is probed continuously; as each platform crosses cell after cell, weight shifts to whichever carrier is currently strongest. The director cuts between feeds without knowing or caring which network carries which one.
3. The climb. The race enters the mountains and the crowd density triples exactly where the coverage thins. Spectator phones saturate the summit cells; forward error correction absorbs the rising loss, and the video sheds bitrate before it sheds continuity.
4. The gorge. On the descent the lead motorcycle drops behind rock and loses every carrier at once. Its feed hops through the chase car and the helicopter — two short links replacing one impossible long one — and the picture on air softens for a few seconds instead of freezing.
5. The run-in. Back on open roads the direct paths return and traffic re-weights onto them on its own, the same continuous re-scoring run in reverse. Redundancy on the intercom de-escalates as the measured loss falls.
6. The debrief. The journal holds a per-kilometre, per-carrier record of the whole stage — which network gave out on which climb, and for how long. Next year’s edition of the race is planned from data, not from the director’s memory of where the picture went soft.

What each mechanism contributes

• Multi-carrier bonding and aggregation — each platform’s carriers as one measured fabric; the stream rides the sum of what currently exists, cell by cell. Shipped.
• Forward error correction — packet loss repaired without retransmission delay; a soft frame instead of a frozen one. Shipped, opt-in.
• Endpoint roaming — handovers and address changes absorbed below the stream; sessions never reset on air because the platform moved. Shipped.
• Relay through the convoy — chase car and helicopter as authenticated mesh nodes; the worst valleys carried by a short hop to a platform that still sees a tower. Shipped.
• Continuous measurement and the journal — a per-kilometre, per-carrier record of the stage, for the debrief and for planning the next one. Shipped.

The honest boundary: Atlas cannot make a carrier serve a gorge that no carrier serves — there the answer is the relay geometry, and the aircraft that flies it, its fuel and its permissions are the production’s and the organiser’s. The cameras, the encoders, the programme and the broadcast chain are yours; Atlas carries the bits between them and proves afterwards what every network actually did.

What a pilot should prove

• Side-by-side link records over a full stage: each single carrier versus the bond, from the built-in measurement.
• On-air continuity through the worst measured section of the route — the count of frozen or dropped intervals, bonded versus unbonded.
• A relay event: a camera platform losing every direct carrier and its feed carried through the chase car or helicopter without a stream reset.
• The debrief artefact: a per-kilometre journal of where each carrier gave out, usable for next season’s route and platform planning.

One race, one stage, one camera platform. The evaluation format covers the structure.