Android Provisioning process sending provision PDUs in queue

[matej1410]

Hello.

I found in Provisioing chapter on this document: https://www.bluetooth.com/specifications/mesh-specifications/

something like list of provisioning commands:

0x00 Provisioning Invite Invites a device to join a mesh network

0x01 Provisioning Capabilities Indicates the capabilities of the device

0x02 Provisioning Start Indicates the provisioning method selected by the Provisioner based on the capabilities of the device

0x03 Provisioning Public Key Contains the Public Key of the device or the Provisioner

0x04 Provisioning Input Complete Indicates that the user has completed inputting a value

0x05 Provisioning Confirmation Contains the provisioning confirmation value of the device or the Provisioner

0x06 Provisioning Random Contains the provisioning random value of the device or the Provisioner

0x07 Provisioning Data Includes the assigned unicast address of the primary element, a network key, NetKey Index, Flags and the IV Index

0x08 Provisioning Complete Indicates that provisioning is complete

0x09 Provisioning Failed Indicates that provisioning was unsuccessful

My question is if should I send all this data above in separated threads or in queue one after one? What is the correct mechanism of sending these data to device?

[Hung Bui]

Hi Matej, 

The opcode list you provided is not the data you need to send but the list of opcode can be used in provisioning process. The provisioning procedure is described at section 5.3.2 and 5.3.3 in the Mesh specification v1.1 

You can also have a look at the chart here: https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v4.0.0/md_doc_getting_started_provisioning_procedure-api.html?cp=7_2_1_6_1

If you are developing your app on Android for doing PBGATT provisioning, I would suggest you to have a look at our nRF Mesh source code: https://github.com/NordicSemiconductor/Android-nRF-Mesh-Library