Back to overview
Data usage

Your platform: from the network server to your application

The data first lands in the network server – from there it travels via standardized interfaces to dashboards, MES or your own software. This page explains the path: sensor → gateway → network server → application.

How do the data reach your application?

The network server is the end of the radio link – not the destination. From there the data is handed over via standardized interfaces: via MQTT into any common message queue, via webhook directly into your application on every uplink, or on demand via REST API whenever your software needs the values. Dashboards, databases, BI tools and MES/ERP systems connect this way – no proprietary silo required.

Which network servers are there?

The market is open: AION LIO works with common LoRaWAN network servers – for example ChirpStack, The Things Stack, Actility ThingPark, Loriot or AWS IoT Core for LoRaWAN. They run in the operator's cloud or self-hosted in your infrastructure. The IODD interpretation already happens inside AION LIO – the network server only has to receive the payload and forward it.

The path of the data

Sensor → gateway → network server → application

Every LoRaWAN link follows the same architecture: AION LIO sends, the gateway receives, the network server processes – your application uses the data.

  1. 01
    Field level

    IO-Link sensor

    AION LIO reads the sensor, interprets the IODD and sends the values as a LoRaWAN uplink.

  2. 02
    Radio reception

    Gateway

    Receives the packets over long distances and forwards them to the network server via the internet.

  3. 03
    Processing

    Network server

    Decrypts the uplinks, removes duplicates and distributes the data to the connected applications.

  4. 04
    Data usage

    Your application

    Dashboards, MES, ERP or your own evaluation – connected via MQTT, webhooks or REST API.

Standardized interfaces

Hand over instead of building silos

Operation stays deliberately open: run your own gateways and your own network server – in your own server room, in your cloud or with an operator of your choice. Or take everything ready-made: the Sentinum Cloud brings the network server, automatic IODD parsing and a web application from one source. Both paths end at the same point: your readings are where you process them.

  • MQTT integration
  • Webhooks
  • REST API
  • Dashboards & alerting
  • MES & ERP integration
  • Your own databases
On-premises networks are possible

If you want to keep the data in-house, run a private LoRaWAN network: your own gateways, your own network server – for example ChirpStack or The Things Stack self-hosted – and interfaces into your own system landscape. The radio technology stays the same; operation and data storage remain with you. That maps compliance, network and data protection requirements directly.

Operation: on-premises or cloud

Alternatively: Sentinum Cloud

You prefer not to set anything up yourself? The Sentinum Cloud comes with a network server, automatic IODD parsing and a ready-made web application – readings, dashboards and alerting without extra effort. IODA and IOWA show what this looks like in practice.