Smart cities and Tech Evolution - XXVI Service Infrastructure - FIWare // EIT Digital

Smart cities and Tech Evolution - XXVI Service Infrastructure - FIWare

FIWare overall architecture. Credit: FIWare

An example of a SOA is FIWare.

FIWARE is the main result of the EU Future Internet Public-Private Partnership (FI-PPP) and of the EU commitment to help entrepreneurs thrive in Europe via the Startup Europe initiative, an investment of several hundred million euros over the last five years. FIWARE provides enhanced OpenStack-based cloud hosting capabilities and a rich library of components. These components, called the “Generic Enablers”, provide open standard APIs that make it easier to connect to Internet of Things devices, process data and media in real-time at large scale, perform Big Data analysis or incorporate advanced features to interact with the user, build applications easy to replicate in various relevant sectors. They allow developers to set the foundations of the architecture associated to their application. In FIWARE, Generic Enabler (GE) API specifications are public and royalty-free, supported by open source reference implementations. Thanks to that, alternative FIWARE providers can emerge faster in the market. 
 FIWare is deploying all around Europe, and it is also getting ready to do so around the world, a set of FiWare Lab Nodes also including a Security Operations Centre (SOC) in order to address security issues on an organizational and technical level.

Service Developers can access the FIWARE catalogue to deploy and use the City Enabler in a city. It is compliant and connected to other catalogues, namely the 

 

 

These will let the City Enabler support micro proxies to collect the data from IoT infrastructures installed in cities. 

The FIWare Service Infrastructure facilitates the access to sensors (IoT) acting as a Context Broker managing a variety of protocols at the physical level letting the service operate at an abstract level. Hence a service can interact with a sensor/actuator by acting on its virtual representation in FIWare that will take care of the “implementation” of that interaction at physical level. This is particulalry useful given the variety of IoT in a city and their evoelution over time that would require, in absence of a virtualisation, a continuous update of the service.

These properties facilitate urban service providers and the Industry to rapidly develop micro proxies that are able to get data from IoT infrastructures and put them in the City Data workspace.

Clearly the City should move on a path to create a virtual representation of itself, as I will discuss when dealing with the Data Fabric.

Author - Roberto Saracco

© 2010-2018 EIT Digital IVZW. All rights reserved. Legal notice. Privacy Policy.