Research and development of bIoTope project technologies will continue through May 2019. The following public results developed up through month 27 of the project are available for download:
Requirements, Methods and Pilot Validation
D2.2 Evaluation Methodology for Pilots Validation - This report describes the approach that will be utilised to evaluate all pilot case implementations of the bIoTope technologies in order to ensure high quality results are produced by the project. The evaluation will be used to monitor the progress of bIoTope in achieving the targeted innovations and will be used to assess the technical approaches of bIoTope and refine bIoTope’s research and development specifications during the operation of the project.
D2.3 Open Source Project Requirements and Specification - The work within bIoTope on different components is apportioned among different organisations for a faster implementation and realisation of the project objectives, which requires a set of common software engineering policies and procedures to be established for a proper integration of the different components. This report is orientated towards the adoption of common practices found amongst successful open source projects. The best practices described are not only found in successful open source projects, but also in general within mature software development organisations and these approaches and procedures will be used within the bIoTope project.
D2.4 bIoTope SoS Reference Platform Specification v1 - This report transforms fundamental requirements, elicited from the pilot cases stakeholders within the project, into a specification of the overall architectural framework supported by architectural viewpoints (Application and Infrastructure) in ArchiMate. Complementary to the bottom-up approach from each pilot case point of view, a top-down approach with an architectural framework was applied. Both perspectives are important to consider the needs of each pilot and the development of services inside of the bIoTope ecosystem, are converging and will be jointly integrated during the project.
D2.6 Evaluation Report of the bIoTope Pilots - This report describes the evaluation of technologies developed within bIoTope, especially the domain-specific pilots, the cross-domain smart city pilots, and the technologies developed in the development workpackages that have been used in the initial pilots. This report keeps track of the development of the project by assessing the Technology Readiness Level (TRL) as well as the Integration Readiness Level (IRL) for the core components, the cross-domain city pilots and the domain-specific pilots. The report also evaluates the matching of Key Performance Indicators (KPIs) and requirements for the cross-domain smart city pilots and the domain-specific pilots. Finally, the report prepares the ex-post evaluation of the bIoTope pilots based on user acceptance testing and for the cross-domain smart city pilots.
D2.7 bIoTope SoS Reference Platform Specification v2 - This report builds on the previous iteration of the bIoTope SoS Reference Platform Specifications (D2.4) and focusses on a more detailed level of system architecture specification. This version was planned to allow the consortium to cope with the further development of the bIoTope ecosystem throughout the project, for example to allow for capturing input from additional project partners or changes in architecture due to performance issues. It furthermore documents the refinement of the structuring principles and interfaces previously outlined and describes in more detail the interfaces between the different software components developed in each of the development workpackages.
Building a Secure, Open and Standardised SoS Platform for IoT
D3.1 Framework for Identity Creation, Management and Authentication v1 - This report describes a solution and serves as a technical roadmap for providing a secure foundation for a completely generic IoT (or IoE) platform, using identities. The identity does not merely refer to physical entity but rather to all systems and objects that have to be identified. The report provides an overview of existing relevant security technologies, solutions, and evaluates their applicability by pointing out possible drawbacks and shortcomings.
D3.2 Information Source Publication and Consumption Framework v1 - IoT is entering a new phase with an increased focus on how to avoid the continual emergence of vertical silos, which hamper developers in producing disruptive and added value services across multiple platforms and sectors (data is “siloed” in a unique system, cloud, domain, and stays there). This report details the mechanisms to be developed in the project for enabling any IoT device and IoT-related information system to publish its presence, and be discovered by, other IoT systems.
D3.3 Context-Sensitive Security, Privacy Management, Adaptation Framework v1 - This report provides the technological foundation of the bIoTope Systems of Systems (SoS) Platform for information source publication and consumption in the IoT, based on the O-MI and O-DF standards. This includes new mechanisms to better manage ‘Identities’ and ‘Context-sensitive Security and Privacy’ (SaaS) of Connected Smart Objects and People to cope with the dynamic nature of the IoT.
D3.4 Safe Micro-Billing Framework for IoT v1 - The report describes a technical roadmap towards providing an adequate billing system for the IoTBnB service marketplace as an integral part of the bIoTope ecosystem. In an attempt to fulfil certain fundamental technical requirements inherent to the service marketplace, and in order to remain in the overall peer-to-peer spirit governing its design, the focus is on emerging decentralized currency technologies, the prime example of which is Bitcoin. The report identifies the technical requirements, which consist essentially in the support of micropayments, the ability to conduct fast transactions, and the capacity to scale massively in the number of users and payments. An overview of the current academic and industrial state-of-the art in decentralized ledger techniques leaning towards these goals reveals that while existing systems fall short of our expectations, one technology in particular – the Lightning Network - is an adequate starting point for experimentation, with a view towards prototyping for IoTBnB.
D3.5 Prototype of Platform Integration using API Mediators - This report defines the overall bIoTope Systems of Systems (SoS) ecosystem architecture by providing a state-of-the-art framework for information source publication and consumption developed around Open API standards including Open Messaging Interface (O-MI) and Open Data Format (O-DF) specifications. This SoS platform will enable users, developers, and resource providers to publish, consume, compose, and integrate services in order to explain the coordination of various platforms with the standardized APIs. For the platform to be successful, the APIs and platforms need to be robust and better managed, acting as technological foundation for an open IoT innovation ecosystem.
D3.6 Information Source Publication and Consumption Framework v2 - This report presents the enhanced/final version of the mechanisms used to enable IoT devices and IoT related information systems to publish their presence, and to be discovered by other IoT systems. This framework is in the form of open API standards that are defined by the Open Group and are implemented by Aalto University developers. The main objective is to describe version 1 and version 2 of O-MI/O-DF messaging standards and list all the features offered by both versions (the reference implementation of these standards is available online)
D3.7 Framework for Identity Creation, Management and Authentication v2 - By utilizing insights about the paradigm shift towards distributed computing in multi-vendor environments, such as the industrial Internet, the project partners have developed an identity management technology called Mist. It is productized and designed to be reused in every connected device, app and system. The uniqueness is the distributed neutral approach, with no implicitly trusted third party authority1. The technology bundles autonomous identities, peer-to-peer communication, a new distributed PKI, authentication and authorization together in an intuitive way. It runs a level below the O-MI/O-DF, providing a more agile alternative to HTTPS and other transport protocols and security models.
D3.8 Safe micro-billing framework for IoT v2 - This deliverable describes the technical details of the Billing-as-a-Service (BaaS component) implementation that allows micro-transactions between different entities. This component is intended to be mainly used by the bIoTope Marketplace / Service Catalogue – also referred as IoTBnB – for providing to its users a way to sell/pay for IoT data/services. The BaaS component gives the opportunity to offer to the IoTBnB users a way to monetize their data/services on an API call basis (i.e. the user will pay for each O-MI/O-DF request). To this end, it is necessary to have a micro-billing functionality in place to enable fast and secure micro-payments.
Context-Aware Service Provisioning for IoT
D4.1 Edge Data Storage and Intelligent Filtering v1 - The primary objective of this report is to provide insight into Big Data technologies and frameworks that shape today’s Big Data landscape. This state-of-the-art review could serve as a reference study for future design choices during bIoTope development and implementation stages, and even beyond the project itself. The second objective is to provide an overview of the storage and analytics capabilities that are currently supported/offered by the platforms of the different partners involved in bIoTope, along with a first view of additional key building blocks that need to be developed to foster the creation of a unified IoT ecosystem. Some preliminary elements about the conceptual framework to be developed in the different bIoTope pilot cases are also presented.
D4.2 Knowledge Representation and Inference Framework v1 - This report describes the state of the art of knowledge representation in the Internet of Things and the challenges of integrating context and situation awareness inside a framework of bIoTope knowledge services.The main purpose of this report is to provide insights into today’s knowledge engineering by describing the state of the art, which will enable us to understand research gaps and the direction to take in the context of the bIoTope Knowledge Framework.
D4.3 Theoretical Framework for Context and Situation Awareness in IoT - The primary objective of this report is to provide insight into context- and situation-awareness theory, technologies and frameworks. This state-of-the-art review could serve as a reference study for future design choices during bIoTope development and implementation stages, and even beyond the project itself.
D4.4 Framework for Knowledge Extraction from IoT Data Sources - The main purpose of this report is to propose an architecture and implement a framework that is capable to let the users to extract valuable knowledge out of IoT data sources and thus permitting the user to gain insight into the interactions of various phenomena of everyday life. A plethora of knowledge extraction and data fusion mechanisms are presented and implemented inside the Knowledge as a Service (KnaaS) framework. In order to measure the effectiveness of the proposed conceptual framework as well as the prototype implementation of it various scenarios of the Lyon’s Heat Wave Mitigation use case are examined and concrete implemented solutions are provided. However, the work presented in this deliverable is not specific to this use case.
D4.5 Context-Aware Actions and Self-Adaptation Framework - This report presents the bIoTope context management system called Context-as-a-Service (CoaaS) and associated software components. Key functionality of the bIoTope CoaaS includes i) real-time context query engine, ii) context storage management system which is intended to address scalability and real-time data stream monitoring for situation reasoning. A prototype/demonstrator is presented together with the report.
D4.6 Edge Data Storage and Intelligent Filtering Framework v2 - The objective of this report is to provide insight into the architectural design choices and implementations made in the bIoTope project regarding IoT data/service storage (and indexing) with respect to three key bIoTope ecosystem’s building blocks in which management of sensor data and web services is of the utmost importance. In a second part of this report, a more detailed overview of how the bIoTope pilots benefit from the storage and indexing components developed/set-up in bIoTope is presented.
D4.7 Knowledge Representation and Inference Framework v2 - The main purpose of this report is to describe the coordinated work in bIoTope to provide an extensible and sustainable methodology for extending the O-DF messages with semantic annotations. For that reason, existing state-of-the- art vocabularies for representing semantic information in IoT data are presented. What is more, semantic vocabularies and ontologies that were designed inside the bIoTope project (i.e., MobiVoc and the O-MI/O-DF OWL Ontology) are documented. Furthermore, various bIoTope components that constitute the catalytic center for the annotation, the data exposure and the extraction of knowledge are presented.
User Interaction Development and Adaptation
D5.1 IoT Interaction Patterns Report - This report focuses on user interaction (UI) with the IoT services and objects that were identified by the pilot use cases and extracts “interaction situations”, i.e., ways to make use of the proposed system from a user’s perspective. The identified interaction situations allow deduction of more abstract “interaction patterns” and to identify a set of IoT services and objects involved as well as the UI interface elements that should be utilised in the implementation of the pilots.
D5.2 Service Composition Framework v1 - This report presents an approach towards establishing a service composition framework which allows non-programmers to orchestrate IoT devices, i.e., to detect and react on certain events by specifying data flows. It is based on leveraging the standards O-MI and O-DF, which are used by IoT devices throughout the bIoTope ecosystem and provide a standard method to interact (e.g., update, subscribe for notifications) with IoT devices and data. However, the standardized representation of O-MI/O-DF is based on XML, which has disadvantages when integrating data from multiple sources. In this document, an approach is introduced of a representation method for O-MI/O-DF data in an easily integrable RDF-based format that lays the foundation for using existing graphical tools to query and manipulate the data. An implementation of this approach is provided as well as an overview on graphical tools that are available and which are likely to be used together with the data representation approach to establish GUI-driven service composition.
D5.3 Context-Sensitive End-User Dashboard Framework v1 - This report partly builds on the work done in deliverable D5.1 and puts the focus on User Interaction with the IoT services by the means of interactive end-user dashboards. It reports on the analysis and comparison of several dashboard frameworks and the selection of the one, which better supports visual representations of the IoT data that were identified by the pilot use cases, and a subset of the identified “interaction patterns”.
D5.4 2D and 3D UI Widgets Library - This report presents the approach for representing the contents and setting up visual dashboards that aggregate information from IoT devices in the bIoTope ecosystem. An architecture is proposed and a framework implemented that is capable to let users create and define personalized dashboards. In addition, the framework incorporates a solution for specifying rules to detect certain situations (contexts) in a graphical way so that changes in the dashboard’s content can be triggered. The central contribution is an overview of GUI elements (widgets) that are usable as building blocks for end user dashboards of IoT devices, which are capable to display data published on O-MI nodes using the O-DF data structure format.
D5.5 Service Composition Framework v2 - This report presents an approach for standardized workflow composition between biotope XaaS components. It shows how this approach can be implemented on a technical level as a framework where the framework resembles a toolbox of building blocks that allow the definition of workflows between bIoTope XaaS components, thus fostering integration and interoperability. It is centred around an open source visual programming environment (Node-RED) that was compiled as an easy to use package. It contains visual representations (nodes) of XaaS components provided by the bIoTope consortium, to compose bIoTope services, as well as predefined workflows and useful services that aim to support end-users in orchestrating and working with bIoTope components.
Pilot Deployment and Testing
D6.1 Proof-of-Concept “Smart Air Quality Services” Implementation v1 - This reports on the intermediate state of the Air Quality Monitoring and Prediction (AQMP) use case. It includes two scenarios: air quality and dust concentration measurement using OpenIoT IoT platform and wrapping the communications with external tools and applications using OMI/ODF; the second scenario involves indoor air quality measurement and prediction using a mobile app. Both scenarios are demonstrated and discussed.
D6.2 Proof-of-Concept “Smart Building and Equipment” Implementation v1 - This report describes the progress of the proof of concepts and Smart Building and Smart Equipment pilot deployment progress.The Smart Building pilot is complementing the Helsinki Smart City pilot and Smart Mobility pilot, by enabling private people to publish their own private parking slot as a sharing economy. The Smart City pilot is focusing on publishing existing commercial charging service provider assets to the same service catalogue, while the Smart Mobility pilot will enable BMW drivers to discover the published services from the in-car dashboard. The Smart Equipment pilot demonstrates how this same technology can be utilized in a completely different domain, by inviting experts to enable remote assistance of air handling unit problem pinpointing.
D6.3 Proof-of-Concept “Smart Electric Car” Implementation v1 - This report describes the progress of the proof of concepts for the Smart Mobility Use Case that addresses the issues that are involved when connecting different systems of different domains and ages. The implementation involves nearly the whole ecosystem and thus has the higher-order goals of building a sustainable way to make use of cross domain information and services, reducing or handling uncertainty for data-usage and extending the existing (de facto) standards and formats with open, scalable solutions.
D6.4 Proof-of-Concept "Greater Lyon Pilot" Implementation v1 - This report presents the two pilot use cases deployed in Lyon: bottle banks management and heat wave mitigation. It describes how the use cases meet the smart metropolis strategy, the expectations of the different stakeholders, and which services are provided. Hardware and software solutions contributing to the services are described: some are existing, others have been designed for the purpose of the pilots, some are managed by the metropolis, others are managed by our private partners. A focus is made on the integration of the heat wave mitigation use case in the bIoTope ecosystem including the description of the gateways built between heterogeneous systems and the O-DF/O-MI standard, the semantic annotations added to data and the publication on the bIoTope marketplace. For the bottle banks use case, the interoperability enabled by the bIoTope ecosystem makes it possible to develop new collaborative services with several partners and the metropolis.
D6.5 Proof-of-Concept "Brussels-Capital Region Pilot" Implementation v1 - This report presents 3 pilots (2 already deployed and 1 to be deployed): Safety Around Schools, Waterbus, and Smart Parking for Disabled People (v1 is to be deployed by mid 2018). A focus is made on the integration of the bIoTope building blocks, mainly in the ‘Safety Around School’ use case, which is at the most advanced stage. In particular, it includes the implementation of the IoT gateway based on the O-MI and O-DF standards that enables to publish data coming from heterogeneous systems and its registration on the bIoTope marketplace (referred to as IoTBnB) for discovery purposes.
D6.6 Proof-of-Concept "Helsinki Pilot" Implementation v1 - This report describes in detail the goals and use case of the Helsinki pilot, architecture of the solution, the relation to the other use cases, the current state of implementation, demonstrated scenarios, and the plan to accomplish the implementation from the demo stage to the final solution. The proof of concept and demonstration of the current stage of implementation has been shown by a demonstrator that consists of three components: Client Android app, O-MI Reference implemented Agent, and the charging hardware box. The basic scenario of searching and selection of a suitable charging station in the area has been implemented and shown.
D6.13 Proof-of-Concept "IoT-enabled Waste Management - St. Petersburg" Implementation v1 - This report describes the design and development work with regards to a Smart Waste Management (SWM) use case. The deliverable addresses functionality for various stakeholders, namely, city administration, garbage fleet dispatchers, truck drivers and citizens. Functions include visualization on the map, routing of garbage trucks, providing context in response to context queries, developing and working with a waste management ontology, data collection from smart garbage bins using LoRaWAN technology, deploying FIWARE components and providing a mobile app for citizens.
Open Call Management and Support
D7.1 Open Call Methodology, Management and Support Framework - The report outlines the basic process for organizing open calls in the bIoTope project. It describes the open call methodology, management procedures and support mechanism. The bIoTope project organizes a first open call for the total amount of in May-August 2017. The open calls are targeted to support the use case implementation for proof of concept validation, as well as for use case extension and broader stakeholder engagement. The call is divided into three entities by the pilot cities where the actual use cases take place.
D7.2 Open Call Publication, Evaluation and Negotiation Report - The report describes the process for publishing and evaluating open calls in the bIoTope project. It further describes the negotiation process and finalization of the contracts. The open call 1 was targeted to support the implementation of the four bIoTope use cases for the proof of concept validation, as well as for use case extension and broader stakeholder engagement. The calls were published on 22 May 2017 for a duration of three months. The methodology for open calls followed the guidelines set by the European Commission, and the benchmarked best practices from earlier Future Internet open calls.
Dissemination, Exploitation, Evaluation and Standardisation
D8.6 IoT Ecosystem Management, Exploitation & Business Modelling Report - The reportpresents the frameworks and typologies that will be used to describe the ecosystems created over the various thematic and cross-sectorial use cases, related orchestration and collaboration processes and means to address IoT business models.
D8.10 IoT Ecosystem Management, Exploitation & Business Modelling Report 2 - The report expands on the frameworks and typologies that were designed to describe the ecosystems and orchestration models (see deliverable D8.6), and builds the foundation and structure for data collection and scenario building for business and exploitation opportunities for different bIoTope partner organizations, as well as presents scalable ecosystem level archetypes for roles, activities and value capture for IoT Use Cases. Work is done in collaboration with the EPI IoT business model group.