Fleet communication past the fence
A multi-hop mesh between tractors, trailer gateways, handhelds, and dock infrastructure, with no tower in the loop. Gate checks, dock assignments, telematics, and proof of delivery keep working in the yard, the port, and the corridor where trackers go dark.
A driver handheld completes a yard gate check over an offline mesh network, relaying through two parked trailers to the gate gateway dashboard with no yard WiFi and no cellular.
A handheld at the far fence completes a gate check through the trailers parked between it and the gateway.
Freight does not stop where coverage does
Telematics go dark where freight concentrates. Terminals, ports, parking structures, and dock walls are concrete and steel by design. The highest-density hours of an operation are exactly the hours the trackers stop reporting.
The yard is the network. Trailers, handhelds, and gateways relay for each other. A handheld at the far fence reaches the gate service through the trailers parked between them, up to 8 hops.
The record covers the whole route. Signed scans and the telematics record are kept on the device through the corridor and sync in order when any device in the mesh regains a link.
One trailer, gate to road
What happens to a load when the yard WiFi ends at the fence and the corridor has no LTE.
- GateDriver and trailer verify each other device to device at check-in. No server is asked.
- YardThe handheld invokes the dock-assignment service on the yard gateway, three hops through parked trailers.
- DockThe scan and signature are signed with OfflineID at the point of handoff and queued on the handheld.
- CorridorTelematics are queued on the device through the dead zone and uploaded when a link returns.
- Link returnsProof of delivery and the telematics record sync in order the moment any device has a path.
What you can build
Each of these runs on the shipped SDK primitives.
Capture scans and signatures on the handheld, sign them with OfflineID at the handoff, and queue them on-device. Tamper-evident whether or not the dock had signal.
A handheld at the far fence invokes the gate-check service on the yard gateway through the trailers between them. No access points at the fence line.
Opt-in telemetry is queued on the device through rural corridors and dock walls and uploaded in order when a link returns.
Customer stories
How an evaluation runs
- Integrate
- The SDK goes onto rugged handhelds, cab devices, trailer gateways, and a yard gateway. Devices join the mesh and authenticate with fleet-provisioned OfflineIDs.
- Exercise
- A defined offline scenario in your yard and on your lanes: gate checks, dock assignments, and proof of delivery running mesh-only.
- Measure
- Success criteria agreed before week one, evaluated against the opt-in telemetry record: delivery rates, hop counts, sync completeness when a link returns.
- Timeline
- 4 to 16 weeks, scoped up front, no open-ended commitments.
The primitives behind it
- DORS
- Tractors, trailer gateways, and handhelds meshed over BLE, WiFi Direct, and the internet with automatic failover. How mesh networking works.
- Service discovery
- Gate-check and dock-assignment services discoverable and invocable from anywhere within 8 hops. How service discovery works.
- OfflineID
- Every driver, vehicle, and gateway carries an Ed25519 identity verifiable device to device. How offline identity works.
- Telemetry
- Transport transitions and routing decisions, identifiers scrubbed by default, uploaded by the SDK. How telemetry works.
- File transfer
- Manifests and scan payloads up to 100 MB move between authenticated peers in ordered chunks. How file transfer works.
Logistics FAQ
How do fleets stay connected in cellular dead zones?
By adding device-to-device paths that do not depend on a tower. DORS meshes tractors, trailer gateways, and driver handhelds over BLE and WiFi Direct with relay up to 8 hops, so telematics, gate checks, and dispatch messages keep moving through yards, terminals, and rural corridors with no coverage.
Can proof of delivery work without internet?
Yes. Scans and signatures are captured, signed, and queued on-device, authenticated with OfflineID at the point of handoff, then synced the moment any device in the mesh regains a link. The record is tamper-evident whether or not the loading dock had signal.
Does this replace our cellular telematics?
No. The mesh adds device-to-device paths alongside whatever connectivity you already run. When cellular is available, DORS uses it. When it is not, coordination continues over BLE and WiFi Direct between vehicles, handhelds, and fixed gateways.
What range does the mesh cover across a yard or terminal?
Routing is multi-hop up to 8 hops, so coverage grows with density rather than radio range. Every tractor, trailer gateway, and handheld in the yard extends the mesh, and chunked transfer moves payloads up to 100MB across it.
What hardware do drivers and yard crews need?
The SDK ships as a React Native binding over a Rust core, so it runs on the phones and rugged Android handhelds crews already carry. Fixed gateways and vehicle compute that can run the Rust core join the same mesh directly.
How is freight data secured between devices?
Sessions are encrypted end-to-end with MLS (RFC 9420) by default, and every device carries an Ed25519 OfflineID verified device-to-device. Payloads move between authenticated peers, never in the clear.
What happens to telematics recorded in a dead zone?
The SDK keeps them. Telemetry is opt-in, and once it is on, transport switches and routing decisions are queued on the device through the dead zone and uploaded in order when a link returns. Your app does not write that plumbing.
How does an evaluation work?
A 4 to 16 week scoped evaluation against your yard, your lanes, and success criteria we agree up front. Contact us to scope it.
