Direct advertising with unbonded Android phone's IRK

RE: Direct advertising with unbonded Android phone's IRK

ovrebekk — Wed, 06 Feb 2019 15:09:06 GMT

The problem in this case is that the directed advertising packet will not be reported to the application as a normal advertising packet, so the phone would have to know about the device in some other way.

This is outside our control since it is handled by the Bluetooth stack in the phone.

Best regards
Torbjørn

RE: Direct advertising with unbonded Android phone's IRK

Pureer — Fri, 01 Feb 2019 09:13:33 GMT

Hi ovrebekk ,

In my phone Oneplus3 Android8.0,nrf52832 with direct advertising didn't show up in nRF Connect's list, but I didn't close the device tab ,so I can push the connect button.

RE: Direct advertising with unbonded Android phone's IRK

ovrebekk — Fri, 01 Feb 2019 08:22:03 GMT

How are you scanning for the device on the phone side?

I don't know if nRF Connect it set up to show direct advertisers, but I will check with the developer when he is in office.

Best regards
Torbjørn

RE: Direct advertising with unbonded Android phone's IRK

Pureer — Fri, 01 Feb 2019 01:51:53 GMT

ovrebekk,whitelist with manual IRK is working fine,do you know why direct advertising didn't work with manual IRK? What did I miss in my code above?According to BT core Vol 6 Part D 5.4 ,it should work.

RE: Direct advertising with unbonded Android phone's IRK

ovrebekk — Thu, 31 Jan 2019 10:02:34 GMT

It sounds like white listing is the way to go then. If you include the BLE address and OOB pairing data in the sound wave transmission you can use this information to set up the white list in the peripheral.

If you want the phone to only try to connect to peripherals that have received the sound wave information, you could include some information here that needs to be reflected in the advertise packet sent from the peripheral (for instance you can generate a random number that needs to be included in the advertise packet, and only try to connect to advertisers that include this).

Best regards
Torbjørn

RE: Direct advertising with unbonded Android phone's IRK

Pureer — Wed, 30 Jan 2019 07:42:27 GMT

ovrebekk, this is a bit like nfc pairing,I call it sound wave pairing but data is one-way transmission, people take up the phone and close to the peripheral, peripheral will get the IRK.

By the way , whitelist works fine ,direct advertising dosen't work.

RE: Direct advertising with unbonded Android phone's IRK

ovrebekk — Wed, 30 Jan 2019 07:27:59 GMT

Who decides then which phone should be connected to which peripheral, if there is no human to control the procedure?

Is this controlled from the cloud?

Best regards
Torbjørn

RE: Direct advertising with unbonded Android phone's IRK

Pureer — Tue, 29 Jan 2019 14:41:26 GMT

Hi,

My goal is to establish a connection without human involved. And if there has many peripherals,it will take a lot time to find specific peripheral. So I think direct advertising is a good way.

RE: Direct advertising with unbonded Android phone's IRK

ovrebekk — Tue, 29 Jan 2019 14:27:46 GMT

Why can't you bond to the phone that you want to connect to?

If you don't bond with the phone first you don't have any guarantee that the phone will accept the connection.

Best regards
Torbjørn

RE: Direct advertising with unbonded Android phone's IRK

Pureer — Tue, 29 Jan 2019 03:24:29 GMT

Below is my code snippets

//Global var
ble_gap_id_key_t oneplus3_key = {
    .id_addr_info={
        0,
        BLE_GAP_ADDR_TYPE_RANDOM_STATIC,
        {0x76,0x53,0xd6,0xfb,0xee,0xc0},          //one_plus3  android phone
    }
};

//........................
//........................
//........................
//........................
//........................
//........................

void init_advertising(void){
..................................................................
..................................................................
    uint8_t *oneplus3_irk_string = "076b01ad29fcbb56bda76d3c9adb0ec0";  // adb shell ,/data/misc/bluedroid/bt_config.config grep "LOCAL_IRK"

    uint8_t temp[2];
    uint8_t *ptr = NULL;
    unsigned long ret = 0;

    for (int i = 0,j=0; i < BLE_GAP_SEC_KEY_LEN;i++,j+=2)
    {
        memmove(temp,&oneplus3_irk_string[j],sizeof(uint8_t)*2);
        ret = strtoul(temp, &ptr, 16);

        oneplus3_key.id_info.irk[i] = (uint8_t)ret;
    }
    // The irk is right ,I have test it in fast advertising with pm_address_resolve();
..............................................................
..................................................................



static void on_adv_evt(ble_adv_evt_t ble_adv_evt){
................................................
        case BLE_ADV_EVT_WHITELIST_REQUEST:
        {
            ble_gap_id_key_t* key_list[BLE_GAP_DEVICE_IDENTITIES_MAX_COUNT];
            memset(key_list,0,BLE_GAP_DEVICE_IDENTITIES_MAX_COUNT*sizeof(int));
            key_list[0] =    &oneplus3_key;
            sd_ble_gap_device_identities_set(key_list,NULL,1);

            ble_gap_addr_t const* whitelist_addrs_gap[BLE_GAP_WHITELIST_ADDR_MAX_COUNT];

            ble_gap_addr_t whitelist_addrs[BLE_GAP_WHITELIST_ADDR_MAX_COUNT];
            ble_gap_irk_t  whitelist_irks[BLE_GAP_WHITELIST_ADDR_MAX_COUNT];
            uint32_t       addr_cnt = BLE_GAP_WHITELIST_ADDR_MAX_COUNT;
            uint32_t       irk_cnt  = BLE_GAP_WHITELIST_ADDR_MAX_COUNT;

            whitelist_addrs_gap[0] = &oneplus3_key.id_addr_info;
            memmove(&whitelist_addrs[0],&oneplus3_key.id_addr_info,sizeof(ble_gap_addr_t));
            memmove(&whitelist_irks[0],&oneplus3_key.id_info,sizeof(ble_gap_irk_t));
            addr_cnt = 1;
            irk_cnt = 1;

            err_code = sd_ble_gap_whitelist_set(whitelist_addrs_gap, 1);
            APP_ERROR_CHECK(err_code);

            // Apply the whitelist.
            err_code = ble_advertising_whitelist_reply(&m_advertising,
                                                       whitelist_addrs,
                                                       addr_cnt,
                                                       whitelist_irks,
                                                       irk_cnt);
            APP_ERROR_CHECK(err_code);
        }
        break;
......................................................