Central link timing-events are added relative to already running central link timing-events.
Central link timing-events are offset from each other by tevent depending on the configuration of the connection. For details about tevent, see Initiator timing.
Multilink scheduling - one or more connections as a Central, factored intervals shows a scenario where two central links are established. C0 timing-events correspond to the first Central connection, and C1 timing-events correspond to the second Central connection. C1 timing-events are initially offset from C0 timing-events by tevent-C0. In this example, C1 has exactly double the connection interval of C0 (the connection intervals have a common factor which is “connectionInterval 0”), so the timing-events remain forever offset by tevent-C0.
In Multilink scheduling - one or more connections as a Central, unfactored intervals the connection intervals do not have a common factor. This connection parameter configuration is possible, though this will result in dropped packets when events overlap. In this scenario, the second timing-event shown for C1 is dropped because it collides with the C0 timing-event.
Multilink scheduling with eight connections as a Central and minimum interval shows eight concurrent links as a Central with an event length of 2.5 ms and a connection interval of 20 ms. In this case, all eight Centrals will have a connection event within the 20 ms interval, and the connection events will be 2.5 ms apart.
Multilink scheduling of connections as a Central and interval > min shows a scenario similar to the one illustrated above except the connection interval is longer than 20 ms, and Central 1 and 4 has been disconnected or does not have a timing-event in this time period. It shows the idle time during a connection interval and that the timings of central link timing-events are not affected if other central links disconnect.
