Pairing & Bonding issue with concurrent peripheral + central app

RE: Pairing & Bonding issue with concurrent peripheral + central app

Amanda Hsieh — Thu, 12 Aug 2021 13:24:47 GMT

Hi,

Seems BLE_GAP_IO_CAPS_KEYBOARD_ONLY or BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY can get the BLE_GAP_EVT_AUTH_KEY_REQUEST event. See this Passkey Entry with static passkey MSC. Then static passkey cannot use the same security parameter for SEC_PARAMS_IO_CAPABILITIES on multirole. If you want to use the same security parameters on multirole, you could take a look at this LE Secure Connections Multirole Example.

-Amanda H.

RE: Pairing & Bonding issue with concurrent peripheral + central app

vineeth17 — Wed, 11 Aug 2021 13:21:13 GMT

Hi,

Thanks for the response.

When I tried the " #define SEC_PARAMS_IO_CAPABILITIES BLE_GAP_IO_CAPS_DISPLAY_YESNO"

the pairing between the Device A and Device C works, but the pairing between the Device A and Device B failed, because I didn't get the BLE_GAP_EVT_AUTH_KEY_REQUEST in Device A.

RE: Pairing & Bonding issue with concurrent peripheral + central app

Amanda Hsieh — Wed, 11 Aug 2021 09:35:43 GMT

Hi,

Try to set BLE_GAP_IO_CAPS_DISPLAY_YESNO for For the Device A.

#define SEC_PARAMS_IO_CAPABILITIES   BLE_GAP_IO_CAPS_DISPLAY_YESNO

-Amanda H.

RE: Pairing & Bonding issue with concurrent peripheral + central app

vineeth17 — Tue, 10 Aug 2021 17:42:14 GMT

Thanks for the response.

We have 3 devices

1) Simultaneous Central + Peripheral side name it as "Device A"

2)External Peripheral side name it as "Device B"

3)External Central Side name it as "Device C"(like NRF connect APP)

Yes, When I tried the pairing and static passkey implementation with Device A and Device C .It just displays the pass key, I can't enter the passkey.( parameters attached below)

But for the static passkey implementation with Device A and Device B, I Used the below parameters and its working fine.

So how to achieve the bonding , pairing and static passkey implementation with the Device A and Device C using the same parameters (Attached below) ?

For the Device A

#define SEC_PARAM_BOND                  1                                           /**< Perform bonding. */
#define SEC_PARAM_MITM                  1                                           /**< Man In The Middle protection not required. */
#define SEC_PARAM_LESC                  0                                           /**< LE Secure Connections not enabled. */
#define SEC_PARAM_KEYPRESS              0                                           /**< Keypress notifications not enabled. */
#define SEC_PARAM_IO_CAPABILITIES       BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY                       /**< No I/O capabilities. */
#define SEC_PARAM_OOB                   0                                           /**< Out Of Band data not available. */
#define SEC_PARAM_MIN_KEY_SIZE          7                                           /**< Minimum encryption key size in octets. */
#define SEC_PARAM_MAX_KEY_SIZE          16                                          /**< Maximum encryption key size in octets. */
#define SCAN_DURATION_WITELIST          0

For the Device B

#define SEC_PARAM_BOND                      1                                       /**< Perform bonding. */
#define SEC_PARAM_MITM                      1                                       /**< Man In The Middle protection not required. */
#define SEC_PARAM_LESC                      0                                       /**< LE Secure Connections enabled. */
#define SEC_PARAM_KEYPRESS                  0                                       /**< Keypress notifications not enabled. */
#define SEC_PARAM_IO_CAPABILITIES           BLE_GAP_IO_CAPS_DISPLAY_ONLY                    /**< No I/O capabilities. */
#define SEC_PARAM_OOB                       0                                       /**< Out Of Band data not available. */
#define SEC_PARAM_MIN_KEY_SIZE              7                                       /**< Minimum encryption key size. */
#define SEC_PARAM_MAX_KEY_SIZE              16

RE: Pairing & Bonding issue with concurrent peripheral + central app

Amanda Hsieh — Tue, 10 Aug 2021 10:58:21 GMT

Hi,

I think it should also work in the peripheral. Do you see any issues?

-Amanda H.

RE: Pairing & Bonding issue with concurrent peripheral + central app

vineeth17 — Mon, 09 Aug 2021 12:36:20 GMT

Thanks for the response.

We have 3 devices

1) Simultaneous Central + Peripheral Role Device

2)External Peripheral side

3)External Central Side

I want to pair/bond other peers in the ( central + peripheral ) (concurrent).

I have already done the bonding , pairing and static passkey implementation in the concurrent central (to another peripheral device). I would like to do the same for the concurrent peripheral as well. The parameters set for the central + peripheral and external peripheral side are already shared above.

Is it possible to do the bonding , pairing and static passkey implementation in the concurrent peripheral side with external central(Like NRF connect) using the same parameters and peer manager. Please note that I have already set the parameters for the central side in peer manager. Does this limit me from doing the same in peripheral ?

RE: Pairing & Bonding issue with concurrent peripheral + central app

Amanda Hsieh — Mon, 09 Aug 2021 11:41:33 GMT

Hi,

The Paired devices can be bonded. This means that they store the keys that have already been exchanged when they are paired and use those again the next time they connect. it cannot only do bonding without pairing.

See this post.

-Amanda H.

RE: Pairing & Bonding issue with concurrent peripheral + central app

vineeth17 — Fri, 06 Aug 2021 16:37:59 GMT

Thanks for the response.

Is there any other way to achieve this?

I want to do the bonding and pairing in concurrent central side with external peripheral(Already done using peer manager) and bonding only with the concurrent peripheral side with external central(like NRF connect ).

RE: Pairing & Bonding issue with concurrent peripheral + central app

Amanda Hsieh — Fri, 06 Aug 2021 15:03:05 GMT

Hi,

[quote user=""]I would like to know Is it possible to achieve the bonding without pairing here using the same parameters which I have been used already for the other side using peer manager?.[/quote]

The peer manager (PM) doesn't support that because PM initiates pairing first, encrypts the link, then bonds (could be optional).

-Amanda H.