Networking

The present document specifies requirements and templates for describing Network Functions Virtualisation (NFV) Network Services (NSs) in the form of meta-data.

The present document defines the interfaces supported over the Os-Ma-nfvo reference point of the NFV-MANO architectural framework as well as the information elements exchanged over those interfaces.

Network Functions Virtualisation (NFV) Release 2; Management and Orchestration; Os-Ma-Nfvo reference point - Interface and Information Model Specification

The present document develops specifications for packaging of VNFs to be delivered to service providers, focusing on the holistic end-to-end view of the VNF Package lifecycle, from design to runtime, capturing development as well as operational views. The present document provides an analysis of end-to-end VNF Package lifecycle management operations based on use-cases and NFV Architectural Framework functional blocks.
 
A VNF Package contains all of the required files and meta-data descriptors required to validate and instantiate a VNF.
 
Standardized meta-data descriptors are required to:

• describe the NFV infrastructure resource requirements for a VNF in a service provider environment;
• describe design constraints and other dependencies in order for the VNF to successfully install, instantiate and terminate; and
• describe VNF operational behaviour including VNF lifecycle events (e.g. scaling, upgrading).

Standardized packaging and validation of VNFs is required to:

• provide a consistent, documented method for VNF providers to package VNFs;
• harmonize the service provider on-boarding process for VNFs coming from different VNF providers;
• ensure integrity, trust and auditability of a VNF Package;
• allow for a flexible and extensible VNF packaging structure that accommodates a wide variety of NFV infrastructure scenarios; and
• allow the packaged VNF-related meta-data to be interpreted and the packaged VNF to be instantiated in a wide variety of orchestration systems irrespective of technology choice or infrastructure environment.

The present document develops specifications for packaging of VNFs to be delivered to service providers, focusing on the holistic end-to-end view of the VNF Package lifecycle, from design to runtime, capturing development as well as operational views. The present document provides an analysis of end-to-end VNF Package lifecycle management operations based on use-cases and NFV Architectural Framework functional blocks.
 
A VNF Package contains all of the required files and meta-data descriptors required to validate and instantiate a VNF.
 
Standardized meta-data descriptors are required to:

• describe the NFV infrastructure resource requirements for a VNF in a service provider environment;
• describe design constraints and other dependencies in order for the VNF to successfully install, instantiate and terminate; and
• describe VNF operational behaviour including VNF lifecycle events (e.g. scaling, upgrading).
•  

Standardized packaging and validation of VNFs is required to:

• provide a consistent, documented method for VNF providers to package VNFs;
• harmonize the service provider on-boarding process for VNFs coming from different VNF providers;
• ensure integrity, trust and auditability of a VNF Package;
• allow for a flexible and extensible VNF packaging structure that accommodates a wide variety of NFV infrastructure scenarios; and
• allow the packaged VNF-related meta-data to be interpreted and the packaged VNF to be instantiated in a wide variety of orchestration systems irrespective of technology choice or infrastructure environment.

Network Functions Virtualisation (NFV) adds new capabilities to communications networks and requires a new set of management and orchestration functions to be added to the current model of operations, administration, maintenance and provisioning. The NFV Management and Orchestration (NFV-MANO) architectural framework has the role to manage the infrastructure and orchestrate the resources needed by the Network Services (NSs) and Virtualised Network Functions (VNFs).
 
In order to guide the development of the specification of the interfaces exposed between the NFV-MANO Functional Blocks (FBs), it is important to have a clear and consolidated set of functional requirements to be addressed by the NFV-MANO. The present document is providing functional requirements on NFV MANO e.g. VNF lifecycle management (LCM), NS LCM, virtualised resource management, etc.
 
The functional requirements specified in the present document are mainly derived from functional requirements identified in ETSI GS NFV 002, ETSI GS NFV 003, ETSI GS NFV 004, ETSI GS NFV-MAN 001, ETSI GS NFV-SWA 001, ETSI GS NFV-REL 001 and ETSI GS NFV-INF 001 or derived from concepts defined in these documents.

The present document specifies the functional requirements, interfaces and operations to support the provision of network services across multiple administrative domains based on the interactions between NFVOs in different administrative domains (supported over the Or-Or reference point).
 
