RE: nRF51822 Identification based on device address

run_ar — Wed, 18 Jan 2017 08:11:10 GMT

You can use the static address as well. Just be aware that you cannot authenticate anything based on the address.

RE: nRF51822 Identification based on device address

Aymen Rejeb — Mon, 16 Jan 2017 17:19:48 GMT

Thanks a lot run_ar,

So as I can conclude the only way to globally identify a nRF51 BLE device is to go through a resolvable private address (using the IRK) process? am I correct?

Kind Regards, Ayman.

RE: nRF51822 Identification based on device address

run_ar — Thu, 12 Jan 2017 10:02:44 GMT

A resolvable private address can be resolved using the IRK. However the IRK is normally exchanged as part of the bonding process. But it would probably be possible to get this as part of the production process if you choose to go that way. Another option would be to identify the device based on advertisement data., e.gg. you could advertise an id as manufacturer specific data.

Please note that security whise it's fairly easy to copy a device address or advertisement data to impersonate another device, so identification between a central an peripheral should be done based on the LTK exchange while bonding. But since this is generated during the bonding process you cannot use it as a global identifier.

Another issue is what kind of central you are using, as an example iOS doesn't forward the device address to the application so it's not possible to use this for identification. But manufacturer specific data could be used.