https://devzone.nordicsemi.com/f/nordic-q-a/1953/ble-nrf51-how-to-not-stop-advertising-on-connectThe way i understood GAP, it&#39;s supposed to be some sort of stateless key/value protocol. In order to get GAP working with an ibeacon, i took the ibeacon example, and changed m_adv_params.type from BLE_GAP_ADV_TYPE_ADV_NONCONN_IND to BLE_GAP_ADV_TYPE_ADV_INDen-USTelligent Community 13Fri, 21 Mar 2014 09:48:12 GMThttps://devzone.nordicsemi.com/thread/8406?ContentTypeID=1Fri, 21 Mar 2014 09:48:12 GMT137ad170-7792-4731-bb38-c0d22fbe4515:02f9261e-12c6-4b34-9da8-272048fb7339Ole Morten<p>I can&#39;t really see any way to solve your use case except to let each device connect, run the query and then disconnect. This will cause small periods of lockout for the other devices, but these should be short (i.e. &lt; 1 s), so unless you have very many devices and very short response time requirements, I don&#39;t think this should be a problem.</p> <p>The problem with a pure Broadcaster/Observer setup is the requirement to send a query to the device, as you don&#39;t have control over the contents of the Scan Request that the Observer sends. Its contents are defined in the Core Specification, and there is no room for user data. There is hence no way to transfer the value of the query to the Broadcaster without establishing a connection.</p> <p>I would not describe the GAP layer of the BLE specification as stateless, but it might make sense to talk about GATT as stateless. This is the layer at which data transfers happen once in a connection, but even here there is in some sense a state (for example if you&#39;re in the middle of a Long Writes, or if have enabled notifications).</p><div style="clear:both;"></div>