Concurrent Dual Role BLE Connection Scheduling

RE: Concurrent Dual Role BLE Connection Scheduling

Hung Bui — Tue, 28 Feb 2023 08:20:12 GMT

Hi Dylan,

Thanks for the explanation. The challenge with the scheduler on resource constrained embedded device is that we need to balance between performance, robustness and simplicity. As far as I know the scheduling priority is hardcoded as you can find in the priority table in the documentation. So no option to specify a connection should have a higher priority than the other.
A connection may have higher priority than other but it's only applied when the connection is going to be terminated due to timeout.

RE: Concurrent Dual Role BLE Connection Scheduling

dpm — Mon, 27 Feb 2023 16:40:16 GMT

Yes, I am looking to have the connection event extended. The connection event length extension is enabled (default). And we can see it extending, but it looks like it will not extend if there is an event scheduled on the other connection. "A connection event cannot be extended if it will collide with another timing-event, regardless of the priorities of the timing-events".

Is there anyway to prioritize the connection event extension over servicing the other connection?

RE: Concurrent Dual Role BLE Connection Scheduling

Hung Bui — Mon, 27 Feb 2023 14:33:04 GMT

Hi Dylan,
Please correct me if I'm wrong. My understanding is that you want dynamic scheduling, meaning that the even length can be extended based on the amount of data that the peer or the device need to send in a certain connection event. And this can exceed the max event length configuration.

From my undestanding that is already supported in our scheduler when connection event length extension is enable. Please have a look here.
By default this feature should already be enable, see here.
Could you double if in your case the connection event length extension is enabled or not ?