Project Deliverables

Deliverables

D1.2 AGILE Gateway hardware final prototypes 2nd AGILE Release – Hardware Platform

This deliverable presents the concept of AGILE gateway and describes the prototypes of the
makers and industrial versions of the gateway. Following the requirements identified in D1.1 and
D8.1, the final hardware architecture and the final gateway specifications are defined. Finally,
the deliverable provides preliminary information about the adoption of the gateway prototypes in
the pilots.

D1.1 AGILE Gateway architecture specifications and initial design

This deliverable introduces the concept of AGILE gateway and presents the preliminary hardware architecture of the makers and industrial versions of the gateway. The deliverable illustrates the methodology adopted for the design of the gateway, reports the results of the requirements analysis performed in WP1 and WP8 and provides the preliminary specifications of AGILE gateways.

D2.3 Final version of gateway self-configuration, IoT Device discovery & Remote gateway management

This report forms the second iteration, and final deliverable, of Work Package 2 “Core Module Integration & Gateway SW framework development” part of the AGILE EC-funded Horizon 2020 project.
We report on functionality of the gateway and orchestration components such as the Operating System selected and being further developed, the underlying AGILE stack components (e.g. SDKs and APIs), the accompanying systems for configuration and recommendations as well as device provisioning and discovery subsystems.
Finally, we include the original review of requirements incl. assessment of IoT Protocols and Standards to facilitate use-case and pilot development.

D2.2 Initial version of gateway self-configuration, IoT Device discovery & Remote gateway management

This report forms the second Work Package 2 contractual deliverable of the AGILE H2020 ECfunded project. It provides the initial version of the mechanisms integrated and developed for the self-configuration (auto-configuration with support of the Configurator) of the gateway, the discovery and communication with IoT device as well as the framework for the remote gateway management.
The final version, that provides auto-configuration capabilities, will be presented in deliverable D2.3 (Final version of Gateway Self-configuration (auto-configuration with support of the Configurator), IoT Device discovery & Remote gateway management).

D2.1 Core requirements specification and IoT protocol integration

This report forms part of the contractual deliverables of the AGILE H2020 EC-funded project. It documents the results from the analysis of available IoT Standards and protocols (for IoT and Machine-to-Machine communication) that will be integrated within AGILE for maximising the connected device support and interoperability. Support of the selected protocols (for integration in various layers such as the operating system, device management and the userspace) is assessed for features such as device discovery, communication and, additionally, utilisation of external protocols (e.g. for messaging).
In addition, the deliverable illustrates a process for auto-configuring hardware modules within the gateway, focusing on the configuration steps required during the deployment of the gateway and on the resource optimisation at runtime. This will allow the AGILE gateway to be autoconfigured based on the application context and user preferences. A preliminary mechanism to implement the configurator service is documented herein. A more detailed documentation of the configuration, will be presented in deliverable D2.2 (initial version of Gateway Selfconfiguration, IoT Device discovery & Remote gateway management).

D3.3 Application Interfaces (Gateway, Data Management & Developer’s Interface)

This deliverable presents how the AGILE software stack integrates components developed by the consortium and additional open source components into a modular framework, and how this framework is exposed to the user through the AGILE Graphical User Interface (GUI). In addition, it describes some non-GUI related elements that were not documented in previous deliverables, namely: how Kura is integrated with the AGILE framework; the local data storage API; and the JavaScript AGILE SDK. The document has been further edited since version one, to address feedback from AGILE project reviewers.

D3.2 Application Interfaces (Gateway, Data Management & Developer’s Interface) – initial implementation

This deliverable presents the initial implementation of the core application interfaces of the AGILE gateway: The Gateway management Interface, the Data Management & the Developer’s UI.

D3.1 Requirements Specification & SW Architecture

This deliverable presents the initial outcome of the requirements analysis for the hardware and software features of the AGILE gateway. It also contains the proposed software stack architecture for the software components of the gateway.

D4.3 Cloud integration With Pilots

This deliverable reports the work done until M34. The main objective of the document is describing how cloud services have been utilised by the AGILE pilots. Special focus will be given in the evaluation of horizontal interoperability achievement between different platforms and AGILE. The document also updates the description of the cloud integration components with regards to the previous deliverable.

D4.1, D4.2 Cloud integration and horizontal interoperability

