Handling Unwanted Advertising Name in BLE Multi Advertising

[mg Jeong]

hello.
Currently I am implementing BLE Multi advertising in 

NCS SDK: version 2.6.0.

I have a question during development through the samples/bluetooth/multiple_adv_sets example.

static const struct bt_le_adv_param *adv1_param = BT_LE_ADV_NCONN_IDENTITY; 


I set the adv_param value as above, and after setting the value, I confirmed that ADV is performed by MAC Address when advertising. 

(I need that feature(MAC Address) 

However, it seems that the scan response is advertised together or the advertising name(bt setting name) is included separately. 

The behavior I want is for only the advertising data I set to be advertised,

 but the problem is that the advertising name is also advertised. 

(I would like to inquire as to whether this behavior operates as a scan response.) 

Thanks.

[Hieu]

Hi mg Jeong,

Do I understand right that you find the Scan Response containing the device name, and you don't want the Scan Response nor the device name in your advertising?

You set up Scan Response during advertising setup. If you don't want it, simply pass NULL as the sd param, and 0 as the sd_len param when you call bt_le_ext_adv_set_data().

If you don't have any Scan Response setup, and the issue persists, please check if BT_LE_ADV_OPT_USE_NAME is set in your advertising option.

Hieu

[mg Jeong]

hello! Thanks for your answer.

What you understood is correct.

A total of 5 advertisements are running through ext adv, and when I scanned, 
I saw that the advertisements included the device name and RSSI, 
so I inquired (In addition to the 5 advertisements, RSSI+BT Name information is being advertised).  

If I set the bit below, will the BT name be retrieved via bt_id_get in the bt_le_oob_get_local function and advertised separately? Is the task a scan response task? 
I would like to inquire whether this is a general advertisement.

/**
	 * @brief Advertise using identity address.
	 *
	 * Advertise using the identity address as the advertiser address.
	 * @warning This will compromise the privacy of the device, so care
	 *          must be taken when using this option.
	 * @note The address used for advertising will not be the same as
	 *        returned by @ref bt_le_oob_get_local, instead @ref bt_id_get
	 *        should be used to get the LE address.
	 */
	BT_LE_ADV_OPT_USE_IDENTITY = BIT(2),

[Hieu]

BT_LE_ADV_OPT_USE_IDENTITY makes the advertising uses its identity address, i.e. public address, as the advertising address. It doesn't have anything to do with name.

Please also remember that some phone OS cache a device's name from a previous connection. Subsequently, when it sees a device with the same address, it will load the cached name. See Bluetooth name caching | Apple Developer Forums.

RSSI is otherwise a common feature of scanner devices. Both Android and iOS support it. It reports the signal strength of the advertising packet as the phone receive it; not a part of the advertising packet.

[mg Jeong]

Thank you for answer.

As a result of BLE Scan, we confirmed that BLE Device Name Advertising is not being performed in other modules.

It seems that the connected app remembers the device name and appears.

thank you

[Hieu]

I am happy things are working as expected and are clear now. Please feel free to close this case at your convenience.