<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>BLE Assigned UUID 128-bit Base</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/90010/ble-assigned-uuid-128-bit-base</link><description>Hi All, 
 I just had a quick question about the SDK as it pertains to assigned services. Is the BLE Base UUID defined anywher ein the SDK files? i have looked all over; ble_types.h, ble_gap.h, ble_gatt.h, the files contain definitions for many 16-bit</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 15 Jul 2022 11:44:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/90010/ble-assigned-uuid-128-bit-base" /><item><title>RE: BLE Assigned UUID 128-bit Base</title><link>https://devzone.nordicsemi.com/thread/377177?ContentTypeID=1</link><pubDate>Fri, 15 Jul 2022 11:44:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:222210e0-c8c7-428d-a30a-dc908dde35fa</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The base UUID for 16 bit UUIDs is not explicitly mentioned in the SDK, since it is handled by the stack itself and the SoftDevice Controller is not provided as source code. On the SDK level, the UUID is registered with a UUID type of 16 bit UUID, and only the 16 bit part is explicitly needed.&lt;/p&gt;
&lt;p&gt;The SDK uses different macros for handling different types of UUID. See e.g. the &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/zephyr/connectivity/bluetooth/api/uuid.html"&gt;API reference for Universal Unique Identifiers (UIIDs)&lt;/a&gt;. The API contains defines for SIG defined UUIDs such as BT_UUID_DIS, which should be what you are looking for.&lt;/p&gt;
&lt;p&gt;For anyone implementing this on a different platform, where for some reason 16 bit UUIDs must be implemented through manually applying the full 128 bit UUID, the &amp;quot;base UUID&amp;quot; has the value 0000xxxx-0000-1000-8000-&lt;br /&gt;00805F9B34FB, where the xxxx is where the 16 bit value is positioned. Ref. the Bluetooth core specification v5.3, Vol 3, Part B, section 2.5.1 UUID.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>