This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Hardware

how many provisioner should be set up in one bluetooth mesh network?
Many provisioner and one provisioner with remote provisioning, which is better?

Parents
  • Hi Tuấn, 

    Bluetooth SIG doesn't have a clear recommendation on how many provisioners should/can be in a Bluetooth Mesh network. You can find these lines in the spec: 

    Although only a single Provisioner is required on a network to do provisioning, multiple Provisioners may be used. The method to share cached data and coordinate across multiple Provisioners is implementation specific.

    So it's up to the vendor to choose how to share cached data and to coordinate between provisioners. Some of the info that you need to share and coordinate: 

    - Share network keys, device keys, composition data of all nodes. 

    - Define the provisioning range of each provisioner so that they don't provision new nodes to same addresses. 

    - Coordinate when there is a key refresh etc. 

    Regarding remote provisioning, it could be a solution if the provisioner(s) can't cover the whole network. But remote provisioning is Nordic's proprietary solution and has not been standardize by Bluetooth SIG yet.  

    There isn't a "better" solution, it more depends on your application requirements. 

Reply
  • Hi Tuấn, 

    Bluetooth SIG doesn't have a clear recommendation on how many provisioners should/can be in a Bluetooth Mesh network. You can find these lines in the spec: 

    Although only a single Provisioner is required on a network to do provisioning, multiple Provisioners may be used. The method to share cached data and coordinate across multiple Provisioners is implementation specific.

    So it's up to the vendor to choose how to share cached data and to coordinate between provisioners. Some of the info that you need to share and coordinate: 

    - Share network keys, device keys, composition data of all nodes. 

    - Define the provisioning range of each provisioner so that they don't provision new nodes to same addresses. 

    - Coordinate when there is a key refresh etc. 

    Regarding remote provisioning, it could be a solution if the provisioner(s) can't cover the whole network. But remote provisioning is Nordic's proprietary solution and has not been standardize by Bluetooth SIG yet.  

    There isn't a "better" solution, it more depends on your application requirements. 

Children
No Data
Related