How can a peripheral maintain multiconnections with several centrals in [Experimental: BLE Multiperipheral Application]

[kren]

Hi there, 

I just found an example, Experimental: BLE Multiperipheral Application, https://www.nordicsemi.com/DocLib/Content/SDK_Doc/nRF5_SDK/v15-2-0/ble_sdk_app_multiperipheral?1505#project_multiperipheral_setup

I have a question about the connection parameters:

I just had a quick look at the source code, I found that a peripheral in this example can support 4 connections simultaneously, but as I know, the connection parameters like:

• connection interval
• transmitWindowOffset
• transmitWindowSize, etc

they are assigned to peripheral by central, how can the central avoid the connection overlap? 

For example, centralA connects with this peripheral and assigns the connection interval, coincidently, centralB's connection interval and offset are overlapped with centralA, it's possible, how does peripheral handle this kind of situation?

Kai 

[Einar Thorsrud]

Hi,

You are right that there might (and typically will from time to time) be overlap between events on the different links for a multi-peripheral device. This is in principle no different from other conflicts in other multi role configurations described under Peripheral connection setup and connection timing. In that case, when events collide the event with highest priority will be handled, and the other will be dropped. However, if a connection event is dropped on one link this will get higher priority so that it will typically not be dropped if there is also a collision for the next connection event. See SoftDevice timing-activities and priorities for details.

You can influence the likelihood of overlaps by following the suggestions from Suggested intervals and windows (more so if you control both the central and peripheral devices).

[kren]

Thank you so much for the prompt reply and it answered my question, totally clear!