resolve BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE address without using whitelist advertising

[chd]

Hi there,

Is there any way to resolve a BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE address without using whitelist advertising? If not, I guess I should implement the ah function by myself.

I know that Nordic softdevice certainly has this function implemented. My question is, could I have the access to it?

Thank you for any information

[chd]

@Hung, Ulrich: Thank you so much for your swift responses. I haven't tested your solutions yet but after a quick look I think both of the implementations can resolve the problem I mentioned in the first time. Another question: currently I use the irk directly to identify my peer devices since I believe that the irk is unchanged during device's lifetime. Am I right?

[Ulrich Myhre]

This is correct. An IRK should be static as long as the bond is valid. For our devices it is based on some randomly generated factory settings, but can be manually overridden with the options API.

[chd]

What do you mean by "as long as the bond is valid"? As my observation the irk is unchanged even when I do a manually "forget device" in bluetooth settings (iOS) then do the bonding again. Did you mean that as long as the 2 devices are successfully bonded to each other?

[Ulrich Myhre]

Yes, the IRK has to be static for the life-time of a bond if the devices are supposed to recognize each other for subsequent connections. Sorry for the confusion, but in theory it does not have to be static forever, so there might be devices out there that change their IRK on a hard reset (that deletes all bonds). In practice it will likely be static, and you should assume as much.