BluKo Contact

Bluetooth® Mesh Synchronization

Keep the Mesh configuration database in sync across devices, users and the cloud.

A Bluetooth® Mesh network usually gets set up (commissioned) by one or many people using some kind of smartphone or tablet. During the commissioning process the network is formed and nodes receive their purpose. For that a lot of cryptographic keys need to be created, distributed and stored as well as information about the nodes, groups, addresses, etc. The sum of that data is called configuration database (CDB).

If the CDB gets lost or gets corrupted you cannot access the network anymore. If it falls into the wrong hands, the wrong people might get access to your network. And if multiple people or devices should access the network at the same time, the CDB needs to get distributed to all of them in a secure and conflict-free way.

The CDB is absolutely essential to a working Bluetooth® Mesh network and special care must be taken to keep it up to date, consistent, distributed and yet secure.

Some projects tried to solve that issue using an export and an import feature where on one phone a JSON file gets exported and on another phone it gets imported. Needless to say that this is clunky, insecure and prone to errors.

Others added proprietary synchronization services right into their products as a closed system. Not only inaccessible from other apps/systems but often also limited regarding security and concurrent use.

Because of that we have developed a CDB sync server engine that you can directly integrate into your software. Making CDB synchronization seamless and, if you use bluko.mesh.lib, build-in.

Main Features

  • Multiple provisioner support: Have multiple people provision a building in parallel.
  • Offline first: No Wifi or cellular network connection on the construction site? No problem!
  • Live sync: When online, each change gets synced in near real time through push-messages.
  • Conflict avoidance: The best conflict resolution is not to have any conflicts.
  • Conflict resolution: Solid built-in conflict resolution for 2-way synchronization.
  • Flexible hosting: Use managed hosting with us or host yourself.
  • Roles and permissions: Using role based access control (RBAC).
  • External identity management: Integrate with Auth0, Azure or any other OICD identity provider.
  • Export: No lock-in through standardized CDB export.

Availability

Availability is planned for 2027. Let us know if this is relevant for your project.