Connection timing as a central

Central link timing-events are added relative to already running central link timing-events.

Central link timing-events are offset from each other by t_EEO depending on the bandwidth requirement of links. Refer Initiator timing for details about t_EEO and Table 2 for its timing ranges.

Figure 1 shows a scenario where there are two links as a central established. C0 timing-events correspond to the first connection as a central made and C1 timing-events correspond to the second connection made. C1 timing-events are initially offset from C0 timing-events by t_EEO-C0. C1, in this example, have 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 t_EEO-C0.

In Figure 2 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.

Figure 3 shows the maximum possible number of links as a Central (8) at the same time with minimum bandwidth (LOW bandwidth configuration) and with the minimum connection interval (17.5 ms ), without having timing-event collisions and dropped packets. In this case, all available time is used for the links as a central.

Figure 4 shows a scenario similar to the one illustrated above except the connectionInterval is longer than the minimum, and Central 1 and 4 has been disconnected or does not have an timing-event in this time period. It shows the idle time during connection interval, and also shows that the timings of central link timing-events are not affected if other central links disconnects.