This deliverable reports the work done until M18 on Task 4.2 and 4.3, about the integration of the AGILE platform with cloud services.

D5.3 Secure Data Sharing

Data sharing is a key element of IoT environments; however, security and privacy concerns can diminish the potential of certain applications as users are reluctant to give data to third parties unconditionally. This deliverable describes how the AGILE security framework supports data sharing mechanisms while offering security assurances to users storing information on the gateway or sharing it with external systems.

First of all we explain enforcement mechanisms applied within the gateway. Those include enforcement points to ensure authorised access to container APIs, encryption of data stored within the gateway, and a policy decision point that can be used from applications running within or outside of the gateway.

Afterward, we explain mechanisms supporting use cases when data needs to be sent or received to/from external systems. For instance, AGILE offers a one-time token mechanism allowing external devices to authenticate in a lightweight manner towards the gateway. To demonstrate the feasibility of this approach in resource constrained devices, we implemented the client-side mechanism to generate tokens on RIOT (an OS for the IoT).

With regard to outsourcing data to external systems, we developed an SQL connector. This connector allows AGILE users to apply policies based on tables and actions performed on them when an application executes database queries. More importantly, when used in combination with CryptDB (an existing encrypted database), this connector can be used to offload data storage and querying computational resources to more powerful servers, yet without letting the external service to see the data in plain text. This is possible because information is encrypted before it is shared with external services.

To offer a wide range of integration possibilities, we do not only describe how to interact with a structured query language in a secure manner; on the contrary, we also include an approach that enables developers to apply policies on any kind of data they need to process. To this end, we created a sample application that is easily extensible and documents how to use the policy decision points from AGILE in different scenarios. These scenarios range from operating on an in-memory array of objects to obtaining information from external HTTP endpoints, e.g. github API, and applying policies on it.

D5.2 Usage Control and Provenance Management

This document discusses the goal of usage control and monitoring of security-sensitive actions executed on the gateway.

This deliverable describes how usage control and monitoring is achieved through the implementation of the AGILE security architecture. To this end, the security architecture is placed in the big picture of the AGILE project, and the location of the enforcement points required to achieve proper access and usage control of the data is covered herein. Additionally, this report illustrates how monitoring of actions to track provenance of data access gives insights to security-aware users on how systems interacting with the gateway APIs act on their behalf and access their data.

From the technical perspective, the policy language used by AGILE and the evaluation of the security policies with their dimensions are discussed. Later sections describe how the desired role-based access control model presented in earlier deliverables has been implemented on top of our generic attribute-based security architecture. More importantly, this document clarifies how the role-based access control currently configured by default for the gateway is realised by explaining entity definitions and their policies. The aforementioned role-based access control mechanisms serve as the foundation to apply policies capable of ensuring proper usage control on the gateway’s data. This takes place through a flexible policy framework implemented based on usage lock policies.

D5.1 First Prototype of the AGILE Identity Management System

Before defining security policies of any kind, entities in a system need to be authenticated. To achieve this, identity management components provide authentication mechanisms and administer attributes and credentials for the system’s entities. In this deliverable we introduce AGILE IDM (Identity Management) and its relation to the gateway’s architecture, the model chosen to handle entities attributes, and functionalities provided by AGILE IDM to gateway components and applications. Last but not least, some examples of use, tutorials (also available in github) and additional resources for piloting activities and developers are explained.

D6.3 Report about the crowdfunding campaign, information about the crowdfunding tools used, the delivery process, and the users involved into AGILE through the campaign and initial user feedback

This document reports on the work plan that has been carried for the crowdfunding campaign design and how it has been organized to spread the visibility of the AGILE project and attract early adopters from the worldwide Internet of Things (IoT) users and entrepreneurs’ communities. The deliverable consists in the following sections:

  • Chapter 1: The first chapters lays out the context for the strategic planning of the AGILE crowdfunding campaign and the platform election to enhance the impact of the campaign.
  • Chapter 2: In this chapter, the crowdfunding plan is presented along with the detailed schedule and scope. It shows all the steps followed and explains to the reader how to understand all the decisions taken to carry out the campaign.
  • Chapter 3: The third chapter offers an overview of tools, channels, and activities performed for disseminating the AGILE crowdfunding campaign. It consists of custom blog and social media content.
  • Chapter 4: In this chapter, the outcomes of the crowdfunding campaign are shown, and the real impact of the campaign are described. It addresses monitoring and evaluation of the crowdfunding campaign.
