Skip to main content
Skip table of contents

Navixy IoT Gateway introduction

While collaborating with Telematics Service Providers (TSPs), system integrators, third-party developers, and device manufacturers, we made an intriguing observation. Not everyone needed the front-end part of our platform. Why? Because they were using the data from devices to display everything on their own side. The most important thing for them was simply having access to the decoded data from these devices. They were happy to handle the universal data themselves and provide various custom solutions to their customers.

Some developers were using our APIs to create their own front-end or to offer some of our platform's features to their clients in applications. However, if there were a lot of devices or if they had several big customers who wanted custom applications, our existing solution didn't quite meet all their needs.

We decided to create a new product that could be helpful for them. We named it the IoT Gateway.

The IoT Gateway is like a traffic manager for data. It gets data from devices, third-party services, and applications. It can read, decode, convert, and send this data in real-time to other platforms and services, including the Navixy platform.

The gateway has four main parts:

  1. Input Stream service: This is the place in the IoT Gateway where data from different devices first comes in. Think of it as the entrance where the system greets the data, decodes it and then saves it in a common format for various parameters.

  2. Data Enrichment Manager: This is where you get to decide where the data should go. For example, you might want to send one kind of data to one app, and a different kind of data to another app. Plus, you can change, compute and enhance the data from devices into the form you need. You also get to name each parameter in your own way.

  3. Output Stream Service: This is where the IoT Gateway sends data off to other places, like third-party servers and applications. Think of it as the postman who delivers the sorted mail to the right addresses.

  4. Diagnostic Interface: It's like a tool that allows you to see all the incoming data from your devices. You can use it to check and fix devices if there are any problems. It's also useful for making changes in device settings when necessary.

So, in simple terms, the IoT Gateway is a tool that helps manage and control the flow of data from your devices to different places.

The Navixy IoT Gateway receives information from different Data sources. It uses various methods like TCP/UDP, MQTT, and HTTP to get this data. The data comes in a protocol specific to the equipment manufacturer.
Once the Navixy IoT Gateway gets the data, it decodes it and enriches it based on your instructions. Here's what you can do using Navixy IoT Gateway:

  1. You can pick which data should be delivered to your server or app, and which data should be left out.

  2. You can give names to the parameters that are sent from the Navixy IoT Gateway, just how you like it.

  3. You can tell the IoT Gateway which parameters need to be multiplied, changed, or divided, and it'll do the math for you.

  4. You can set conditions for using logical operations. For example, if the data from field 1 equals X, the system will recalculate and send the result from field 2. Or, if data from both field 1 and field 2 are present in the message, it will send the result.

Once the data has been enriched, you have the choice of where to send it, and by what method. You can specify multiple recipients - OEM servers and applications. The method you choose, whether it's TCP/UDP, MQTT or HTTP, depends on the most convenient way for your server or program to receive the data.

Crucially, this entire process happens in real time. It's almost as if the device is sending the data directly to your service, but without the need for your server to understand each device protocol or implement conditions. Vendors also have the option to integrate their solutions directly, further increasing the range of supported devices.

Navixy is renowned for its user-friendly platform and interfaces. Simply set up the data stream and receive data in the correct format from all devices, allowing you to focus on other solutions that will be immediately visible to your users and available for your solution growth and monetization.

  1. Give the target audience a tool to work with decrypted data from any telematics data sources, thus saving customers from having to deal with device protocols, decoders and processing devices data on their servers.

  2. Provide the ability to transform data that comes from customer data sources. The transformation includes filtering, mathematical and other transformations, calculating new parameters and organizing server side logic.

  3. Provide convenient ways to retrieve data on target servers and client services. All necessary variety of options is supported: TCP/UDP transmission, MQTT protocol subscription, Webhook.

  4. Provide the client with an opportunity for diagnostics of transmitted data for in-depth analysis of possible malfunctions.

When working with large clients who need to have their own customized GPS platforms, telematics solutions integrators need a tool that can seamlessly manage and transmit device data.

For example, you’re TSP client, who have a lot of customers and every uses its own stack of devices. Without such product as IoT Gateway, you need to develop decoders and support data processing from different devices. After it, you should have a huge team to support this data processing and server availability always to provide huge amount of data every second from these devices. At the same time there should be another team who works on Frontend part of your application to show information to end customers and develop new features based on it. IoT Gateway closes all these questions and takes that work on it.

Application developers will find Navixy IoT Gateway particularly useful. The ability to receive data for their application from different devices in universal form allows them focus on data processing to provide useful information to their customers instead of reading and decoding different and in some cases unnecessary data from devices. Along with the same issues on data decoding and receiving we shortly described previously. As a telematics data tool, Navixy IoT Gateway simplifies and accelerates application development, enhancing the functionality of existing applications.

GPS vendor partners aiming to expand their market footprint and boost brand awareness will find Navixy IoT Gateway invaluable. By broadening the list of products that support their devices, Navixy IoT Gateway amplifies their market presence, offering a competitive edge in a crowded marketplace.

For example, you have created a new great device for reading different vehicles and IoT data. Different clients are using different platforms. So to be able to buy and use your devices, their platforms require this data reading correctly on their side. It slows product incorporation into their ecosystem a lot. Trying to provide your protocol to different platforms will be a real pain in this case. But supporting this protocol on the IOT Gateway side creates benefits for users who want to use your products and for you since you don’t need to implement the same work for every solution. It is implemented once and output is easy to decode data in universal format. As a result - your devices are working with safety protocols and clients can buy your devices and implement them to solve their cases much faster.

The following is what makes the Navixy IoT Gateway product stand out:

  1. It makes sure all the data that comes into the IoT Gateway app is uniform. Every piece of data is changed into a single format called the Navixy Generic Protocol, which is easy to read and open source.

  2. Flexible and intuitive Data Enrichment Manager (aka Message Processor) tool where you can filter unnecessary parameters, calculate new ones and transform others.

  3. Working with streams instead of individual data sources. It is now possible to work with telematics in a larger and higher-level representation - a stream. This simplifies working with telematics, as it reduces the number of actions that need to be done to enrich incoming parameters and make telematics more useful.

  4. It lets you send a variety of parameters to different sources through the IoT Gateway. For example, from one device, you can pick one group of data to send to the government, another group to send to your server, and a third group to send to your app. Plus, for each output, you can set specific definitions to parameters.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.