Architecture

The LPWAN Server is meant to be a flexible wrapper around the numerous IoT data delivery networks. To enable this flexibility, parts of the system support a plug-in architecture that allows for future expansion. In some cases, these expansion areas correspond with others (e.g., UI support for entering custom data for a network). The following is a general look at the system architecture:

Architecture

At a very high level:

The Application Vendor uses the UI to interact with the system. The UI uses the REST API of the REST Server to access and update data. The REST Server then communicates with the remote network via the Internet. The remote networks pass data back, and the data is passed to the Reporting Protocols that send the data back to the Application Vendor’s server(s).

Note that there are four points of system customization:

The Data Model

The LPWAN Server data model is meant to be a general model that can represent the data of many remote networks, while providing significant customization for each type of network. The following outlines the basic elements of the system and how they interact:

Public Data

Internal Data