PROTOCOL NOTES / 01

Overview & architecture

Understand the boundaries before following the bytes.

Android and iOS software implemented · Apple Wi-Fi Aware, Bluetooth LE and mixing tested on hosts and emulators only · Physical qualification pending

A conversation carried by a tree

RWCP v2 is the RideWeave Communication Protocol. It connects an approved group of nearby riders through a changing tree of phone-to-phone links. A phone can play incoming voice locally and forward it to other branches. The forwarding path does not wait for local playback.

Neighboring phones link over Wi-Fi Aware. Where Wi-Fi Aware cannot join two phones, for example an iPhone and an Android phone without NAN Pairing, a Bluetooth LE link joins them. Above the link there is one protocol: the same TLS, signed control, hop authentication and media envelope on every link kind.

Application, shared protocol engine, Android adapter, and neighboring phones.
Application, shared protocol engine, Android adapter, and neighboring phones. · Open full size ↗

Three distinctions make the design easier to follow: membership is not connectivity; a discovered peer is not an authenticated link; and an authenticated link is not necessarily allowed to carry media. Each chapter follows one of these boundaries.

From a rider’s action to a packet

LayerResponsibility
Product UICreate/join, approval, local microphone controls and status
Native service and adapterPlatform lifecycle, permissions, helmet route, Wi-Fi Aware and Bluetooth LE link resources
Shared engineIdentity, signed membership, route selection and handoff
Control planeTLS-protected JSON, signed messages, direct health checks
Media planeOpus in protected RTP; bundled, authenticated per-hop forwarding; one bridge mix per direction on a Bluetooth LE edge

The Android and iOS adapters are implemented. Rides that mix iPhones and Android phones are an implemented protocol capability: the Apple Wi-Fi Aware path, Bluetooth LE links and bridge mixing are implemented software, tested on hosts, emulators and the iOS simulator only; no mixed ride has been qualified on physical phones.

Wi-Fi Aware routing, Bluetooth LE range, moving-group behavior, headset acoustics, coexistence with headset calls, and battery endurance require physical qualification; deterministic host and emulator checks do not establish those results.

Follow one ride through the system

Start with an invitation and an organizer-approved roster. Follow discovery into an authenticated connection, then trace one voice packet across the tree. Finally, examine what changes when a parent disappears or a better route becomes available.

Ride creation, admission, voice exchange, and local departure.
Ride creation, admission, voice exchange, and local departure. · Open full size ↗

Authority: Architecture and native protocol. Public examples are synthetic. This guide is maintained against the private implementation; it does not imply access to its source.