Our management deliverables are not publically available.
WP2: Architectural Specification
This report describes the first version of our Use Cases which showcase areas where POINT can be better than existing IP networks. It goes on to specify high level Requirements that our prototype should satisfy and a number of verifiable Key Performance Indicators (KPIs) to measure for each Use Case. Finally, Finally, a detailed (initial) architecture for the POINT platform and a set of Specifications is derived from the KPIs to inform future development.
This document presents the second version in our cycle-driven platform development which follows the same structure as D2.1. The focus on this deliverable is to improve the description and targeting of the scenarios, while refining and expanding the corresponding requirements.
This document focuses on the extensions to the baseline POINT architecture that were included in the Cycle-1 prototype, as well as those planned for inclusion in the Cycle-2 prototype which are advanced enough to warrant their inclusion.
D2.4 presents the final version of the POINT architecture, thus updating D2.3. In addition, it presents the final version of the scenarios, requirements and KPIs, thus also updating D2.2. With respect to the architecture, we describe the extensions to the original FP7 PURSUIT architecture and its network node prototype (Blackadder), as well as the software components that execute on top of that extended network node prototype, reflecting the multiple cycles of development in WP3 and evaluation in WP4. With respect to the scenarios, requirements and KPIs, we present their final versions, reflecting the evaluation in WP4 and the trial planning and setup in WP5.
This Technical Report presents the final version of the POINT architecture and the specifications of the entire POINT system, at the stage of its final software release. It is a unified version of the specifications presented in POINT deliverables D2.3 and D2.4, covering the extensions to the Blackadder prototype made by POINT, the additional components operating on top of the core ICN node, the user-level libraries available to programmers and all the protocols used between the POINT nodes.
This document is the first of three WP3 deliverables describing the progress of platform design and development in POINT. The project is taking an iterative approach that aligns the key WP3 deliverables and milestones with three cycles. This document describes the work completed in Cycle 0 including some of the main components being developed for Cycle 1.
This document marks the delivery of Cycle-1 of the POINT platform and documents this latest evolution of the project. Rather than acting as the documentation itself, this document mainly acts as a guide to the documentation that can be found in the POINT first public release that embodies Cycle-1.
This document marks the delivery of Cycle-2 of the POINT platform and documents this latest evolution of the project. Rather than acting as the documentation itself, this document mainly acts as a guide to the documentation that can be found in the POINT first public release that embodies Cycle-2.
Similar to D3.3, this document is kept intentionally concise, as it mainly acts as a guide to the POINT final public release documentation that can be found on Github. The document also acts as a guide to the documentation of the POINT evaluation tool public release, which can be found on Github. For this, the document provides hyperlinks to the elevant documents in the Github repositories.
In this document the detailed planning of POINT validation and evaluation activities are laid out, and the validation results of the first platform version – the cycle 0 prototype – are given. Further, initial evaluation results are also given that have resulted in design choices and proposals on how to refine the platform during cycle 1.
D4.2 Testbed Design and Setup
This document provides an overview of the design and setup of the various POINT testbed, all of which are used for various development, testing, and evaluation efforts in the project.
Here we present the first evaluation results for the IP-over-ICN framework being developed in the POINT project. These include the first experiences from extensive prototype deployments, the first quantitative and qualitative evaluation results from the Cycle 1 prototype platform described in detail in deliverable D3.2 (which has been publicly released to the community), and additional evaluation results on technologies currently being developed within the project and being considered for further development towards the Cycle 2 prototype. We also present some intermediate results of our ongoing security evaluation work, which seeks to establish what kind of security impact the adoption of our IP-over-ICN architecture would have on network operators and other stakeholders, compared to today’s native IP based networks. In addition to these results, the document also contains an updated evaluation plan given on a per-requirement basis, following the structure of the project goals established in deliverable D2.2.
In this deliverable we present the first system-level evaluation results for the IP-over-ICN framework being developed in the POINT project. Our focus here is in particular on the performance gains an operator can expect from the adoption of IP-over-ICN based technologies, including the impact of network topology, usage of the network, as well as the behaviour of the users.
In this deliverable we present the second collection of system-level evaluation results for the IPover-ICN framework being developed in the POINT project. Our focus here is on reporting detailed results from the various field trials conducted in the project (as described in deliverable D5.3), as well as on additional simulation studies that have been conducted to better understand the benefits the POINT platform can bring to network operators of various kinds.
This document reports on the planned test scenarios to be used in support of the trial evaluation process and describes the planned evaluation methodology. It describes the use cases we will use for the trials and presents initial plans on the foreseen topologies , together with a description of the requirements or limitations of those topologies, to better support the ongoing development activities of WP3.
This document describes the evaluation process of the POINT platform to be performed under real operating conditions. Evaluation methodologies are defined to determine what data should be collected, how they will be collected, and how they will be processed to enable reaching valid conclusions and maximize their value for the improvement of the POINT platform. Finally the two planned trials are described.
This document reports upon the preparation and final design of the field trials with the most recent stable version of the POINT platform. These research activities have uncovered some valuable operational insights for POINT, as well as on its impact on the perceived QoE of users and usability of multimedia services (conventional and emerging).
WP6: Impact Creation
D6.3 POINT Flyer
The first version of our flyer offers early ideas on the benefits of placing POINT software in the network by detailing two use cases – one from the point of view of an operator looking to upgrade their network, and one from a user looking to set up a new live video streaming service.
Our second flyer consolidates a range of benefits of POINT and describes how we are planning on testing and evaluating them throughout the project.
Our third flyer presents the trials which we have carried out during the latter part of the project.
A short report detailing how the POINT consortium will disseminate project achievements, and exploit the outputs.
A short report detailing how the POINT consortium will manage research data.
This Document provides a review of out communication actions throughout the first year of the project.
This Document provides a review of out communication actions throughout the second year of the project.
This report presents the results of our investigation into the business implications and opportunities which will be brought about by a transition to ICN-inspired network solutions which maintain compatibility with current IP networks.