The Set Resolving List command is sent to the datasource for creation of a device-address resolving list when capturing data from BR/EDR devices. If there is the potential for capture of data from devices with addresses that have the same UAP and LAP as those already in the device database, the resolving list may be used to give an address priority. This command does not require capture hardware to be connected.
The command format is:
“Set Resolving List;<address list>”
Where “address list” is:
-
“BD_ADDR0,BD_ADDR1,…,BD_ADDRn” – a comma-separated list of valid BD_ADDRs in the
form “0x001122334455”
-
“” – an empty list to clear the resolving list.
Response: “SET RESOLVING LIST;<status>;Reason=<reason>” where a reason will be supplied for SUCCEEDED and FAILED status.
The reason value will be:
-
"resolving_list_set=clear" – The resolving list was successfully cleared.
-
“resolving_list_set=all| BD_ADDR0|BD_ADDR1|…|BD_ADDRn” – All requested BD_ADDRs were added to the list.
-
“resolving_list_set=some| BD_ADDR0|BD_ADDR1|…|BD_ADDRn|resolving_list_error=error0|error1|…|errorn” – Some requested BD_ADDRs were added to the list; some BD_ADDRs could not be added to the list with the accompanying errors.
-
“resolving_list_set=none|resolving_list_error=error0|error1|…|errorn” – No BD_ADDRs were added to the resolving list.
The resolving list is indexed on the UAP and LAP portions of the BD_ADDR and the keys are unique. That means that the resolving list can only hold one address per value of UAP and LAP. If the specified address list contains BD_ADDRs such that two or more of them have the same UAP and LAP, they will be added to the list such that only the last one with those values will be on the list. However, the reason value will still show that the earlier valid BD_ADDRs in the request were added and the error list will show that that BD_ADDR was replaced.