Please state for each of the below 5G EVE innovations whether you / your organisation has contributed to creating any of them, and / or whether you or someone in your organisation plans to make use of any of them, whether in 5G EVE or beyond.


WP1: Reference architecture, vertical requirements and description of KPI collection framework

1.1 KPI collection Framework description

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
1.1KPI collection Framework descriptionDescription on how the KPI is collected and integrated in the project and how this can be used for different verticals and architectures validationsThe virtualization of the KPIs as VNFs of the 5G Network that can be delivered as part of the Service that are monitoring. The usability of the KPIs has been included in the 5G-PPP Architechture Whitepaper 3.0 (Point 6.1.2)All sites - Architecture for KPIs

1.2 Requirements definition and analysis from vertical industries and core applications

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
1.2Requirements definition and analysis from vertical industries and core applicationsRequirements from all potential vertical industries as defined in ICT-19-2019 as well as systems interoperability of core applications as defined in ICT-22-2018Not, as this is a list of requirements from vertical industriesEach Use case has a predefined site. In general the methodology can be applied to any project

1.3 5G-EVE end to end facility reference architecture for vertical industries and core applications

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
1.35G-EVE end to end facility reference architecture for vertical industries and core applicationsDescription of the 5G end to end facility architecture to be supported in the project facility for the vertical industriesThe Intent-based interface towards verticals. By the Intent-Based Interface the humans declare their “intent” to the platform by using an abstract language as close as possible to the natural one, then the platform deploys the experiment.All sites - Intend-based interface


WP2: Open Framework

2.1 RAN: Enhanced NR 5G radio transmission

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
2.1RAN: Enhanced NR 5G radio transmissionRAN equipment in 5G EVE follow the different 3GPP releases (from R15 to R16). The radio equipment will support different frequency bands (especially the N78) following the countries regulations. The BW is variable depending on the vertical (eMBB from 20 MHz to 100 MHz whereas mMTC UC are using lower BW below 20 MHz). Exploiting field deployment of NR 5G commercial network to ensure extensive coverage to the different use casesAt the time being, no specific innovations at this RAN level (or vendor specific?)Each site facility declared to implement the R15 (and R16 at the end) RAN specifications

2.2 RAN: RRH MIMO schemes

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
2.2RAN: RRH MIMO schemesSeveral MIMO schemes are implemented. MIMO 4x4 and MIMO 32T32R as well as 64T64R are provisioned. Depending on the targeted radio coverage, specific schemes are implementedAt the time being, no specific innovations at this RAN level (or vendor specific such as MU-MIMO ressource allocation or analo beamforming?)Each site facility declared to implement the R15 (and R16 at the end) RAN specifications

2.3 Radio Technology: 5G NR

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
2.3Radio Technology: 5G NRespecially parameters configurations for eMBB scenarioNoEach site is implementing NR 5G. Some are proposing to use specific Mm waves for transmission in next steps (French site for instance)

2.4 Radio Technology: LTE, LTE-M, NB-IoT

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
2.4Radio Technology: LTE, LTE-M, NB-IoTLTE is the basis of the site facility implementation. Each site facility starts with LTE implementation for first verticals integration and testing. For mMTC, sites have made choice to use either LTE-M or NB-IoT.NoLTE as a basis at each site. Then some specific technologies are proposed in some site

2.5 Radio Technology: WiFi

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
2.5Radio Technology: WiFias well known, WiFi can supply LTE/NR 5G to off-load the mobile network. WiFi is mainly used in indoor environments or in specific hotspots. Can be complementary to radio mobile networkNoWiFi is mainly used by the Italian site for the smart tourism UC

2.6 UE: Commercial ones

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
2.6UE: Commercial onesEach site facility is using its own UEs. Excepted the French site that proposes OpenSource UE based on OAI, other sites are using vendor's specific UEsNoAll sites with specific requirements (in terms of bands for instance)

2.7 CN: vEPC

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
2.7CN: vEPCA Virtual Evolved Packet Core (vEPC) is a framework for mobile networks' voice and data processing and switching that is implemented by Network Functions Virtualization (NFV), which virtualizes the functions of an Evolved Packet Core (EPC). The vEPC framework has been in use for 4G LTE mobile networks and will also form a key part of upcoming 5G network architecture.NoAll sites

