https://devzone.nordicsemi.com/f/nordic-q-a/313/why-service-discovery-command-of-ble-takes-a-lot-of-timeHi, I am trying to test my UART using some simple loopback test, and I have noticed that the service discovery command of BLE will occupy the CPU a quite long time. I am just wondering if there is any way to reduce it? Does the SoftDevice handle the serviceen-USTelligent Community 13Tue, 20 Aug 2013 11:19:34 GMThttps://devzone.nordicsemi.com/thread/1647?ContentTypeID=1Tue, 20 Aug 2013 11:19:34 GMT137ad170-7792-4731-bb38-c0d22fbe4515:603704de-4590-4cef-8583-f7f6316c95acHung Bui<p>Hi,</p> <p>Service Discovery is a process of discover Primary Services, its relationship and its characteristics UUIDs and values. This process is described at section 4.4, Part G Vol 3 in Bluetooth Core Specification V4.0</p> <p>It&#39;s not a single radio request but requires lots of requests from client to go through the server Attribute table. On each connection event you can only send less than 6 requests, depend on the master property. This explains why service discovery may take a long time if your connection interval is long.</p> <p>So the way to speed up service discovery is to reduce the connection interval when doing service discovery. Depend on the master , you can get the connection interval as low as 7.5ms.</p><div style="clear:both;"></div>