Up

Deliverables

Public deliverables

Executive Summary

Background

Work Package 5 “Overall platform integration and validation” of UMOBILE project aims at the evaluation of the solutions developed in the project. A proof-of-concept is expected as an outcome of WP5. Task 5.3 “Proof-of-Concept” concerns, indeed, the integration of the architecture and services, derived from results developed in WP3 and WP4, with different components, such as mobile nodes, sensor nodes, backhaul links of different type, Wi-Fi infrastructure/equipment etc. This Report is written in the framework of Task 5.3 “Proof of Concept”.

Objectives

The goal of this document is to provide a description of the integration of UMOBILE system. The UMOBILE devices are defined; the interaction between software modules is described and will be then evaluated through the proof-of-concept software (please refer to D.5.1 “Validation methodology and evaluation report” for the devices evaluation). The proof-of-concept is created on two specific demos: two independent technological demonstrations based on software developed during UMOBILE. The demonstrations rely on two of the use-cases selected in WP2. The proof-of-concept is initially described in this deliverable; then, in M34, the full aspects concerning the proof-of-concept and software availability will be described and reported in D5.4 “Proof-of-Concept (2)”.

D4.5 Report on Data Collection and Inference Models

Executive Summary

Background:

This report is written in the framework of the UMOBILE project WP4 “Services enablement”, task 4.2 “Data Collection and Contextual Inference”. The task dealt with data mining in the networking context. Specifically, the task has worked upon i) devising mechanisms and tools that assist inthe collection of data from sensors and other sources; ii) working on contextual awareness aspects relevant to networking in general, and to UMOBILE in particular; iii) the dissemination of the processed data to other UMOBILE services and modules, to assist in a future optimization of the network operation, based on contextualization.

A relevant aspect worked in this task is the notion of usage contextualization and service personalization. A second relevant aspect concerns the capability to infer roaming behaviour in a way that keeps anonymity and privacy of the user as well as of the device. A third relevant aspect of the task was to understand how to assist UMOBILE, namely, which modules could benefit of such contextualization operation, and what/how to integrate this operation in the UMOBILE architecture. A fourth aspect worked upon in this task concerned derivingrelevant guidelines for the community, based on data collection and experimentation.

For the purpose of contextualization, the task started with ananalysis of UMOBILE requirements and how to best fit such requirements when considering data capture on the network. Operationally, the task startedwitha model derived from the Senception’s product PerSense™

D2.4 System and Network Deployability Design

Executive Summary

This document corresponds to the output of Task 2.3 and covers the full specification for the system, including refined assumptions, requirements, as well as design choices. It shall include technology to be applied from previous/related work, as wellas clearly indicate the contributions to be provided by the UMOBILE system.

The purpose of this document is to ensure that the system and network specification as well as the end-user requirements can meet operational expectations within the UMOBILE time-frame. Focus has been given in analysing how the proposed concepts can be easily deployable based on current and future technology.

Backward compatibility with current IP infrastructures isa central aspect to the deployment of UMOBILE.

D4.4 Set of QoS interfaces and algorithms

Executive summary

Background: This document is the D4.4 deliverable: Set of QoS interfaces and algorithms. D4.4 is due on month 30 (Jul 2017) and is one of the five deliverables included in WP4: Service enablement.

The main objective of WP4 is to enhance UMOBILE architecture by means of the development of mechanisms to provide QoS. These mechanisms will enable the deployment of services with different levels of QoS demands ranging from less-than-besteffort to guaranteed QoS. In this delivery, we contemplate three classes of services: lessthan- best-effort, best-effort and premium.

In pursuit of this aim, these mechanisms are expected to take advantage of the ICN features of the UMOBILE architecture.

The specific objectives of the WP4 are the following:

  • O4.1: To enable services which fully exploit the inherent opportunistic nature of communication.
  • O4.2: To enable the “Internet” experience as many people know it, with applications such as web, email, and the like. The challenge here lies in dealing with the inherent disconnectivity of challenged environments by catering to the network challenges and/or adjusting the expected user experience.
  • O4.3: To develop mechanisms for processing of sensor data through context understanding.
  • O4.4: To provide different levels of QoS depending on the needs of each user/network ranging from less-than-best-effort to guaranteed services.