2.8 CN: 3GPP NSA solution

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
2.8CN: 3GPP NSA solution5G network proposes to revisit the core architecture especially to answer to latency constraints. The first implementation is in NSA (Non StandAlone mode) that requires to continue to use the LTE network as a basis for the control plan (devices network registration) and to isolate the data plane for 5G NR transmission.Noall sites with a progressive upgarde to SA mode that will lead to a pure 5G transmission with latency minimization

2.9 MEC cloudification

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
2.9MEC cloudificationMulti-Access Edge Computing aims to create a platform-independent from the rest of the network exposing its own virtualization or containerization environment, with tools and set of standardized APIs both for services and lifecycle management. Ideally, an application built on this infrastructure can be migrated on other MEC platforms, assumed they expose the same standard APIs.NoAll sites implements MEC approach

2.10 Interfaces definition: O-RAN implementation issues

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
2.1Interfaces definition:

O-RAN implementation issues
At the RAN level, O-RAN specifies some standardized interfaces that allow operators to integrate in their network different components issued from different vendors. This allows to be vendor's agnostic in the network buildingNoSpecific to the French (Orange, Nokia) and Italian (TIM) sites that plan to test multi-technologies solutions (OpenSource with vendors specific) via the O-RAN interfaces definition

2.11 Orchestrator: OSM / ONAP / specific network equipments providers

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
2.11Orchestrator:

OSM / ONAP / specific network equipments providers
The major role of NFV orchestrator is the responsibility for making decisions about executions of specified process and automated sequencing of activities, tasks, rules and policies needed for creation, modification, removal of network application, infrastructure services or resources. Management and orchestration can be applied to both virtualized and non-virtualized resources. In 5G EVE 2 main orchestrators are implemented: OSM and ONAP.Could be considered as innovation because 5G EVE is considering multi-orchestrator management (To be check with Marc M.).OSM is implemented in Italy, Spain and Greece.

ONAP is implemented in the France site facilty

2.12 Slicing: Services isolation

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
2.12Slicing:

Services isolation
Slicing aims at proposing different level of QoS depending on the service we want to transmit and to prioritize some specific data flows compared to others.??RAN and Core slicing are currently in discussions to be implemented in all sites. RAN slicing seems to be the 1st solution that will be implemented.

2.13 OpenSource: OpenAirInterface / ONAP

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
2.13OpenSource:

OpenAirInterface / ONAP
OAI and ONAP are 2 OpenSource Frameworks that helps to orchestrate (ONAP) and deploy RAN and CORE solutions (OAI).Yes. Open Source could be used to add and easy test some specific innovations inside the code that is opened.Greece, Italia and France implement OAI solution in parallel to vendor specific infrastructure


WP3: Interworking framework

3.1 Single-site Experiment Monitoring. I/W FW module: Data Collection Manager

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
3.1Single-site Experiment Monitoring. I/W FW module: Data Collection ManagerThe Data Collection Manager component is responsible for the collection, aggregation, distribution, and persistence of all the network and vertical performance metrics requested during the execution of the experiments, with two main objectives: monitor the experiment and validate the targeted KPIs.The Data Collection Manager component is not a new invention, however, the inclusion of Kafka event bus to route metrics and logs towards higher layers is an innovation and novelty in 5G platforms, and as such, the Data Collection Manager component architecture is being exported to ICT-19 platforms (i.e. 5GROWTH as an improvement of 5G-Transformer monitoring platform).All sites - Orchestration

3.2 Single-site Applications Deployment. I/W FW modules: Multi-site NSO, Multi-site Inventory

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
3.2Single-site Applications Deployment. I/W FW modules: Multi-site NSO, Multi-site InventoryThe Multi-Site Network Orchestrator is the IWL component in charge of orchestrating the onboarding and deployment of the Network Services in 5G EVE sites. The Multi-Site Inventory offers a view of the status of Network Service in 5G EVE sitesBoth MSNO and MSI are not a new inventory, as they are part of a well-known hieratical orchestration implementation. The novelty in our implementation consists on the introduction of multi-site multi-heterogeneous abstraction layer, which allows to reuse the same NS definition across different sites.All sites - Orchestration

