Klaas his Test Webform

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

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

2.3

Radio Technology: 5G NR

especially parameters configurations for eMBB scenario

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

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.

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.

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.

2.13

OpenSource:
OpenAirInterface / ONAP

OAI and ONAP are 2 OpenSource Frameworks that helps to orchestrate (ONAP) and deploy RAN and CORE solutions (OAI).

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

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.

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.

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.

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.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.