The outcome of WP4 will be the enablement of services that support the key characteristics of the developed platform: delay-tolerance and content-centricity.

To fulfill these objectives and as part of the activities envisioned by Task 4.1, UCAM, ATHENA (formerly DUTH) and UCL have implemented independently different mechanisms that operate at different levels of the software stack when offering UMOBILE services to users.

In the UMOBILE project, we have defined and developed another set of mechanisms aimed at prioritizing emergency traffic limited in certain areas and time space, called Name-based replication priorities, for opportunistic communications without infrastructure using Device-to-Device communications. However, these QoS mechanisms for opportunistic communications are developed in Task 4.3 and not in Task 4.1 of the WP4 and have already been defined and detailed in D3.1 deliverable [1]. Therefore this document does not include the Name-based replication priorities mechanisms and is focused on QoS mechanisms of UMOBILE services.

The set of QoS mechanisms that this document describes are the following:

  • Application level QoS mechanisms
    • Service Migration Platform (SM)
  • Network level QoS mechanisms
    • Delay-Tolerant Framework (DTN)
    • Flowlet Congestion Control (INRPP).

These mechanisms have been implemented to operate independently in the sense that they use their own algorithms to address QoS requirements. However, they can also be integrated to operate in collaboration mode offering a unified approach towards QoS. Their collaboration is highly desirable in applications that involve QoS parameters that are visible and amenable to manipulation at different levels of the software stack. In account of potential integration, we have built interfaces that a designer can use to integrate one with another.

D4.2 Flowlet Congestion Control - Final Report

Executive Summary

This deliverable (D4.2) is part of the five produced deliverables by WP4 that deal with QoS. In WP4 we address the challenges of QoS with congestion control mechanisms that enhance QoS by means of avoiding congestion problems that might result in packet loss, latency and low throughput. The UMOBILE project devises different mechanisms to provide QoS to users. In the task 4.1, and described in D4.4 [1], we developed a set of mechanisms including service migration, congestion control and delay-tolerant mechanisms.

In this document we define the specifications of the new flowlet congestion control called In-Network Resource Pooling Protocol (INRPP), outcome of the UMOBILE project. D4.1 [2] discusses the first version of a congestion control protocol that addresses congestion control in TCP/IP networks, and in D4.2 we define the specifications of the flowlet congestion control INRPP over NDN networks, that will be integrated in UMOBILE networks, as specified in D4.4, to provide QoS.

In D4.2 we also a discussion about how we achieve the design issues identified in D4.1. A broad performance evaluation through simulations to assess the INRPP mechanisms and to quantify the improvement of INRPP over other congestion control protocols will be included in D5.2 (second validation methodology and evaluation report).

D4.2 is based on deliverables D2.1[3], D2.3[4], D3.2[5] and D3.4[6]. Deliverables D2.1 and D2.3 describe the requirements of the end-user and the system, respectively. On the other hand, D3.2 and D3.4 cover the UMOBILE architecture.

  • The methodology used in this deliverable is as follows:
  • We identify congestion control limitations that can be improved using in- network resources.
  • We analyse existing work for congestion control in NDN networks.
  • We detail a set of mechanisms required for the INRPP to implement the new congestion control over NDN networks

The document is organized as follows: Section 1 introduces core concepts of flowlets congestion control over UMOBILE framework. Section 2 presents the related work of congestion control in ICN networks. Section 3, provides details of INRPP flowlet congestion control design. In Section 4, we argue how we deal the INRPP implementation issues identified in D4.1 for the UMOBILE project. Finally, in the Conclusion section we summarize our findings and discuss open questions that we are currently addressing.

D3.2. UMOBILE architecture report (2)

Executive Summary

Background: This report is written within the framework of the UMOBILE project WP3 “System and node architecture development”. The deliverable aims to describe the final UMOBILE architecture, accompanied by the implementation of the architecture and documentation on the code.

Objectives: The core activity of WP3 is the design and implementation of the UMOBILE platform. Departing from the existing properties of ICN, DTN and opportunistic networking, we establish an architectural framework that extends connectivity options by being delay-tolerant and by exposing a common information-centric abstraction to applications.

