Remote Provisioning Server

.. _bluetooth_mesh_models_rpr_srv:

Remote Provisioning Server ##########################

The Remote Provisioning Server model is a foundation model defined by the Bluetooth mesh specification. It is enabled with the :kconfig:option:CONFIG_BT_MESH_RPR_SRV option.

The Remote Provisioning Server model is introduced in the Bluetooth Mesh Protocol Specification version 1.1, and is used to support the functionality of remotely provisioning devices into a mesh network.

The Remote Provisioning Server does not have an API of its own, but relies on a :ref:bluetooth_mesh_models_rpr_cli to control it. The Remote Provisioning Server model only accepts messages encrypted with the node's device key.

If present, the Remote Provisioning Server model must be instantiated on the primary element.

Note that after refreshing the device key, node address or Composition Data through a Node Provisioning Protocol Interface (NPPI) procedure, the :c:member:bt_mesh_prov.reprovisioned callback is triggered. See section :ref:bluetooth_mesh_models_rpr_cli for further details.

How to integrate the model into an application

To add the Remote Provisioning Server model in your application, do the following:

1. Enable Kconfig in your project configuration:

   .. code-block:: cfg

   CONFIG_BT_MESH_RPR_SRV=y

2. Add the model instance into the model list :c:member:bt_mesh_elem.models of the primary element using the :c:macro:BT_MESH_MODEL_RPR_SRV macro, for example:

   .. code-block:: c

   static const struct bt_mesh_model models[] = { BT_MESH_MODEL_CFG_SRV, BT_MESH_MODEL_HEALTH_SRV(&health_srv, &health_pub), BT_MESH_MODEL_RPR_SRV, /* ... */ };

   static const struct bt_mesh_elem elements[] = { BT_MESH_ELEM(0, models, BT_MESH_MODEL_NONE), };

3. Enable PB-Remote by calling :c:func:bt_mesh_prov_enable with :c:enumerator:BT_MESH_PROV_REMOTE:

   .. code-block:: c

   err = bt_mesh_prov_enable(BT_MESH_PROV_REMOTE); if (err) { printk("PB-Remote enable failed (err %d)\n", err); }

Limitations

The following limitations apply to Remote Provisioning Server model:

• Provisioning of unprovisioned device using PB-GATT is not supported.
• All Node Provisioning Protocol Interface (NPPI) procedures are supported. However, if the composition data of a device gets changed after device firmware update (see :ref:firmware effect <bluetooth_mesh_dfu_firmware_effect>), it is not possible for the device to remain provisioned. The device should be unprovisioned if its composition data is expected to change.

API reference

---

.. doxygengroup:: bt_mesh_rpr_srv