Introduction
Smart power distribution systems require every metering point to deliver data to a gateway with predictable latency and packet success rate. Bluetooth SIG Mesh, ratified as a standard profile, was designed for exactly this kind of many-to-one control and reporting traffic.
Why One-to-Many Matters in Power Distribution
A single distribution room may contain 30–80 metering points that all need to report to one or two gateways. A point-to-point BLE link from each meter to the gateway would require either many simultaneous connections (which the gateway cannot sustain) or sequential polling (which introduces minutes of latency across the full population).
Mesh solves this by letting every meter publish its data once, and have the network carry the message to any subscribed gateway.
Managed Flooding
Bluetooth Mesh uses managed flooding rather than routing. Every relay-capable node re-broadcasts a message up to a configured hop count (typically 3–7 hops in distribution rooms). Duplicate detection and a Time-To-Live (TTL) field prevent infinite loops.
The trade-off: more network traffic per message, but no routing tables to maintain and no single point of failure.
Publish / Subscribe Model
Each meter publishes to a group address (e.g. "all three-phase meters on floor 3"). Gateways subscribe to relevant groups. Adding a new gateway is as simple as subscribing — no reconfiguration of meters is needed.
This decoupling is what makes Mesh retrofits so much cheaper than traditional wired systems.
Packet Structure and Reliability
Mesh packets carry a 32-bit network ID, 16-bit application key, sequence number, and source/destination addresses. The application layer adds a 4-byte MIC computed with AES-CCM, providing both integrity and authentication.
On the physical layer, advertising channels (37, 38, 39) are used for transmission, which improves coexistence with Wi-Fi by hopping around the most-used Wi-Fi channels.
Friendship and Low-Power Nodes
Battery-powered or energy-harvesting meters can use the Friendship feature: a powered "Friend" node buffers messages while the low-power node sleeps, delivering them on wake-up. This makes Mesh practical for metering points that cannot be continuously powered.
Engineering Trade-Offs
Three trade-offs dominate Mesh deployment in distribution systems: (1) hop count vs. latency — too many hops add 50–100 ms per hop; (2) relay density vs. airtime — too many relays saturate the channel; (3) group address design vs. filtering — too few groups force unnecessary processing at gateways.
In practice, 3 hops with 4–6 relay-capable nodes per floor gives the best balance.
Coexistence with Wi-Fi and Other 2.4 GHz Systems
Mesh uses the same 2.4 GHz band as Wi-Fi, but its low duty cycle (typically <1% in metering applications) and adaptive frequency hopping keep coexistence losses below 5% in measured deployments.
Security Considerations
Mesh mandates AES-128 encryption with separate network key, application key, and device key. Provisioning is performed via PB-ADV or PB-GATT over an out-of-band secure channel. Once provisioned, devices cannot be impersonated even if the radio channel is monitored.
Practical Deployment Numbers
In a 60-meter deployment over three electrical rooms with two Mesh gateways, end-to-end latency from meter to cloud averages 1.8 s. Packet success rate over 7 days is 99.92%, exceeding the 99.5% target for billing-grade metering.