UMOBILE aims to advance networking technologies and architectures towards the conception and realization of Future Internet. In particular, UMOBILE extends Internet (i) functionally – by combining ICN and DTN technologies within a new architecture, (ii) geographically – by allowing for internetworking on demand over remote and isolated areas – and (iii) socially – by allowing low-cost access and free user-to-user networking. The basis for UMOBILE platform is the Named Data Networking (NDN) architecture, one of the most promising ICN implementations, and UMOBILE features are being built in line with NDN. The result is a novel architecture that allows for new services and applications.

The goal of this document is to provide a detailed description, along with a manual when applicable, of the new features, mechanisms and applications that have been developed as part of the UMOBILE architecture. The code that we have implemented is also discussed and made available from the UMOBILE project public GitHub repository.

In the rest of the document, we present our vision and provide the full architectural picture, as well as the specific modules and their interconnections.

D3.4 UMOBILE ICN layer abstraction final specification

Executive Summary

This document covers the UMOBILE architecture, as well as UMOBILE services that apply to scenarios detailed in D2.1 (End-user requirements report), for the specification of the UMOBILE architecture. This document incorporates the final and refined version of the UMOBILE architecture high-level specification that was initially defined in D3.3 (UMOBILE ICN layer abstraction initial specification) [1].

The goal of this document is to provide a high-level description of the overall specification of the UMOBILE architecture. Special attention is given to the necessary alignment with the Delay-Tolerant Networking (DTN) architecture [2], and the most relevant proposal for an Information-Centric Networking (ICN) architecture [3] that fits the identified UMOBILE system and network requirements. The specification provided here drives the development and implementation of the UMOBILE architecture, which is described in detail in deliverable D3.1 [4] and D3.2 [5] “UMOBILE architecture report 1 and 2” (e.g. core platform, API, protocols, software).

The starting point for this report are deliverables D2.1 “End-user requirements report” [6], D2.2 “Systems and network requirements report (initial version)” [7] and D2.3 “Systems and network requirements report (final version)” [8], which describes typical accessibility scenarios in different environments, namely, urban, remote and disaster areas, as well as requirements from the end-user (D2.1) and the network and system (D2.2 and D2.3) perspective, that the UMOBILE platform will support. The UMOBILE architecture specification, provided in this document, is complemented by the following deliverables:

a) D3.2 [5] with a detailed specification of the UMOBILE architecture and the implementation of it.

b) D4.1 [9] and D4.2 [10]with a detailed specification of the proposed flow control and rate-regulation scheme for UMOBILE.

c) D4.3 [11] with a detailed specification of the proposed mobile name-based replication scheme aimed at improving certain services by using priorities.

d) D4.4 [12] with a detailed specification of the different supported services and the QoS mechanisms in the UMOBILE project.

e) D4.5 [13] with a detailed specification about sensing data collection and users’ behaviour inference.

The methodology used in this deliverable is as follows:

a) Start from the applicability pictures identified in D2.1 and derive application services that must be implemented using the UMOBILE architecture.

b) Identify the network services required for the services previously detailed.

c) Describe the high-level design of UMOBILE architecture based on the overall assumptions and requirements described in D2.3, as well as the capabilities provided by the selected DTN and ICN architectures.

d) Detail the different modules and describe the full specification of the UMOBILE ICN layer abstraction architecture, highlighting the components that need to be further described in D3.2, D4.1/D4.2, D4.3, D4.4 and D4.5

D2.3 System and Network Requirements Specification

Executive Summary

This document covers system and network requirements (described based on RFC2119 notation), as well as assumptions, for the high-level design of the UMOBILE architecture. A first version is provided on M18, as deliverable D2.2, while a refined description of system requirements, assumptions will be provided on M28 (initially planned for M30), as deliverable D2.3.

The goal of the current deliverable, D2.3, is to describe the final set of requirements and assumptions of the UMOBILE framework, which is being developed based on the analysis of the four applicability pictures described in D2.1 [1], and the initial set of requirements and assumptions set in D2.2 [2].

Special attention is given to the needed alignment with the Delay-Tolerant Networking (DTN) architecture [3], and the most relevant proposal for an information-centric networking architecture (ICN) [4] that fits the identified UMOBILE system and the network requirements.

The starting point for this report is deliverable D2.2, which describes the initial set of requirements and assumptions for the project. Deliverable D2.3 aims to revise that initial set of requirements and assumptions, to reflect the strategic and development decisions that were taken during the project.

