Revision as of 12:34, 12 October 2021 by Registered User (→‎Topology)

1. Introduction

BLE-mesh connects multiple Bluetooth Low Energy technology devices with mesh networking capability for internet of things (IoT) solutions. Mesh network has a many-to-many topology, with each device able to communicate with every other device in the network.

The BLE-mesh communication is done using messages relayed by the devices which are part of the mesh network (called nodes). In this way, the end-to-end communication range is extended far beyond the radio range of each individual node.


2. Topology

There are different types of nodes:

  • Simple Nodes
  • Proxy Nodes
  • Relay Nodes
  • Low-Power Nodes
  • Friend Nodes

For more information about the node types, please refer to ST BLE-Mesh Application Note [1].

A typical BLE mesh topology is illustrated in the figure below.

3. Elements and Models

Each BLE-mesh node contains one or more elements, and each element can support different models.

3.1. Elements

The elements define the functionalities of a single node, each element can be independently controlled.

3.2. Models

Models define the functionality of a specific element. Several models are defined by the Bluetooth® SIG, and many of them are deliberately defined as “generic” models, having potential use across a wide range of device types.

Refer to ST BLE-Mesh Application Note for more details about Element and Models.

4. Provisioning

The process of adding a device into a BLE-mesh network, and configuring it, is called provisioning.

This process is started by a device called “provisioner”, which can be a smartphone with a BLE mesh application installed on it, or a mesh platform as STM35WBx5 line microcontroller. The provisioned device is now known as a node.

Refer to ST BLE-Mesh Application Note for more details about provisioning steps: AN5292 - How to build a Bluetooth® Low Energy mesh application for STM32WBx5 line microcontrollers

5. Go further

BLE-Mesh basic example: ST_BLE-Mesh_Lighting_Example

Friendship: Friendship

Embedded Provisioner: Embedded_Provisioning


6. References