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

Advertising service UUID, SIG or VS ?

Hello,

I have an application that advertise specific data. Data is long enough that I cannot fit my 128bit service UUID. I think of 3 options:

1. Use my service UUID but marking it as `BLE_UUID_TYPE_BLE`
2. Use a BLE SIG service UUID that I dont really offer.
3. Implement some additional bytes in manufacturer data to be able to distinguish my device.

I know that 1. and 2. are not perfect but I wonder if they are at least 'legal'. Does bluetooth standard says something against it?

Regards

Parents Reply Children
  • Hi Michael

    Sorry for the slow response, I was out on travel all last week. 

    I don't think the spec itself discusses this, but the Bluetooth SIG clearly does in the following article:
    https://www.bluetooth.com/specifications/assigned-numbers/16-bit-uuids-for-members/

    In particular, the comment in bold: "BLUETOOTH SIG MEMBERS SHALL USE THE NUMBER ASSIGNED TO YOU BY BLUETOOTH SIG ONCE THE PROCESS IS COMPLETED. DO NOT ASSUME A SPECIFIC NUMBER IS AVAILABLE."

    What the article discusses is a program that allows companies to purchase 16-bit UUID's for a $2500 fee, which is a 4th alternative that I forgot to mention earlier. 

    By doing this you would get a legal and safe way to use a 16-bit UUID, that is assigned to your company alone, the only drawback being that you have to pay a one time fee. 

    Best regards
    Torbjørn

Related