IoT Operations

Aruba Central supports transporting IoT data over an enterprise WLAN Wireless Local Area Network. WLAN is a 802.11 standards-based LAN that the users access through a wireless connection.. IoT data from partners who provide access control systems, industrial manufacturing systems, hospital, healthcare management, hospitality, and building management systems is supported. APs receive data from the IoT devices and send the dashboard metadata to Aruba Central and the IoT data to external servers through IoT Connectors. The IoT Connector aggregates the device data, performs edge-compute, and runs business logic on the raw data before sending the dashboard metadata and IoT data. Partner-developed applications can be used to send the IoT data to external servers.

Aruba Central provides IoT Connector control, management, and dashboard visibility. The dashboard provides a view of the IoT Connectors, IoT devices, and installed applications. An application store that contains the applications from supported partners is integrated with Aruba Central. Aruba Central does not store the device data, display the device data, or derive insights from the device data. The following is an illustration of IoT Operations architecture.

Figure 1  IoT Operations Architecture

Terminology

IoT Operations uses the following terminology:

Table 1: IoT Operations Terminology

Term Description

Data Collector

A Data Collector is a platform that processes network data. A Data Collector is available both as a physical appliance or a virtual appliance.

IoT Connector

An IoT Connector is an application that runs on the Data Collector platform. The IoT Connector receives IoT data from APs through a secure tunnel. An IoT Connector sends the IoT metadata to Aruba Central and the IoT device details to the endpoints of third party partners.

IoT Transport Profile

An IoT transport profile allows an IoT Connector to send the collected IoT data to a partner server.

IoT Radio Profile

An IoT radio profile runs on an AP and it allows an AP to collect IoT data from the IoT devices.

Apps

Apps are developed by partners and are available on the App Store. Apps are deployed on IoT Connectors and run inside the IoT Connector.

Applications

Applications is an element in the Aruba Central web user interface.

IoT Devices

IoT devices are client devices using BLE Bluetooth Low Energy. The BLE functionality is offered by Bluetooth® to enable devices to run for long durations with low power consumption., Zigbee, or other protocols to communicate with Aruba APs.

Specifications

IoT Operations supports the following specifications:

Table 2: IoT Operations Specifications

Parameter Mini VM Virtual Machine. A VM is an emulation of a computer system. VMs are based on computer architectures and provide functionality of a physical computer. Small VM Medium VM DC-2000

APs

50

250

1000

1000

BLE Devices

2000

5000

20000

20000

Zigbee Devices

200

500

2000

2000

The DC-2000 is a physical appliance.

The IoT Connectors support the following specifications:

Table 3: IoT Connector Specifications

Parameter Mini VM Small VM Medium VM DC-2000

CPU Central Processing Unit. A CPU is an electronic circuitry in a computer for processing instructions. (cores)

4

8

24

24

Memory (GB)

4

16

64

64

Storage (GB)

256

256

480

512

IoT Connectors are available as virtual appliances or physical appliances. Before you can use an IoT Connector, you need to set up appliances. To setup virtual appliances, see Set Up Virtual Appliances.

Licensing

IoT Operations is available to Aruba Central customers using ArubaOS 10, with Foundation and/or Advanced AP licenses. Separate licenses are not required for IoT Operations.

IoT Operations utilizes an IoT Connector to receive IoT data from APs and sends IoT device metadata to Aruba Central and IoT data to partner cloud servers. The APs that are assigned to an IoT Connector utilize their IoT radios to act as IoT gateways for myriad IoT devices in the physical environment.