D6.4 Innovation and Exploitation Report 1

The goal of this deliverable is to provide a baseline for the exploitation management of AGILE. In this first iteration, the focus is on the innovation potential the individual project partners see for AGILE as an opportunity to explore alternative exploitation and monetization paths, or to enhance existing ones. In order to achieve a structured overview, a business model validation tool is introduced and applied to each participating partner in AGILE. The tool identifies each partners’ envisaged customer segments, their common need, the value promise of the solution, the technical aspects involved, the value network of stakeholders, the identifiable competition and the potential financial model. Each of these aspects is briefly explained with the goal of providing a starting point for later iterations of this deliverable.

The initial conclusions show that various partners in the project have compatible customer segments and value propositions that revolve around the AGILE solution. This compatibility is important, as it will allow individual partners to exploit results from the project in their respective businesses: it is clear that the integrated solution that AGILE promises to be will be exploitable as such, but at the same time it will allow several partners to build on and exploit the results even without a further commercialised, integrated platform.

D6.1 Open Call Dissemination, Management & Submission Portal

D6.1 – Open Call Dissemination, Management & Submission Portal – was defined as being a website or part of a website linked to the main AGILE project website that will host all the information.

The information of the Open Call 1 is found on the homepage of the Agile IoT project: http://agile-iot.eu/

As part of this deliverable, a guide for applicants has been developed based on the internal call manual. This guide was also published on the call site.

Next to the information on the Agile IOT site, the site on F6S is used to gather and evaluate the proposals for the open calls: https://www.f6s.com/opencall1agile

All consortium partners were asked to assist in the dissemination of the open call in the respective markets where they are active. Eclipse foundation also helped spread the open call through their channels as part of their dissemination effort. Startupbootcamp IoT will promote the call worldwide through various dissemination channels (network of startups, IoT evens, etc.).

D6.5 Innovation and Exploitation Planning and Report

The goal of this deliverable is to provide an additional layer for the exploitation management of AGILE and enable exploitation planning. In this second iteration, the focus is put on the exploitation opportunities for each pilot conducted within AGILE to explore avenues for monetization and go-to-market strategies. To build up on the Business Modelling assessment from the first iteration of this deliverable, a stakeholder-based business modelling approach was chosen to define the business model scenarios of the single pilots as archetypes for AGILE exploitation possibilities. The approach defines the stakeholder environment in which the AGILE-driven solutions of the pilots are integrated and then defines which stakeholders could provide revenue to make the solution sustainable and which users would have to cooperate in order for the pilot-specific business models to be sustainable a the targeted market.
The business model solutions were drafted collaboratively in a workshop on the consortium meeting in Q1 2017 and refined afterwards. The initial conclusions from the business modelling exercise and following research show that each pilot has solid exploitation options and a variety of stakeholder that are likely to provide a sustainable inflow of revenue. The diversity of the pilot business models shows how flexibly AGILE can be deployed, without being limited to a specific application or a specific domain.

D7.1 Eclipse IoT Proposal, Developer RFC and Dissemination Activity Planning

This report contains the result from the Eclipse IoT community on creating/embracing a new Eclipse IoT project based on AGILE software components, the outcome of the RFC to developers about the utilization of existing open source components, and finally the plan for dissemination activities to take place (identification of workshops to create/participate, list of additional tentative events for promoting AGILE).

D8.2 Initial Pilot Components Development & Deployment Report

The aim of this deliverable is to report on the development and integration of the hardware and software components for the execution of the pilots, including a description of each pilot architecture and main used cases covered by the implementation. The document includes also an initial version of the deployment plan of each pilot, covering aspects such as the specific scenario, calendar, or main evaluation metrics to consider.

D8.1 Pilot Design and Analysis Requirements and Specification

The aim of this deliverable is to present the results from the analysis of requirements and the design specifications providing a first insight on the utilization and validation of the AGILE solution in the project’s pilots. The cornerstone for the requirements elicitation and the pilots definition has been the early engagement of all the project stakeholders into the pilots execution. The deliverable highlights the initial inputs on pilots and technical deals concerning the components definition and pilot preparation as part of the overall AGILE pilots execution and evaluation methodology.