5G-ROUTES: D2.9 Report on integration and testing of technological enablers for CAM
Creators: name: Guillermo Gomez, Elisa Jimeno
Publisher: name: Zenodo
Year: 2022

description: Being 5G-ROUTES a Phase-3 5G-PPP project, one of its objectives is to provide a practical and novel 5G Platform specialized in the field of Connected and Automated Mobility (CAM) services with emphasis on cross-domain scenarios. Such Platform will serve Use Cases (UCs) as the gate to an underlaying 5G infrastructure, which will be first tested in a controlled laboratory prior to the actual production-grade tests in a field trial. The 5G-ROUTES Platform is a multi-cloud system (core and edge) built as the combination of innovative technological enablers developed within the project to comply with the needs of CAM UCs. Therefore, enablers are to be understood in this project as pieces of software that facilitate an enhancement or new functionality over a 5G Infrastructure. Each enabler will offer and/or produce functionalities from the 5G-ROUTES Platform to the UC Services. The 5GROUTES Platform is the output of Work Package (WP) 2 to successive WPs. WP3 will ensure that enablers provide compatible interfaces with the field trial 5G infrastructure and orchestrator specifications so that UCs are able to proceed with their testing cycles in commercial field trials environments. T2.5 aims at the integration and deployment as well as the validation and testing of a 5G Platform that coordinates the interaction between the set of enablers developed in WP2. It will ensure that enablers are developed to a high standard and that they can all be integrated as a single 5G-ROUTES Platform deployed in a 5G-compatible approach within one of the available testbeds of the project. Functionality of enablers in isolation as well as deployment and connectivity among enablers will be tested in a continuous and automatized process. This document will set the grounds for a seamless integration of the work done by different partners developing the 5G-ROUTES technological enablers, in a way that will make it possible to start the integration of enablers into the Platform as soon as possible and have it work seamlessly for all teams for the duration of their development. By endorsing the different guidelines and procedures that this document holds, WP2 will be able to prove that:  Enablers offer some level of unit and functional testing which in turn relates to the quality of the code, the coverage of testing and the correctness of the most critical features offered.  Enablers offer a virtualization mechanism compatible with a 5G deployment.  The 5G-ROUTES Platform is offered as a 5G-compatible deployment that is tested to work with a 5G Orchestrator. In particular, Containerized Network Functions (CNF) deployed via ETSI Open-Source MANO (OSM) in a testbed environment.  The 5G-ROUTES Platform tests that enablers deployed have network connectivity among each other and that they are deployed to the desired location (core and edge clouds).  The 5G-ROUTES Platform tests that the interfaces of enablers are aligned and that the main functionalities offered to UCs are tested in a dry-run configuration. WP3 will continuously provide insight on the 5G infrastructure available in testbeds and field trials so that enablers can be configured to interface with those systems. The resulting Platform will be afterwards integrated into field infrastructure within WP3 as well, to execute localized and extended trials of the UCs. This document includes a summary of the latest interfaces and artefacts produced by enablers which are used to offer an initial integration and deployment strategy that will be later advanced by T3.3 to adapt the 5G-ROUTES Platform to the field trials. A series of common guidelines will be defined along with a number of resources that will be made available for the teams to use. The most immediate achievement of this document is a collection of development and testing guidelines that will drive the upcoming development of the enablers. The contributions of partners towards enablers will follow an automated validation framework in the form of continuous integration and continuous delivery (CICD) pipelines. Firstly, covering the isolated development and testing, and secondly in a common environment where their communication with other enablers. New features and improvements originated from the interaction between WP2, WP3 and WP4 will be identified and requested to the corresponding partner to include into their enabler. Thus, enabling an early iteration of an enabler’s release to facilitate that UCs are able to meet the KPIs detailed in WP1. Upcoming deliverable from T2.5 (D2.10) due to M36 of the project will report on the final 5G-ROUTES Platform containing a full description of the interactions and capabilities that were tested. The final deployment strategy, configuration and lessons learnt. Enablers will provide the final set of functionalities offered to the Platform and UCs along with the improvements carried out during the different testing cycles in the context of WP2, WP3 and WP4.