How to store characteristic handles in NVM after pairing/bonding

[Michael-1965]

Hi.

In other discussion I have seen pairing/bonding should store all necessary parameters of a discovered service. It's possible then to reconnect to a bonded device without doing the service discovery again. So for example parameters like the characteristic handles or enabled notifications should be stored in NVM together with the pairing keys during the pairing/discovery process. When connecting to this bonded device, the handles of the characteristics should be restored and be usable.

How can I do that? Up to now I have not seen the procedure to store handles of characteristic together with the pairing keys.

Thanks in advance.

Cheers Michael

[Einar Thorsrud]

Hi Michael,

The peer manager supports storing the remote database, which is suitable in this case. Typically it is used so that the database is stored once service discovery has completed (when handling the NRF_BLE_GATTS_C_EVT_DISCOVERY_COMPLETE event) by calling pm_peer_data_remote_db_store(). When connecting to a allready bonded peer at a later point the database is restored by a call to pm_peer_data_remote_db_load(). There are two examples that demonstrate this in the nRF5 SDK: GATT Service Client Example Application and Apple Notification Center Service (ANCS) Client Application. See Storing data section in the Peer manager documentation for more details.

Einar

[Michael-1965]

Hi Einar.

Thanks a lot, I will have a look.

Cheers Michael

[Michael-1965]

Hi Einar.
Thanks, it works now. The problem is solved. We can close the ticket.
Cheers Michael