Mesh

The easiest way to misunderstand BLE Mesh is to say: if many BLE devices are connected to each other, then it is a Mesh. That mistake is common because people already know BLE advertising, scanning, connections, and GATT service discovery, so it is tempting to think of Mesh as “just a BLE network with more connections.”

The real issue is that BLE Mesh is not about adding more Central/Peripheral connections, nor is it about making one node maintain many GATT sessions. It is more like a new networking style built on top of BLE air interfaces, where the system is redesigned around multi-node forwarding, address distribution, publish/subscribe behavior, and low-power reception.

Wi-Fi Mesh is often reduced to one simple image: there are several nodes in the house or office, the phone stays on the same SSID (Service Set Identifier) all the time, and internet access follows you everywhere. That leads to the overly simplified explanation: multiple AP (Access Point) devices are just broadcasting the same name, and the terminal simply chooses the closest one.

That sentence only describes the surface experience. It does not explain the key difference between Mesh and “several independent APs with the same name.” What separates Mesh from plain same-name AP deployment is not the SSID itself, but the fact that these three things are organized together: