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.
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.
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.
The service layer is the s-NFV which will orchestrate the deployment of services like IoT, Versa, Citrix environments, etc.
The connectivity layer provides connectivity between the layers and any monitoring of it. E2E Visibility is provided using vDPI.
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.
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.
The NFV-O provides orchestration at a very high level, with an end-to-end view of the infrastructure, network, and applications.
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).
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.