Managed Flooding

What Is Managed Flooding?

Managed flooding is the core message-relay strategy in Bluetooth Mesh. When a relay node receives a mesh message via the advertising bearer, it rebroadcasts the message on the same advertising channels. This simple approach ensures broad network coverage without requiring routing tables, link-state databases, or path-discovery protocols.

How It Works

A node that wants to send a message transmits it as a non-connectable advertising PDU on one of the three BLE advertising channels (37, 38, 39). Relay nodes within radio range receive the PDU, decrement the TTL (Time-to-Live) field, and retransmit it. The message propagates outward through the network in concentric waves. Each relay node maintains a message cache (keyed by source address and sequence number) to suppress duplicates -- if a relay has already forwarded a specific message, it silently drops subsequent copies.

TTL and Hop Limits

The TTL field is a 7-bit value (0 -- 127) set by the originating node. A TTL of 0 means the message is not relayed at all -- it reaches only direct neighbors. Each relay hop decrements the TTL by 1, and the message is discarded when TTL reaches 1 (meaning no further relaying). Choosing the right initial TTL is a design trade-off: too low and distant nodes are unreachable; too high and the network floods with unnecessary rebroadcasts.

Network Density and Scalability

Managed flooding works well in dense networks (commercial buildings with many light fixtures) because the redundant paths provide natural resilience -- if one relay node fails, neighbors pick up the message. However, density also means more duplicate packets consuming airtime on the advertising channels. The Bluetooth Mesh specification recommends a relay retransmit count of 2 -- 3 with a random delay of 0 -- 10 ms between retransmissions to spread the load and reduce collisions.

Limitations

The primary limitation is inefficiency. Every relay node rebroadcasts every message it receives (minus cached duplicates), regardless of whether the message is relevant to any node in its vicinity. In large linear networks (e.g., a highway lighting strip), a message from one end must traverse every relay to reach the other end, generating O(N) rebroadcasts. This wastes airtime and energy, particularly for battery-powered relay nodes.

Managed Flooding vs. Directed Forwarding

Directed Forwarding, introduced in Mesh 1.1, addresses flooding's inefficiency by discovering and caching optimal paths between specific source-destination pairs. Messages follow these paths with unicast-like precision, dramatically reducing network traffic. In practice, many deployments use managed flooding for group-addressed messages (e.g., "all lights in Zone A, turn on") and directed forwarding for unicast messages (e.g., "sensor node 42, report status").

Practical Guidance

For networks with fewer than 100 nodes and moderate message rates, managed flooding is robust and simple. Beyond that scale, consider enabling directed forwarding for unicast traffic, tuning relay retransmit parameters, and strategically designating which nodes act as relays rather than enabling relay on every node.