CN106161173A - A kind of virtual network function that realizes disposes the method and device of specification configuration - Google Patents

Abstract

The present invention provides a method and device for implementing virtual network function deployment specification configuration. The method includes: receiving an instantiation request of a virtual network function VNF, the instantiation request carrying a virtual network function descriptor VNFD identifier and a VNF deployment specification identifier ; Perform VNF instantiation processing according to the VNFD corresponding to the VNFD identifier and the VNF deployment specification corresponding to the VNF deployment specification identifier, wherein the VNFD describes one or more VNF deployment specifications and the VNF deployment specifications available The selected one or more configuration description information, the VNF deployment specification includes one or more configuration description information. Through the present invention, the VNFD can provide a flexible mechanism to ensure that VNF developers and VNF deployers are provided with differentiated customization functions when deploying VNFs of various specifications, and reduce manual intervention and uncertain factors in the VNF deployment process.

Description

A method and device for implementing virtual network function deployment specification configuration

technical field

The present invention relates to the technical field of network function virtualization, in particular to a method and a device for realizing virtual network function deployment specification configuration in an operator's network function virtualization environment.

Background technique

With the development of telecommunication network functions and services, more and more types of network elements are deployed in the network. The increase in the type and quantity of network elements has brought many problems, such as various types of hardware platforms and complex maintenance; hardware cannot be shared, resulting in waste of resources; new services require support from new hardware platforms, increasing service time to market (TTM), etc.

In recent years, cloud computing technology has developed rapidly, and cloud computing technology can effectively reduce construction and operation and maintenance costs. Cloud computing hardware platforms generally use general-purpose or customized servers, with small hardware differences and fully shared resources, reducing equipment procurement costs (CAPEX); centralized construction, deployment, and maintenance of hardware equipment reduce operation and maintenance management costs (OPEX); Virtualization technology realizes the decoupling of software and hardware, allocates resources on demand, improves resource utilization, and dynamically adjusts resources according to business loads to meet the business processing capabilities of network functions. At the same time, using virtualization technology can realize flexible allocation of resources, automatic distribution of images, and improve service deployment efficiency.

The ultimate goal of network function virtualization (NFV) technology is to replace the dedicated hardware provided by traditional telecom equipment manufacturers by providing network functions on industry-standard high-capacity servers, high-capacity storage and high-capacity switching equipment equipment. The resulting benefits are that, on the one hand, the cost of standard-based IT equipment is low, which can save huge investment costs for operators; on the other hand, the open API (Application Programming Interface, application programming interface) interface can also help operators Providers open up more telecom basic network capabilities to improve return on investment (RIO); unified resource scheduling, flexible resource allocation and network deployment, ensure service quality, and improve resource utilization efficiency; network deployment can be quickly and flexibly adjusted to meet system dynamics , Real-time expansion and contraction requirements.

While using IT technologies such as virtualization and cloud computing to realize network function virtualization, telecom operators also hope to provide a quick way to speed up service deployment time, such as using Virtualized Network Function Descriptor (VNFD for short) ) describes the composition of the virtual network function, such as the included virtual deployment unit (Virtualization Deployment Unit, referred to as VDU), virtual links, dependencies between VDUs, and link requirements between VNFs (Virtual Network Features, virtual network functions) , automatic scaling policies, monitoring parameters, network function deployment specifications, and VNF lifecycle events. The VNF deployment specification describes the deployment requirements of a specific VNF, such as supporting different requirements of users in terms of VNF capacity and performance. Different VNF deployment specifications are different in terms of network connection, number of instantiated virtual machines, and automated deployment strategies. of.

Figure 1 shows an example network function virtualization framework model diagram. The model diagram includes an operation/business management system (OSS/BSS) 101, which provides support functions for operator operations and services, including registration of network services and virtual network functions, and service management, such as performance and exception handling, and policy Management, etc.; network element management (EMS) 102, responsible for the application-related configuration, error, billing, performance and security management of virtual network functions, etc.; virtual network function (VNF) 103, using virtual computing, storage and network resources Deployed virtualized network functions; network function virtualization infrastructure layer (NFVI) 104, which is responsible for providing the infrastructure of computing, storage and network resources for the deployment of network service instances and virtual network functions; network function virtualization orchestrator (NFVO ) 105, responsible for the registration of network services and virtual network functions, resource arrangement and life cycle management of network service instances, etc.; virtual network function manager (VNFM) 106, responsible for the instantiation and life cycle management of virtual network functions (VNF) , and application-independent configuration; the virtual infrastructure manager (VIM) 107 is responsible for the control and management of computing, storage and network resources in the operator's infrastructure domain, as well as the storage and management of image files during VNF package registration. The network service, VNF and infrastructure description 108 is responsible for the description information record when the network service is registered, the description information record when the VNF package is registered, the network service and VNF instantiation information, and the NFVI resource status information.

Fig. 2 shows a structural diagram of a virtual network function descriptor (VNFD). VNFD 201 is a template describing the configuration and operation behavior of a virtual network function (VNF), which is used for VNF registration, instantiation, and life cycle management of VNF instances. In this structure diagram, VNFD includes information related to VNFD such as VNFD identification, equipment vendor and version 202; virtual data unit (VDU) 203 is used to describe the components contained in VNF, that is, the resource configuration information description template of the virtual machine ;Connection Point (CP for short) 204 is used to describe the external interface exposed by the VNF and used to connect to the external virtual network; the virtual link description (VLD) 205 constitutes a part of the VNF and is used to describe the virtual network in the VNF. Network connection; VNF lifecycle execution script 206, describing script files and processes to be executed for VNF instantiation, termination, smooth shutdown, update and upgrade, and elastic scaling; dependency relationship between VDUs 207, describing dependency relationship between VDUs, It is used to control the instantiation sequence between VDUs during VNF instantiation; the VNF monitoring parameter 208 is used to monitor VNF-related memory consumption, CPU usage, bandwidth consumption, etc., or the number of calls per second, number of users, and second traffic or VNF failure time, etc.; VNF deployment specification 209 is used to describe the requirements for VNF when deploying a VNF with specified capacity, processing capability and performance. The VDU further includes the instance number 231 of a virtual machine (Virtualised Machine, VM for short) created according to the VDU, VM-specific connection point information 232, and the like. The auto-scaling policy 210 is used to describe satisfied condition parameters and executed scaling actions.