3.3 Single-site Network Automation. I/W FW modules: Runtime Configurator

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
3.3Single-site Network Automation. I/W FW modules: Runtime ConfiguratorThe Runtime Configurator component is responsible for the execution of tailored runtime configurations to the provisioned end-to-end NSs and NFs in support of the Vertical use case experiments, complementing the network orchestrator as a Day2 configurator for both VNFs/PNFs or infrastructure components, and the experiment execution itself.The Runtime Configurator component is not a new invention, and the use of Ansible to configure network functions and services has already been used in other orchestrators platforms, the innovation and novelty comes by using Ansible to automate the deployment of day two configurations, and its integration with an experiment life cycle manager.All sites - Orchestration

3.4 Adaptation Layer of MSO. I/W FW modules: MSO-LO

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
3.4Adaptation Layer of MSO. I/W FW modules: MSO-LOThe Multi-Site NSO to local Orchestrator interface (MSO-LO) is the portion of the Adaptation Layer that enables the Interworking Layer to access the orchestration features provided by the trial sites involved in the 5G EVE project. Trial sites can expose one or more local Network Function Virtualization Orchestrator (NFVO), each one managing a different set of resources.The MSO-LO is not a new invention because it is our implementation of the concept of hierarchical orchestration. The novelty consists in the adoption of a driver model that can abstract different types of NFV orchestrators, providing a standardized ETSI NFV-SOL 005 interface towards the MSO.All sites - Orchestration

3.5 IWF Repository. (to be delivered at Drop 2 - Jun-20)

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
3.5IWF Repository.

(to be delivered at Drop 2 - Jun-20)
The 5G EVE IWF Repository is the component in charge of storing shared information about sites and their features. It acts as a centralized storage element, exposing its data to other components of the Interworking Framework via a REST HTTP interface.The IWF Repository is not a new invention because it is relevant to our implementation of the concept of hierarchical orchestration. However, it greatly simplifies the management (including addition, upgrade, or removal of sites) of shared information relevant to different sites and it is one of the main enablers to support multi-site use case.All sites - Orchestration

3.6 Multi-Site Catalogue (delivered at Drop 1 - Jan 20, new version delivered at Drop 2 - Jun 20)

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
3.6Multi-Site Catalogue (delivered at Drop 1 - Jan 20, new version delivered at Drop 2 - Jun 20)The 5G EVE Multi-site Catalogue is the I/W framework component that is responsible for storing all of the Networks Service Descriptors (NSDs) and VNF Descriptors (VNFDs) that model single-site and multi-site vertical experiments following a unified model based on ETSI NFV SOL specifications. It is accessed by the 5G EVE portal to retrieve the capabilities of each site facility in terms of available Network Services and VNFs to properly compose experiments according to the specific vertical requirements and constraints.The Multi-Site Catalogue is not a new invention, as it is a catalogue function as normally linked and available in service orchestration platforms. However, its main innovative features include the coordination and maintenance of NSDs modelling vertical experiments across several site facilities using different local orchestrators, thus taking care to translate the NSDs from/to the common ETSI NFV SOL data model.All sites - Orchestration and local catalogues


WP4: Reference architecture, vertical requirements and description of KPI collection framework

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
4.1Intent-based experimentation (work by WINGS, UC3M)The 5G-EVE Intent Based Networking mechanism is processing natural language input from the user and translates it into service requirements for their experiment. The innovation lies in the translation engine where specific vertical terminology is translated into types of service (slices) and in the first implementation of an itterative interogation technique for soliciting additional information from the user. The mechanim results in a Service Descriptor, which is later used for setting-up and configuring the user's experiment over the 5G-EVE platform.Not at the moment (more development would be necessary)The IBN mechanism developed within 5G-EVE is part of the 5G-EVE portal (applicable to all sites) to help the vertical users of the portal to define their slice requirements (translation to a Sevice Blueprint).

