This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Relation between 16- and 128-bit UUIDs

When using custom 128-bit base UUIDs and 16-bit UUIDs to address services or characteristics within the formerly specified base UUID, it seems the Nordic softdevices always build the resulting UUID by replacing bytes 12 and 13 of the base UUID with the 16-bit UUID (the digits 'X' in this sample UUID: 8353XXXX-14ee-11e9-ab14-d663bd873d93).

I understand this rule is used for 16-bit UUIDs within the Bluetooth SIG base UUID and thus the Nordic softdevice can handle custom services more efficiently when following this rule for these custom services, too.

My question finally is: is this required by the Bluetooth specifications to always build resulting UUIDs by placing the 16-bit UUID to bytes 12 and 13? I know of the specification of this regarding the Bluetooth SIG base UUID, but not for custom UUIDs.

Thank you in advance!

Related