Timeout Resolvable Private Address

RE: Timeout Resolvable Private Address

Jørgen Holmefjord — Thu, 05 Mar 2020 16:38:43 GMT

I would recommend you to read the following chapter in the Bluetooth specifications v5.0 - Vol 6, Part B, Chapter 6. This should answer your questions.

Bonding and flash storage of keys are handled by the Peer Manager library.

RE: Timeout Resolvable Private Address

nobody_19 — Wed, 04 Mar 2020 21:20:06 GMT

So now I am a bit confused.

I am trying to bond an android 9.0 (central) smartphone and a nrf52832 with the SD 4.0.2 (peripheral).

So which one is defining the the RPA change interval?

Central
Peripheral
Both (lower cycle interval)?

Is the android device allways doing a RPA change, also when the peripheral is not able to do that?

For what I have to verify th ethe IRK?

Should not after I bonded succesful, the whitelist be updated with the IRK, IRK count etc.?

Did I understood it correct,the softdevice does not stores the IRK permanently? That is the task of my application?

Thanks a lot

RE: Timeout Resolvable Private Address

Jørgen Holmefjord — Wed, 04 Mar 2020 13:03:53 GMT

Hi,

There is no timeout, but you can set the private_addr_cycle_s to the interval at which you want the address to be updated by the softdevice (default is BLE_GAP_DEFAULT_PRIVATE_ADDR_CYCLE_INTERVAL_S). You can also use a timer in your application to update the address yourself.

Maximum address update interval is set by BLE_GAP_MAX_PRIVATE_ADDR_CYCLE_INTERVAL_S.

As far as I know, there is no way to change the address settings in nRF Connect App, it will use the default from the phone OS/HW.

If the devices have established a bond, the address can be verified using the IRK. This thread has some good information.

Best regards,
Jørgen