Advertiser is started as early as possible, asynchronously to any other role timing-events. If no roles are running, advertiser timing-evens are able to start and run without any collision.
When other role timing-events are running in addition, the advertiser role timing-event may collide with those. Figure 2 shows a scenario of advertiser colliding with peripheral (P).
Directed advertiser is different compared to other advertiser types because it is not periodic. The scheduling of the single timing-event required by directed advertiser is done in the same way as other advertiser type timing-events. Directed advertiser timing-event is also started as early as possible, and its priority (refer to Table 1) is raised if it is blocked by other role timing-events multiple times.