Implementation Overview

An IoT access point (AP) is capable of detecting iBeacon and Eddystone BLE packets and sending them to the Ruckus IoT Controller. The Ruckus IoT Controller reads these BLE packets and reformats them into an API call. The IoT Controller then packages these packets and sends them out to the BLE beacon vendor's cloud service.

Standard Packet Support

The Ruckus IoT Suite supports standard-length iBeacon and Eddystone packets. If the BLE beacon payload is greater than the standard payload, there is no guarantee that the Ruckus IoT Suite can receive and relay the complete or partial packets.

Aggregation, Compression, and Filter Support

The Ruckus IoT Suite aggregates all packets received for an interval of one second before sending them out. The receiving beacon vendor's cloud service should be able to handle the aggregated packets. The format of the packet is provided in Beacon Payload Format. Additionally, the filtering option is enabled so that the duplicate beacon messages (per device) are removed.

Customization Support

The Ruckus IoT Suite does not support any customization or payload parser functionalities, but provides as-is passthrough of beacon data to the vendor plugin side.

Latency and Reordered Packets

When the Ruckus IoT Controller posts the beacon payload to the BLE beacon vendor's cloud service endpoint (which may be collocated or a cloud operating system), there is no guarantee of latency, jitter, or ordered packet delivery. The BLE vendor's cloud service is required to take into consideration any latency, drops, and reorder issues.