Organisation (required)
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
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
1.1
|
KPI collection Framework description
|
Description on how the KPI is collected and integrated in the project and how this can be used for different verticals and architectures validations
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-111]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-112]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
1.2 Requirements definition and analysis from vertical industries and core applications
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
1.2
|
Requirements definition and analysis from vertical industries and core applications
|
Requirements from all potential vertical industries as defined in ICT-19-2019 as well as systems interoperability of core applications as defined in ICT-22-2018
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-121]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-122]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
1.3 5G-EVE end to end facility reference architecture for vertical industries and core applications
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
1.3
|
5G-EVE end to end facility reference architecture for vertical industries and core applications
|
Description of the 5G end to end facility architecture to be supported in the project facility for the vertical industries
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-131]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-132]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
WP2: Open Framework
2.1 RAN: Enhanced NR 5G radio transmission
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
2.1
|
RAN: Enhanced NR 5G radio transmission
|
RAN 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 cases
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-211]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-212]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
2.2 RAN: RRH MIMO schemes
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
2.2
|
RAN: RRH MIMO schemes
|
Several MIMO schemes are implemented. MIMO 4x4 and MIMO 32T32R as well as 64T64R are provisioned. Depending on the targeted radio coverage, specific schemes are implemented
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-221]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-222]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
2.3 Radio Technology: 5G NR
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
2.3
|
Radio Technology: 5G NR
|
especially parameters configurations for eMBB scenario
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-231]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-232]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
2.4 Radio Technology: LTE, LTE-M, NB-IoT
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
2.4
|
Radio Technology: LTE, LTE-M, NB-IoT
|
LTE 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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-241]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-242]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
2.5 Radio Technology: WiFi
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
2.5
|
Radio Technology: WiFi
|
as 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 network
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-251]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-252]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
2.6 UE: Commercial ones
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
2.6
|
UE: Commercial ones
|
Each 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 UEs
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-261]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-262]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
2.7 CN: vEPC
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
2.7
|
CN: vEPC
|
A 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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-271]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-272]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
2.8 CN: 3GPP NSA solution
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
2.8
|
CN: 3GPP NSA solution
|
5G 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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-281]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-282]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
2.9 MEC cloudification
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
2.9
|
MEC cloudification
|
Multi-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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-291]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-292]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
2.10 Interfaces definition: O-RAN implementation issues
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
2.1
|
Interfaces 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 building
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-2101]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-2102]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
2.11 Orchestrator: OSM / ONAP / specific network equipments providers
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
2.11
|
Orchestrator:
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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-2111]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-2112]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
2.12 Slicing: Services isolation
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
2.12
|
Slicing:
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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-2121]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-2122]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
2.13 OpenSource: OpenAirInterface / ONAP
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
2.13
|
OpenSource:
OpenAirInterface / ONAP
|
OAI and ONAP are 2 OpenSource Frameworks that helps to orchestrate (ONAP) and deploy RAN and CORE solutions (OAI).
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-2131]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-2132]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
WP3: Interworking framework
3.1 Single-site Experiment Monitoring. I/W FW module: Data Collection Manager
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
3.1
|
Single-site Experiment Monitoring. I/W FW module: Data Collection Manager
|
The 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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-311]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-312]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
3.2 Single-site Applications Deployment. I/W FW modules: Multi-site NSO, Multi-site Inventory
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
3.2
|
Single-site Applications Deployment. I/W FW modules: Multi-site NSO, Multi-site Inventory
|
The 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 sites
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-321]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-322]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
3.3 Single-site Network Automation. I/W FW modules: Runtime Configurator
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
3.3
|
Single-site Network Automation. I/W FW modules: Runtime Configurator
|
The 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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-331]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-332]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
3.4 Adaptation Layer of MSO. I/W FW modules: MSO-LO
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
3.4
|
Adaptation Layer of MSO. I/W FW modules: MSO-LO
|
The 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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-341]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-342]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
3.5 IWF Repository. (to be delivered at Drop 2 - Jun-20)
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
3.5
|
IWF 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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-351]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-352]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
3.6 Multi-Site Catalogue (delivered at Drop 1 - Jan 20, new version delivered at Drop 2 - Jun 20)
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
3.6
|
Multi-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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-361]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-362]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
WP4: Reference architecture, vertical requirements and description of KPI collection framework
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
4.1
|
Intent-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.
|
4.1 Intent-based experimentation (work by WINGS, UC3M)
Has your organisation contributed to generating this innovation?
YesNo
[group group-411]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-412]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
4.2 Blueprint-based experimentation, NSD composition
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
4.2
|
Blueprint-based experimentation, NSD composition
|
Usage 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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-421]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-422]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
WP5: Advanced KPI framework
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
5.1
|
WP5: KPI collection framework
|
The 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.
|
5.1 WP5: KPI collection framework
Has your organisation contributed to generating this innovation?
YesNo
[group group-511]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-512]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
5.2 WP5: KPI testing/validation framework
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
5.2
|
WP5: KPI testing/validation framework
|
As 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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-521]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-522]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
5.3 WP5: Performance Diagnosis framework
|
ID
|
Name of the innovation
|
Short description of the innovation
|
|
5.3
|
WP5: Performance Diagnosis framework
|
Verticals 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.
|
Has your organisation contributed to generating this innovation?
YesNo
[group group-531]
Please describe briefly your contribution to this innovation
[/group]
Do you or someone in your organisation plan to use this innovation, whether in the scope of 5G EVE or beyond?
YesMaybeNo
[group group-532]
Please explain briefly how you‘ll make use of this innovation (in what part of 5G EVE activities or beyond)
[/group]
