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 tEEO depending on the bandwidth requirement of links. Refer to Initiator timing for details about tEEO 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 tEEO-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 tEEO-C0.

Figure 1. Multilink scheduling - one or more connections as a Central, factored intervals

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 2. Multilink scheduling - one or more connections as a Central, unfactored intervals

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

Figure 3. Multilink scheduling with maximum connections as a Central and minimum interval

Figure 4 shows a scenario similar to the one illustrated above except the connection interval 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.

Figure 4. Multilink scheduling of connections as a Central and interval > min

Documentation feedback | Developer Zone | Subscribe | Updated 2016-12-09