Legal Disclaimer: The resource assets in this website may include abbreviated and/or legacy terminology for HPE Aruba Networking products. See www.arubanetworks.com for current and complete HPE Aruba Networking product lines and names.
IoT Application Ecosystem
Figure 1 IoT Application Ecosystem
From the components shown above in the IoT Internet of Things. IoT refers to the internetworking of devices that are embedded with electronics, software, sensors, and network connectivity features allowing data exchange over the Internet. application ecosystem, developers have control to define and configure the following:
On the IoT Connector:
BLE Bluetooth Low Energy. The BLE functionality is offered by Bluetooth® to enable devices to run for long durations with low power consumption. Decoder Service—The BLE decoder service is an engine that runs Lua scripts that are defined in the IoT application. The purpose of these Lua scripts is to decode Bluetooth packets and assign device class and set any other properties for the BLE IoT devices. The permissions system here is used to specify what device classifications can be made and what properties can be set by the Lua script.
Subscriptions—The subscription service distributes all the IoT payload to either transport them directly or to the BLE decoder or to the partner API Application Programming Interface. Refers to a set of functions, procedures, protocols, and tools that enable users to build application software.. An application can subscribe to data streams from specific types of IoT devices. Applications can subscribe to IoT device data based on the the following 4 filters: Vendor, UUID, Local Name, Device Class.
Application Container—The docker container for your IoT application will reside in a container sandbox. You application will mainly interact with the partner APIs. These RESTful APIs allow your application container to read and write to the IoT device database. You can find the partner and application API documentation here.
Application firewall Firewall is a network security system used for preventing unauthorized access to or from a private network. configuration—Your application metadata can specify configurations needed on the outbound firewall for allowing the application container to set up a connection to your business application in the cloud or on-prem.
Partner API permissions—The application metadata specifies the exact API permissions required. The API permissions system ensures that applications can access only the IoT device data relevant to them and restricts applications from affecting other IoT device data via the partner API.
On the Access Point:
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. Access Control Descriptor—The USB descriptor allows your application to enable new types of USB devices and the AP to recognize and classify your USB device properly. The descriptor is part of the application metadata. USB devices that have serial interfaces or Ethernet Ethernet is a network protocol for data transmission over LAN. interfaces are supported, and as such the most common Ethernet and serial drivers built into the AP firmware. For USB Ethernet devices, the application installs a descriptor, it effectively turns the APs’ USB port into an Ethernet interface. The data is then sent over the APs data plane and does not go through the IoT connector pipeline.
USB Serial Data Framing Lua Script—For USB serial type devices, a TTY TeleTypeWriter. TTY-enabled devices allow telephones to transmit text communications for people who are deaf or hard of hearing as well as transmit voice communication. device serial device in Linux, the data needs to framed by a Lua script in the partner’s IoT application. The framed data then follows the same pipeline as BLE and Zigbee data and is tunneled to the IoT Connector.
Aruba IoT Radio custom radio firmware—This feature is currently work in progress This feature allows different firmware to run within the IoT radios on the AP. A typical example for this is if your IoT have devices that use proprietary radio protocols that is based on the 802.15.4 standard, the partner would need to develop firmware for the AP IoT radio. The IoT data from the IoT radio running partners’ private firmware can be tunneled it through the pipeline to the partners’ business application back-end.