D4.3 Name-based Replication Priorities

Executive Summary

This deliverable (D4.3) summarizes the work developed in WP4 (Services Enablement, month 6 to month 30), task 4.3 (Name-based replication priorities, month 6 to month 24).

The main objective of WP4 is to enhance UMOBILE architecture in terms of QoS and QoE and enable solutions that take advantage of the unique features of the developed architecture. This WP will use the architecture developed during WP3 to provide a set of services. Hence, the outcome of WP4 is the enablement of services that support the key characteristics of the developed platform, such as the provision of multiple QoS levels and the collection, processing and dissemination of different types of data.

The main goal of task 4.3 was to develop mechanisms that assist the UMOBILE architecture in supporting a mobile name-based replication system, where message replication is limited by time and space, that is, within a certain geographic area and with specific life expectancy. As starting point in the task, replication optimization was based on prioritization rules expected to be integrated within the information message’s name to favor spreading of the most important messages. This prioritization rules will include as well some social parameters in order to select first the best node to replicate the information.

The focus was on cases where Internet access is intermittent (mobile infrastructure may not always be accessible) or missing and therefore messages would have to be stored, carried, as well as forwarded via mobile nodes.

Deliverables related with this deliverable are deliverables D2.1 and D2.2, which describe the requirements from the end-user (D2.1) and the system (D2.2) perspective; deliverables D3.1 and D3.3 which describe the UMOBILE architecture.

The deliverable is organized as follows: Section 1. gives a brief introduction on the topic of name-based replication, motivation and goals of this task. Section 2 presents background work on data and content replication, focusing on social-aware approaches and describing in detail UMOBILE NREP. Section 3 concerns device-to-device communication and information-centric aspects, focusing on direct communication between end-user devices based on Wi-Fi direct, as this is the technology considered in UMOBILE. Section 4 presents the NREP adaptation in UMOBILE. Section 5 provides the validation carried out via discrete event simulations. Section 6 concludes this deliverable.

D5.1 Validation methodology and evaluation report

Executive Summary

Background

Work Package 5 “Overall platform integration and validation” of UMOBILE project evaluates the solutions developed in the project. This Report is written in the framework of Tasks 5.1 “Definition of the validation of the setup” and 5.2: “Evaluation through Simulation and Emulation” of UMOBILE project. These two tasks aim to validate the architecture and services, derived from results developed in WP3 and WP4.

The ultimate objective of UMOBILE is to advance networking technologies and architectures towards the conception and realization of Future Internet. In particular, UMOBILE extends Internet (i) functionally – by combining ICN and DTN technologies within a new architecture -, (ii) geographically – by allowing for internetworking on demand over remote and isolated areas – and (iii) socially – by allowing low-cost access to users but also free user-to-user networking.

Objectives

This document focuses on the description of the UMOBILE system components from a functional point of view. Furthermore, this deliverable presents the validation setup of the overall system. This entails defining the setup and assets involved in the validation scenarios, use cases, operational and environmental conditions, measures of performance, and measures of effectiveness. There will be both component and system-level validations. The platform is also evaluated through a series of planned simulations and emulations.

D6.4 Exploitation Plan

Executive Summary

Background: This Report is written in the framework of Task 6.2 “Exploitation” of UMOBILE project.

The ultimate objective of UMOBILE is to advance networking technologies and architectures towards the conception and realization of Future Internet. In particular, UMOBILE extends Internet

  • functionally, by combining ICN and DTN technologies within a new architecture,
  • geographically, by allowing for internetworking on demand over remote and isolated areas
  • socially, by allowing low-cost access to users but also free user-to-user networking.

Objectives: This document is aimed at providing a clear description of the plan through which the project results will be effectively exploited up to and after its ending date. In fact, the consortium partners firmly believe that each activity of the project should be executed with a clear focus on the possibility to use the arising results.

D6.2 Dissemination Report (1)

Executive Summary

As stated in the DoW (Description of Work), the objectives of the UMOBILE work package 6 “Dissemination, exploitation and standardisation”, related to the dissemination activities, are: 

  • To widely disseminate the project concept, developments and findings to all key actors in the field in an interactive way, integrating their feedback at key points of the specification, design, development and evaluation work.
  • To develop a project dissemination and communication strategy.
  • To develop an user friendly website to inform the general public and relevant stakeholders about the project.
  • To organize and/or publish results in international conferences and workshops to inform the scientific community about the project, its goals and achievements and to gather valuable information on related issues.

