Work packages


The PRISTINE project activities are distributed into seven work packages (WPs), as illustrated in the figure below. The project lifetime has been divided into two iterations, implementing cycles of research, design, implementation and trial of the solutions. Iterations will allow the project to run two complete loops, therefore providing an opportunity for the work packages to provide feedback to each other and to improve their results in the next iteration, taking into account the provided feedback.

Diagram showing the interaction between the different work packages

Diagram showing the interaction between the different work packages

 

WP1 Project Management is responsible for the overall strategic and day-to-day management of the project. It will ensure that all work packages operate in a co-ordinated and coherent manner. It involves various administrative tasks, including time and resource management, progress reporting and organisation of plenary meetings.

WP2 Use cases, requirements analysis and programmable reference architecture. This WP will set the overall framework and scope of the project, and will provide the tools to allow the core technical work packages to perform their work. WP2 will define the project use cases, all of them gravitating around the 3 PRISTINE scenarios: distributed cloud, network service provider and datacenter networking. This WP will also define the project reference architecture, defining the interfaces to the programmable behavior for each of the technological areas addressed in the project (in work packages 3, 4, 5). A core task of this WP is to design and develop a Software Development Kit (SDK) for PRISTINE’s baseline prototype, enabling WPs 3-5 to program their solutions on top of it. Finally, WP2 will also provide a RINA simulator to work packages 3,4 and 5, so that they can evaluate the behavior of their solutions at large scale.

WP3. Programmable performance enhancing functions and protocols. WP3 will design and develop innovative solutions around the areas of aggregate-based congestion control, distributed resource allocation and topological addressing in order to maximize the efficiency of the use of network resources in the three project scenarios. This WP will use the simulator developed by WP2 to evaluate how WP3 designs work at scale, but the main output will be a set of components developed with PRISTINE’s SDK. These components will be implementing WP3 solutions on top of PRISTINE’s baseline prototype.

WP4. Innovative security and reliability enablers. WP4 will design and develop innovative solutions around the areas of authentication, access control, encryption, distributed security coordination, multi-homing and reliability in order to maximize the security and reliability of the networks used in the three project scenarios. As in WP3, this WP will use the simulator developed by WP2 to evaluate how WP4 designs work at scale, but the main output will be a set of components developed with PRISTINE’s SDK. These components will be implementing WP4 solutions on top of PRISTINE’s baseline prototype.

WP5. Multi-layer management plane. WP5 will investigate an effective multi-layer management plane exploiting the commonality provided by the RINA architecture. WP5 will initially formalize the characteristics of the common elements to the RINA management plane, implementing these elements with PRISTINE’s SDK. After that, this common structure will be utilized in designing and implementing multi-layer configuration, performance and security management features within the management plane.

WP6. System-level integration, validation, trials and assessment. The role of this WP is to trial the different use cases and analyze the technical and business impact of PRISTINE’s solution in each one of them. In order to do so, WP6 will first integrate, on a use-case per use-case basis, all the components developed by work packages 3,4 and 5. This integration work will produce three comprehensive solutions for each one of the project scenarios. In parallel to the integration work, WP6 will design and setup three separate infrastructures to conduct the trials for each use case. The trial infrastructure will be formed by a mix of partner’s contributions and existing adequate FIRE facilities. Finally WP6 will conduct the trials, concentrating in the different aspects of each scenario lifecycle, and the result will be analyzed.

WP7. Dissemination, Standardisation, Exploitation aims to promote the project results outside the consortium and represents a core activity. A dissemination plan will be developed to ensure that project results are distributed to a wide audience, maximising the impact of the project, raising awareness for the project results and stimulating interest on PRISTINE. Contribution to standardisation activities is also an important aspect of the project. WP7 will also provide a roadmap for exploitation describing the ways how the results from the project will and could be mapped and used in use-case scenarios and beyond and how their further development is anticipated to proceed after the project.