Autonomous Fleet Coordinated Time

1. Regulatory and Domain Context

Coordinated time is the foundation of every multi-vehicle interaction. Vehicle-to-everything (V2X) communications under SAE J2735 and ETSI ITS-G5 / C-V2X profiles assume that participating vehicles share a common time reference accurate to the order of a millisecond, so that basic safety messages, maneuver-coordination messages, and signal-phase-and-timing messages compose coherently. The FAA's Concept of Operations for Unmanned Aircraft System Traffic Management (UTM) presupposes shared timing across UAS service suppliers, operators, and the supplemental data sources that feed conformance monitoring; EASA's U-space regulatory package imposes comparable timing assumptions on European unmanned operations. Autonomous truck platooning — Level 1 and Level 2 cooperative driving across mixed OEM fleets — requires inter-vehicle synchronization tight enough to support the coordinated braking and gap-control control loops that yield the platoon's fuel-efficiency and safety benefits. Defense swarm coordination, where dozens to hundreds of platforms must execute joint maneuvers without GNSS, drives the requirement to its hardest edge.

The fleets in question are increasingly mixed. A single intersection may host vehicles from a dozen OEMs running V2X stacks from several suppliers; a single UTM operating volume may contain UAS from multiple service suppliers under multiple operator authorities; a single highway corridor may carry platoons from competing logistics carriers operating cooperatively under sector agreements. Coordination across these mixed populations is the operating reality, not a corner case.

Regulatory pressure is converging on the same point from multiple directions. The FAA's 14 CFR Part 89 Remote ID rule already requires UAS to broadcast time-stamped position with sufficient precision that downstream consumers can correlate events across operators; the FAA Reauthorization Act of 2024 directs the agency to extend BVLOS rulemaking on a schedule that presupposes shared timing. EASA's U-space Regulation (EU) 2021/664 makes coordinated time an interoperability requirement among U-space service providers. NHTSA's V2X Communications Deployment Plan, the U.S. Department of Transportation's ITS Strategic Plan, and the European Commission's ITS Directive 2010/40/EU revisions all assume coordinated time as a baseline service that the deployed architecture must furnish. The procedural posture under each of these regimes - "operators shall maintain coordinated time" - leaves the architectural means unspecified, and current industry practice fills the gap with infrastructure assumptions that do not survive the operational conditions in which fleets actually operate.

2. Architectural Requirement

The architectural requirement is coordinated time that is simultaneously (a) accurate enough for the control loops it underwrites, (b) resilient against the loss or denial of any single timing source, (c) federable across operator boundaries without forcing a single dominant operator's infrastructure on the others, and (d) auditable after the fact so that incident reconstruction — collision review, near-miss analysis, conformance investigation — can establish the timing context of contributing actions with evidentiary confidence.

Accuracy alone is well understood and partially solved by existing techniques: GNSS-disciplined oscillators, IEEE 1588 over local networks, time-from-cellular references. Resilience against single-source loss is partially addressed by holdover oscillators, but holdover degrades with time and does not address adversarial denial. Cross-operator federation is essentially unsolved at the architectural level — the deployed solution is operator-specific time infrastructure that other operators trust by contract or by reference to a shared GNSS source. Auditability is uneven: per-vehicle telemetry retains timing locally, but cross-vehicle reconstruction requires reconciling timestamps that originated under different clocks with different drift histories under different operator authorities, and the reconciliation is rarely defensible to evidentiary standards.

3. Why Procedural Compliance Fails

Procedural posture toward fleet timing rests on three assumptions, each of which fails in operational reality. The first is that GNSS will be available — the fleet's timing is GNSS-disciplined, and the procedure documents that fact. The assumption fails in urban canyons, indoor staging areas, tunnels, jamming environments, spoofing environments, and any operation that crosses a denial volume; the procedural documentation cannot help because the procedure trusts the source whose loss is the failure mode. The second assumption is that hardware clocks will hold within tolerance during holdover — the procedure documents the oscillator's specification. The assumption fails because oscillator drift in operational conditions (temperature swings, vibration, aging) exceeds bench specification, and the drift is silent: the clock continues to issue timestamps that pass procedural validation but drift away from consensus reality.

