https://devzone.nordicsemi.com/f/nordic-q-a/11993/questions-regarding-establishing-connectionHi All, We are in design Phase of our product and would like to use NRF52 Chipsets for it. Please Clarify our query regarding it. I have two Nordic NRF52 Chipsets , One acting as Central and other as Peripheral . This Peripheral is a Smart Watch thaten-USTelligent Community 13Wed, 24 Feb 2016 17:53:07 GMThttps://devzone.nordicsemi.com/thread/45396?ContentTypeID=1Wed, 24 Feb 2016 17:53:07 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2901c090-2790-4563-9d48-fdd9a459e673Henrik M.<p>@run_ar - can you point to an example in the SDK where this bonding is performed?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/45395?ContentTypeID=1Mon, 22 Feb 2016 04:15:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:85b86429-65f6-4afc-a8f7-c2fb198b0f3bThangaraj<p>Thanks run_ar for your quick response !!</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/45394?ContentTypeID=1Fri, 19 Feb 2016 15:37:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bf7c6b70-f83b-462a-9f58-119e8161013crun_ar<ol> <li> <p>You would have to bond with the central devices to get the address and IRK of these. I would use a pairing mode, where you advertise without a whitelist to pair with a device. This should be entered manually by the user</p> </li> <li> <p>When bonded, used the whitelist unless the user tell the watch to bond with a new device. In addition you could use a lower tx output power to limit the range of the device while in pairing mode. For authenticathion you should use MITM. This way you will have to be able to see the passkey on the watch to succesfully bond with the device.</p> </li> <li> <p>This can be handled on an application level. Basically the central will have to start scanning for the peripheral when the connection is lost, and the peripheral will have to advertise.</p> </li> </ol><div style="clear:both;"></div>