The present document also specifies the information elements exchanged over the specified interfaces.
 
The different aspects specified in the present document are derived from ETSI GR NFV-IFA 028.

The present document focusses on the characterization of Virtualised Network Functions (VNF) as part of their configuration and deployment in "the Cloud". Such VNFs are assumed to be implemented using generic cloud computing techniques beyond virtualization [i.1]. For example, the VNFs can be built with re-usable components as opposed to a unique - and potentially proprietary - block of functions.
 
Cloud native VNFs are expected to function efficiently on any network Cloud, private, hybrid, or public. The VNF developer is therefore expected to carefully engineer VNFs such that they can operate independently in the desired Cloud environment. Cloud environment can be implemented based on hypervisor/VM or container technology. This is an indication of the "readiness" of VNFs to perform as expected in the Cloud. The objective of the present document is to develop the characterization of the "Cloud Readiness" of VNFs.
 
From an operator perspective, it is essential to have a complete description of cloud native readiness of VNFs; this description will help operators in their VNF selection process. To do this, it is essential that a set of non-functional parametric characterizations be developed that appropriately describe the cloud native nature of VNFs. Non-functional parameters describe the environmental behaviour of VNFs residing in the Cloud. They do not describe the actual working functions of the VNF; rather they describe how the VNF can reside independently in the Cloud without constant operator involvement.
 
The present document considers not only the "pure" cloud native VNF implementations (e.g. no internal resiliency or state) but also some transition implementations to cloud native such as the VNFs with internal resiliency.
 
Non-functional characteristics of a cloud native VNF are described through a VNF Product Characteristic Descriptor (VNFPCD) created by the VNF provider. Usage of the cloud native VNFPCD is as follows:

• The cloud native VNFPCD is used by an operator to decide on what VNF product to deploy to fulfil a particular functionality, when the decision is based on non-functional parameters.
• The VNFPCD can be used in a VNF market place for a standardized description of the VNF products non- functional characteristics and as such can be checked/searched for automatically.

The intent of the present document is to identify a minimum set of non-functional parameters by which VNFs are characterized as cloud native. The non-functional parameters are classified according to the specific environmental behaviour of the VNF.
 
Each behaviour then provides a list of specific non-functional parameters along with specific requirements such that the cloud native nature of the VNF can be satisfactorily established.

The present document develops a set of normative interoperability requirements for the Network Function Virtualisation (NFV) hardware ecosystem and telecommunications physical environment to support NFV deployment. It builds on the work originated in ETSI GS NFV 003.
 
The present document focusses on the development of requirements to enable interoperability of equipment in the telecommunications environment to support NFV deployment. The following areas are examined:

• Operations
• Environmental
• Mechanical
• Cabling
• Maintenance
• Security

The present document focuses on unique aspects related to network and service resiliency in a virtualised network environment. The challenges result from failures of virtualised network functions, failures of the underlying hardware and software infrastructure arising from conditions such as design faults, intrinsic wear out, operational mistakes, or other adverse conditions, e.g. natural disasters, excessive traffic demand, etc.
 
The scope of the present document includes:

• Usecase analysis for reliability and availability in a virtualised network environment.
• Analysis of service availability levels.
• Identification of requirements for maintaining network resiliency and service availability, the focus being additional requirements introduced by virtualisation. The mechanisms to be considered include the following:
  •     Network function migration within and across system boundaries.
  •     Failure detection and reporting at the various layers.
  •     Failure prediction, prevention, and remediation.
  •     State management.
  •     Solving network availability issues caused by overload/call blocking conditions.
• Engineering and deployment guidelines for maintaining network resiliency and ensuring service availability.

The present document defines a framework for use within ETSI NFV ISG to coordinate and promote public demonstrations of Proofs of Concept (PoC) illustrating key aspects of NFV.
 
The objective for the PoCs is to build commercial awareness and confidence and encourage development of an open ecosystem by integrating components from different players.

 
This framework outlines:

• rationale for NFV ISG PoCs;
• NFV ISG PoC process;
• format and criteria for NFV ISG PoC Proposals;
• NFV ISG PoC Report format and requirements.