Custom Service Data UUID

RE: Custom Service Data UUID

24thFrame — Fri, 17 Jul 2020 14:17:01 GMT

Thank you! I am already using what you showed (setting uuids_complete.p_uuids with my custom service ID).

Unfortunately, in the BLE advertising module in the SDK, we have only implemented support for 16-bit UUIDs when it comes to Service Data. Sorry for this inconvenience.

Ah thank you, that answers my question. I guess I should either use the manufacture data or just use the service data with a generic ID.

RE: Custom Service Data UUID

Sigurd — Fri, 17 Jul 2020 08:45:22 GMT

When advertising what 128 bit service UUID you have, it's usually done like this (from ble_app_uart example), by putting it into the "Service UUID" field.

static void advertising_init(void)
{
    uint32_t               err_code;
    ble_advertising_init_t init;

    memset(&init, 0, sizeof(init));

    init.advdata.name_type          = BLE_ADVDATA_FULL_NAME;
    init.advdata.include_appearance = false;
    init.advdata.flags              = BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE;

    init.srdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
    init.srdata.uuids_complete.p_uuids  = m_adv_uuids;

    init.config.ble_adv_fast_enabled  = true;
    init.config.ble_adv_fast_interval = APP_ADV_INTERVAL;
    init.config.ble_adv_fast_timeout  = APP_ADV_DURATION;
    init.evt_handler = on_adv_evt;

    err_code = ble_advertising_init(&m_advertising, &init);
    APP_ERROR_CHECK(err_code);

    ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);
}

where

static ble_uuid_t m_adv_uuids[]          =                                          /**< Universally unique service identifier. */
{
    {BLE_UUID_NUS_SERVICE, NUS_SERVICE_UUID_TYPE}
};

You are instead trying to put your 128bit service UUID in the "Service Data" field.

Looking at the Bluetooth Core Specification Supplement, this is described like this:

Unfortunately, in the BLE advertising module in the SDK, we have only implemented support for 16-bit UUIDs when it comes to Service Data. Sorry for this inconvenience.

RE: Custom Service Data UUID

24thFrame — Wed, 15 Jul 2020 22:54:01 GMT

Thanks Sigurd, good catch with the 056 -> 0x56. :)

Sorry, I don't think I phrased my question correctly. I'm aware that the base ID is the base for all bytes except 13 and 14 bytes, which are replaced by the two bytes for each specific service or characteristic (in my case TIMECODE_SERVICE_UUID, though I now realize from your example that I should be setting it to 0x0001 for consistency). What I don't understand is how to pass that value to service_data.service_uuid.

For example, with the code above, service_data.service_uuid = TIMECODE_SERVICE_UUID will return 00000001-0000-1000-8000-00805f9b34fb (according to the Bluetooth library on my phone app I am working on), the Bluetooth base ID with my TIMECODE_SERVICE_UUID (0x0001). I need it to be my custom service ID (3fe10001-3073-4194-a4fa-2d14c2742e8b, which is TIMECODE_SERVICE_UUID using TIMECODE_SERVICE_UUID_BASE as the base).

Is this possible? Or am I misunderstanding how service data sends the ID (eg. it it always 2 bytes, as the expected value for p_service_data_array.service_uuid is uint16_t)? Or maybe the ID I posted above is how the app library I am using on my phone interprets the service ID in the service data?

RE: Custom Service Data UUID

Sigurd — Tue, 14 Jul 2020 07:46:59 GMT

Hi,

Note that the service UUID is formed by the UUID base, but byte 13 and 14 of the UUID is formed by the 2 bytes of the service UUID.

E.g. for the NUS service,
The BASE is {{0x9E, 0xCA, 0xDC, 0x24, 0x0E, 0xE5, 0xA9, 0xE0, 0x93, 0xF3, 0xA3, 0xB5, 0x00, 0x00, 0x40, 0x6E}}
and the 2 byte UUID for the NUS service is 0x0001

The complete NUS service UUID will then be 0x9E, 0xCA, 0xDC, 0x24, 0x0E, 0xE5, 0xA9, 0xE0, 0x93, 0xF3, 0xA3, 0xB5, 0x01, 0x00, 0x40, 0x6E

Byte 13 and 14 in your TIMECODE_SERVICE_UUID_BASE, "0xDA, 0x19,", is therefore ignored.

Also note that in your TIMECODE_SERVICE_UUID_BASE, your second byte, 056, is not defined as hex value.