Enhanced NFV

Enhanced Network Function Virtualisation
eNFV stands for enhanced NFV and it extends the NFV platform into a lot more functionality in the back office such as a redundancy and big data, but its actual definition is based on Service Visibility relativity, and control. It allows the NFV environment to extend itself into understanding the services it hosts. It is an Etheria creation allowing for customers to functionally host all types of services inside the eNFV structure and for the solutions to be covered. eNFV covers for multi-tenancy failures, lack of redundancy, lack of backup, lack of scale, and many other times built into poorly designed solutions. We have found that instead of trying to figure out how to fix each piece of software, like standard SD WAN solutions, that lack many of the above, and spending a fortune on redesigning or adding features in proprietary code, Etheria has fixed the problems in the platform that virtualises and gives the services an environment to sit in giving incredible value.

Common infrastructure

Common infrastructure is a term used by many and understood by fewer. eNFV actually gives the customer a chance to have a direct common infrastructure for all services, OSS platforms, BSS and other such platform requirements into the same environment with the same management protocols, DMZ and with massive efficiency gains due to hardware being a shared for each service and application.

eNFV Design

Expression Layer

The expression layer can provide open APIs or could include a common management portal, eCommerce portal, etc. to function within the service environment as a common platform layer allowing ALL the service to use the same expression layer.

Orchestration Layer Management

The orchestration layer is the NFV-O which will be based on Open Network Automation Platform (ONAP). This layer orchestrates the i-NFV, s-NFV and contains service lifecycle, ONAP Operations Manager (OOM), VNF SDK, Third Part Controllers, Policy Framework, etc.

Middleware Layer

The middleware layer provides a layer for integrating anything quickly. This layer also contains the SSO and IDM for unified authentication across the layers. This layer not only attaches legacy OSS and BSS, big data, but also a broker layer that allows for massive scale increases.

Infrastructure Layer

The infrastructure layer is the i-NFV which will be delivered by OpenStack, Rancher and the likes. This layer orchestrates the Infrastructure with VMs, Containers, Storage, etc.

Service Layer

The service layer is the s-NFV which will orchestrate the deployment of services like IoT, Versa, Citrix environments, etc.

Connectivity Layer

The connectivity layer provides connectivity between the layers and any monitoring of it. E2E Visibility is provided using vDPI.

Hardware Layer

The hardware layer provides Plug n Play for hardware scaling. This includes computing nodes, networking nodes, etc.

Service Design and Creation

Designing the service by defining the resources, services and products. The service design module allows to easily create new E2E services with full lifecycle support. This includes instantiation, delivery, lifecycle resource management, services, products and certifying.

3rd Party VNFs

A VNF ecosystem is available with packaging and validation tools containing VNF APIs and VNF SDK. Once certified and approved, the VNF can be added in to the list of components for the Service Design and Creation phase.

External APIs

The External API provides access for third-party frameworks such as MEF, TM Forum and potentially others, to facilitate interactions between operator BSS and any other components.

Integrated NFV-O

The NFV-O provides orchestration at a very high level, with an end-to-end view of the infrastructure, network, and applications.

Selfhealing

Closed-loop control is provided by Data Collection, Analytics and Events (DCAE) and one or more of the other runtime components. Collectively, they provide FCAPS (Fault Configuration Accounting Performance Security) functionality. DCAE collects performance, usage, and configuration data; provides computation of analytics; aids in troubleshooting; and publishes events, data and analytics (e.g., to policy, orchestration, and the data lake).

Change Control

NFV will bring with it an era of continuous, incremental changes instead of periodic step-function software upgrades. Change control provides a consistent interface and mechanisms to manage complex dependencies, different upgrade mechanisms (in-place vs. scale-out and replace), A/B testing, conflict checking, pre- and post-change testing, change scheduling, rollbacks, and traffic draining, redirection and load-balancing.

Open Standards and Open Source

Built using many open standards and open source projects like: ONAP, OpenStack, Kubernetes, APIs, MAAS, etc.