Limited number of mesh nodes in a remote provisioning client

Hi to everybody.

I'm evaluating the possible options to perform self provisioning of nodes in a mesh network starting from the pb_remote client and server examples.

I read that the maximum number of nodes in the network, is limited by te memory capacity of the client because the information of every single node provisioned (network key, app key ecc. ecc.) are saved in the client's memory. 

My network scenario is:

network of maximum 900 nodes.

All nodes shares application key and device key

No different groups

Same publication and subscription addresses for all nodes

Just one provisioning client in the network.

I'm asking if in the scenario described is it still necessary to save provisioning node informations on the provisioning client. I think that it could be enough to take trace of the node address assigned to each provisioning server. In case my assumption wouldn't correct, do you think it is possible to save node's provisioning information in an external device communicating with the provisioning client? My goal is to avoid the calls to the following functions in the pc_remote_client example, module main.c, function static void prov_evt_handler(const nrf_mesh_prov_evt_t * p_evt)in the event type NRF_MESH_PROV_EVT_COMPLETE:

dsm_address_publish_add

dsm_devkey_add

For some reasons, i will prefer to avoid the use of the Interactive PyACI.

Thank you and regards.

Parents
  • Hi!

    I'm asking if in the scenario described is it still necessary to save provisioning node informations on the provisioning client.

    Yes, you would still have to store the information of each node. Each node will have at least one unique address and you will have to add and store the provisioning data for each.

    I can ask if our developers have some suggestions to how this can be handled best, if you want?

    Br,
    Joakim

  • Hi Joakim!

    Thank you for the answer.

    My idea is to store only the unique address assigned by the privisioner. I think that key storage is not strictrly necessary for every provisioned devices since they are the same for all devices. I have a doubt regarding the device key: using a unique key for all devices could lead to security problems?

    Yes please, if it's not a problem for you, please ask to your developers.

    Br,

    Gianluca

Reply
  • Hi Joakim!

    Thank you for the answer.

    My idea is to store only the unique address assigned by the privisioner. I think that key storage is not strictrly necessary for every provisioned devices since they are the same for all devices. I have a doubt regarding the device key: using a unique key for all devices could lead to security problems?

    Yes please, if it's not a problem for you, please ask to your developers.

    Br,

    Gianluca

Children
No Data
Related