...
This question sometimes arises from integrators who run their own type of IoT platform tailored to a particular use-case and don't want an intermediate between their system and the IoT hardware to integrate. In contrast to this our platform is primary considered for device management of Lobaro and 3rd party sensors and gateways. It's meant as secure, stable and scalable abstraction layer to the actual hardware complexity and gives the following benefits to the integrator or end-user:
- Asymmetrically encrypted Encrypted data transfers, client and server certificate-based, using DTLS, while still being able to use battery life friendly UDP transfers with little overhead.
- Administration of client and server certificates.
- Remote configuration of sensors via simple APIs (HTTPS PUSHWeb UI, REST, MQTT, SFTP).
- Support for Firmware Updates Over The Air (FOTA).
- Good system scalabilityScalability, even with many thousands of data nodes.
- Intermediate storage for sensor data before further processing in the downstream platform.
- Simple interface Data insight and export independent of downstream platform with via CSV export of data for simple applicationsor REST API.
- Integration of ChirpStack LoRaWAN network server.with LoRaWAN Network Servers (ChirpStack, TTN / TTI, Lotiot, and many more ...).
- Unified API for downstream system across different connectivity technologies on the device side Possibility of merging sensors of different wireless technologies (e.g. NB-IoT, LoRaWAN, wireless MBUS) with a uniform API to the downstream system, LAN).
- Quickly bring IoT applications to market by focusing on the use case and the actual data without having to deal with hardware and firmware implementation details or properly secured data transfers from the sensor to the cloud.
- Usually low Low hardware requirements for the server on which the on-premise instance of the Lobaro Platform is installed. Often it can Can run in parallel on a server next to the use-case specific platform or even an Raspberry PI for embedded use-cases.
- Internal APIs between hardware and Lobaro Platform can be changed, e.g. for firmware extensions, without compromising a stable API to the downstream system and thus increasing the stability of the end application.
As one might see, all these functionality require a high level of knowledge about the hardware and how it internally works. Lobaro can only provide support and guarantees that all features of our NB-IoT products are available and function as expected if the Lobaro Platform is also used as a counterpart.
| Note | ||
|---|---|---|
| ||
A direct connection |
...
between our hardware |
...
and a customers IoT Platform can be discussed for high volume projects, as there is usually an adequate budget to go this way. In the vast majority of cases, the manageable prices for using the Lobaro Platform as SaaS or |
...
On-Premise is more economical. Integration effort and support overhead gets reduced. Free trial periods |
...
for our platform are |
...
available. |
If using the Lobaro IoT platform is absolutely no not an option many of our NB-IoT products can alternatively also be configured to use LoRaWAN uplinks which shifts the dependence to the used LoRaWAN network server beside the well-known challenges of LoRaWAN networks compared to cellular IoT.