Figure 3 shows the example VDU applied to the VNF deployment specification. VNF descriptor (VNFD) 301 specifically refers to 201 virtual network function descriptor VNFD in Figure 2; VDU302 describes the virtual machine template that constitutes the VNF, and a VNFD generally includes 1 or more VDUs that constitute the VNF, as shown in the figure 4 VDUs : VDU01, VDU02, VDU03 and VDU04, each VDU contains its own different VNF components, record the specific connection point information related to the VDU, for example, VDU01 contains specific VNFC11 and VNFC12, VDU02 contains specific VNFC21 and VNFC22, VDU03 contains Specific VNFC31 and VNFC32, VDU04 contains specific VNFC41 and VNFC42. VNFD includes multiple VNF deployment specifications, among which VNF deployment specification 01 example includes two constituted VDUs: constituted VDU1 and constituted VDU2, constituted VDU1 refers to VDU01, selects VNFC11 for specific connection point information, constitutes VDU2 refers to VDU02, Select VNFC21 for the specific connection point information; the VNF deployment specification 02 example includes 4 composed VDUs: composed VDU1, composed VDU2, composed VDU3, and composed VDU4. For the composed VDU1, refer to VDU01, and select VNFC11 for the specific connection point information. Refer to VDU02 for the configured VDU2, select VNFC21 for the specific connection point information, refer to VDU03 for the configured VDU3, select VNFC31 for the specific connection point information, refer to VDU04 for the configured VDU4, and select VNFC41 for the specific connection point information; VNF deployment specification 03 example includes 6 composed VDUs : For VDU1, VDU2, VDU3, VDU4, VDU5, and VDU6, refer to VDU01 for VDU1, select VNFC11 for specific connection point information, refer to VDU02 for VDU2, and select VNFC21 for specific connection point information For VDU3, refer to VDU03, select VNFC31 for specific connection point information, for VDU4, refer to VDU04, for specific connection point information, select VNFC41, for VDU5, refer to VDU01, for specific connection point information, select VNFC12, for VDU6, refer to VDU02, for specific connection point information Select VNFC22; VNF Deployment Specification 04 example contains 8 constituted VDUs: constituted VDU1, constituted VDU2, constituted VDU3, constituted VDU4, constituted VDU5, constituted VDU6, constituted VDU7 and constituted VDU8, constituted VDU1 Refer to VDU01, select VNFC11 for the specific connection point information, refer to VDU02 for the composed VDU2, select VNFC21 for the specific connection point information, refer to VDU03 for the composed VDU3, select VNFC31 for the specific connection point information, refer to VDU04 for the composed VDU4, select VNFC41 for the specific connection point information, and select VNFC41 for the composed VDU4 For VDU5, refer to VDU01, select VNFC12 for the specific connection point information, refer to VDU02 for the composed VDU6, select VNFC22 for the specific connection point information, refer to VDU03 for the composed VDU7, select VNFC32 for the specific connection point information, refer to VDU04 for the composed VDU8, and select VNFC42 for the specific connection point information .

In a network function virtualization environment, VNF deployment specifications describe the configuration requirements for resources, networks, and virtual links required for the instantiation of VNFs with performance requirements such as various specified capacities and processing capabilities; VNFs of different specifications are deployed The requirements for virtual links and the dependencies between VDUs are also different; after the deployment of VNFs of different specifications, the configuration requirements for automatic scaling policies, life cycle events, and parameter monitoring are also different. However, the current standard only defines the VDU information included in the VNF deployment specification. For the network connection in the VNF, the dependency relationship between VDUs, automatic scaling policies, life cycle events, and monitoring parameters are not defined. This will result in a lack of flexibility when VNFs are instantiated according to specified specifications.

Contents of the invention

The technical problem to be solved by the present invention is to provide a method and device for implementing virtual network function deployment specification configuration, so as to provide VNF deployment of various specifications.

In order to solve the above technical problems, the present invention provides a method for implementing virtual network function deployment specification configuration, including:

Receive an instantiation request of a virtual network function VNF, where the instantiation request carries a virtual network function descriptor VNFD identifier and a VNF deployment specification identifier;

Perform VNF instantiation processing according to the VNFD corresponding to the VNFD identifier and the VNF deployment specification corresponding to the VNF deployment specification identifier, wherein,

The VNFD describes one or more VNF deployment specifications and one or more configuration description information that can be selected by the VNF deployment specification, and the VNF deployment specification includes one or more configuration description information.

Further, the above method also has the following characteristics: the configuration description information included in the VNF deployment specification includes one or more of the following:

Virtual link configuration description information between virtual deployment units VDU;

Connection point configuration description information;

VDU configuration description information;

Dependency configuration description information between VDUs;

Automatic scaling policy configuration description information;

Monitoring indicator parameter configuration description information;

VNF lifecycle management executes scripts and process configuration description information.

Furthermore, the above method also has the following characteristics:

Each configuration description information described in the VNFD includes one or more optional configuration options, and each configuration description information included in the VNF deployment specification includes one or more configuration options.

Further, the above method also has the following characteristics: performing VNF instantiation processing according to the VNFD corresponding to the VNFD identifier and the VNF deployment specification corresponding to the VNF deployment specification identifier, including:

Create a virtual link according to the virtual link configuration description information between the VDUs of the VNF deployment specification, wherein,

The virtual link configuration description information between VDUs of the VNF deployment specification includes one or more configuration options of the virtual link configuration description information between VDUs described by the VNFD.

Further, the above method also has the following characteristics: performing VNF instantiation processing according to the VNFD corresponding to the VNFD identifier and the VNF deployment specification corresponding to the VNF deployment specification identifier, including:

Create an external connection interface of the VNF according to the connection point configuration description information of the VNF deployment specification, wherein,

The connection point configuration description letter of the VNF deployment specification includes one or more configuration options of the connection point configuration description letter described by the VNFD.

Further, the above method also has the following characteristics: performing VNF instantiation processing according to the VNFD corresponding to the VNFD identifier and the VNF deployment specification corresponding to the VNF deployment specification identifier, including:

The virtual machine is instantiated according to the VDU configuration description information of the VNF deployment specification, wherein,

The VDU configuration description information of the VNF deployment specification includes one or more configuration options of the VDU configuration description information described by the VNFD.

Further, the above method also has the following characteristics: performing VNF instantiation processing according to the VNFD corresponding to the VNFD identifier and the VNF deployment specification corresponding to the VNF deployment specification identifier, including:

According to the dependency configuration description information between the VDUs of the VNF deployment specification, the sequence of virtual machine instantiation is controlled, wherein,

The dependency configuration description information between VDUs of the VNF deployment specification includes one or more configuration options of the dependency configuration description information between VDUs described by the VNFD.

Further, the above method also has the following characteristics: performing VNF instantiation processing according to the VNFD corresponding to the VNFD identifier and the VNF deployment specification corresponding to the VNF deployment specification identifier, including:

Save the automatic scaling policy configuration description information of the VNF deployment specification for the instantiated virtual machine, wherein,

The automatic scaling policy configuration description information of the VNF deployment specification includes one or more configuration options of the automatic scaling policy configuration description information described by the VNFD.

Further, the above-mentioned method also has the following characteristics: it also includes:

When the instantiated virtual machine checks whether there is a corresponding automatic scaling policy according to the monitored performance index parameters, if so, executes the automatic scaling policy.

Further, the above method also has the following characteristics: performing VNF instantiation processing according to the VNFD corresponding to the VNFD identifier and the VNF deployment specification corresponding to the VNF deployment specification identifier, including:

According to the monitoring indicator parameter configuration description information of the VNF deployment specification, the monitoring parameters are set for the instantiated virtual machine, wherein,

The monitoring indicator parameter configuration description information of the VNF deployment specification includes one or more configuration options of the monitoring indicator parameter configuration description information described by the VNFD.

Further, the above method also has the following characteristics: performing VNF instantiation processing according to the VNFD corresponding to the VNFD identifier and the VNF deployment specification corresponding to the VNF deployment specification identifier, including:

Save the VNF lifecycle management execution script and process configuration description information of the VNF deployment specification for the instantiated virtual machine, wherein,

The VNF lifecycle management execution script and process configuration description information of the VNF deployment specification include one or more configuration options of the VNF lifecycle management execution script and process configuration description information described by the VNFD.

Furthermore, the above method also has the following characteristics:

When the instantiated virtual machine detects a specific life cycle event, it detects whether there is a corresponding VNF life cycle management execution script and process, and if so, executes the VNF life cycle management execution script and process.

In order to solve the above problems, the present invention also provides a device for implementing virtual network function deployment specification configuration, which includes:

A receiving module, configured to receive an instantiation request of a virtual network function VNF, where the instantiation request carries a virtual network function descriptor VNFD identifier and a VNF deployment specification identifier;

The instantiation module is configured to perform VNF instantiation processing according to the VNFD corresponding to the VNFD identifier and the VNF deployment specification corresponding to the VNF deployment specification identifier, wherein,

The VNFD describes one or more VNF deployment specifications and one or more configuration description information that can be selected by the VNF deployment specification, and the VNF deployment specification includes one or more configuration description information.

