What is it?

The NSGI-LD Context Broker is a digital platform component that enables the integration of gathered data. The Context Broker is a reference implementation of NGSI-LD standard specifications that comply with ETSI standards. IoT data is collected, processed and stored with dynamic context and the use of linked data concepts. The Context Broker provides an implementation of REST API endpoints for various data context operations that conform to the NGSI-LD API specification. The context broker allows us to collect, process, report and store IoT data with dynamic context using advanced data concepts.

What do we offer?

First and foremost, you can install the NGSI-LD Context Broker on your Azure environment for free* from the Azure Marketplace. But we also offer expert consultancy to do this for you. 

*downloading the NGSI-LD Context Broker is free, but the required Azure resources do have their price tag (have a look at the costs further down this page).

How does it work?

Cities, companies, governments, or other organizations gather a lot of data (e.g. air quality, parking spots, shared transport solutions). But most of the time, this data misses the required context and interoperability. By posting data from different data streams – in NGSI-LD format – to the Context Broker, this data will be centralized in the Context Broker. This way, all data is easily accessible and comparable. By combining different data streams, you get a complete picture of the meaning of this data. The Context Broker is meant for streaming data and realtime data, and has possibilities to query historical data. The Context Broker makes sure all harmonized NSGI-LD data is made available and can be consulted online. Furthermore, you can consult the context broker to find links between data entities. For example when you want to map out the relation between a certain sensor and the location of this sensor.

For whom?

All organizations who want to make data available to other parties. A city gathering data about air quality or parking spots can use the Context Broker to make this data available to other organizations in the city. They can even choose to put subscriptions on the use of this data. Other organizations can then use this available data via their API to build user-friendly applications. Every time new data is available or data is adapted, these organizations get the update. Furthermore, historical data (e.g. from a week ago) can be consulted.

Public and private companies and local governments looking for a way of making data available to other parties and offer this data in the standard NSG-LD language, will find it very easy to use the context broker for this purpose.

Example of how to use the data made available by the Context Broker

Okay, so the Context Broker combines different data streams and makes data – in the NGSI-LD format – easily accessible. But what can organizations then do with this data? The Context Broker is no visual tool, it does not contain a dashboard for you to visualize this date, it just provides you with the data you need, in one standardized format. Organizations can then build applications to visualize this data.

An example of a tool that visualizes the data from the Context Broker is Slim Naar Antwerpen

This tool displays the data from the Context Broker in a user-friendly and visually clear application. The traffic information of the shared mobility in the city is easily accessible on the platform. Since the different sensors in the city gain new data each day, hour and minute, this data is automatically updated in the application via the Context Broker. This way, you always have an up-to-date overview of the traffic in Antwerp City.


We have modified the Scorpio Context Broker configuration to work with Azure Event Hub and Azure PostgreSQL server. The Scorpio Context Broker container is running inside Azure App Service (Linux, B1) and uses an Event Hub for internal messaging and an Azure Database for PostgreSQL single server for data storage.

The costs

Downloading the Context Broker is completely free of charge. The PostgreSQL server, App Service and Event Hub however, do come with their own pricing. The App Service uses the Basic service plan (Linux, B1), the Event Hub uses the Standard tier and the Azure Database for PostgreSQL is a single server Basic, 1 vCore(s), 5 GB. This will keep initial costs low, the resources can be scaled up by the user. The application will simulate a picture of the costs associated with the these aspects.

The advantages


You can download the Sirus Context Broker in just one click. By following the different steps, you set up the Scorpio Context Broker, Azure Event Hub and Azure PostgreSQL server.


You can download the Sirus Context Broker in just one click. By following the different steps, you set up the Scorpio Context Broker, Azure Event Hub and Azure PostgreSQL server.


But you can also get tailor-made consultancy from our Sirus developers. Our implementation workshop results in a requirements analysis and a detailed description of work effort to be done. A reference implementation of the Scorpio NGSI-LD Context Broker is foreseen. We can also add tailor-made consultancy if that’s what you’re looking for.


The constraints

Important to keep in mind is that this Context Broker is still in its trial phase. You can download and use this Context Broker to test the capacity and possibilities, thereby using a light PostgreSQL and Event Hub, but you are limited in the unboarding of data streams (there’s a limit to the amount of data you can unboard) and you are limited in the different services. If you wish to unboard more data, you can scale up the app service. If you wish to expand other services as well, our consultancy service will gladly assist you. The tailor-made installation of your Context Broker has no limitations.

Another consideration to keep in mind is that the app service is publicly available. Everyone with the link can read and post data, this can be solved by changing the app service configuration to restrict access.. In the following versions, we will add more flexibility and security and there will be extra features like authentication and an expanded architecture with API functions. Keep an eye on our social media accounts (LinkedIn & Instagram) and this webpage for updated versions of this Context Broker. If you do want a secure and scalable version of the Context Broker already, you can rely on our consultancy service.

The application does not use any personal data, unless you send data with personal information in it yourself. In that case, the privacy of this data will be your responsibility.


How to begin?

If you want to set up the Context Broker yourself, you can follow this guide

If you need help or if you are looking for a tailor-made service to set up the Context Broker for your company, you can always have a look at our consultancy service. 

Keep in mind that you need an Azure environment and the necessary rights to be able to use this Context Broker.

Context Broker Consultancy Service

Custom built reference implementation of the Scorpio Context Broker, tailor made to your requirements and Azure data platform environment.
The Context Broker as described above, is available in the Azure Marketplace. This light version is freely available for testing purposes. However, as Sirus has set up multiple Scorpio context brokers in multiple environments, we are also offering a consultancy service in the marketplace. Within this implementation workshop, Sirus will provide a requirements analysis and a detailed description of work effort to be done. A reference implementation of the Scorpio NGSI-LD Context Broker is foreseen.
Within this Consultancy Service, we will:

This will create a running, scalable and secure Scorpio Context Broker connected to your Azure data platform environment.

Or contact us for tailor-made consultancy where we can add additional requirements personalized to your company’s needs.