Configuration des bornes ARUBA BLE compatible dans SIGSCAN Healthcare

Architecture

SIGSCAN uses a very simple architecture:

Bluetooth Low Energy (BLE) Tags as emitter

ARUBA AP receive tags frames and forward to the AP controller

The AP controller send the BLE frames through a WebSocket secure connection to SIGSCAN

The SIGSCAN software suite can be installed on Premise or used as a SaaS.

SIGSCAN BLE tag frame

The SIGSCAN BLE tag sends BLE advertising frames at periodic intervals (default 5s, time range: 100ms-5s configurable). The used BLE advertising protocol is Eddystone TLM.

The tags mainly send in each advertisement frames:

· Its own MAC address

· The battery voltage

· A temperature

See the Eddystone TLM protocol specifications for more details:

· https://github.com/google/eddystone/blob/master/protocol-specification.md

· https://github.com/google/eddystone/blob/master/eddystone-tlm/tlm-plain.md

ARUBA AP - BLE data exchanges

The ARUBA AP job is to receive the BLE advertisement frames and forward the information to the SIGSCAN software through the WebSocket protocol.

In order to get SIGSCAN working, the ARUBA APs don’t need to transmit any data on the Bluetooth network.

On a periodic interval (default: every 5s), the Aruba APs send the data that they caught to the SIGSCAN software suite (through the AP controller).

The main exchanged data sent from an AP to SIGSCAN are:

· The ARUBA AP IP address

· The ARUBA AP BLE MAC address

· For each caught BLE frame

o The BLE device MAC address

o The RSSI of the frame

o The advertisement data of the frame

The packet size sent by the AP depends on the number of received tags frames. In average, each packet size is around 2KB.

ARUBA AP – SIGSCAN IOT configuration

SIGSCAN relies on Aruba IoT feature when used with ARUBA Access points.

Supported hardware

Old ARUBA APs may not have BLE feature. Refer to the AP datasheet to check it out. Below is the list of AP models supporting BLE:

· AP 207

· AP-303, AP-303P, AP-304/305, AP-314/315, AP-324/325, AP-334/335, AP-344/345, AP 360/365

· All the AP-5xx

· All the AP-6xx

Note: Some non BLE AP may support an external BLE dongle.

Supported firmware

Depending on the controller type (Physical controller or Virtual controller), and depending on your APs models, the IoT feature may be available or not.

Starting from the firmware v8.6 it is possible to use the IoT feature but not all the parameters are available in the Web interface. In this case, proceed with configuration via command line interface (CLI). Starting from the firmware v8.10 all the parameters needed for the IoT configuration are available from the Web interface.

Web interface configuration

To enable Aruba APs to receive and transmit BLE frames to the Sigscan server you need to create and configure Transport Profile and IoT radio profile.

IoT radio profile

Below are the parameters to be set in the iot radio profile

Name: choose a name for your iot radio profile

Radio: Internal

Radio model: BLE

BLE operational mode: Scanning

Tx power: 4 dBm

Transport profile

Below are the parameters to be set in the transport profile

Name: choose a name for your transport profile

Server type: Telemetry-Websocket

Enabled: Yes

>Destination

>Authentication

Method: Token

Server URL: To determine depending on the Sigscan installation

Access token: sigscan

Client ID: choose a name for you client ID

Transport services: BLE telemetry

>BLE Telemetry

BLE devices: Eddystone

Reporting interval: 5 seconds

>Advanced

RSSI reporting format: Last

Environment type: Office

CLI configuration

The following configuration must be applied to get Sigscan working with Aruba APs:

00:11:22:33:44:55 # configure terminal

00:11:22:33:44:55 (config) # iot radio-profile ble

00:11:22:33:44:55 (IoT Radio Profile "ble") # ble-opmode scanning

00:11:22:33:44:55 (IoT Radio Profile "ble") # radio-mode ble

00:11:22:33:44:55 (IoT Radio Profile "ble") # exit

00:11:22:33:44:55 (config) # iot transportProfile sigscan

00:11:22:33:44:55 (IoT Transport Profile "sigscan") # endpointURL <SIGSCAN URL>

00:11:22:33:44:55 (IoT Transport Profile "sigscan") # transportInterval 5

00:11:22:33:44:55 (IoT Transport Profile "sigscan") # endpointType telemetry-websocket

00:11:22:33:44:55 (IoT Transport Profile "sigscan") # rssiReporting last

00:11:22:33:44:55 (IoT Transport Profile "sigscan") # endpointToken sigscan

00:11:22:33:44:55 (IoT Transport Profile "sigscan") # payloadContent eddystone

00:11:22:33:44:55 (IoT Transport Profile "sigscan") # exit

00:11:22:33:44:55 (config) # iot use-radio-profile ble

00:11:22:33:44:55 (config) # iot useTransportProfile sigscan

00:11:22:33:44:55 (config) # exit

00:11:22:33:44:55 # commit apply

committing configuration...

configuration committed.

00:11:22:33:44:55 # show iot transportProfile sigscan

IoT Data Profile "sigscan"

---------------------

Parameter Value

--------- ------

EndpointURL <SIGSCAN URL>

EndpointType telemetry-websocket

PayloadContent eddystone

TransportInterval 5 second

EndpointToken sigscan

EndpointID

Username

Password

UUIDFilter

CellSizeFilter

MovementFilter

AgeFilter

AuthenticationURL

UIDNamespaceFilter

URLFilter

VendorFilter

RSSIReporting last

EnvironmentType office

Custom Fading Factor 20

AccessID

ProxyServer

ProxyPort

ProxyUsername

ProxyPassword

VLAN none

rtlsDestMAC

deviceCountOnly FALSE

cc:d0:83:c2:2c:b6 # show iot radio-profile ble

Name ble

References 1

Instance internal

Mode ble

BLE Opmode scanning

BLE Console off

BLE TxPower (dBm) 4

Zigbee Mode coordinator

Zigbee Channel(s) auto