Further, the above device also has the following characteristics: the configuration description information included in the VNF deployment specification includes one or more of the following:

Virtual link configuration description information between virtual deployment units VDU;

Connection point configuration description information;

VDU configuration description information;

Dependency configuration description information between VDUs;

Automatic scaling policy configuration description information;

Monitoring indicator parameter configuration description information;

VNF life cycle management execution script and process configuration description information,

Each configuration description information described in the VNFD includes one or more optional configuration options, and each configuration description information included in the VNF deployment specification includes one or more configuration options.

Furthermore, the above-mentioned device also has the following characteristics:

The instantiation module is specifically configured to create a virtual link according to the virtual link configuration description information between the VDUs of the VNF deployment specification, wherein the virtual link configuration description information between the VDUs of the VNF deployment specification includes One or more configuration options of virtual link configuration description information between VDUs described by VNFD.

Furthermore, the above-mentioned device also has the following characteristics:

The instantiation module is specifically configured to create an external connection interface of the VNF according to the connection point configuration description information of the VNF deployment specification, wherein the connection point configuration description letter of the VNF deployment specification includes the connection point configuration description information described by the VNFD One or more configuration options for .

Furthermore, the above-mentioned device also has the following characteristics:

The instantiation module is specifically configured to instantiate the virtual machine according to the VDU configuration description information of the VNF deployment specification, wherein the VDU configuration description information of the VNF deployment specification includes one or more of the VDU configuration description information described by the VNFD. Multiple configuration options.

Furthermore, the above-mentioned device also has the following characteristics:

The instantiation module is specifically used to control the sequence of virtual machine instantiation according to the dependency configuration description information between the VDUs of the VNF deployment specification, wherein the dependency configuration description between the VDUs of the VNF deployment specification The information includes one or more configuration options of the dependency configuration description information between VDUs described by the VNFD.

Furthermore, the above-mentioned device also has the following characteristics:

The instantiation module is specifically configured to save the automatic scaling policy configuration description information of the VNF deployment specification for the instantiated virtual machine, wherein the automatic scaling policy configuration description information of the VNF deployment specification includes the automatic scaling policy described by the VNFD One or more configuration options for the configuration description.

Furthermore, the above-mentioned device also has the following characteristics:

The instantiation module is also used to detect whether there is a corresponding automatic scaling strategy when the instantiated virtual machine is based on the monitored performance index parameters, and if so, execute the automatic scaling strategy.

Furthermore, the above-mentioned device also has the following characteristics:

The instantiation module is specifically configured to set monitoring parameters for the instantiated virtual machine according to the monitoring indicator parameter configuration description information of the VNF deployment specification, wherein the monitoring indicator parameter configuration description information of the VNF deployment specification includes VNFD described One or more configuration options for monitoring indicator parameter configuration description information.

Furthermore, the above-mentioned device also has the following characteristics:

The instantiation module is specifically configured to save the VNF life cycle management execution script and process configuration description information of the VNF deployment specification for the instantiated virtual machine, wherein the VNF life cycle management execution script and process of the VNF deployment specification The configuration description information includes one or more configuration options of the VNF lifecycle management execution script and process configuration description information described by the VNFD.

Furthermore, the above-mentioned device also has the following characteristics:

The instantiation module is also used to detect whether there is a corresponding VNF life cycle management execution script and process when the instantiated virtual machine detects a specific life cycle event, and if so, execute the VNF life cycle management execution scripts and processes.

In summary, the present invention provides a method and device for implementing virtual network function deployment specification configuration, so that VNFD can provide a flexible mechanism to ensure that VNF developers and VNF deployers can provide differentiated customization functions when deploying VNFs of various specifications. , to reduce manual intervention and uncertain factors in the VNF deployment process.

Description of drawings

FIG. 1 is a schematic diagram of a network function virtualization framework model in the prior art;

Fig. 2 is the schematic diagram of the virtual network function descriptor (VNFD) structure of prior art;

FIG. 3 is a schematic diagram of a prior art VDU applied to a VNF deployment specification;

FIG. 4 is a flowchart of a method for implementing virtual network function deployment specification configuration according to an embodiment of the present invention;

5 is a schematic diagram of a virtual link descriptor VLD applied to a VNF deployment specification according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of a connection point applied to a VNF deployment specification according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of VNF lifecycle execution scripts and processes applied to VNF deployment specifications according to an embodiment of the present invention;

8 is a schematic diagram of the application of the dependency relationship between VDUs in the embodiment of the present invention to the VNF deployment specification;

FIG. 9 is a schematic diagram of monitoring parameters applied to VNF deployment specifications according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of an automatic scaling strategy applied to a VNF deployment specification according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of an extended VDU applied to a VNF deployment specification according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of VNF deployment specification expansion according to an embodiment of the present invention;

13 is a flowchart of a method for registering a VNF package according to an embodiment of the present invention;

FIG. 14 is a flowchart of a method for VNF instantiation according to an embodiment of the present invention;

Fig. 15 is a flow chart of the elastic scaling process of the VNF instance according to the embodiment of the present invention;

Fig. 16 is a flow chart of changing the automatic scaling strategy caused by the change of the VNF deployment specification according to the embodiment of the present invention;

Fig. 17 is a flowchart of connection point and VDU update according to an embodiment of the present invention;

Fig. 18 is a flow chart of the compromise of configuration properties of auto scaling according to the embodiment of the present invention;

FIG. 19 is a schematic diagram of an apparatus for implementing virtual network function deployment specification configuration according to an embodiment of the present invention.

detailed description

In order to make the purpose, technical solution and advantages of the present invention more clear, the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined arbitrarily with each other.

The technical problem to be solved by the present invention is that when deploying VNF, users have performance requirements for VNF such as capacity and processing capability. In order to meet this requirement, VNFD is required to provide multiple optional VNF deployment specifications. In addition to providing the constituent VDUs, the VNF deployment specification also needs to provide customized options for connection points, dependencies between VDUs, virtual link VL attributes, automatic deployment strategies, parameter monitoring, and VNF lifecycle event script execution. Functions to flexibly meet user requirements when selecting VNF deployment specifications.

FIG. 4 is a flow chart of a method for implementing virtual network function deployment specification configuration according to an embodiment of the present invention. As shown in FIG. 4 , the method of this embodiment includes:

Step 401: Receive a VNF instantiation request, the instantiation request carrying a VNFD identifier and a VNF deployment specification identifier;

Step 402: Perform VNF instantiation processing according to the VNFD corresponding to the VNFD identifier and the VNF deployment specification corresponding to the VNF deployment specification identifier, wherein,

The VNFD describes one or more VNF deployment specifications and one or more configuration description information that can be selected by the VNF deployment specification, and the VNF deployment specification includes one or more configuration description information.

Wherein, the configuration description information included in the VNF deployment specification includes one or more of the following:

VL configuration description information between VDUs;

Connection point configuration description information;

VDU configuration description information;

Dependency configuration description information between VDUs, such as the order in which virtual machines are instantiated;

Automatic scaling policy configuration description information;

Monitoring indicator parameter configuration description information;

VNF lifecycle management executes scripts and process configuration description information.

Wherein, the optional VL configuration description information includes VL requirements on QoS such as bandwidth, delay, error rate and jitter.

Among them, these optional VDUs include different deployment descriptions, such as affinity deployment requirements, placement requirements between this VDU and other VDUs; backup relationship configuration requirements, whether there are active and standby machines; resource deployment requirements: CPU and Resource requirements such as memory resource requirements, storage resource requirements, network interfaces, and virtual switching.