The third assumption is that cross-operator timing can be reconciled by reference to a common upstream source, typically GNSS. The assumption fails not only when GNSS fails but when operators' interpretations of GNSS time diverge — different leap-second handling, different propagation-delay corrections, different disciplining-loop time constants — and the divergence is silent until a cross-operator event reveals it, often in incident reconstruction where the reveal is too late to matter operationally. Procedural mitigation of cross-operator timing produces operator-specific lock-in: whichever operator's infrastructure becomes the de facto reference accumulates governance leverage over the others, and the federation is not really a federation but a hub-and-spoke with the hub's interests prioritized.

4. What the AQ Mesh-Time Primitive Provides (USPTO 64/049,409)

The mesh-time primitive provides master-less coordinated time produced by joint spacetime estimation across the fleet's participating units. Each unit contributes credentialed time observations into a consensus that is jointly inferred with the relative geometry of the participants. The consensus does not depend on a single privileged master; loss of any one contributor — including loss of GNSS for any subset of contributors — degrades the consensus gracefully rather than collapsing it. Ranging-piggyback synchronization extracts timing information from the cooperative ranging exchanges that V2X, UTM, and platooning protocols already perform, so the timing improvement is obtained without additional bandwidth or sensing burden. Per-agent learned drift models become part of each unit's credential: an oscillator's drift behavior, learned over operating experience, is itself attested, and a sudden departure from learned drift surfaces as a credentialed integrity event rather than as silent error.

Cross-fleet federation maps onto operational reality. Defense-civilian coordination during disaster response, commercial cross-carrier platoon coordination on shared highway corridors, multi-operator UAS coordination within a UTM volume, and multi-OEM V2X coordination at an intersection all federate through declared cross-fleet timing agreements. Each fleet retains its operator authority; each fleet's contributions carry that authority's credential; the federated consensus carries lineage admissible to each contributing operator and to any regulator with jurisdiction over any of them. No operator captures the federation's timing infrastructure, because the consensus is produced by the participants jointly rather than by any one's master.

5. Compliance Mapping

FAA UTM ConOps timing assumptions are satisfied by the consensus value, with the contributing-attester set retained for the conformance-investigation horizon; UAS service suppliers and operators each contribute as credentialed attesters, and the federated lineage supports the FAA's conformance-monitoring data flows. EASA U-space timing requirements admit through the same composition with the appropriate authority set. SAE J2735 / ETSI ITS-G5 / C-V2X timing assumptions are satisfied by the consensus operating at the V2X exchange cadence, with mixed-OEM intersections admitting through declared cross-OEM federation rather than through a designated lead OEM. Autonomous truck platooning admits cooperatively across carriers without forcing a lead carrier's time master; defense swarm coordination admits in GNSS-denied conditions because the consensus does not depend on GNSS as a single source.

Incident reconstruction admits structurally. The collision-review record carries the consensus timestamps with their contributing-attester sets and dispersions; the investigator can replay the contributing observations, verify the credentials, and establish the timing context of each contributing action with the same evidentiary standard that applies to financial-settlement timing or surveillance-system timestamping. Cross-jurisdiction operations — a platoon crossing a state or national boundary, a UAS mission crossing a UTM-to-U-space handoff — admit through declared cross-jurisdiction federation, with each jurisdiction's regulator authority joining the federation for operations within its scope.

6. Adoption Pathway

Adoption proceeds incrementally and does not require any operator to discard existing timing infrastructure. The first stage is intra-fleet: an operator's existing units begin contributing credentialed observations into mesh-time consensus alongside the existing GNSS-disciplined oscillator, gaining resilience against GNSS loss and gaining lineage for incident reconstruction without changing the rest of the stack. The second stage is bilateral cross-fleet federation between operators whose operations already require coordination — a corridor-sharing agreement between two logistics carriers, a UTM service supplier pair sharing an operating volume, two defense partners coordinating during exercise — admitted through declared federation rules. The third stage is multilateral federation across mixed-vendor populations, where the federation is the default coordination structure and bilateral arrangements compose into it.

The architecture accommodates the fleet ecosystem's own evolution. Higher-density urban-mobility deployments, cross-domain operations spanning ground and air, swarm sizes growing toward the hundreds and thousands of participants, and emerging cooperative-perception protocols that piggyback on the same ranging exchanges already used for synchronization all admit through declared specification. The architectural commitment — credentialed master-less consensus with retained lineage and cross-operator federation as a first-class property — does not need to change to accommodate them. Whatever the autonomous-fleet operational future is, the timing it depends on will be defensible, federable, and resilient, because those properties are structural rather than properties of any one operator's posture.