• State Verified Answer
  • Replies 1 reply
  • Subscribers 73 subscribers
  • Views 448 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 292059
Options

Automatic Provisioning

akira fujimura

hi

I would like to use BLE Mesh to control my products.
I would like to build a mesh network in advance, install a provisioner and automatically provision the nodes when they are turned on at the site.
The provisioner will also act as a proxy node and will be connected via GATT to the device (android) that manages the application.
What methods should I develop to form such a system?

Also, we may use multiple units of the same product.
At this time, how do we know which unicast address to use to manage each product?


The products operate as LPN.
Is it possible to automatically assign the closest device as a friend node?

Lots of problems, but I'd appreciate some solutions.

I expect we need at least one example of pb_remote.

I'm using a translation tool, sorry if there are any problems with my english.

  • 0

    Hi,

    What methods should I develop to form such a system?

    Automatic provisioning should be a good solution. You may for instance give the node a spesific UUID for unprovisioned beacon (the beacon you send out when you call for a network to be incorporated in), such that the provisioner knows what devices to add and what type of devices they are.

    You may also use the same UUID to connect a specific unit/device to a given address to keep track in the provisioner and/or on your phone.

    Depending on what you may want to do further, but you should take a look at group-addresses and the publish/subscribe paradigme in Bluetooth mesh (found under the section regarding "Addressing" and "Models and elements". This will allow you  to configure nodes to subscribe to given group-addresses and to publish to given group-addresses instead of configuring the network with unicast-addresses directly.

    Unfortunately some of the features you are asking for does only exist in nRF5 SDK, but as far as possible I would recommend you to work with nRF Connect SDK (NCS) instead, so I will ask around to see if I can find any information I can give you that will help you work around those limitations.

    Kind regards,
    Andreas

Related
Terms of service