Among them, the execution scripts and processes of VNF life cycle management include the execution scripts and processes of VNF instantiation, termination, smooth shutdown, elastic scaling, update and upgrade, etc.

The VNFD of this embodiment specifies various configuration descriptions such as connection points, VDUs, dependencies between VDUs, VL attributes, automatic scaling policies, monitoring parameters, and VNF lifecycle management execution scripts for various VNF deployment specifications.

The VNF deployment specification selects some or all of the various configuration descriptions according to the performance requirements such as capacity and processing capability specified in the VNF deployment specification, and specifies the corresponding configuration capability information for each type of configuration description.

When the VNF is instantiated and running, it must meet the description requirements of the capability information specified in the specified VNF deployment specification for various configuration information.

During the elastic scaling process of a VNF instance, when the VNF changes from one VNF deployment specification to another, the VNF must update the resource configuration according to the target VNF deployment specification to achieve the capacity and Performance requirements such as processing power.

Furthermore, when a VNF instance is transformed from one VNF deployment specification to another during the elastic scaling process, if the network function virtualization (NFV) platform cannot meet the configuration requirements of the target VNF deployment specification, the NFV According to the configuration policy, the platform decides to use a compromise method to downgrade the configuration, or refuses auto scaling, and rolls back the ongoing auto scaling.

Furthermore, during the elastic scaling process of the VNF instance, when the network function virtualization (NFV) platform cannot meet the configuration requirements of the target VNF deployment specification and adopts a compromise method for downgrading the configuration, the availability of the VNF function must be guaranteed.

FIG. 5 is a schematic diagram of a virtual link descriptor VLD applied to a VNF deployment specification according to an embodiment of the present invention. As shown in FIG. 5, the VNF descriptor (VNFD) 501 specifically refers to the virtual network function descriptor VNFD 301 in FIG. The VLD of this VNF, as shown in the figure, shows four VLDs: VLD01, VLD02, VLD03 and VLD04.

VNFD includes multiple VNF deployment specifications, among which VNF deployment specification 01 example includes 1 VL: VL1, VL1 refers to VLD01; VNF deployment specification 02 example includes 2 VLs: VL1 and VL2, VL1 refers to VLD01, VL2 refers to VLD02 ; VNF deployment specification 03 example includes 3 VLs: VL1, VL2 and VL3, VL1 refers to VLD01, VL2 refers to VLD02, VL3 refers to VLD03; VNF deployment specification 04 example includes 4 VLs: VL1, VL2, VL3 and VL8 , VL1 refers to VLD01, VL2 refers to VLD02, VL3 refers to VLD03, and VL4 refers to VLD04.

The VLD is used to describe the network connection inside the VNF. For the application scenario of this embodiment, it can be understood that VL1 and VL3 are different control plane networks of the VNF, and VL2 and VL4 are different user plane networks of the VNF.

Fig. 6 is a schematic diagram of the application of the connection point in the embodiment of the present invention to the VNF deployment specification. As shown in Fig. 6, the VNF descriptor (VNFD) 601 specifically refers to the 501 virtual network function descriptor VNFD in Fig. 5; the connection point CP602 describes and constitutes the VNF A VNFD generally includes 1 or more CPs that make up the VNF. The figure shows five CPs: CP01, CP02, CP03, CP04, and CP05.

VNFD includes multiple VNF deployment specifications, among which VNF deployment specification 01 example includes two VMs: VM1 and VM2, VM1 refers to VDU01, and connects to the VNF internal network VL01 through CP01, VM2 refers to VDU02, and connects to the inside of the VNF through CP02 Network VL02; VNF deployment specification 02 example includes 2 VMs: VM1 and VM2, VM1 refers to VDU01, and is connected to the VNF internal network VL01 through CP01 and CP05, that is, VM1 is connected to the same internal network through dual network cards, and VM2 refers to VDU02 , and connected to VNF internal network VL02 through CP02; VNF deployment specification 03 example contains 3 VMs: VM1, VM2 and VM3, VM1 refers to VDU01, and connects to VNF internal network VL01 through CP01, VM2 refers to VDU02, and passes CP02 Connected to VNF internal network VL02, VM3 refers to VDU01, and connects to VNF internal network VL01 through CP03, that is, VM1 and VM3 have the same configuration and are connected to the same VNF internal network; VNF deployment specification 04 example contains 4 VMs composed : VM1, VM2, VM3 and VM4, VM1 refers to VDU01, and connects to VNF internal network VL01 through CP01 and CP05, VM2 refers to VDU02, and connects to VNF internal network VL02 through CP02, VM3 refers to VDU01, and connects to VNF internal network through CP03 Network VL01, VM4 refers to VDU02, and is connected to VNF internal network VL02 through CP04.

Fig. 7 is a schematic diagram of VNF lifecycle execution scripts and processes in an embodiment of the present invention applied to VNF deployment specifications. As shown in Fig. 7, VNF descriptor (VNFD) 701 specifically refers to 501 virtual network function descriptor VNFD in Fig. 5; Periodic event script flow 702 describes the execution scripts and procedures corresponding to lifecycle events of different VNF specifications. A VNFD generally includes one or more lifecycle event script flows, which are convenient for VNFs with different deployment specifications to call and execute when corresponding events occur. The figure shows five LCSs: LCS01, LCS02, LCS03, LCS04, and LCS05. LCS01 and LCS02 illustrate the execution process script when VNF is instantiated, but correspond to different VNF specifications.

VNFD includes multiple VNF deployment specifications. The VNF deployment specification 01 example corresponds to the VNF of this deployment specification and does not include the life cycle event script process; the VNF deployment specification 02 example corresponds to the VNF of this deployment specification and contains two life cycle event script processes: LCS01 and LCS02 and LSC01 correspond to the execution script process when the VNF is instantiated, and LCS02 corresponds to the execution script process when the VNF is terminated; the VNF deployment specification 03 example corresponds to the VNF of this deployment specification, which contains 3 life cycle event script processes: LCS02, LCS04 and LCS05, LSC02 Corresponds to the execution script process when VNF is instantiated, LCS04 corresponds to the execution script process when VNF is upgraded, and LCS05 corresponds to the execution script process when VNF is terminated; the example of VNF deployment specification 04 corresponds to the VNF of this deployment specification contains 4 life cycle event script processes: LCS02, LCS03, LCS04, and LCS05, LSC02 corresponds to the script execution process when the VNF is instantiated, LCS03 corresponds to the script execution process when the VNF is expanded, LCS04 corresponds to the script execution process when the VNF is upgraded, and LCS05 corresponds to the script execution process when the VNF is terminated.

For the different VNF deployment specifications above, VNF deployment specification 1 shows that the VNF does not need to execute the script process corresponding to the lifecycle event; VNF deployment specification 2 shows that the VNF only supports instantiation and release, and does not support elastic scaling and update upgrades, so only The execution script process corresponding to instantiation and release needs to be included; VNF deployment specification 3 shows that the VNF only supports instantiation, upgrade, and release, and does not support elastic scaling, so it only needs to include the execution script process corresponding to instantiation, update, and release. In addition, the instantiation execution script of the VNF of this deployment specification is inconsistent with the instantiation execution script of deployment specification 2, and two instantiation execution script processes LCS01 and LCS02 need to be defined at the VNFD level; VNF deployment specification 4 shows that the VNF supports instantiation, Expansion, upgrade and release, so it only needs to include the corresponding execution script process of instantiation, expansion, update and release.

