RTIO
RTIO serves as an IoT communication proxy, aiming to reduce the complexity of IoT application development. Unlike the publish-subscribe model of MQTT proxy services, RTIO follows a synchronous remote call model in a REST-Like2 style, where a single call returns the device execution result.
Targeting Remote Control Scenarios for IoT Devices3.
RTIO decouples endpoints, and its value becomes more apparent as the number of endpoint iterations increases3.
- The requester is able to access the RTIO service via public or dedicated networks.
- REST-Like refers to a style similar to RESTful, using URIs to identify capability interfaces.
- Refer to the FAQ to understand the evaluation model. The efficiency improvement may vary depending on the specific application.
Features
The requester directly uses the HTTP protocol to initiate a call to the target IoT device, with the result of the IoT device's processing returned immediately.
Similar to the RESTful style, using URIs to identify capability interfaces, making it easier to manage classification and versioning.
The observation mode is similar to MQTT message subscriptions but more flexible, allowing observations to be initiated and canceled at any time.
The RTIO device access protocol is designed for constrained devices, based on the TCP protocol.
The IoT device SDK supports a reconnection mechanism.
The IoT device supports TLS, and the requester supports HTTPS protocol.
The HTTP requester supports JWT authentication.
The RTIO service can support a million device connections per single node.
Application Scenarios
Users can remotely control IoT devices through mobile apps or PC/WEB platforms, using the HTTP protocol directly.
The server does not need to integrate an SDK and can directly use the HTTP protocol.
The RTIO service is implemented in Golang, making it easy to deploy on edge devices with ARM, x86, and other architectures. IoT devices can be accessed via HTTP through the edge-side RTIO service.
Start Now
>>> Obtain business support