{ "access": { "embargo": { "active": false, "reason": null }, "files": "public", "record": "public", "status": "open" }, "created": "2020-01-23T11:53:56.965224+00:00", "custom_fields": {}, "deletion_status": { "is_deleted": false, "status": "P" }, "files": { "count": 1, "enabled": true, "entries": { "5geve_d3.2-interworking-reference-model.pdf": { "checksum": "md5:6150f61a9bb954bbb62d4b245a5f64b7", "ext": "pdf", "id": "962f59cb-5186-4e4d-bc65-8a0ab1953c29", "key": "5geve_d3.2-interworking-reference-model.pdf", "metadata": null, "mimetype": "application/pdf", "size": 4140917 } }, "order": [], "total_bytes": 4140917 }, "id": "3625689", "is_draft": false, "is_published": true, "links": { "access": "https://zenodo.org/api/records/3625689/access", "access_links": "https://zenodo.org/api/records/3625689/access/links", "access_request": "https://zenodo.org/api/records/3625689/access/request", "access_users": "https://zenodo.org/api/records/3625689/access/users", "archive": "https://zenodo.org/api/records/3625689/files-archive", "archive_media": "https://zenodo.org/api/records/3625689/media-files-archive", "communities": "https://zenodo.org/api/records/3625689/communities", "communities-suggestions": "https://zenodo.org/api/records/3625689/communities-suggestions", "doi": "https://doi.org/10.5281/zenodo.3625689", "draft": "https://zenodo.org/api/records/3625689/draft", "files": "https://zenodo.org/api/records/3625689/files", "latest": "https://zenodo.org/api/records/3625689/versions/latest", "latest_html": "https://zenodo.org/records/3625689/latest", "media_files": "https://zenodo.org/api/records/3625689/media-files", "parent": "https://zenodo.org/api/records/3625688", "parent_doi": "https://zenodo.org/doi/10.5281/zenodo.3625688", "parent_html": "https://zenodo.org/records/3625688", "requests": "https://zenodo.org/api/records/3625689/requests", "reserve_doi": "https://zenodo.org/api/records/3625689/draft/pids/doi", "self": "https://zenodo.org/api/records/3625689", "self_doi": "https://zenodo.org/doi/10.5281/zenodo.3625689", "self_html": "https://zenodo.org/records/3625689", "self_iiif_manifest": "https://zenodo.org/api/iiif/record:3625689/manifest", "self_iiif_sequence": "https://zenodo.org/api/iiif/record:3625689/sequence/default", "versions": "https://zenodo.org/api/records/3625689/versions" }, "media_files": { "count": 0, "enabled": false, "entries": {}, "order": [], "total_bytes": 0 }, "metadata": { "creators": [ { "affiliations": [ { "name": "Telef\u00f3nica Investigaci\u00f3n y Desarrollo" } ], "person_or_org": { "family_name": "Lourdes Luque Cant\u00f3", "name": "Lourdes Luque Cant\u00f3", "type": "personal" } }, { "affiliations": [ { "name": "Telef\u00f3nica Investigaci\u00f3n y Desarrollo" } ], "person_or_org": { "family_name": "Luis Miguel Contreras", "name": "Luis Miguel Contreras", "type": "personal" } }, { "affiliations": [ { "name": "Telef\u00f3nica Investigaci\u00f3n y Desarrollo" } ], "person_or_org": { "family_name": "Juan Rodr\u00edguez", "name": "Juan Rodr\u00edguez", "type": "personal" } }, { "affiliations": [ { "name": "NEXTWORKS S.r.l." } ], "person_or_org": { "family_name": "Giacomo Bernini", "name": "Giacomo Bernini", "type": "personal" } }, { "affiliations": [ { "name": "Ericsson Espa\u00f1a S.A" } ], "person_or_org": { "family_name": "Marc Molla", "name": "Marc Molla", "type": "personal" } }, { "affiliations": [ { "name": "B-COM" } ], "person_or_org": { "family_name": "Sergio Morant", "name": "Sergio Morant", "type": "personal" } }, { "affiliations": [ { "name": "Telecom Italia" } ], "person_or_org": { "family_name": "Fabrizio Moggio", "name": "Fabrizio Moggio", "type": "personal" } }, { "affiliations": [ { "name": "Telecom Italia" } ], "person_or_org": { "family_name": "Carmen Catalano", "name": "Carmen Catalano", "type": "personal" } }, { "affiliations": [ { "name": "Consorzio Nazionale Interuniversitario per le Telecomunicazioni" } ], "person_or_org": { "family_name": "Nicola Blefari", "name": "Nicola Blefari", "type": "personal" } }, { "affiliations": [ { "name": "Consorzio Nazionale Interuniversitario per le Telecomunicazioni" } ], "person_or_org": { "family_name": "Mauro Femminella", "name": "Mauro Femminella", "type": "personal" } }, { "affiliations": [ { "name": "Consorzio Nazionale Interuniversitario per le Telecomunicazioni" } ], "person_or_org": { "family_name": "Paolo Lungaroni", "name": "Paolo Lungaroni", "type": "personal" } }, { "affiliations": [ { "name": "Consorzio Nazionale Interuniversitario per le Telecomunicazioni" } ], "person_or_org": { "family_name": "Matteo Pergolesi", "name": "Matteo Pergolesi", "type": "personal" } }, { "affiliations": [ { "name": "Consorzio Nazionale Interuniversitario per le Telecomunicazioni" } ], "person_or_org": { "family_name": "Gianluca Reali", "name": "Gianluca Reali", "type": "personal" } }, { "affiliations": [ { "name": "Consorzio Nazionale Interuniversitario per le Telecomunicazioni" } ], "person_or_org": { "family_name": "Stefano Salsano", "name": "Stefano Salsano", "type": "personal" } }, { "affiliations": [ { "name": "Telcaria Ideas S.L." } ], "person_or_org": { "family_name": "Ram\u00f3n P\u00e9rez", "name": "Ram\u00f3n P\u00e9rez", "type": "personal" } }, { "affiliations": [ { "name": "Telcaria Ideas S.L." } ], "person_or_org": { "family_name": "Aitor Zabala", "name": "Aitor Zabala", "type": "personal" } }, { "affiliations": [ { "name": "ORANGE POLSKA SPOLKA AKCYJNA" } ], "person_or_org": { "family_name": "Michal Chabiera", "name": "Michal Chabiera", "type": "personal" } }, { "affiliations": [ { "name": "ORANGE POLSKA SPOLKA AKCYJNA" } ], "person_or_org": { "family_name": "Grzegorz Panek", "name": "Grzegorz Panek", "type": "personal" } }, { "affiliations": [ { "name": "B-COM" } ], "person_or_org": { "family_name": "Cao Phan", "name": "Cao Phan", "type": "personal" } }, { "affiliations": [ { "name": "B-COM" } ], "person_or_org": { "family_name": "Cao Phan", "name": "Cao Phan", "type": "personal" } }, { "affiliations": [ { "name": "B-COM" } ], "person_or_org": { "family_name": "Rabah Guedrez", "name": "Rabah Guedrez", "type": "personal" } }, { "affiliations": [ { "name": "B-COM" } ], "person_or_org": { "family_name": "Sergio Morant", "name": "Sergio Morant", "type": "personal" } } ], "description": "
Experimenters from Verticals willing to execute an experiment on top of the 5G EVE infrastructure will be able to interact with 5G EVE Experimentation Portal in order to completely define their interests and requirements. However, it is not the Portal the component that directly interacts with the elements at the different sites to deploy such experiment, or modify the testing conditions after different repetitions, for example. That component is the 5G EVE Interworking (I/W) Layer, which provides the required abstraction to permit the Portal not to be aware of the different underlying technologies, and to permit the parallel evolution of the different sites without affecting our single and common frontend for Verticals.
\nThe present D3.2 document, Interworking Reference Model, is the specification of the Interworking Framework for 5G EVE, further developing the initial specification provided in Deliverable D3.1 (Interworking Capability Definition and Gap Analysis).
\nThe foundations of the architecture have not been changed. The proposed I/W Framework is composed of five modules, with the following summarized functionalities:
\n• The Multi-Site Network Service Orchestrator (NSO), Multi-site Catalogue and Multi-site Inventory are responsible for the management of the lifecycle of the deployed components, jointly allowing for multi-site slices supporting Verticals’ experiments.
\n• The Data Collection Manager collects the required performance metrics to ensure the correct operation of the infrastructure and to validate the targeted KPIs.
\n• The Runtime Configurator applies the required runtime configurations to the provisioned services.
\nIn this document, a detailed description of the features required to those five modules is provided, together with the specifications of north-bound and south-bound reference points allowing for the envisioned interactions. In that sense, the Interworking API or NBI (North-Bound Interface) allows for the communication with the Experimentation Portal, while the Adaptation Layer or SBI (South-Bound Interface) is the one abstracting the heterogeneous site capabilities. Both interfaces have been defined for the Data Collection Manager, the Runtime Configurator and the Multi-site NSO. However, the Multi-site Catalogue and Inventory will only interact with the sites using the Multi-site Orchestrator as a proxy. The reason is that we can leverage on features already supported by available orchestrators to simplify the Adaptation Layer.
\nA very important decision, valid for the first release of the I/W Framework, is that only the local NFVO components will be exposed to the Multi-site Orchestrator. This means that local orchestrators will maintain the direct control over the local infrastructure, with other local components like the VIM or the SDN controller not exposed directly to the upper layers. This approach can be revisited in future versions of the I/W Framework, depending on new interworking requirements. In any case, we have also accounted for the possibility of any site deploying an additional SDN controller, for example for the WAN, in which case it should be possible for the I/W Framework to interact directly with it via the WIM.
\nThe biggest complexity, however, comes from the wide range of components which could be targeted by the Runtime Configurator and the Data Collection Manager. The amount of software drivers to be implemented in the I/W Layer will depend on the number of Vertical experiments, the complexity of those experiments in terms of number of required VNFs or PNFs, the tools that are available in the different sites, the vendors providing those tools, etc. Although some level of harmonization will be sought in the project as a whole, the I/W Layer will have to be deal with a very heterogeneous environment, therefore subject to interoperability issues.
\nFrom the design point of view, it is not realistic to try and define an SBI valid for all the uses cases. Therefore, for these components, we will follow an approach based on continuous integration of new features, starting from the ones required by the Verticals participating on 5G EVE, and building on top of those as new requirements appear.
\nAnother design decision taken to minimize integrations is to rely on standards whenever these are available, even in a very preliminary stage. That should guarantee the design being future-proof, leveraging on subsequent industry implementations, and also opens the possibility to contribute on the standards that need extensions. For
\n5G EVE (H2020-ICT-17-2018)
\nDeliverable D3.1 Page 16 / 124
\nthat purpose, the work on D3.2 began with a State of the Art covering the main references regarding NFV, network slicing and SDN control. That study was complemented with a detailed analysis of other European projects dealing with concepts similar to those of 5G EVE. The main goal was to understand what results were reusable from these projects, and where we needed to put the main focus for new implementations.
\nThe first conclusion was the confirmation that, until 5G EVE, there had not been an effort to build a system allowing for multi-site Vertical experimentation across such a complex and heterogeneous environment. Therefore, all the adoptions made in 5G EVE will have to be carefully assessed, as they most probably will not be valid straight away. The second conclusion was that if there is a component that has not been sufficiently tackled yet is precisely the Runtime Configurator, for the reasons mentioned above.
\nApart from a technical description of the I/W Framework itself, the document also describes the services it will offer to the Verticals, in line with the ongoing work in WP1.
\nIn the first stage, experiments will only be deployed in a single site, so the I/W Framework will be able to support single-site Applications Deployment, Experiment Monitoring and Network Automation, the latter to build the required connectivity services (e.g., a VLAN or a VxLAN tunnel) among the deployed components. In the second phase, the I/W Framework will be upgraded with additional capabilities, like the multi-site E2E Orchestration and extended Experiment Monitoring. The E2E Orchestration feature includes the capability to deploy multi-site slices, and VNFs on top of them, across all the sites participating in a given experiment.
\nEven with all these considerations, experiments will only be possible in 5G EVE with the deployment of an underlying connectivity supporting the identified requirements. The first part of the activity, the requirements definition, was already included in D3.1; in D3.2, we have complemented the analysis by studying all the technical possibilities to achieve this connectivity in the different communication Planes (orchestration, control and data). Although the final implementation decision corresponds to WP2, a proposal is outlined here aiming at securing compliance with the needs of the I/W Layer in the Orchestration Plane: a star-based topology, with the I/W Framework components located in the hub, placed in the Turin site to minimize the delay. The technical implementation would be based on IPSec VPN tunnels, and an addressing scheme should have to be agreed among all the sites to avoid duplications.
\nWe have also defined additional services or functionalities required from the 5G EVE site facilities, some of them fundamental to ensure the correct operation, and others to provide added value to the Verticals. An example of the first ones is the adoption of appropriate security measures, even more importantly, taking into account the multi-site characteristic of the 5G EVE environment. Therefore, items like hardening of the infrastructure, authentication in the Orchestration Plane, firewalling, filtering, etc., are discussed. On the other hand, the necessity of services like the remote access for Vertical to their deployed VNFs, or the availability of a ticketing tool even in scenarios as automated as 5G EVE, has also been included.
\nFinally, another objective of the document is to define the requirements or capabilities that WP3 is imposing to 5G EVE sites that want to participate of the interworking solution that will be developed. And more specifically, a list of requirements for the site hosting the I/W Layer has been identified, together with some considerations in case new sites wanted to join the 5G EVE ecosystem.
\nBeyond the obvious need to make available the required compute capacity to actually install all the software modules forming the I/W Framework, the central site will have to consider topics like the required encryption capability to ensure correct communications across the star, the operational costs (updates, troubleshooting, bug resolution, resolution of physical impairments…), the capability to monitor the status of all the Orchestration Layer components from the hub, or the potential availability of mirror platforms which can be used for preliminary testing without affecting the system in production.
Accepting results of projects of the 5G PPP initiative
\r\n", "page": "The 5G Infrastructure Public Private Partnership (5G PPP) is a joint initiative between the European Commission and European ICT industry (ICT manufacturers, telecommunications operators, service providers, SMEs and researcher Institutions). The 5G PPP will deliver solutions, architectures, technologies and standards for the ubiquitous next generation communication infrastructures of the coming decade. The challenge for the 5G Public Private Partnership (5G PPP) is to secure Europe’s leadership in the particular areas where Europe is strong or where there is potential for creating new markets such as smart cities, e-health, intelligent transport, education or entertainment & media. The 5G PPP initiative will reinforce the European industry to successfully compete on global markets and open new innovation opportunities. It will “open a platform that helps us reach our common goal to maintain and strengthen the global technological lead”.
", "title": "5G Infrastructure Public-Private-Partnership" }, "revision_id": 0, "slug": "5g-ppp", "updated": "2021-01-13T16:28:05.551520+00:00" }, { "access": { "member_policy": "open", "members_visibility": "restricted", "record_policy": "open", "review_policy": "closed", "visibility": "public" }, "children": { "allow": true }, "created": "2022-11-23T15:53:29.436323+00:00", "custom_fields": {}, "deletion_status": { "is_deleted": false, "status": "P" }, "id": "f0a8b890-f97a-4eb2-9eac-8b8a712d3a6c", "links": {}, "metadata": { "curation_policy": "The EU Open Research Repository serves as a repository for research outputs (data, software, posters, presentations, publications, etc) which have been funded under an EU research funding programme such as Horizon Europe, Euratom or earlier Framework Programmes.
\nThe community is managed by CERN on behalf of the European Commission.
\nZenodo’s general policies and Terms of Use apply to all content.
\nThe EU Open Research Repository accepts all digital research objects which is a research output stemming from one of EU’s research and innovation funding programmes. The funding programmes currently include:
\nHorizon Europe (including ERC, MSCA), earlier Framework Programmes (eg Horizon 2020) as well as Euratom.
\nIn line with the principle as open as possible, as closed as necessary both public and restricted content is accepted. See note on how Zenodo handles restricted content.
\nEU programme beneficiaries are eligible to submit content to the community. The community supports three types of content submissions:
\nSubmission via an EU Project Community (through user interface or programmatic APIs).
\nSubmission directly to the EU Open Research Repository.
\nAutomated harvesting from existing Zenodo content.
\nA representative of an EU project may request an EU Project Community and invite other project participants as members of the community. The project community is linked to one or more European Commission grants. All records in the project community are automatically integrated into the EU Open Research Repository immediately upon acceptance into the project community.
\nAny user may submit a record directly to the EU Open Research Repository. The submission will be moderated by Zenodo staff for compliance with the minimal required metadata requirements and its correctness.
\nRecords found among Zenodo’s existing content will on a regular basis automatically be integrated if they are found to comply with the requirements. The submissions through this method are integrated into the EU Open Research Repository with delay in a fully automated way.
\nRecords in the EU Open Research Repository are required to comply with the following minimal metadata requirements:
\nVisibility: Both public and restricted (with or without embargo and/or access request)
\nResource types: All resource types.
\nLicenses: Public and embargoed records MUST specify a license.
\nFunding information: Records MUST specify at least one grant from the European Commission.
\nCreators: Creators SHOULD be identified with a persistent identifier (e.g. ORCID, GND, …), and affiliations SHOULD be identified with a persistent identifier (e.g. ROR, ISNI, …)
\nSubjects: Records SHOULD specify one or more fields of science from the European Science Vocabulary.
\nAll submissions will undergo automated curation checks for compliance with the policy. Submissions through project communities are reviewed by the project community. Submission directly to the EU Open Research Repository is reviewed by Zenodo staff.
\nCommunity curators may at any point edit metadata of the records in the community without notice through human or automated processing. The curators may at their sole discretion remove records from the community that are deemed not to comply with the content and curation policy or which are deemed of insufficient quality.
\nThe content and curation policy is subject to change by the community owner at any time and without notice, other than through updating this page.
", "description": "Open repository for EU-funded research outputs from Horizon Europe, Euratom and earlier Framework Programmes.", "organizations": [ { "id": "00k4n6c32" } ], "page": "The EU Open Research Repository is a Zenodo-community dedicated to fostering open science and enhancing the visibility and accessibility of research outputs funded by the European Union. The community is managed by CERN on behalf of the European Commission.
\nThe mission of the repository is to support the implementation of the EU's open science policy, providing a trusted and comprehensive space for researchers to share their research outputs such as data, software, reports, presentations, posters and more. The EU Open Research Repository simplifies the process of complying with open science requirements, ensuring that research outputs from Horizon Europe, Euratom, and earlier Framework Programmes are freely accessible, thereby accelerating scientific discovery and innovation.
\nThe EU Open Research Repository serves as a complementary platform to the Open Research Europe (ORE) publishing platform. Open Research Europe focuses on providing a publishing venue for peer-reviewed articles, ensuring that research meets rigorous academic standards. The EU Open Research Repository provides a space for all the other research outputs including data sets, software, posters, and presentations that are out of scope for ORE. This holistic approach enables researchers to not only publish their findings but also share the underlying data and materials that support their work, fostering transparency and reproducibility in the scientific process.
\nCurrently in its pilot phase and set to be fully operational during autumn 2024, the EU Open Research Repository is constantly evolving. Efforts are committed to integrating cutting-edge features, including automated curation checks and FAIR (Findable, Accessible, Interoperable, and Reusable) assistance, to further support the research community. The goal is to provide researchers with a simple goto solution for making their publicly funded research open and as FAIR as possible.
\nThe EU Open Research Repository is funded by the European Union under grant agreement no. 101122956(HORIZON-ZEN). For more information about the project see https://about.zenodo.org/projects/horizon-zen/.
", "title": "EU Open Research Repository (Pilot)", "type": { "id": "organization" }, "website": "https://research-and-innovation.ec.europa.eu" }, "revision_id": 16, "slug": "eu", "theme": { "brand": "horizon", "enabled": true, "style": { "font": { "family": "Arial, sans-serif", "size": "16px", "weight": 600 }, "mainHeaderBackgroundColor": "#FFFFFF", "primaryColor": "#004494", "primaryTextColor": "#FFFFFF", "secondaryColor": "#FFD617", "secondaryTextColor": "#000000", "tertiaryColor": "#e3eefd", "tertiaryTextColor": "#1c5694" } }, "updated": "2024-03-20T06:47:47.577483+00:00" } ], "ids": [ "2722addc-6961-488c-acaf-c6f5455d3390", "f0a8b890-f97a-4eb2-9eac-8b8a712d3a6c" ] }, "id": "3625688", "pids": { "doi": { "client": "datacite", "identifier": "10.5281/zenodo.3625688", "provider": "datacite" } } }, "pids": { "doi": { "client": "datacite", "identifier": "10.5281/zenodo.3625689", "provider": "datacite" }, "oai": { "identifier": "oai:zenodo.org:3625689", "provider": "oai" } }, "revision_id": 3, "stats": { "all_versions": { "data_volume": 1333375274.0, "downloads": 322, "unique_downloads": 271, "unique_views": 258, "views": 267 }, "this_version": { "data_volume": 1333375274.0, "downloads": 322, "unique_downloads": 271, "unique_views": 258, "views": 267 } }, "status": "published", "updated": "2020-01-27T10:26:26.761718+00:00", "versions": { "index": 1, "is_latest": true } }