PB-Remote Bearer#

The PB-Remote provisioning bearer uses the existing mesh network to provision an unprovisioned device that is not within immediate radio range of the Provisioner.

PB-Remote uses the PB-ADV bearer or the PB-GATT bearer for the last hop to the unprovisioned device. PB-Remote uses one of the mesh nodes as a PB-Remote Server to manage the PB-ADV or PB-GATT bearer link on behalf of the Provisioner.

Secure Provisioning should be used when PB-Remote is used. Secure Provisioning with an Authentication with No OOB or an Authentication with Static OOB of any size should be used, because these authentication methods do not require direct physical interaction with the unprovisioned device.

When PB-Remote is supported by the Provisioner, the Provisioner uses the PB-Remote Client role. When the node supports the Remote Provisioning Server model, the node uses the PB-Remote Server role.

PB-Remote may also be used to execute the Device Key Refresh procedure or the Node Address Refresh procedure or the Node Composition Refresh procedure between the Provisioner (PB-Remote Client) and the PB-Remote Server.

Multiple instances of the PB-Remote Client can be used by the Provisioner to communicate with many nodes implementing the PB-Remote Server, thus providing the capability to provision many unprovisioned devices at the same time. The PB-Remote Server can only communicate with one PB-Remote Client and can only open one supported provisioning bearer at a time.

For more details, refer to the Bluetooth Mesh Profile specification (1.1 draft) Chapter 5.2.3 PB Remote.