The RIVIR R200 Direct to Cellular satellite IoT gateway
The easy way to connect your industrial assets and sensor fleet by satellite
The launch of direct to device cellular satellite networks is set to disrupt industries around the world. RIVIR makes it easy and seamless for organisations to connect large fleets of industrial assets and sensors to the new generation of satellite networks including Sklyo’s NB-IoT service and the new Starlink D2C LTE cellular satellite network.
Leveraging the LwM2M data standard for scalability and performance
Connecting to a higher latency, lower bandwidth cellular satellite network is not easy for older generation cellular IoT gateways that employ the MQTT protocol. This is because these systems require a stable end to end connection that LEO networks cannot reliably provide. At the core of the RIVIR R200 satellite IoT gateway system is the future proof LwM2M IoT data protocol which reduces data payloads by up to 88% while eliminating the reliance on a stable end to end connection for data transmission. Designed as a device management protocol that also manages data transmission and security, RIVIR’s core LwM2M software layer makes it extremely easy to deploy and manage a large fleet of IoT or Scada enabled assets.
Easy integration with edge equipment and core business systems
RIVIR’s gateway hardware is designed for easy integration with edge equipment over wired Modbus connections or wireless Lora. RIVIR’s REST API makes integration of the satellite IoT data network with central business systems easy and fast.
Using the LwM2M protocol to make IoT solutions scalable over constrained satellite networks
The two big challenges with running remote IoT over the new NTN networks, are scalability and overcoming network latency.
It is very hard to maintain a fleet of geographically scattered IoT devices. Its doubly hard to operate a TCP based MQTT IoT system, which requires a stable server connection, within the constraints of intermittent NTN satellite networks.
The RIVIR R200 gateway system solves both these problems for remote industrial IoT by employing the cutting edge LwM2M data protocol.
The LwM2M protocol is purpose built for running massively scalable, remote IoT applications over cellular NTNs (Non Terrestrial Networks).
Specified by the Open Mobile Alliance, the Lightweight Machine to Machine protocol is a fast, light, and “structured session-based” protocol with a very efficient resource data model. The protocol uses a firmware client, instantiated on the RIVIR gateway, tied to cloud based server software to manage secure, continuous two way device-to-server communication sessions which transcend any network interruptions.
Specified by the Open Mobile Alliance (OMA) as a global standard for IoT over constrained networks, the LwM2M specification provides general APIs for device configuration, connectivity monitoring/statistics, security and firmware update, server provisioning and is being constantly extended. The widely used Constrained Application Protocol (CoAP) provides in-built binding for LwM2M, thus making the LwM2M protocol particularly appealing for the Internet of Things (IoT). The standard is targeted, in particular, at constrained devices, e.g., devices with low-power microcontrollers and small amounts of Flash and RAM over networks requiring efficient bandwidth usage. At the same time, LwM2M can also be utilized with more powerful embedded devices that benefit from efficient communication.Hyperscalers rely on MQTT today because it is very capable, but it is simply not efficient enough for modern LPWAN IoT solutions which often use less data and have power constraints. With lightweight M2M (LwM2M), organizations create a substantially smaller use of data. LwM2M offers 72% less data transfer at initial connection, 31% less data transfer for steady-state device connection and power consumption can be 33% lower.
| Features | LwM2M | MQTT |
|---|---|---|
Resources | Low to very low footprint | Medium footprint |
Powered devices | Very low power consumption | Medium to high power consumption |
Bandwidth | Low – up to 88% more efficient than MQTT | Medium to high depending on encoding used |
Operating cost | Low – up to 88% lower data costs | High depending on encoding used and network availability |