RE: CAF BLE state bond limit

langestefann — Fri, 27 Aug 2021 08:19:23 GMT

Hi Kenneth,

Thanks a lot for your very detailed answer. This cleared up many doubts I had.

Kind regards,

Stefan

RE: CAF BLE state bond limit

Kenneth — Mon, 23 Aug 2021 15:13:36 GMT

Hi,

Some background information:

BLE state module was previously part of nRF Desktop application, then it was separated to CAF. It follows nRF Desktop's assumptions related to Bluetooth operations. E.g. it assumes that peripheral has one bond per Bluetooth local identity, but the peripheral could use multiple Bluetooth local identities. When peripheral device uses given local identity, only the Bluetooth central that is bonded with that local identity can connect with the peripheral (if peripheral device has no bonded central for given local identity, any central may connect and bond to it).

Because of this assumption, the module disallows for peripheral to have more than one bond per local identity.

To answer your questions:

How should I use the CAF BLE state module regarding bonds? I would like to be able to store multiple bonds.

The Bluetooth bonds management is not actually performed by CAF BLE state. Still, you could use multiple Bluetooth local identities and switch between them using ble_peer_operation_event. In nRF Desktop this task is implemented in ble_bond. The ble_bond module has many application-specific features (e.g. in nRF Desktop Bluetooth bonds are controlled using click_event related to predefined button), so the module is not part of CAF. You could implement needed functionalities in similar way for your application using Zephyr's Bluetooth API. See the following documentation pages for details:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/nrf_desktop/doc/ble_bond.html#nrf-desktop-ble-bond - BLE bond module from nRF Desktop (source code available in src/applications/nrf_desktop/modules/ble_bond.c)

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/libraries/caf/caf_overview.html#c.ble_peer_operation_event - BLE peer operation event

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/nrf_desktop/README.html#bluetooth-in-nrf-desktop - Bluetooth guide related to nRF Destkop and Bluetooth Kconfig options that could be relevant for your application.

How can I delete bond information on the peripheral device (nRF52840)?

Use bt_unpair function. https://docs.zephyrproject.org/latest/reference/bluetooth/gap.html#c.bt_unpair

See https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/nrf_desktop/doc/ble_bond.html#peer-erasing for details regarding bond erase in nRF Desktop. Keep in mind that peer erase functionality on nRF52840DK is by default enabled only in configuration that works as a dongle. You must enable it in configuration in order to use it for other configurations.

I have noticed that if I delete bond information from my phone and try to reconnect to my peripheral device it will refuse the connection. Is there any way to handle this behaviour so that I can allow the device to reconnect again?

If your phone (central) has deleted bond information it is expected to be unable to reconnect with peripheral device. In that case you should remove bond information from peripheral and bond with the phone again. If you really want to let your phone to connect with the peripheral overwriting bond on peripheral device you should enable CONFIG_BT_SMP_ALLOW_UNAUTH_OVERWRITE. Keep in mind that it's not a good practice, since this would enable cases where an attacker could copy the peer device address to connect and start an unauthenticated pairing procedure to replace the existing bond.