bluetooth - BLE - HCI LE Advertising Report event data format -
bluetooth - BLE - HCI LE Advertising Report event data format -
bluetooth standard v4.0 [vol. 2, 7.7.65.2] allows controller "queue advertising reports , send info multiple devices in 1 le advertising study event".
to manage feature, hci protocol includes, among event parameters, field num_reports (with values between 1 , 25).
in case num_reports > 1, how event parameters organized in event packet received through hci?
note 1: bluetooth standard seems specify unusual ordering of data, not packing each advertising study after other (as suggested event description), packing instead each type of info after other (i.e. event_types each advertiser, followed address types, addresses, , on till lastly field, rssi values). understand well?
note 2: didn't find software illustration managing more 1 advertising study in 1 single event. mean feature of standard isn't used real-world devices?
you understand correctly.
when there more (num_reports > 1) advertising reports packed 1 event, these parameters contained event:
subevent_code, num_reports, event_type[i], address_type[i], address[i], length[i], data[i], rssi[i]
so illustration if num_reports = 3, follow 3 event_type (each beingness 1 of adv_ind, adv_direct_ind etc.) 3 reports, in order received.
the same order preserved other parameters marked [i]
.
to reply sec question: standard says controller may queue more reports 1 event. perhaps implementations have looked don't it.
bluetooth bluetooth-lowenergy hci
Comments
Post a Comment