Figure 8 is a schematic diagram of the application of the dependency relationship between VDUs in the embodiment of the present invention to the VNF deployment specification, as shown in Figure 8, the VNF descriptor (VNFD) 801 specifically refers to the 501 virtual network function descriptor VNFD in Figure 5; VDU dependency 802 describes the dependencies between different VDUs in the VNF. For example, the original VDU must be initialized/deployed before the target VDU. A VNFD generally contains one or more dependency descriptions between VDUs, which is convenient for VNFs with different deployment specifications to be deployed according to the deployment requirements. Make a selection, as shown in the figure, there are 4 VDU dependencies: dependency 01, dependency 02, dependency 03 and dependency 04, where dependency 01 describes that VDU02 depends on VDU01, dependency 02 describes that VDU03 depends on VDU01, and dependency 03 describes that VDU03 depends on VDU02, and dependency 04 describes that VDU04 depends on VDU03.

VNFD includes multiple VNF deployment specifications. Among them, the VNF deployment specification 01 example does not contain any VDU dependencies for the VNF of this deployment specification, that is, when the VNF of this specification is instantiated, there is no sequence requirement for the VDUs in the VNF to start; VNF deployment specification 02 Example The VNF corresponding to the deployment specification contains two VDU dependencies: dependency 01 and dependency 02, that is, when the VNF of this specification is instantiated, the virtual machine corresponding to VDU01 in the VNF must be corresponding to the virtual machine corresponding to VDU02 and VDU03 The virtual machine corresponding to VDU02 and the virtual machine corresponding to VDU03 have no start-up sequence requirements; the VNF deployment specification 03 example corresponds to the VNF of this deployment specification, which contains 3 VDU dependencies: dependency 01, dependency 02 and dependency 03, that is, when a VNF of this specification is instantiated, the virtual machine corresponding to VDU01 in the VNF must be started before the virtual machine corresponding to VDU02, and the virtual machine corresponding to VDU02 must be started before the virtual machine corresponding to VDU03; The VNF of the specification that should be deployed contains four VDU dependencies: dependency 01, dependency 02, dependency 03, and dependency 04. That is, when a VNF of this specification is instantiated, the virtual machine corresponding to VDU01 in the VNF must be corresponding to VDU02 before The virtual machine corresponding to VDU02 must be started before the virtual machine corresponding to VDU03, and the virtual machine corresponding to VDU03 must be started before the virtual machine corresponding to VDU04.

Fig. 9 is a schematic diagram of monitoring parameters applied to VNF deployment specifications according to an embodiment of the present invention. As shown in Fig. 9, VNF descriptor (VNFD) 901 specifically refers to 501 virtual network function descriptor VNFD in Fig. 5; Monitoring of different aspects, such as memory consumption, CPU usage, bandwidth consumption, etc., or the number of calls per second, number of users, traffic per second, etc., a VNFD generally contains one or more monitoring parameter descriptions, which is convenient for VNFs with different deployment specifications according to Deployment requires monitoring. The monitoring parameters will be used for the elastic scaling of the VNF. The figure shows four monitoring parameters (MP): MP01, MP02, MP03, and MP04.

VNFD includes multiple VNF deployment specifications. Among them, the VNF deployment specification 01 example does not monitor any parameters for the VNF of the deployment specification. For example, the VNF of this specification does not support auto-scaling, so parameter monitoring is not required; The VNF of the deployment specification contains 2 monitoring parameters: MP01 and MP02; the VNF deployment specification 03 example corresponds to the VNF of the deployment specification contains 3 monitoring parameters: MP01, MP02 and MP03; the VNF deployment specification 04 example corresponds to the VNF of the deployment specification contains 4 Monitoring parameters: MP01, MP02, MP03 and MP04.

FIG. 10 is a schematic diagram of the application of the Auto-Scaling Policy (ASP for short) in the embodiment of the present invention to the VNF deployment specification. As shown in FIG. 10 , the VNF descriptor (VNFD) 901 specifically refers to the virtual network function 501 in FIG. Descriptor VNFD; auto-scaling policy ASP802 describes the auto-scaling policy parameters and execution actions of the VNF. A VNFD generally contains one or more auto-scaling policy descriptions, which is convenient for VNFs with different deployment specifications to be selected according to deployment requirements. The figure shows four auto-scaling policies Scaling policy ASP: ASP01, ASP02, ASP03, and ASP04.

VNFD includes multiple VNF deployment specifications. The VNF deployment specification 01 example corresponds to the VNF configuration ASP of the deployment specification. For example, the VNF of this specification does not support auto-scaling; the VNF deployment specification 02 example corresponds to the VNF of the deployment specification and contains 2 automatic scaling policies. : ASP01 and ASP02; the VNF deployment specification 03 example corresponds to the VNF of this deployment specification and includes 3 automatic scaling policies: ASP01, ASP02, and ASP03; the VNF deployment specification 04 example corresponds to the deployment specification of the VNF and includes 4 automatic scaling policies: ASP01 and ASP02 , ASP03 and ASP04.

Figure 11 is a schematic diagram of the application of the extended VDU in the embodiment of the present invention to the VNF deployment specification. The specific information of the VDUs that constitute the VNF deployment specification, such as whether the VDUs of the composition have redundant backup and the backup mode: dual-active, or active-standby mode, the affinity relationship between the VDUs of the composition: close relationship (location during deployment) As close as possible) or usable relationship (deploy as far away as possible). The figure shows an example of 4 VDUs: VDU01, VDU02, VDU03 and VDU04.

VNFD includes multiple VNF deployment specifications, among which,

The example of VNF deployment specification 01 corresponds to the VNF of this deployment specification including two VDUs: VDU1 and VDU2, and there is a close affinity requirement between VDU1 and VDU2. There is no affinity requirement between VDU1 and VDU2. The VDU1 refers to VDU01 and has no redundant backup requirements, and the VDU2 constitutes refers to VDU02, and has no redundant backup requirements;

Example of VNF deployment specification 02. The VNF of this deployment specification contains three VDUs: VDU1, VDU2, and VDU3, and there is a close affinity requirement between VDU1 and VDU2, and there is an available affinity between VDU1 and VDU3. Affinity requirements, VDU1 refers to VDU01, and there is no redundant backup requirement; VDU2 refers to VDU02, which has dual master requirements; VDU3 refers to VDU03, which has master and backup requirements;

The example of VNF deployment specification 03 corresponds to the VNF of this deployment specification including four VDUs: VDU1, VDU2, VDU3, and VDU4, and there is a close affinity requirement between the VDU1 and VDU3, and there is a affinity between the VDU1 and VDU4. For available affinity requirements, refer to VDU01 for the constituted VDU1, which has master-standby requirements; refer to VDU02 for constituted VDU2, which has master-standby requirements; refer to VDU03 for constituted VDU3, which has dual-master requirements; refer to VDU04 for constituted VDU4, which has dual-master requirements ;

The VNF deployment specification 04 example corresponds to the VNF of this deployment specification including six VDUs: VDU1, VDU2, VDU3, VDU4, VDU5, and VDU6, and there is a close affinity requirement between the VDU1, VDU2, and VDU3. There are available affinity requirements among VDU4, VDU5, and VDU6. The composed VDU1 refers to VDU01, which has the master/standby requirement; the constituted VDU2 refers to VDU02, which has the master/standby requirement; VDU4 refers to VDU04, which has dual-master requirements, and VDU5, which consists of VDU01, has master-standby requirements, and VDU6, which consists of VDU02, which has master-standby requirements.

Fig. 12 is a schematic diagram of VNF deployment specification expansion according to an embodiment of the present invention, as shown in Fig. 12 , specifically including:

VNFD 1201, see the description of VNFD 201;

VNF deployment specification 1202, two VNF deployment specifications 01 and 02 included in the example VNFD;

The connection point 1203 is an example of a set of connection points contained in two VNF deployment specifications 01 and 02 respectively. These two groups of connection points may have different lists according to the requirements of the VNF deployment specification;

