With the latest R700H Protect software you have the possibility to activate BLE background scanning.

The handset scans BT beacons periodically in scan time (Ts) and idle time (Ti) interval, as presented below. The scanning time (Ts) and idle time (Ti) are configured in deciseconds (ds), defined as 10^(−1) second using the SI prefix system. Both timers range is 0[ds] - 600[ds] (0[s] - 60[s]) and stored in PP NVM memory. If one of time frame (Ts or Ti) is set to 0 the background scanning is inactive - in the other words it's not possible to configure permanent scanning (e.g. Ts = 600 and Ti = 0).

Both time intervals (Ts, Ti) can be configured via PP provisioning or local PP editor (hidden procedure). Default values: Ts = 15s, Ti=10. This configuration has significant impact on power consumption.

Filtering beacon scanning results

Beacon scanning results can be limited to specific beacons via filtering mechanism. Up to 5 beacon filters can be applied and configure via provisioning. Only beacons that fit to configured filter will be saved, if no filter strings set, all found beacons will be saved. 


Storing beacon scanning results

The handset will keep 10 last found beacons. The beacons data may be stored locally in RAM memory (so beacon data  can be loose after device power off/restart). If, during the single scanning cycle, the handset would find more beacons (that fits to the configured filters) than can be stored in the buffer, then the 10 found beacons witch strongest signal signal strength will be stored. The handset will keep following information separately for each beacon: <<public device address>>, <<random device address>>,  <<advertising data>>, <<extend signal strength>>, <<data age>>.


<<public device address>> and <<random device address>> structure:

This information element shall contain the device address of the Bluetooth beacon as specified in 'Specification of the Bluetooth® System, version 4.2, 2014-12-02 Vol.6, part B, clause 1.3 “Device Address”'. The length of this information element shall be 6 bytes.


<<advertising data>> structure:

This information element shall contain the so-called Bluetooth advertising data as specified in Specification of the Bluetooth® System, version 4.2, 2014-12-02, Vol.3, part C, clause 11 “Advertising and Scan Response Data Format”.  The length of this information field shall be less than or equal to 31.


<<extend signal strength>> structure:

The <<extend signal strength>> contains maximum, average and minimum received signal strength and number of beacon signal occurrences.

The received signal strength of the Bluetooth beacon, is expressed in dBm, in two’s complement representation. Valid values range from −127 to +20.

Number of occurrences provides number of occurrences certain BLE beacon during one scanning cycle, if number of occurrences is higher than 255 the value 255 shall be send.

The length of this information field shall be equal to 4 bytes.


<<Data age>>  structure:

This element contains the 'data age' in seconds. Possible range 0 - 65535. If data age is older than 65535 or if if data age is not available the value 65535 shall be send. The length of this information field shall be equal to 2 bytes.


Auto-provisioning parameters
alarm_srv_ble_scan_interval_active_time;<param name="alarm_srv_ble_scan_interval_active_time" value="200"/>;Value in deciseconds (10^(−1)) from 0 to 65535. 0 = feature inactive;
------
alarm_srv_ble_scan_interval_idle_time;<param name="alarm_srv_ble_scan_interval_idle_time" value="100"/>;Value in deciseconds (10^(−1)) from 0 to 65535. 0 = feature inactive;


FAQ

How many beacons are stored by the Background scanning service?

Up to 10 different beacons are stored


How to disable BLE background scanning?

Via auto-provisioning set the timers to "0"


How to collect the BLE background scanned beacons?

This can only be done by using a certified alarm server connected via MQTT. The Alarm server triggers an BLE scan result request

  • No labels