Bluetooth LE mesh

How it works

Bluetooth Low Energy (BLE) is optimized for low power: it advertises and connects in short bursts and moves small amounts of data efficiently, which is why it suits sensors, wearables, and beacons. On its own, BLE is a short-range point-to-point link.

A BLE mesh has devices forward messages for one another so that reach extends past a single hop. The official Bluetooth Mesh profile uses a managed flooding approach: a message is rebroadcast by relay nodes and propagates across the network, with time-to-live limits and message caches to control spread. It is widely used in smart lighting and building automation.

Separately, many phone applications build their own mesh at the app layer, using BLE for discovery and small messages and pairing it with a higher-bandwidth radio for bulk data. This is distinct from the Bluetooth Mesh profile and is how phone-native meshes typically operate.

Why it matters

BLE is present in essentially every modern phone and countless embedded devices, and it draws very little power, so it is an ideal substrate for always-on discovery and lightweight messaging in a mesh.

The trade-off is bandwidth: BLE is not built for large transfers, so meshes that need to move files pair it with WiFi Direct or another high-throughput link.

How it relates to Offline Protocol

Offline Protocol uses BLE as one transport in its multi-transport mesh, DORS, alongside WiFi Direct and the internet. BLE handles low-power peer discovery and small messages; WiFi Direct carries bulk data such as chunked file transfer up to 100MB. DORS runs these concurrently and fails over between them automatically, relaying up to 8 hops.

This is an app-level phone-native mesh rather than the Bluetooth Mesh lighting profile, and it runs on ordinary iOS and Android phones with no extra hardware. See peer-to-peer mesh networking for the transport in depth.