Table of contents
The Aruba IoT server interface is an Aruba proprietary server-side connectivity interface to connect to IoT servers using the Aruba AP’s or Aruba controllers management IP address. The interface provide multiple transport protocol and data encapsulation options and is specified in the Aruba IoT Server Interface Guide.
All Aruba IoT server interface related aspects are configured in an iot transport profile.
Up to 4 iot transport profiles can be concurrently enabled per Aruba Instant AP or ArubaOS AP group.
This allows to run up to 4 IoT applications concurrently on an Aruba access point ,e.g. Aruba Meridian Beacon Management + Aruba Meridian Asset Tracking + 3rd Party BLE Asset Tracking + EnOcean.
The following chapters describe the Aruba IoT server interface related options and services.
The Aruba IoT server interface supports vendor specific and generic server connections types.
The following generic connection types allow IoT data forwarding for the different IoT connectivity (radio-side) options previously described.
The Telemetry-Https connection type can be use to send BLE telemetry reports in one direction only, from the radio-side to the server-side, using HTTP POST requests.
This connection type can be used for BLE-based asset tracking or sensor monitoring use cases using easily consumable JSON data. The used JSON data structure is defined in the Aruba IoT Telemetry JSON Schema.
Telemetry-Https is only meant to be used for low thoughput application/use cases with a low amount of APs (<20) and a high report intervall (>60 s). Trying to use Telemetry-Https for low latency/high toughput use cases may BLE mesages beeing dropped/delayed. Please only use Telemetry-Websocket for low latency/high toughput use cases.
Starting with ArubaOS/Aruba Instant 126.96.36.199 or higher no new BLE device classes will be added to be used with Telemetry-Https.
The Telemetry-Websocket connection type can be used for all supported IoT transport services providing a bi-directional communication channel though a web socket (ws) or secure web socket (wss) connection.
Communication via the Telemetry-Websocket connection is encoded using the Google Protocol Buffers serialization protocol. Supported messages types (northbound/southbound API) and the encoding and decoding of the data payloads is defined in the Aruba IoT Protobuf Specification.
This connection type enables the full set of IoT connection capabilities of an Aruba infrastructure.
The IoT-Utilities app only supports Telemetry-Websocket connections.
With this connection type Aruba controller’s or Aruba Instant access points work as a protocol translation gateway (in Azure terms) to send data to Azure IoT Hub on behalf of connected IoT devices.
For details please see the Azure IoT Hub Integration Tech Note
Even if un-encrypted HTTP or web socket connectivity is supported by the Aruba IoT server interface, it is recommended to only use encrypted connections to remote IoT systems.
In order to establish secure web socket (wss) or HTTPS connections the remote server’s self-signed certificate or root CA certificate has to be added to the Aruba controller/Aruba Instant access points trusted CA list.
If the IoT server certificate is un-trusted the server connection will not be established.
Please refer to importing certificates for how to add/import required certificates on the Aruba infrastructure.
The IoT-Utilities app provides a download link on the web dashboard to download the self-signed server certificate. Alternatively a certificate signed by a private or public CA certificate that is trusted by the Aruba infrastructure can be installed into the app.
Depending on the Aruba IoT server connection type different authentication and authorization methods are supported/required to establish server-side connections.
Supported authentication and authorization methods are:
- static access token
Details about the different authentication methods are documented in the Aruba IoT Server Interface Guide.
Server connections are established form every single Aruba Instant access point, in case of a controller-less setup, or from every Aruba controller in case of a controller-based setup.
For example, in a controller cluster setup with 4 controllers every controller will establish a connection to the remote server.
In an ArubaOS controller setup the number of server connections equals the number of controllers.
In an Aruba Instant setup the number of server connections equals the number of APs.
In a controller based setup IoT data is forwarded to/from the remote IoT server via the APs active controller only. In case of a failover the IoT communication will also failover to the backup controller’s IoT interface connection.
Redundant controller based setups requires proper connection management on the IoT server side for bi-directional communication to continue to work in case of a failover. The remote server application has to keep tack of which AP and IoT radio is reachable via which connection.
For details please refer to the Aruba IoT Server Interface Guide.