VM 1204 is an example of a group of VDUs contained in two VNF deployment specifications 01 and 02 respectively. These two groups of VDUs may have different types, instantiation numbers and resource capability requirements according to the requirements of the VNF deployment specification;

Dependency between VDUs 1205, for example, two VNF deployment specifications 01 and 02 respectively contain dependencies between VDUs, and the dependencies between these two sets of VDUs describe the dependencies between VDU groups included in the VNF deployment specifications;

VL 1206, an example of the virtual link VL attributes included in two VNF deployment specifications 01 and 02 respectively, these two sets of virtual link VL attributes describe the virtual link relationship between the connection points included in the VNF deployment specification;

The automated scaling policy 1207 is an example of the automated scaling policies contained in two VNF deployment specifications 01 and 02 respectively. These two sets of automated scaling policies may have different scaling thresholds according to the requirements of the VNF deployment specifications;

Monitoring parameter 1208 is an example of the monitoring parameters contained in two VNF deployment specifications 01 and 02 respectively. These two sets of monitoring parameters may be different according to the requirements of the VNF deployment specification;

The lifecycle management script 1209 is an example of the VNF lifecycle management scripts included in two VNF deployment specifications 01 and 02 respectively. These two sets of VNF lifecycle management scripts may be different according to the requirements of the VNF deployment specification. For example, VNF deployment specification 01 does not allow Scaling, so there is no scaling execution script.

FIG. 13 is a flow chart of a method for registering a VNF package according to an embodiment of the present invention. As shown in FIG. 13 , the method of this embodiment includes the following steps:

Step 1301, OSS/BSS initiates a VNF package registration request to NFVO, wherein the VNF package includes VNFD and image files, and VNFD further includes VNF deployment specification 01 and VNF deployment specification 02;

Step 1302, NFVO verifies the legitimacy of the registered VNF package user, and checks the integrity of the VNFD, including mandatory parameter checks, etc.;

Step 1303, NFVO interacts with VIM to save the image file of the VNF package.

Step 1304, the NFVO checks to be qualified, and saves the VNFD into the VNF directory.

FIG. 14 is a flowchart of a method for instantiating a VNF according to an embodiment of the present invention. As shown in FIG. 14, this embodiment includes the following steps:

Step 1401, OSS/BSS initiates a VNF instantiation request to NFVO, which carries information such as VNFD identifier, VNF deployment specification identifier, and user input parameters;

Step 1402, NFVO creates a VNF manager (VNFM), and forwards the instantiation request of the VNF to the VNFM;

Step 1403, the VNFM obtains the VNF deployment specification information from the VNF directory according to the VNFD identifier and the VNF deployment specification identifier, and performs a compliance check on the parameter information input by the user, such as the threshold of the automatic scaling policy reset by the user for the VNF deployment specification, and Other restrictive information, etc.;

Step 1404, the VNFM interacts with the VIM to apply for the creation of the connection point according to the connection point configuration description information of the VNF deployment specification, and creates an external connection interface of the VNF;

Step 1405, the VNFM interacts with the VIM to instantiate the virtual machine according to the VDU group of the VNF deployment specification, and satisfies the description of the dependency between VDUs in the VNF deployment specification;

Step 1406, the VNFM interacts with the VIM to create a virtual link according to the virtual link configuration description information between VDUs in the VNF deployment specification, and connects the virtual machine;

Step 1407, the VNFM records the automatic scaling policy of the VNF deployment specification.

Step 1408, the VNFM sets monitoring parameters for the instantiated virtual machine according to the monitoring parameter description of the VNF deployment specification.

Step 1409, if the VNF deployment specification includes a VNF instantiation script, the VNFM executes the VNF instantiation script.

Step 1410, the VNFM returns a VNF instantiation complete message.

FIG. 15 is a flow chart of a method for elastic scaling of a VNF according to an embodiment of the present invention. As shown in FIG. 15 , this embodiment includes the following steps:

Step 1501, OSS/BSS interacts with NFVO/VNFM to complete VNF instantiation, adopting VNF deployment specification 01;

Step 1502, as the change (increase or decrease) of the business load triggers VNF automatic elastic scaling, it is necessary to adjust the VNF deployment specification from 01 to 02;

Step 1503, the VNFM interacts with the VIM to update the connection point according to the connection point description of the VNF deployment specification 02, including modifying, creating or deleting the connection point, etc.;

Step 1504, the VNFM interacts with the VIM to update the virtual machine instance according to the VDU group of the VNF deployment specification 02, and ensures that the description of the dependency between VDUs in the VNF deployment specification 02 is met;

Step 1505, the VNFM interacts with the VIM to update the virtual link according to the description of the virtual link in the VNF deployment specification 02, and connects the virtual machine to the designated connection point;

Step 1506, the VNFM records the automatic scaling policy of the VNF instance according to the automatic scaling policy of the VNF deployment specification 02.

Step 1507, the NFVO updates the monitoring parameters set by the VNF instance according to the monitoring parameter description of the VNF deployment specification 02.

Step 1508, if the VNF deployment specification 02 includes the auto-scaling script of the network service, the VNFM executes the auto-scaling script of the network service.

In step 1509, scaling of the VNF instance is completed.

FIG. 16 is a flow chart of a method for automatic scaling policy update of a VNF instance according to an embodiment of the present invention. As shown in FIG. 16 , this embodiment includes the following steps:

Step 1601, OSS/BSS interacts with NFVO/VNFM to complete VNF instantiation, using VNF deployment specification 01, where the automatic scaling policy threshold of VNF deployment specification 01 is: the load will be scaled down when the load is lower than 20%, and the load will be higher than 80%. will be expanded;

Step 1602, as the business load increases, automatic elastic expansion of the VNF is triggered, and the VNF deployment specification needs to be adjusted from 01 to 02, wherein the automatic scaling policy threshold of the VNF deployment specification 02 is: the load will be reduced if the load is less than 10%. Capacity expansion will be carried out if the load is higher than 90%;

In steps 1603-1605, the VNFM modifies or creates the original connection point, virtual machine and virtual link of the VNF instance according to the description of the connection point in the VNF deployment specification 02, the description of the formed VDU, and the virtual link. Refer to the description of steps 1503-1506;

Step 1606, the VNFM updates the automatic scaling policy of the VNF deployment specification 02 to the record of the automatic scaling policy of the VNF instance.

Step 1607, completing the elastic expansion of the VNF instance.

Fig. 17 is a flow chart of the connection point of the VNF instance and the method for updating the virtual machine according to the embodiment of the present invention. As shown in Fig. 17, this implementation includes the following steps:

Preset: VNFD includes two VNF deployment specifications: VNF deployment specification 01 and VNF deployment specification 02.

1701. The VNF deployment specification 01 includes connection points and virtual links, and constitutes virtual machines VM01, VM02, VM03, VM04, and VM05. VM01-VM05 each have a capacity of 1. VM03 can be regarded as a service convergence and distribution node, that is, a convergence Receive service requests from VM01 and VM02, and distribute them to VM04 and VM05 for service processing according to the load sharing method.

1702. VNF deployment specification 02 includes connection points and virtual links, and constitutes virtual machines VM01, VM02, VM03, VM04, VM05, VM06 and server 01. VM01-VM03 maintain capacity 1, VM04 and VM05 are adjusted to capacity 2, and VM06 and server 01 as capacity 1, VM03 is a business tandem node, that is, tandem service requests from VM01 and VM02 are forwarded to service distribution node VM06, and VM06 tandems service requests from VM03 and server 01, and distributes them to VM04 and VM05 perform business processing.

Step 1711, OSS/BSS interacts with NFVO/VNFM to complete VNF instantiation, using VNF deployment specification 01, and the specific configuration is as described in 1701;