Through this dissemination report, WP6 intends to inform about the achievement of the mentioned goals.

The document reports information on all the dissemination actions till July 31st, 2016. All meeting agendas, presentations and number of participants are included.

D4.1 Flowlet Congestion Control – Initial Report

Executive Summary

This deliverable (D4.1) is the first out of five to be produced by WP4 to deal with QoS. In WP4 we address the challenges of QoS with congestion control mechanisms that enhance QoS by means of avoiding congestion problems that might result in packet loss, latency and low throughput.

The UMOBILE project devises interactions between two different domains:

  • The UMOBILE Domain which is a local network running the UMOBILE protocols (e.g., NDN, DTN). Providing the Internet access in this domain is optional as UMOBILE users can access the local services through public hotspot (e.g., WiFi AP) or WiFi direct (e.g., direct connection among users).
  • The Internet Domain is the conventional TCP/IP Internet and is an extension of the UMOBILE Domain where UMOBILE users (running either TCP/IP, NDN or DTN protocols) can access Internet services. For instance, as shown in the figure, the UMOBILE network can have a proxy or gateway running TCP/IP in order to connect to the Internet.

D4.1 discusses the first version of a congestion control protocol, called In-Network Resource Pooling Protocol (INRPP) that addresses congestion control in TCP/IP networks. It extensively covers the specifications for a Flowlet Congestion Control to be used in the Internet Domain. In addition, we introduce a preliminary discussion of the development of the Flowlet Congestion Control to be used in the UMOBILE Domain. The final version of the protocol will be discussed in D4.2.

In D4.1 we also provides a broad performance evaluation through simulations to assess the INRPP mechanisms and to quantify the improvement of INRPP over other congestion control protocols.

D4.1 is based on deliverables D2.1, D2.2, D3.1 and D3.3. Deliverables D2.1 and D2.2 describe the requirements of the end-user and the system, respectively. On the other hand, D3.1 and D3.3 cover the UMOBILE architecture. The methodology used in this deliverable is as follows:

  • We identify congestion control limitations that can be improved using innetwork resources.
  • We detail a set of mechanisms required for the INRPP to implement the new congestion control over TCP/IP networks
  • We provide an extensive evaluation of the INRPP congestion control approach
  • We describe the next steps for an implementation of the INRPP congestion control over NDN-based networks that can be extended to the UMOBILE Domain.
D1.3 Project Management Reports (1)

Executive Summary

Background: This report is written in the framework of Tasks 1.2. “Project Administration” and 1.3 “Periodic Management Reports” of UMOBILE project and summarizes the management activities that took place during the first reporting period of the project (February 2015-July 2016). It also presents the key issues addressed in the project, achievements and open issues.

Objectives: The aim of this report is to inform about UMOBILE management procedures and activities that took place from the beginning of the project till the end of the 1st reporting period, July 2016. Deviations from project plan and open issues are also presented.

Results and implications: Full report of management activities and proposed changes to the workplan. It must be noticed that this report express only the authors’ views -the European Commission is not liable for any use that may be made of the information contained therein.

D3.1 - UMOBILE architecture report (1)

Executive Summary

Background:This report is written in the framework of Task 3.1 “DTN overlay design and convergence layers for underlying protocols” of UMOBILE project. The deliverable aims to describe work on the UMOBILE core architecture and is accompanied by the implementation of the architecture so far and documentation on the code.

Objectives: The core activity of WP3 is the design and implementation of the UMOBILE platform. Departing from the existing properties of DTN and ICN, we establish an architectural framework that extends connectivity options by being delay-tolerant and exposing a common information-centric abstraction to applications. UMOBILE aims to advance networking technologies and architectures towards the conception and realization of Future Internet. In particular, UMOBILE extends Internet (i) functionally – by combining ICN and DTN technologies within a new architecture, (ii) geographically – by allowing for internetworking on demand over remote and isolated areas – and (iii) socially – by allowing low-cost access and free user-to-user networking. The goal of this document is to provide a detailed description, along with a manual when applicable, of the new features, mechanisms and applications that have been developed so far as part of the UMOBILE architecture. Implementation code so far is also provided. The basis for UMOBILE platform is the Named Data Networking (NDN) architecture, one of the most promising ICN implementations, and UMOBILE features are being built in line with NDN. In this deliverable:

