The Client application should scan for all BLE devices containing advertising data with Complete Local Name:
“ABW + 9 latest DEVEUI digit” (e.g. ABW012345678).
The tracker is publishing an encrypted value of its unique Hardware ID within advertising SCAN_RESP. Client
application should proceed with an ACTIVE SCAN to request the related remaining advertising data
(SCAN_REQ). The device authentication can be done by sending a request to an Abeeway server with the
content of the response (SCAN_RESP). Note that this step is not mandatory.
Once authenticated, a connection request should be sent by the Client application.
There is no limitation regarding the connection interval within the connection request.
However, we advise to use a fast connection interval during the service discovery process:
➢ Connection interval: 7.5ms
➢ Connection latency: 0ms
➢ Supervision timeout: 2000ms
4.3.2 BLE Bonding procedure
Once the connection has been established, the Client application should send a bond request within a fixed
delay of 1 minute. If no bond request is received during this period, the BLE module is switched off.
If the bonding fails, the device must be switched off then on to restart the bonding procedure.
4.3.3 BLE Secured connection
A secured connection is established when a known Central device initiates a connection request and
bounded information are present.
Security keys are stored in both tracker and Central device. The connection is encrypted.
When the tracker communicates with the Client application using BLE, it acts as a Bluetooth peripheral and
uses GAP and GATT profiles.
The client application should configure its BLE protocol stack as central.
The tracker sends a connection update request 5 and 30 seconds after a secure connection establishment
using the following parameters:
➢ Minimum connection interval: 980ms
➢ Maximum connection interval: 1000ms
➢ Slave latency: 0
➢ Supervision timeout: 6000ms
The Client application should accept the above parameters for energy saving purpose.
As soon as a BLE secure connection is established (with the bond information), the tracker enters in a special
mode where the following applies:
➢ Accelerometer and battery monitoring tasks are maintained
➢ All LoRa communications are stopped.
➢ No geolocation is performed.
Notes:
1- Once connected, the tracker does not accept any other BLE connections.
2- If the tracker has bonding information, only the paired central device can connect to it.
3- Usually the geolocation is done by central device.
To Next Page
Loading...