WAVE · PROTECTED MARITIME COMMUNICATIONS
Protect communications between vessel and shore
A shore team needs to know which vessel it is connected to, which information is current and whether a command was received. WAVE is the NAUTILUS module for that connection, combining SHACE-protected routes with application identity, message handling and delivery records.
IN DEVELOPMENT · PILOT CONVERSATIONS OPEN
NAUTILUS / FILM
Watch WAVE.
ON THIS PAGE→
Page sections appear in preview
01 / WAVE
A communications architecture for uncertain links
Direct radio, cellular and relayed connections have different coverage and failure characteristics. WAVE uses the same logical message contract across permitted routes. Each route still needs its own tested limits and approved operating modes.
The integration team can keep message identity, destinations, deadlines and receipts consistent while selecting the route that suits the vessel.
Direct IP radio and approved external cellular equipment are commissioning candidates. Azure Relay Hybrid Connections is a cloud-path candidate whose compatibility with the required end-to-end SHACE topology still needs to be demonstrated.
02 / WAVE
SHACE below. Authenticated application policy above
SHACE supplies the external secure packet-tunnel layer. WAVE works above the protected route, authenticating the application endpoint and enforcing communications policy before a command reaches WATCH.
NAUTILUS requires a reviewed post-quantum profile for operational remote command. The documented SHACE lab path includes ML-KEM, ML-DSA and AES-GCM, but the operational profile and supported host topology remain release gates. A reachable route, encrypted packet or accepted relay connection does not confer vessel authority.
This separation lets each layer do a specific job: protect the route, verify the application request, then assess the action aboard.
03 / WAVE
Know what was delivered
The delivery design requires accepted observations to enter durable local storage before publication. WAVE sends them with stable message identifiers and recognises an authenticated durable application receipt before marking delivery complete.
An interrupted connection can therefore resume retained observation delivery without turning every retry into another logical event. Original observation timestamps and delayed-delivery indicators let the receiver distinguish historical evidence from a fresh onboard observation.
04 / WAVE
Put important traffic first
The communications design reserves capacity for authority state and bounded control traffic, followed by health and observation data. Camera streams and bulk history must remain within their separate resource budgets.
Remote manual input has short validity and must expire when stale. It belongs to a different delivery policy from retained observations; reconnected links must never replay queued joystick samples as fresh steering or propulsion demands.
05 / WAVE
Make route quality visible
A permitted route needs evidence for latency, jitter, packet loss, bandwidth and failover. A general connected indicator cannot establish that supervised manual control is available.
WAVE reports the selected route, authenticated peer, security profile, trust age and connection state. WATCH uses the relevant vessel and mode policy to determine whether remote authority may continue. Switching bearers requires those conditions to remain satisfied or a fresh handover to take place.
06 / WAVE
Preserve local operation during an outage
The local control loop stays aboard. A valid, staged mission can continue only within its commissioned authority, data and reserve limits, while WAVE retains eligible evidence for later delivery. Expired trust closes remote command admission, and reconnection does not silently extend mission authority.
Operators can see the route in use and the limits that apply. When it fails, the vessel follows its local authority and mission rules, and retained observations remain available for later delivery.
07 / WAVE
Start with the route you actually need
Bring AIC the route you need: direct radio, cellular or a proposed relay. We can define the endpoints, traffic and supervision mode, then identify the security and network tests required for that configuration.
WAVE is in development. SHACE lab integration does not yet establish production secure transport or authorise operational remote vessel control.