Aruba uses the license tier of APs assigned to your IoT Connector to determine the user experience. Currently, that user experience is differentiated in the IoT Operations Application Store. You will either have access to all apps in the IoT Operations Application Store or some of the apps in the IoT Operations Application Store. Regardless of license tier, the supported scale and base functionality of IoT Operations are the same. In the future, Aruba may add new capabilities to IoT Operations which may extend across apps or even be offered independently of the apps themselves. The user experience is currently determined in IoT Operations as:

  • When all APs assigned to an IoT Connector have an Advanced AP license, you have access to all apps in the IoT Operations Application Store.
  • When at least one AP assigned to an IoT Connector has a Foundation AP license, you have access to a subset of apps in the IoT Operations Application Store. The apps that are available are shown in full color, while the apps that are unavailable are shaded gray.

Filters can be used in the IoT Operations App Store user interface to further refine your app search.

IoT Operations App Matrix

IoT Operations supports the following apps:

Table 4: IoT Operations App Matrix

IoT Operations App Supported on VM-based IoT Connector Minimum AOS version for VM-based IoT Connector Supported on AP-based IoT Connector Minimum AOS version for AP-based IoT Connector Lincense Type

Assa Abloy

Yes

AOS 10.3.1.4

Future

Not applicable

Foundation

AOS 8 Emulator

Yes

AOS 10.3.x

Future

Not applicable

Foundation

Aruba Devices

Yes

AOS 10.3.x

Yes

AOS 10.5.x

Foundation

Eddystone Devices

Yes

AOS 10.3.x

Yes

AOS 10.5.x

Foundation

iBecons

Yes

AOS 10.3.x

Yes

AOS 10.5.x

Foundation

EnOcean BLE

Yes

AOS 10.3.x

Yes

AOS 10.5.x

Foundation

Minew Devices

Yes

AOS 10.3.x

Yes

AOS 10.5.x

Foundation

Blyott Devices *

Yes

AOS 10.3.x

Future *

Not applicable

Foundation

Dormakaba

Yes

AOS 10.4.x

Future

Not applicable

Advanced

EnOcean USB Universal Serial Bus. USB is a connection standard that offers a common interface for communication between the external devices and a computer. USB is the most common port used in the client devices. *

Yes

AOS 10.4.x

Future *

Not applicable

Foundation

Hanshow

Yes

AOS 10.4.x

Yes

AOS 10.5.x

Foundation

SoluM

Yes

AOS 10.4.x

Yes

AOS 10.5.x

Foundation

Amberbox Gunshot Detection

Yes

AOS 10.4.x

Yes

AOS 10.5.x

Foundation

Securitas BLE

Yes

AOS 10.4.0.1

Yes

AOS 10.5.x

Foundation

TraknProtect Sensors

Yes

AOS 10.4.0.2

Yes

AOS 10.5.x

Foundation

Onity IoT

Yes

AOS 10.5.0.0

Future

Not applicable

Advanced

Meridian

Yes

AOS 10.5.1.0

Future

Not applicable

Foundation

* Blyott and EnOcean apps require the use of the AOS 8 emulator app to transport data. AOS 8 emulator utilizes a container, and container-based apps are not yet supported on AP-based IoT connector.

AP-based IoT Connector

IoT Operations works with Aruba APs running ArubaOS 10.5 or higher.

The ArubaOS 10 APs enable IoT functionality via the IoT connector application that runs on the Aruba data collector appliance. For small and medium business networks that have simple IoT application requirements or for large networks that have a small number of APs distributed across multiple sites, the Aruba APs can be converted into IoT Connectors. The AP-based IoT Connectors support IoT connector applications like basic BLE data filtering and forwarding and USB-serial data forwarding on the AP.

The AP-based IoT Connector connects to IoT Operations on Aruba Central after getting the initial AP boot-strapping configuration from the Aruba Central. The AP boot-strapping information includes BLE Daemon (BD), API Application Programming Interface. Refers to a set of functions, procedures, protocols, and tools that enable users to build application software. Gateway (APIG), and Container Host (COHO).

The AP-based IoT Connector allows container-based applications to run agnostic of AP infrastructure. This allows the third-party container to interact the same way they do on the standalone IoT Connector.

For more information on configuring AP-based IoT Connectors, see the related procedures in Configuring IoT Operations.