1. We first describe the UMOBILE vision and highlight our contributions in each part of the architecture,

2. We then focus on the specific features that we have designed as part of UMOBILE and

3. We conclude with a clear description of the next steps that the consortium will follow to achieve the integration of all components and the extensive evaluation of UMOBILE platform.

 

D2.2 System and Network Requirements Specification

Executive Summary

This document covers system and network requirements (described based on RFC2119 notation), as well as assumptions, for the high-level design of the UMOBILE architecture. A first version is provided on M18, while a refined description of system requirements, assumptions will be provided on M30, as deliverable D2.3.

The final goal is to identify the overall requirements and assumptions of the UMOBILE framework, which will be devised based on the detailed analysis of the four applicability pictures described in D2.1. Special attention is given to the needed alignment with the Delay-Tolerant Networking (DTN) architecture, and the most relevant proposal for an information-centric networking architecture (ICN) that fits the identified UMOBILE system and the network requirements.

The starting point for this report is deliverable D2.1, which describes typical accessibility scenarios in different environments, namely, urban, remote and disaster areas, as well as requirements from the end-user perspective.

The methodology used to devise deliverable D2.2 is as follows:

  • Derive the system and network requirements from the applicability scenarios identified in D2.1, and, then,
  • Identity the overall system requirements and assumptions that will drive UMOBILE functionality in any of the identified applicability pictures.
D3.3. UMOBILE ICN layer abstraction initial specification

Executive Summary

This document covers the UMOBILE architecture ICN layer specification, as well as UMOBILE services, for the specification of the UMOBILE architecture.

The final goal of this document is to provide a detailed description of the overall specification of the UMOBILE architecture. Special attention is given to the needed alignment with the Delay-Tolerant Network (DTN) architecture and the most relevant proposal for an information-centric network architecture (ICN) that fits the identified UMOBILE system and network requirements. The provided specification drives the development and implementation of the UMOBILE architecture.

D6.6. Standardization Plan

Executive Summary

The deliverable envisions UMOBILE’s main objectives in terms of standardization activities in the area of contributions and co-operation with various standardization bodies.

UMOBILE aims to advance networking technologies and architectures towards the conception and realization of Future Internet. In particular, UMOBILE extends Internet (i) functionally – by combining ICN and DTN technologies within a new architecture, (ii) geographically – by allowing for internetworking on demand over remote and isolated areas – and (iii) socially – by allowing low-cost access to users but also free user-to-user networking as well as to promote user-centric networking in all its aspects.

The UMOBILE project has identified a set of relevant standardization bodies, mostly focused on the ICN, DTN and global Internet fields, that will be monitored to guarantee the alignment of the UMOBILE solution with the latest standards and to identify potential contributions to the ongoing standardization activities.

D1.2 External Liaison Overview

Executive Summary

This report describes Liaison within and outside of the H2020 Programme. The report is divided into seven sections. Section 1 describes UMOBILE Project and liaison targets with other projects and bodies. Section 2 presents related projects funded by FP7 and Horizon 2020, whereas Section 3 presents related national and other projects. Relevant organization and standardization bodies to UMOBILE can be found in Section 4. Liaison planning with local authorities is analysed in Section 5.

D.6.10. Data Management Plan

Executive Summary

Open Access Model garantees free access for users and free dissemination of knowledge. UMOBILE participates in the "Pilot on Open Research in HORIZON 2020": participating projects are required to develop a Data Management Plan (DMP), in which they specify what data will be open.

This Data Management Plan explains which of the research data generated in UMOBILE will be made open, how data will be shared and which procedures will be put in place for long-term preservation of the data.

Following "Guidelines on Data Management in Horizon 2020", the DMP clarifies that scientific generated research data will be easily:

  1. Discoverable
  2. Accessible
  3. Assessable and intelligible
  4. Useable beyond the original purpose for which it was collected Interoperable to specific quality standards
 

Partners

Athena
 
UCL
 
 UCam
 
Copelabs
 
Tecnalia
 
Tekever
 
Senception
 
Fon
 
AFA Systems