The present document provides terms and definitions for conceptual entities within the scope of the ISG NFV, in order to achieve a "common language" across all the ISG NFV working groups.
The present document describes the high-level functional architectural framework and design philosophy of virtualised network functions and of the supporting infrastructure. The document also defines the scope of the NFV Industry Specification Group (ISG) activities to realize this framework.
The purpose of the present document is to abstract the overall problem space in such a way that the requirements and aspects unique to NFV (ETSI GS NFV 004: "Network Functions Virtualisation (NFV); Virtualisation Requirements") are clearly identified so that the work can be scoped and organized. The resulting network architectural framework aims at positioning NFV among relevant telecommunications and IT industry stakeholders, including network operators, solution vendors, service integrators and providers, as well as serving as a reference to NFV ISG working groups.
Another purpose of the present document is to provide guidance to the industry Standards Development Organizations (SDOs) to align existing network related specifications with the NFV architectural framework outlined in the present document. Any further standardization of network functions, architecture and interfaces that are required to properly operate in a virtualised environment will be carried out in relevant SDOs. The resulting standards are expected to support the NFV high-level architectural requirements for both intra- and inter-provider domains.
The scope of the present document is to describe use cases of interest for Network Functions Virtualisation (NFV). It updates and extends ETSI GS NFV 001 V1.1.1
.
The present document provides a review of previous use cases and adds some new use cases in the context of virtualisation that are related to emerging 5G features such as the Network Slicing concept, enhanced Security, IOT virtualisation.
The order of use cases is not intended to give any priority amongst use cases.
.
These service models and use cases are intended to clarify the roles and interactions of the various types of commercial entities acting in a marketplace for services delivered via these VNFs. These actors include commercial entities/roles such as Service Providers, Enterprises, Consumers, etc. The fields of application provide high level descriptions of areas where the industry believes NFV technologies can be applied and which are representative of the business and technical challenges to be overcome.
.
The service models and use cases described in the present document are intended to provide a commercial and technical context that is expected to be useful for discussions to be handled s in further specifications to be developed by the NFV ISG. Other Industry forums may also find these service models and use cases helpful as they consider implementation options for virtualisation of the network functions they have previously standardized. The present document is not intended to provide detailed behavioural modelling of components of the NFV framework. Future documents describing additional components of the NFV framework may develop additional use cases to illustrate the behaviour of those NFV framework components; those components of the NFV framework, however, should be validated against the service models and fields of application described in the present document for consistency
The present document specifies Interoperability Test Descriptions (TDs) for OCCI and CDMI standards. The Test Descriptions cover the OCCI and CDMI protocol specifications where relevant and more specifically:
Recommendation ITU-T M.3070/Y.3521 presents the conceptual view and the common model of end-to-end (E2E) cloud computing management based on the service management interface (SMI) and cloud computing reference architecture, from the perspective of the telecommunications industry.
Recommendation ITU-T Y.3520 presents general concepts of end to end resource management in cloud computing; a vision for adoption of cloud resource management in a telecommunication-rich environment; and multi-cloud, end to end resource management for cloud services, i.e., management of any hardware and software used in support of the delivery of cloud services.
Recommendation ITU-T Y.3517 provides an overview of inter-cloud trust management by specifying isolation and security management mechanisms, inter-cloud trust management model, reputation-based trust management in an inter-cloud environment, cloud service evaluation framework and the relationship with cloud computing reference architecture. It also provides requirements for inter-cloud trust management derived from the corresponding use cases.
Recommendation ITU-T Y.3516 specifies inter-cloud computing functional architecture, including functions and functional components, based on the inter-cloud computing framework specified in [ITU-T Y.3511]. The Recommendation builds upon the functional view of the cloud computing reference architecture [ITU-T Y.3502] and makes extensions to functional components with inter-cloud functions. This Recommendation also describes the mapping between functions and functional requirements of inter-cloud computing and examples of inter-cloud related reference points.
This document defines a simplified profile of the TOSCA version 1.0 specification in a YAML rendering which is intended to simplify the authoring of TOSCA service templates. This profile defines a less verbose and more human-readable YAML rendering, reduced level of indirection between different modeling artifacts as well as the assumption of a base type system.
The TOSCA Simple Profile in YAML specifies a rendering of TOSCA which aims to provide a more accessible syntax as well as a more concise and incremental expressiveness of the TOSCA DSL in order to minimize the learning curve and speed the adoption of the use of TOSCA to portably describe cloud applications.
This proposal describes a YAML rendering for TOSCA. YAML is a human friendly data serialization standard (http://yaml.org/) with a syntax much easier to read and edit than XML. As there are a number of DSLs encoded in YAML, a YAML encoding of the TOSCA DSL makes TOSCA more accessible by these communities.
This proposal prescribes an isomorphic rendering in YAML of a subset of the TOSCA v1.0 XML specification ensuring that TOSCA semantics are preserved and can be transformed from XML to YAML or from YAML to XML. Additionally, in order to streamline the expression of TOSCA semantics, the YAML rendering is sought to be more concise and compact through the use of the YAML syntax.
Recommendation ITU-T M.3071 introduces a new network management functional architecture with cloud-computing technology. In this Recommendation, the background and basic concept of cloud-based network management are provided. This Recommendation also provides details of a cloud-based network management functional architecture, including its basic components, functionalities and the relationship between its components.
This document defines a simplified profile of the TOSCA version 1.0 specification in a YAML rendering which is intended to simplify the authoring of TOSCA service templates. This profile defines a less verbose and more human-readable YAML rendering, reduced level of indirection between different modeling artifacts as well as the assumption of a base type system.
The TOSCA Simple Profile in YAML specifies a rendering of TOSCA which aims to provide a more accessible syntax as well as a more concise and incremental expressiveness of the TOSCA DSL in order to minimize the learning curve and speed the adoption of the use of TOSCA to portably describe cloud applications.
This proposal describes a YAML rendering for TOSCA. YAML is a human friendly data serialization standard (http://yaml.org/) with a syntax much easier to read and edit than XML. As there are a number of DSLs encoded in YAML, a YAML encoding of the TOSCA DSL makes TOSCA more accessible by these communities.
This proposal prescribes an isomorphic rendering in YAML of a subset of the TOSCA v1.0 XML specification ensuring that TOSCA semantics are preserved and can be transformed from XML to YAML or from YAML to XML. Additionally, in order to streamline the expression of TOSCA semantics, the YAML rendering is sought to be more concise and compact through the use of the YAML syntax.
