https://devzone.nordicsemi.com/f/nordic-q-a/78503/naming-problemThe interface &quot;sd_ble_gap_adv_start&quot; uses &quot;adv&quot; to indicate broadcast, but the interface &quot;ble_advertising_start&quot; uses &quot;advertising&quot; to indicate broadcast. Why not use the same name?en-USTelligent Community 13Thu, 12 Aug 2021 12:08:16 GMThttps://devzone.nordicsemi.com/thread/324668?ContentTypeID=1Thu, 12 Aug 2021 12:08:16 GMT137ad170-7792-4731-bb38-c0d22fbe4515:204a8dc9-c019-411e-9715-1cf4429fb430Ding<p>Is it mainly to prevent customer misuse?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/324610?ContentTypeID=1Thu, 12 Aug 2021 08:49:57 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a0fa92f9-8fe3-4ea0-806d-8316cb4eadd8Turbo J<p>Two totally different APIs.</p> <p>The sd_ble_xxx macros call directly into the softdevice and follow a common naming scheme.</p> <p>The ble_advertising_xxx functions are executed in the application space and will eventually call the sd_ble_xxx softdevice, but users are <strong>not</strong> supposed to call the softdevice functions direcly as that can cause errors.</p> <p></p> <p>TL;DR Different naming scheme is intentional.</p><div style="clear:both;"></div>