https://devzone.nordicsemi.com/f/nordic-q-a/8969/differentiation-of-events-in-ble-librariesI&#39;m looking at the ble_app_hrs example and I&#39;m confused about how the drivers are able to differentiate between events originating from various services/characteristics. For example, in main.c under the ble_evt_dispatch we have: void ble_evt_dispatchen-USTelligent Community 13Sun, 30 Aug 2015 01:39:54 GMThttps://devzone.nordicsemi.com/thread/33019?ContentTypeID=1Sun, 30 Aug 2015 01:39:54 GMT137ad170-7792-4731-bb38-c0d22fbe4515:973ff05f-3820-4d95-a0e0-959626ff0042RK<p>It doesn&#39;t have to differentiate the source for a connection event, a connection event is global to the peripheral, not restricted to a given service, so in this case each service which cares about whether or not it&#39;s connected stores the connection handle in its own data structure.</p> <p>If you look at other events, like handling reads and writes, you&#39;ll see that those are differentiated by checking the handle of the characteristic being read/written which is available for those events. For an example of that, look at the ble_rscs code, there are many other examples too.</p> <pre><code>if (p_evt_write-&gt;handle == p_rscs-&gt;meas_handles.cccd_handle) { on_meas_cccd_write(p_rscs, p_evt_write); } </code></pre><div style="clear:both;"></div>