Step 1712, as the business load increases, automatic elastic expansion of the VNF instance is triggered, and the network VNF deployment specification needs to be adjusted from 01 to 02, wherein the configuration of the VNF deployment specification 02 is as described in preset 1702;

Step 1713, the VNFM initiates a request for updating the connection point and logical link according to the description of the connection point and logical link in VNF deployment specification 02, and modifies the connection point and logical link to the description of the network connection point and logical link in VNF deployment specification 02 ;

Step 1714, VNFM initiates a request to update the virtual machine and connect to the physical server according to the VDU description and connection point description of the VNF deployment specification 02, specifically including creating a new virtual machine, such as creating VM06, updating the capacity of the virtual machine, such as adding VM04 Update the processing capacity of VM05 from capacity 1 to capacity 2, and connect VM06 to external server 01;

Step 1715, complete the elastic expansion of the VNF.

FIG. 18 is a flowchart of a method for automatic scaling negotiation processing of a VNF instance according to an embodiment of the present invention. As shown in FIG. 18 , this embodiment includes the following steps:

Step 1801, OSS/BSS interacts with NFVO/VNFM to complete VNF instantiation, adopting VNF deployment specification 01;

Step 1802, as the business load increases, the automatic elastic expansion of the VNF instance is triggered, and the network VNF deployment specification needs to be adjusted from 01 to 02;

Steps 1803-1804, the VNFM modifies, creates or deletes the original connection point and logical link of the VNF instance, and the virtual machine formed according to the description of the connection point and logical link in the VNF deployment specification 02 and the formed VDU description information;

In step 1805, the VNFM updates the specified virtual link according to the QoS requirements of the virtual link in the VNF deployment specification 02, but the NFV virtualization platform checks the QoS of the virtual link, such as delay or bandwidth requirements cannot be met.

In step 1806, the VNFM negotiates the QoS of the unsatisfactory virtual link according to the configured policy, provides a compromise QoS, and notifies the VIM to update the virtual link.

Step 1807, complete the elastic expansion of the VNF instance.

FIG. 19 is a schematic diagram of a device for implementing virtual network function deployment specification configuration according to an embodiment of the present invention. As shown in FIG. 19 , the device of this embodiment includes:

A receiving module, configured to receive an instantiation request of a virtual network function VNF, where the instantiation request carries a virtual network function descriptor VNFD identifier and a VNF deployment specification identifier;

The instantiation module is configured to perform VNF instantiation processing according to the VNFD corresponding to the VNFD identifier and the VNF deployment specification corresponding to the VNF deployment specification identifier, wherein,

The VNFD describes one or more VNF deployment specifications and one or more configuration description information that can be selected by the VNF deployment specification, and the VNF deployment specification includes one or more configuration description information.

Wherein, the configuration description information included in the VNF deployment specification includes one or more of the following:

Virtual link configuration description information between virtual deployment units VDU;

Connection point configuration description information;

VDU configuration description information;

Dependency configuration description information between VDUs;

Automatic scaling policy configuration description information;

Monitoring indicator parameter configuration description information;

VNF life cycle management execution script and process configuration description information,

Each configuration description information described in the VNFD includes one or more optional configuration options, and each configuration description information included in the VNF deployment specification includes one or more configuration options.

In a preferred embodiment, the instantiation module is specifically configured to create a virtual link according to the virtual link configuration description information between VDUs of the VNF deployment specification, wherein the VDUs of the VNF deployment specification The virtual link configuration description information includes one or more configuration options of the virtual link configuration description information between VDUs described by the VNFD.

In a preferred embodiment, the instantiation module may be specifically configured to create a VNF external connection interface according to the connection point configuration description information of the VNF deployment specification, wherein the connection point configuration description information of the VNF deployment specification includes VNFD Describes one or more configuration options for the join point configuration descriptor.

In a preferred embodiment, the instantiation module is specifically configured to instantiate a virtual machine according to the VDU configuration description information of the VNF deployment specification, wherein the VDU configuration description information of the VNF deployment specification includes a VNFD description One or more configuration options of the VDU configuration description information.

In a preferred embodiment, the instantiation module can be specifically configured to control the sequence of virtual machine instantiation according to the dependency configuration description information between VDUs of the VNF deployment specification, wherein the VNF deployment specification The configuration description information of the dependency relationship between VDUs includes one or more configuration options of the configuration description information of the dependency relationship between VDUs described by the VNFD.

In a preferred embodiment, the instantiation module may be specifically configured to save the automatic scaling policy configuration description information of the VNF deployment specification for the instantiated virtual machine, wherein the automatic scaling policy configuration description of the VNF deployment specification The information includes one or more configuration options of the automatic scaling policy configuration description information described by the VNFD.

In a preferred embodiment, the instantiation module can also be used to detect whether there is a corresponding automatic scaling policy according to the monitored performance index parameters of the instantiated virtual machine, and if so, execute the automatic scaling policy.

In a preferred embodiment, the instantiation module can be specifically configured to set monitoring parameters for the instantiated virtual machine according to the monitoring indicator parameter configuration description information of the VNF deployment specification, wherein the monitoring indicator of the VNF deployment specification The parameter configuration description information includes one or more configuration options of the monitoring indicator parameter configuration description information described by the VNFD.

In a preferred embodiment, the instantiation module may be specifically configured to save the VNF lifecycle management execution script and process configuration description information of the VNF deployment specification for the instantiated virtual machine, wherein the VNF deployment specification The VNF lifecycle management execution script and process configuration description information include one or more configuration options of the VNF lifecycle management execution script and process configuration description information described by the VNFD.

In a preferred embodiment, the instantiation module can also be used to detect whether there is a corresponding VNF lifecycle management execution script and process when the instantiated virtual machine detects a specific lifecycle event, and if so, Then execute the VNF life cycle management execution script and process.

Those skilled in the art can understand that all or part of the steps in the above method can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a magnetic disk or an optical disk, and the like. Optionally, all or part of the steps in the foregoing embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiments may be implemented in the form of hardware, or may be implemented in the form of software function modules. The present invention is not limited to any specific combination of hardware and software.

The above are only preferred embodiments of the present invention. Of course, the present invention also has other various embodiments. Without departing from the spirit and essence of the present invention, those skilled in the art can make various Corresponding changes and modifications, but these corresponding changes and modifications should belong to the scope of protection of the appended claims of the present invention.

Claims (23)

1. realize the method that virtual network function disposes specification configuration, including:

Receiving the instantiation request of virtual network function VNF, virtual network merit is carried in described instantiation request Can descriptor VNFD mark and VNF deployment specification mark；

Specification mark is disposed corresponding according to VNFD and the described VNF that described VNFD mark is corresponding VNF deployment specification carries out the instantiation of VNF and processes, wherein,

Described VNFD describes one or more VNF and disposes specification and be available for described VNF deployment specification choosing One or more the configuration description information selected, described VNF disposes specification and includes that one or more configurations describe Information.

2. the method for claim 1, it is characterised in that: described VNF disposes what specification included Configuration description information includes following one or more:

Virtual link configuration description information between virtual deployment unit VDU；

Junction point configuration description information；

VDU configures description information；

Dependence configuration description information between VDU；

Automatization's flexible strategy configuration description information；

Monitor control index parameter configuration describes information；

VNF life management performs script and flow process configuration description information.

3. method as claimed in claim 2, it is characterised in that:

Each configuration description information that described VNFD describes comprises one or more alternative configuration choosing , each configuration description information that described VNF deployment specification comprises comprises one or more described configuration choosing ?.

4. method as claimed in claim 2 or claim 3, it is characterised in that: identify according to described VNFD The VNF deployment specification that corresponding VNFD and described VNF disposes specification mark corresponding carries out VNF's Instantiation processes, including:

