IoT Platform B.One Middleware – An Introduction

Last updated on 02/01/2022

In the QuickGuide –   B.One Middleware we have already gone into how this is served. But what is this middleware actually exactly and what does she do?

In this article, we would like to shed some more light into the darkness for everyone who is not yet familiar with the middleware.

What does the Middleware do in a Nutshell?

First a very rough outline of the functionality.

In short: Our B.One Middleware shows our LoRaWAN® network and all the devices, sensors and gateways of the selected client that are in it. Here you will find overviews of the gateways and sensors created, such as the online status across the entire client, right through to detailed information on individual devices and the data traffic that they send.

What are Clients?

Our LoRaWAN® network is basically divided into individual areas , for example for specific customer groups. This makes it easier to maintain an overview and access can be restricted. A user therefore only has access to the client relevant to him. This keeps the data protected.

Despite the division into tenants, all devices have access to our entire network and can use any gateway within range. This is how we offer the best possible network coverage .

What is the Middleware used for?

With the help of the middleware, statements about the status of the network can be made and possible problems can be identified and then rectified via the online status and various statistics on the gateways. If, for example, packets from a certain device can no longer be received, the gateways in range can be checked.

In addition, administrative activities can be carried out within the middleware. In this way, new devices (gateways and sensors) can be created so that they are assigned to the correct client during the join process and are thus made known to our network. Device information and configurations can also be adjusted (see blog article about sending downlinks to a sensor ) and devices that are no longer used can be removed .

Redirects in the Middleware

Subsequent systems such as e.g. B. our visualization platform B.One Gallery, which is then used to supply the data from our middleware. You can find the technical background to the process of such redirects and how they are set up in the blog article “Forwarding options B.One Middlware”.

B.One Middleware & B.One Gallery

How do the B.One Middleware and the B.One Gallery interact? The middleware manages the data that is sent from the devices and sensors via the gateways and forwards it to the Gallery. It acts as a data hub, so to speak. The data obtained in this way can then be viewed, managed and visualized in the gallery. The prerequisite for this is, as also in the article “Internet of Things (IoT) – it’s quite simple…” described that you already have a ZENNER IoT GatewayPLUS Indoor, Outdoor or Smart with the comfort option ZENNER IoT PLUG&PLAY in use or one in the ZENNER Shop | IoT Sensors and Solutions acquires this option. This gives you access to our network as well as to the B.One Gallery and the middleware. In order for data to arrive in the gallery, your sensors must first be made known in the network by being installed in the middleware (also known as “provisioning”) and then integrated into the Gallery. If you do this yourself with sensors not purchased in the shop, you need access to both systems/applications, which you will receive via email after your order. However, the system/integration can then also take place directly via the B.One Gallery without having to log into both systems. Boris shows you exactly how to do this in the “B.One Gallery Howto: Create Sensors“. If, on the other hand, you order your sensors in the ZENNER shop with the ZENNER IoT PLUG&PLAY option, you don’t have to worry about anything else and just log in to the gallery to access your data and its visualization. In this case, the ZENNER team takes care of the installation in the middleware and the gallery for you.

If you want to know more about the usage of the two systems/Tools, we recommend the following two associated blog categories: 

• Blog posts about B.One Middleware
• Blog posts about B.One Gallery

And everything that has remained unclear up to this point, feel free to put it in the comments!