Connectors add encryption and headers before data reaches the public domain, shifting this responsibility away from the device.

Without a Connector, your SIM acts like a typical data SIM, providing connectivity from your device to the internet. As a result, your device needs to know everything, e.g. where to send data and how to encrypt it. Any changes to this will require device updates.

With Connectors, these choices are made within the Onomondo core network, so your devices do not need to know anything about encryption or where to send data. Any updates are instant, meaning your devices don’t need to be updated. It also lowers the cost of connectivity, by reducing the overall size of each network packet sent from a device.

While you can use Onomondo SIMs without a Connector, these savings add up significantly at larger deployment volumes.
​

There are three steps to set up Onomondo Connectors:

Once the Connector is added to the SIM, any data sent from it will be processed by the Connector and sent to the destination of your choice.

Below, you can read more about setting up Connectors:

Once step one is completed, future changes to data transmissions only require creating and then assigning a new Connector to a SIM.

This means, you only need to update the device when the actual data structure or frequency needs changing. It also means, that you can have different Connectors on different devices and maintain an overview of where your devices send their data.

Currently, there are two kinds of Connectors:

All Connectors that send information directly to cloud platforms are event-based Connectors. Here, the device sends data to be recorded on a cloud platform, such as:

We also offer a Connector that provides Transport Layer Security (TLS) to data from all your devices that are sent to your server. It also creates a device-initiated two-way tunnel, allowing the server to communicate with the device. You can find out more here:

We have a course on how you can use HTTPS Connector and our Messages API walkthrough. It guides you through the steps, from capturing packet information as the device sends it on Traffic Monitor to receiving responses back to your device.

We are currently working on introducing a few other solutions, not mentioned in this guide. The following are currently in available in beta versions:

​