• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 8 replies
  • Subscribers 70 subscribers
  • Views 46349 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 111938
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

connecting, bonding, pairing, and whitelists

GlennEngel

I'm a bit confused about nomenclature and am looking for guidance in how best to implement the needs of my ble app. From the S110 perspective, how are connecting, bonding, pairing, and whitelists related? What do these terms mean in relation to the device_manager?

For my application I can currently discover and connect from android and read and write characteristics. At this point I would like my ble device to only allow connections from the last successful connection until a reset procedure is initiated via a button press. I've read about irks and addresses and it really sounds like using a library is the way to go. I'm not concerned with security and passkeys for my application but wonder if I should be or if there is any downside. There is no visible ui on my ble device other than an led.

What is the most straight forward means of providing the connection storage, connection denial, and reset back to 'open'?

Parents
  • 0

    This is a short description of the terms, and how they are linked together:

    • Connection: A central (master) can connect to a peripheral (slave). While the connection is active the master and slave will communicate regularly at a determined interval. This connection interval can be between 7.5 ms and 4 s.

    • Pairing: Devices that are initially connected can exchange encryption keys and encrypt the link. When they have, the link is secure and they are paired.

    • Bonding: Paired devices can be bonded. This means that they store the keys that have already been exchanged when they paired and use those again the next time they connect.

    • Whitelisting: The whitelist is used to restrict connection or scanning from any other than predetermined (known) devices.

    The SDK provides libraries in order to assist in bonding and whitelisting: The older device manager and the new (currently experimental) peer manager. You can reset all the bonding information and disable the whitelist when desierd. E.g. with the peer manager you can delete all bonds with pm_peer_delete_all() and create a new empty whitelist (pm_wlist_create())and set it (pm_wlist_set()).

  • 0 in reply to Einar Thorsrud

    Just to recap my understanding - A device can be connected to a master and communicate via configured characteristic. If they exchange encryption keys they can become bonded if the keys are stored for the next connection. This somehow allows a whitelist to be used as the stored keys allow the device to recognize a previously connected master even if it has a new mac address. It sounds like whitelisting is not usable with most phones unless they are paired and bonded.

Reply
  • 0 in reply to Einar Thorsrud

    Just to recap my understanding - A device can be connected to a master and communicate via configured characteristic. If they exchange encryption keys they can become bonded if the keys are stored for the next connection. This somehow allows a whitelist to be used as the stored keys allow the device to recognize a previously connected master even if it has a new mac address. It sounds like whitelisting is not usable with most phones unless they are paired and bonded.

Children
No Data
Related