The virtual link configuration description information creating between the VDU of specification is disposed virtual according to described VNF Link, wherein,

Virtual link configuration description information between the VDU of described VNF deployment specification comprises VNFD and retouches One or more config options of the virtual link configuration description information between the VDU stated.

5. method as claimed in claim 2 or claim 3, it is characterised in that: identify according to described VNFD The VNF deployment specification that corresponding VNFD and described VNF disposes specification mark corresponding carries out VNF's Instantiation processes, including:

The connection external for junction point configuration description information creating VNF disposing specification according to described VNF connects Mouthful, wherein,

Described VNF disposes the junction point configuration of specification and describes the junction point configuration that letter comprises VNFD description One or more config options of letter are described.

6. method as claimed in claim 2 or claim 3, it is characterised in that: identify according to described VNFD The VNF deployment specification that corresponding VNFD and described VNF disposes specification mark corresponding carries out VNF's Instantiation processes, including:

VDU configuration description information according to described VNF deployment specification carries out the instantiation of virtual machine, its In,

Described VNF disposes the VDU configuration description information of specification and comprises the VDU configuration that VNFD describes One or more config options of description information.

7. method as claimed in claim 2 or claim 3, it is characterised in that: identify according to described VNFD The VNF deployment specification that corresponding VNFD and described VNF disposes specification mark corresponding carries out VNF's Instantiation processes, including:

The dependence configuration description information disposed according to described VNF between the VDU of specification controls virtual The sequencing of machine instantiation, wherein,

Dependence configuration description information between the VDU of described VNF deployment specification comprises VNFD and retouches One or more config options of the dependence configuration description information between the VDU stated.

8. method as claimed in claim 2 or claim 3, it is characterised in that: identify according to described VNFD The VNF deployment specification that corresponding VNFD and described VNF disposes specification mark corresponding carries out VNF's Instantiation processes, including:

The virtual machine described VNF of preservation to instantiation disposes automatization's flexible strategy configuration description of specification Information, wherein,

Described VNF disposes automatization's flexible strategy configuration description information of specification and comprises what VNFD described One or more config options of automatization's flexible strategy configuration description information.

9. method as claimed in claim 8, it is characterised in that: also include:

When the virtual machine of instantiation is according to the performance indications parameter of monitoring, detect whether the automatization of correspondence Flexible strategy, if it has, then perform the flexible strategy of this automatization.

10. method as claimed in claim 2 or claim 3, it is characterised in that: identify according to described VNFD The VNF deployment specification that corresponding VNFD and described VNF disposes specification mark corresponding carries out VNF's Instantiation processes, including:

The monitor control index parameter configuration disposing specification according to described VNF describes virtual to instantiation of information Machine arranges monitoring parameter, wherein,

The monitor control index parameter configuration of described VNF deployment specification describes information and comprises the prison that VNFD describes One or more config options of control index parameter configuration description information.

11. methods as claimed in claim 2 or claim 3, it is characterised in that: identify according to described VNFD The VNF deployment specification that corresponding VNFD and described VNF disposes specification mark corresponding carries out VNF's Instantiation processes, including:

Virtual machine to instantiation preserves the VNF life management execution script of described VNF deployment specification With flow process configure description information, wherein,

Described VNF disposes the VNF life management of specification and performs script and flow process configuration description information bag The VNF life management execution script described containing VNFD and flow process configure or many of description information Individual config option.

12. methods as claimed in claim 11, it is characterised in that:

When the virtual machine of instantiation is when specific vital stage event being detected, detect whether correspondence VNF life management performs script and flow process, performs if it has, then perform this VNF life management Script and flow process.

13. 1 kinds realize virtual network function and dispose the device of specification configuration, it is characterised in that including:

Receiver module, for receiving the instantiation request of virtual network function VNF, described instantiation is asked Carry virtual network function descriptor VNFD mark and VNF disposes specification mark；

Instantiation module, disposes for the VNFD corresponding according to described VNFD mark and described VNF The VNF deployment specification of specification mark correspondence carries out the instantiation of VNF and processes, wherein,

Described VNFD describes one or more VNF and disposes specification and be available for described VNF deployment specification choosing One or more the configuration description information selected, described VNF disposes specification and includes that one or more configurations describe Information.

14. devices as claimed in claim 13, it is characterised in that

Described VNF disposes the configuration description information that specification includes and includes following one or more:

Virtual link configuration description information between virtual deployment unit VDU；

Junction point configuration description information；

VDU configures description information；

Dependence configuration description information between VDU；

Automatization's flexible strategy configuration description information；

Monitor control index parameter configuration describes information；

VNF life management performs script and flow process configuration description information,

Each configuration description information that described VNFD describes comprises one or more alternative configuration choosing , each configuration description information that described VNF deployment specification comprises comprises one or more described configuration choosing ?.

15. devices as claimed in claim 14, it is characterised in that

Described instantiation module, specifically for according to described VNF dispose specification VDU between virtual Link configuration describes information creating virtual link, and wherein, described VNF disposes between the VDU of specification The virtual link configuration that virtual link configuration description information comprises between the VDU that VNFD describes describes letter One or more config options of breath.

16. devices as claimed in claim 14, it is characterised in that

Described instantiation module, describes letter specifically for disposing the junction point configuration of specification according to described VNF Breath creates the connection interface that VNF is external, and wherein, described VNF disposes the junction point configuration of specification and describes Letter comprises one or more config options of the junction point configuration description letter that VNFD describes.

17. devices as claimed in claim 14, it is characterised in that

Described instantiation module, describes letter specifically for disposing the VDU configuration of specification according to described VNF Breath carries out the instantiation of virtual machine, and wherein, described VNF disposes the VDU of specification and configures description information bag One or more config options containing the VDU configuration description information that VNFD describes.

18. devices as claimed in claim 14, it is characterised in that

Described instantiation module, specifically for the dependence between the VDU according to described VNF deployment specification Relation configuration description information controls the sequencing of virtual machine instantiation, and wherein, described VNF disposes specification VDU between dependence configuration description information comprise VNFD describe VDU between dependence One or more config options of relation configuration description information.

19. devices as claimed in claim 14, it is characterised in that

Described instantiation module, disposes specification specifically for the virtual machine of instantiation is preserved described VNF Automatization's flexible strategy configuration description information, wherein, described VNF disposes the flexible strategy of automatization of specification Configuration description information comprises the one or more of automatization's flexible strategy configuration description information of VNFD description Config option.

20. devices as claimed in claim 19, it is characterised in that

Described instantiation module, is additionally operable to when the virtual machine of instantiation is according to the performance indications parameter monitored, Detect whether the flexible strategy of automatization of correspondence, if it has, then perform the flexible strategy of this automatization.

21. devices as claimed in claim 14, it is characterised in that

Described instantiation module, specifically for disposing the monitor control index parameter configuration of specification according to described VNF Description information arranges monitoring parameter to the virtual machine of instantiation, and wherein, described VNF disposes the monitoring of specification The monitor control index parameter configuration that index parameter configuration description information comprises VNFD description describes of information Or multiple config option.

22. devices as claimed in claim 14, it is characterised in that

Described instantiation module, disposes specification specifically for the virtual machine of instantiation is preserved described VNF VNF life management performs script and flow process configuration description information, and wherein, described VNF disposes specification VNF life management perform script and flow process configuration description information to comprise the VNF that VNFD describes raw Life period management performs script and one or more config options of flow process configuration description information.

23. devices as claimed in claim 22, it is characterised in that

Described instantiation module, is additionally operable to when the virtual machine of instantiation is detecting specific vital stage event Time, detect whether that the VNF life management of correspondence performs script and flow process, if it has, then perform to be somebody's turn to do VNF life management performs script and flow process.