9
Comparison with existing provisioning solutions
Provisioning
method
Provisioning with
dynamic NFC tags
Provisioning with
QR code
Provisioning with
Bluetooth® Low
Energy
UM3146 - Rev 1
Table 5.
Comparison of provisioning solutions
This solution is presented in the current document. The bidirectional capability of the NFC tag is used to
provision the device with keys.
It is important to highlight that, with this solution, the key provisioning is not done at the factory but at
runtime when the user or an installer sets up the product for the first time. As a result, it is not necessary
to do any kind of personalization at the end of the production line.
The NFC interface is used later on in product life to collect some data/logs, configure the product or
update its firmware.
With this solution, the device is provisioned with keys at the factory. The manufacturer should set some
keys in the device and store them as well on a join server in the Cloud. The manufacturer needs to power
the device and use an interface to communicate with the product.
A QR code is put on the product to identify the device and the join server to contact for the registration of
this device.
When the user installs the product, it is necessary to install a specific application on the smartphone used
and to scan the QR code. The application contacts the join server and requests to propagate the keys to
the network server and application server.
This solution requires the implementation of a full Bluetooth® Low Energy stack.
In this solution, as for the provisioning with NFC, the keys are set in the device at runtime when the user
or installer sets up the product.
Comparison with existing provisioning solutions
Comments
UM3146
page 27/33
Need help?
Do you have a question about the ST25DV64KC and is the answer not in the manual?