Overview & Architecture



While developing the APIs, we evaluated and benchmarked many different architectures and technologies.
We focused on having a high performance server and flexible cost effective communication protocol, thus reducing
the devices’ operation overall cost significantly.
On the following simplified diagram, you can see how the system appears to external users (and devices).

Binary Server

The binary is the main entry point for remote devices access.
It has been designed for performance in communication. It encapsulates communication with devices in an efficient binary protocol.
It’s also responsible for calling external Web Services in case of direct Query/Answer services.

Application Server

The application server is the main entry point for external (human or application) access.
Available as a REST WebService API, it’s has been designed to ease integration and provides access to all tracking and messaging features.

The API is used to retrieve data, and push messages directly to the devices in a transparent way.
The protocol enables multiplexing many messages as well as allowing you to target “services” recipients on the device in a transparent way.
It also provides administrative features to secure and manage the visibility of your data.


Databases provide Storage for every data handled by the webservice or binary server.