4.1 Intent-based experimentation (work by WINGS, UC3M)

4.2 Blueprint-based experimentation, NSD composition

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
4.2Blueprint-based experimentation, NSD compositionUsage of blueprints is an alternative way to implement intent-based experimentation. in fact, the vertical-centric approach, based on layers of abstraction, makes use of blueprint models that describe services, service templates, configuration, metrics to collect, and tests to run. Models do not specify how to achieve something, but just the desired object, goal, or status.The concept of blueprint is not new. The invention consists of the set of tools that make automatic the overall process of designing and executing an experiment carried out by means of a model-based approach: starting from models with the highest level of abstraction, which are those presented to the vertical users, and ending with the most detailed one, which are fed into the 5G EVE platform to enforce device configuration and experiment execution.All sites - Orchestration and configuration


WP5: Advanced KPI framework

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
5.1WP5: KPI collection frameworkThe 5G EVE KPI Collection framework is a powerful framework for collecting several 5G related metrics, both on 5G network and application layers. The two main building blocks of the framework are the Data Collection Manager and the Data Shippers. The Data Collection Manager is based on Apache Kafka, which is a well-known publish-subscribe tool that acts as a bus, being able to manage and send data to different applications connected to it. The Data Shippers are the information collection agents responsible for gathering metrics and logs and shipping them to the Data Collection Manager. In order for the implementation of these agents to be robust and modular, the tool adopted for this task are the Beats by Elastic.KPI collections frameworks in general already co-exist, so it is not a new invention, but rather a powerful framework for collecting several 5G related metrics (both on 5G infrastructure and vertical application layers).All sites - Access, Core and Edge

5.1 WP5: KPI collection framework

5.2 WP5: KPI testing/validation framework

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
5.2WP5: KPI testing/validation frameworkAs 5G technology is evolving, consolidation and moving to deployment stage, more and more verticals are exploring how to best leverage the potential of 5G for their business, conceiving and developing new applications. In order to validate the functionality and performance of those applications before launching them in the market, extensive and reliable tests are required (which normally implies a great deal of investments, effort and time). 5G EVE builds and offers a validation framework for easily integrating, executing, testing, validating and monitoring 5G-enabled vertical applications developed by European industry leaders. It powers an agile process that allows vertical “citizen” users to easily define how their application can be deployed in a real 5G environment, over a number of potential configuration plans and validated against a broad set of situations and conditions (realistic scenarios). With that added-value service the vertical can easily validate, improve and fine-tune their service and pinpoint the key requirements that their new 5G-based services under test pose on the target environments for launching them commercially. The impact of this framework is therefore a dramatic reduction of testing investment and vertical’s innovation lead time.The validation framework of 5G EVE can be considered as highly innovative, since it dramatically reduces the testing investment and vertical’s innovation lead time. Testing and validation frameworks in general are already exists, therefore it cannot be characterized as a new invention (in my view), but rather a powerful platform for 5G validation based on open solutions.All sites - Access, Core and Edge

5.3 WP5: Performance Diagnosis framework

IDName / title of the innovation (IP element)Short description of the elementInvention assessment (could it be considered an invention?)Trial site in which the innovation will be used
5.3WP5: Performance Diagnosis frameworkVerticals applications need to accomplish (often stringent) KPI levels, over complex 5G infrastructures, which encompass radio, access/edge, transport/core, cloud, etc. segments. Tools are needed for verifying the degree of KPI compliance, as well as for diagnosing the reasons at the level of the segment, and also for suggesting respective improvements. Such tools are part of the innovation, which will be oriented, primarily, to verticals and, potentially, to operators also. 5G EVE is developing a Performance diagnosis frameworking supporting Anomaly Detection, Root Cause Analysis and Performance Optimization in 5G infrastructures.No invention, but rather highly innovative, the Performance Diagnosis framework as a whole and especially its Route Cause Analysis features.All sites - Access, Core and Edge


Contact Us

We're not around right now. But you can send us an email and we'll get back to you, asap.

Not readable? Change text. captcha txt

Start typing and press Enter to search