WO2018145615A1

WO2018145615A1 - Vnf deployment method and system

Info

Publication number: WO2018145615A1
Application number: PCT/CN2018/075291
Authority: WO
Inventors: 孟宪杰
Original assignee: 华为技术有限公司
Priority date: 2017-02-07
Filing date: 2018-02-05
Publication date: 2018-08-16
Also published as: CN108400998A; CN108400998B

Abstract

The present application discloses a VNF deployment method and system, belonging to the field of virtual network technologies. The method comprises: an NFV system being deployed in distributed DC network architecture, the NFV system comprising an NFVO, a VNFM, and a VIM, the NFVO being able to acquire an NS deployment request, then determining a relevant target VNF, and selecting, according to the DC selection information added in the VNFD, a target DC satisfying the deployment requirements on the target VNF, thereby the target DC being able to perform the deployment of the target VNF. The present application can reduce the latency of data transmissions of a network service, and reduce packet loss, thereby improving service quality.

Description

Method and system for deploying VNF

The present application claims priority to Chinese Patent Application No. JP-A No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. in.

Technical field

The present application relates to the field of virtual network technologies, and in particular, to a method and system for deploying a VNF.

Background technique

Existing NFV systems include an NFV Management and Orchestration (NFV MANO), NFV Infrastructure (NFV), multiple Virtual Network Functions (VNF), and multiple network elements. Element Management (EM), Network Services, VNF and Infrastructure Description (VNF and Infrastructure Description), and Operation-Support System/Business Support System (OSS/BSS). Among them, the NFV management and orchestration system includes NFV Orchestrator (NFVO), one or more VNFM (VNF Manager, VNFM) and Virtualized Infrastructure Manager (VIM).

For each network service, the server can deploy the corresponding VNF in the NFV system to perform the corresponding function. Specifically, when the NFVO receives the NS deployment request of the server for the network service, the NFVO can describe the pre-stored network service (NS). Description, NSD) to determine at least one VNF involved in the network service, and then determine the VNFM and VIM corresponding to each VNF according to the pre-stored virtual network function description (VNFD), so that the VNFM And VIM deploys VNF based on VNFD.

In the process of implementing the present application, the inventors found that the prior art has at least the following problems:

The virtual devices in the existing NFV system are centrally deployed in a data center (DC). For users away from the DC, the data transmission of the network service passes through more data forwarding devices, and the data is transmitted. The distance is long, resulting in a higher delay in data transmission.

Summary of the invention

In order to solve the problem of the prior art, an embodiment of the present invention provides a method and system for deploying a VNF. The technical solution is as follows:

In a first aspect, a method of deploying a VNF is provided, the method being applied to an NFV system deployed in a distributed DC network architecture, the NFV system including at least NFVO, VNFM, and VIM, wherein:

The NFVO may obtain the NS deployment request, and then determine at least one target VNF involved in the NS deployment request according to the preset NSD; then, for each target VNF, the NFVO may select according to the DC selection information added in the target VNFD corresponding to the target VNF. The target DC corresponds to the target DC; thus the NFVO can send a deployment request of the target VNF to the target DC; the target DC can deploy the target VNF through the deployed target VNFM and the target VIM according to the target VNFD.

In the solution shown in the embodiment of the present disclosure, the server may add DC selection information to the VNFD to describe the conditions that the VNF needs to deploy the DC. After the VNF is deployed, the DC may be selected according to the VNFD. The VNF is deployed in a DC that is closer to the user. Therefore, when performing network services, data transmission needs to pass less data forwarding devices, and the data transmission distance is shorter, thereby reducing the delay of data transmission.

In a possible implementation manner, the DC selection information may include DC coverage area information, DC level information, and/or DC location information, and the DC location information includes DC address information, coverage area radius, and/or DC coordinate information.

In the solution shown in the embodiment of the present disclosure, the NFVO may determine the level of the target DC to be deployed by the target VNF according to the DC level information in the DC selection information in the VNFD, and may also select the target DC in the designated area according to the DC location information.

In a possible implementation manner, the technician can write basic information of all DCs in the distributed DC network architecture to the NFVO, so that the NFVO generates a DC resource pool according to the obtained basic information of all DCs, or a distributed DC network. All the DCs in the architecture can report the basic information of the DC to the NFVO, so that the NFVO generates a DC resource pool according to the basic information of all the acquired DCs. Thereafter, the NFVO may select the target DC that satisfies the DC selection information in the DC resource pool according to the DC selection information added in the target VNFD corresponding to the target VNF.

In the solution shown in the embodiment of the present disclosure, the NFVO may be configured with a “DC resource pool”, that is, the basic information of all DCs in the network is recorded, so that when the VNF is deployed, the NFVO may be selected according to the DC in the VNFD in the DC resource pool. The information selects the target DC corresponding to the target VNF.

In a possible implementation manner, if the target VNF includes multiple target VDUs, after the target VNFM deployed on the target DC receives the NFVO, all target VDUs included in the target VNF may be determined according to the VNFD, and thus, for each target The VDU may select a feature DC corresponding to the target VDU according to the DC selection information added in the VDUD corresponding to the target VDU, and then the target VNFM may send a deployment request of the target VDU to the feature DC, and the feature DC is deployed according to the target VDUD. The feature VNFM and feature VIM are used to deploy the target VDU.

In the solution shown in the embodiment of the present disclosure, when the VNF includes multiple VDUs, the DCs to be deployed by the multiple VDUs may be selected according to the DC selection information added in the VDUD, and the corresponding VDUs may be deployed on the selected DCs.

In a possible implementation, the technician can write the basic information of all DCs in the distributed DC network architecture to the VNFM in each DC, so that the VNFM can generate a DC resource pool according to the obtained basic information of all the DCs, or All the DCs in the distributed DC network architecture can forward the respective basic information to other DCs. Therefore, the VNFM on the DC can generate a DC resource pool according to the obtained basic information of all DCs. Afterwards, the target VNFM may select the feature DC that satisfies the DC selection information in the DC resource pool according to the DC selection information added in the VDUD corresponding to the target VDU.

In the solution shown in the embodiment of the present disclosure, the VNFM deployed on each DC may be configured with a “DC resource pool”, that is, the basic information of all DCs in the network is recorded, so that when the VDU is deployed, the VNFM may be in the DC resource pool. The target DC corresponding to the target VDU is selected according to the DC selection information in the VDUD.

In a second aspect, a system for deploying a VNF is provided, the system comprising at least one device, the at least one device for implementing the method for deploying a VNF provided by the above first aspect.

The technical effects obtained by the second aspect of the embodiment of the present disclosure are similar to those obtained by the corresponding technical means in the first aspect, and are not described herein again.

The beneficial effects brought by the technical solutions provided by the embodiments of the present invention are:

In the embodiment of the present invention, for each VNF, the server may record the DC selection information of the VNF in the corresponding VNFD in advance, so that when the server needs to deploy an NS, the NFVO in the NFV system may first determine the All the VNFs involved in the NS are then determined according to the DC selection information in the VNFD corresponding to the VNF, and the DCs satisfying the deployment requirements of the VNFs are determined, so that the VNF deployment can be completed on the determined DCs. In this way, in the distributed DC network architecture, the VNF corresponding to the network service can be deployed in the DC closer to the user. Therefore, when the network service is executed, the data forwarding device that the data transmission needs to pass is less, and the distance of the data transmission is small. It is shorter, which can reduce the delay of data transmission, reduce packet loss, and improve service quality.

DRAWINGS

1 is a system architecture diagram of an NFV system according to an embodiment of the present invention;

2 is a schematic diagram of a distributed data center network architecture according to an embodiment of the present invention;

3 is a schematic diagram of deployment of an NFV system in a distributed data center network architecture according to an embodiment of the present invention;

4 is a flowchart of a method for deploying a VNF according to an embodiment of the present invention;

FIG. 5 is a flowchart of a method for deploying a VDU according to an embodiment of the present invention.

detailed description

In order to make the objects, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

The embodiment of the invention provides a method for deploying a virtual network function (VNF), which can be applied to a network function virtualization (NFV) system, and the execution subject may be a virtual in the NFV system. device. FIG. 1 shows a system architecture diagram of an NFV system that can be used in various networks, such as a data center network, a carrier network, or a local area network. The NFV system 100 includes an NFV Management and Orchestration (NFV MANO) 101, an NFV Infrastructure (NFV) 130, a plurality of Virtual Network Functions (VNF) 108, and multiple networks. Element Management (EM) 122, Network Service, VNF and Infrastructure Description (Network Service, VNF and Infrastructure Description) 126, and Operation-Support System/Business Support System (OSS/BSS) 124. The NFV MANO 101 includes an NFV Orchestrator (NFVO) 102, one or more VNFM (VNF Manager, VNFM) 104, and a Virtualized Infrastructure Manager (VIM) 106. The NFVI 130 includes computing hardware 112, storage hardware 114, network hardware 116, virtualization layer, virtual computing 110, virtual storage 118, and virtual network 120.

Among them, NFV MANO 101 is used to perform monitoring and management of VNF 108 and NFVI 130. The NFVO 102 may implement network services (e.g., L2 and L3 VPN services) on the NFVI 130, may also perform resource related requests from one or more VNFMs 104, send configuration information to the VNFM 104, and collect status information for the VNFs 108. In addition, NFVO 102 can communicate with VIM 106 to enable resource allocation and/or reservation and to exchange configuration and status information for virtualized hardware resources. The VNFM 104 can manage one or more VNFs 108. The VNFM 104 can perform various management functions for the VNF 108, such as instantiation, update, query, scaling, and/or termination. The VIM 106 can perform resource management functions such as managing the allocation of infrastructure resources (eg, adding resources to virtual containers) and operational functions (such as collecting NFVI failure information). VNFM 104 and VIM 106 can communicate with each other for resource allocation and exchange of configuration and status information for virtualized hardware resources.

NFVI 130 includes hardware resources, software resources, and a combination of the two to complete the deployment of the virtualized environment. Specifically, the hardware resources and virtualization layers are used to provide virtualized resources, such as virtual machines and other forms of virtual containers, serving the VNF 108. The hardware resources include computing hardware 112, storage hardware 114, and network hardware 116, which may be commercially available hardware and/or user-customized hardware to provide processing and computing resources. Storage hardware 114 may be storage capacity provided within the network or storage capacity residing on storage hardware 114 itself (local storage located within the server). In one implementation, the resources of computing hardware 112 and storage hardware 114 may be collectively located in the same device. Network hardware 116 can be a switch, a router, and/or any other network device configured to have switching functionality. Network hardware 116 can span multiple domains and can include multiple networks interconnected by one or more transport networks.

The virtualization layer within NFVI 130 can abstract hardware resources from the physical layer and decouple VNF 108 to provide virtualized resources to VNF 108. The virtual resource layer includes virtual computing 110, virtual memory 118, and virtual network 120. Virtual computing 110 and virtual storage 118 may be provided to VNF 108 in the form of virtual machines, and/or other virtual containers. For example, one or more VNFs 108 can be deployed on a virtual machine. The virtualization layer is used to abstract the network hardware 116 to form a virtual network 120, which may include a virtual switch that is used to provide connectivity between the virtual machine and other virtual machines. In addition, the transport network in the network hardware 116 can be virtualized using a centralized control plane and a separate forwarding plane, such as a Software Defined Network (SDN).

VNFM 104 can interact with VNF 108 and EM 122 to manage the lifecycle of the VNF and exchange configuration and status information. The VNF 108 can be configured to virtualize at least one network function performed by one physical network device. For example, in one implementation, the VNF 108 can be configured to provide functions of different network elements in an Information Management System (IMS) network, such as Proxy-Call Session Control Function (P -CSCF), Serving-Call Session Control Function (S-CSCF) or network function of Home Subscriber Server (HSS). The EM 122 is configured to manage one or more VNFs 108.

The solution can deploy the NFV system in a distributed data center network. The distributed data center network can be a multi-layer data center architecture. Here, a 3-layer data center architecture is taken as an example. As shown in FIG. 2, the network architecture includes a center. DC (Central DC), regional DC (Regional DC) and edge DC (Edge DC), where the number of central DCs is small, there may be 2-3 for a province's area, and the regional DC is probably a few Ten, the number of edge DCs will reach hundreds to thousands.

The specific deployment mode of the NFV system in this solution can be as shown in Figure 3. Specifically, the complete NFV management plane (VIM, VNFM, NFVO) and service plane (NFVI, VNF, EM, OSS/BSS) can be deployed on the central DC. ), deploy some NFV management planes (VIM, VNFM) and business planes (NFVI, VNF, EM, OSS/BSS) on the regional DC and edge DC. The management plane and NFVI need to be fixedly deployed (that is, deployed on the DC in advance), and the VNF can be dynamically deployed as needed (that is, it can be dynamically deployed by MANO according to the NS deployment request). In addition, EM, OSS/BSS can be regarded as a special VNF, but the functions are different. This article describes the deployment method of VNF, which is also applicable to EM and OSS/BSS.

The processing flow shown in FIG. 4 will be described in detail below with reference to specific implementations, and the content can be as follows:

Step 401: The NFVO acquires an NS deployment request, and determines at least one target VNF involved in the NS deployment request according to the preset NSD.

In the implementation, the server can deploy the NFVO in the NFV system to the central DC in advance. When the server needs to deploy a new NS, the NS can be deployed through the NFVO. Specifically, the NFVO can obtain the corresponding NS deployment. The request, the deployment request may carry the NS identifier, and then the NFVO may determine, according to the NS identifier, at least one target VNF involved in the NS deployment request in the preset NSD, that is, determine which virtual network functions are included in the NS. It should be noted that all devices included in the NFV system of the solution serve the same server, so the server can set NSD, VNFD, VDUD, etc. as needed.

Step 402: The NFVO selects the target DC corresponding to the target VNF according to the DC selection information added in the target VNFD corresponding to the target VNF.

In the implementation, the server can pre-add the DC selection information that the corresponding VNF is suitable for deployment in the VNFD according to the actual needs of the service, and the DC selection information can determine the area or location where the DC that the VNF can be deployed. In this way, after determining all the target VNFs involved in the NS deployment request, for each target VNF, the NFVO may first obtain the target VNFD corresponding to the target VNF, and then determine, according to the DC selection information added therein, that the target VNF deployment requirement is met. Target DC.

Optionally, the DC selection information includes DC level information and/or DC location information, and the DC location information includes DC coverage area information, DC address information, coverage area radius, and/or DC coordinate information.

In an implementation, the server may add DC selection information to the VNFD in advance, and the DC selection information may include DC level information (ie, a DC Level field in the following text) and/or DC location information (ie, a DC Location Region field in the following). The DC location information includes DC coverage area information (ie, the Region field in the following text), DC address information (ie, the location field in the following text), the coverage area radius (ie, the radius field in the following text), and/or DC coordinate information (ie, The coordinate field in the text), where there is one of the two fields of location and coordinate. Specifically, a "preferred DC" field may be added to the VNFD to describe the target VNF's need for DC location:

Among them, the specific definition of Preferred DC can be as follows:

Among them, the specific definition of DC Location Region is as follows:

Among them, the specific definition of Coordinate can be as follows:

In this way, after determining all the target VNFs involved in the NS deployment request, for each target VNF, the NFVO may first obtain the target VNFD corresponding to the target VNF, and then may determine that the DC selection is satisfied according to the DC selection information (preferred DC field) added thereto. The target DC of the target VNF deployment needs. For example, the preferred DC field can be: "DC Level='Edge DC'and DC Location Region={location='236 main street,Shenzhen',radius=1000}", indicating that the VNF needs to be deployed at "236 main" Street, Shenzhen" is centered on the edge of the DC within a radius of 1000 meters. It should be noted that the DC coverage area information may be recorded in the form of an area identifier, and the area division standard may be an existing administrative area division standard, for example, “Region=Guangdong province”, that is, the DC coverage area is Guangdong Province, and may also be It is the division standard set by the service party.

In step 403, the NFVO sends a deployment request of the target VNF to the target DC.

In an implementation, after determining the target DC corresponding to the target VNF, the NFVO may send a deployment request of the target VNF to the target DC, where the deployment request may carry the identification information of the target VNF.

Step 404: The target DC deploys the target VNF through the deployed target VNFM and the target VIM according to the target VNFD.

In an implementation, the target DC may receive a deployment request of the target VNF sent by the NVFO, so that the deployment of the target VNF may be completed by the target VNFM and the target VIM deployed on the target DC according to the target VNFD. Here, the process of deploying the VNF according to the VNFD belongs to the prior art, and thus is not specifically described in this embodiment.

Optionally, the NFVO may select the target DC according to the pre-recorded basic information of all DCs, and the corresponding processing may be as follows: the NFVO generates a DC resource pool according to the obtained basic information of all DCs; the NFVO is according to the target VNFD corresponding to the target VNF. The added DC selection information selects a target DC in the DC resource pool that satisfies the DC selection information.

The basic information of the DC includes: DC identification information, DC location information, DC level information, and the like.

In the implementation, the technician of the server can obtain the basic information of all the DCs in the network architecture, and then store the basic information of the DCs in the NVFO, so that the NVFO can generate the DC resource pool according to the basic information of all the acquired DCs. Alternatively, the basic information of the DC may be reported by the DCs to the central DC. After the NVFO deployed in the central DC acquires the basic information of the DC, the related information may be supplemented in the DC resource pool. In this way, for the processing of the foregoing step 402, the NFVO obtains the NS deployment request, and after determining the at least one target VNF, the basic information can be selected in the DC resource pool to satisfy the DC selection according to the DC selection information added in the target VNFD corresponding to the target VNF. The target DC of the information.

Optionally, when a VNF is composed of multiple VDUs, the deployment of the VNF can be completed by deploying each VDU, and the corresponding processing can be performed as shown in FIG. 5:

Step 501: If the target VNF includes multiple target VDUs, the target VNFM selects the feature DC corresponding to the target VDU according to the DC selection information added in the VDUD corresponding to the target VDU.

In an implementation, after receiving the deployment request of the target VNF, the target DC may determine whether the target VNF includes multiple target VDUs according to the target VNFD, and if the target VNF includes multiple target VDUs, deploy to the target VNF for each target VDU. The target VNFM can select the feature DC that satisfies the deployment requirement of the target VDU according to the DC selection information added in the VDUD corresponding to the target VDU. Specifically, a "preferred DC" field may be added to the VDUD to describe the DC position requirement of the target VDU. The specific definition of the "preferred DC" field is the same as the "preferred DC" word in the VNFD, and is not described here. .

Step 502: The target VNFM sends a deployment request of the target VDU to the feature DC.

In an implementation, the target VNFM may send a deployment request of the target VDU to the feature DC after selecting the feature DC corresponding to the target VDU, where the deployment request may carry the identification information of the target VDU.

In step 503, the feature DC deploys the target VDU through the deployed feature VNFM and the feature VIM according to the target VDUD.

In an implementation, the feature DC may receive a deployment request of the target VDU sent by the target VNFM, so that the deployment of the target VDU may be completed by the feature VNFM and the feature VIM deployed on the feature DC according to the target VDUD. The process of deploying a VDU according to the VDUD belongs to the prior art, and is not specifically described in this embodiment.

Optionally, the VNFM may select the target DC according to the pre-recorded basic information of all the DCs, and the corresponding processing may be as follows: the target VNFM generates a DC resource pool according to the obtained basic information of all the DCs; the target VNFM is according to the VDUD corresponding to the target VDU. The DC selection information added in the DC resource pool selects the feature DC that satisfies the DC selection information in the DC resource pool.

In the implementation, the server technician can obtain the basic information of all the DCs in the network architecture, and then store the basic information of the DCs in the VNFM of each DC, so that the VNFM can generate DC resources according to the obtained basic information of all DCs. Pool. Alternatively, the DCs can send basic information to each other, so that the VNFM of the target DC can perform related supplementation in the DC resource pool after acquiring the basic information of the DC. In this way, for the processing of step 501 above, the VNFM may select the feature DC that satisfies the DC selection information in the DC resource pool according to the DC selection information added in the target VDUD corresponding to the target VDU.

Based on the same technical concept, an embodiment of the present invention further provides a system for deploying a VNF, where the system is deployed in a distributed DC network architecture, where the system includes at least NFVO, VNFM, and VIM, where:

The NFVO is used to obtain an NS deployment request, and determine at least one target VNF involved in the NS deployment request according to a preset NSD;

The NFVO is further configured to select a target DC corresponding to the target VNF according to the DC selection information added in the target VNFD corresponding to the target VNF;

The NFVO is further configured to send a deployment request of the target VNF to the target DC;

The target DC is configured to deploy the target VNF through the deployed target VNFM and the target VIM according to the target VNFD.

Optionally, the NFVO is further used to:

Generating a DC resource pool according to the obtained basic information of all DCs;

The NFVO is specifically used to:

The NFVO selects a target DC that satisfies the DC selection information in the DC resource pool according to the DC selection information added in the target VNFD corresponding to the target VNF.

Optionally, the target VNFM is further configured to: if the target VNF includes multiple target VDUs, select a feature DC corresponding to the target VDU according to DC selection information added in a VDUD corresponding to the target VDU, Sending a deployment request of the target VDU to the feature DC;

The feature DC is configured to deploy the target VDU by using the deployed feature VNFM and the feature VIM according to the target VDUD.

Optionally, the target VNFM is further used to:

The target VNFM is specifically used to:

And selecting, according to the DC selection information added in the VDUD corresponding to the target VDU, that the basic information satisfies the feature DC of the DC selection information in the DC resource pool.

A person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium. The storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

The above description is only an illustrative example of the present application, and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application are included in the protection of the present application. Within the scope.

Claims

A method for deploying a VNF, the method being applied to a network function virtualization NFV system, the NFV system being deployed in a distributed data center DC network architecture, the NFV system including at least a network function virtualization orchestration NFVO, Virtual Network Function Manager VNFM and Virtualization Infrastructure Manager VIM, where:

The NFVO acquires a network service NS deployment request, and determines at least one target virtual network function VNF involved in the NS deployment request according to a preset network service description NSD;

The NFVO selects a target DC corresponding to the target VNF according to the DC selection information added in the VNFD according to the target virtual network function corresponding to the target VNF;

Sending, by the NFVO, a deployment request of the target VNF to the target DC;

The target DC deploys the target VNF through the deployed target VNFM and the target VIM according to the target VNFD.
The method of claim 1, wherein the DC selection information comprises DC level information and/or DC location information, the DC location information comprising DC coverage area information, DC address information, coverage area radius, and/or DC coordinate information.
The method of claim 1 further comprising:

The NFVO generates a DC resource pool according to the obtained basic information of all DCs;

And selecting, by the NFVO, the target DC corresponding to the target VNF according to the DC selection information added in the target VNFD corresponding to the target VNF, including:

The NFVO selects a target DC that satisfies the DC selection information in the DC resource pool according to the DC selection information added in the target VNFD corresponding to the target VNF.
The method of claim 1 further comprising:

If the target VNF includes a plurality of target virtualization deployment unit VDUs, the target VNFM selects the DCs corresponding to the target VDUs according to the DC selection information added in the VDUDs according to the virtualization deployment unit corresponding to the target VDUs;

Sending, by the target VNFM, a deployment request of the target VDU to the feature DC;

The feature DC deploys the target VDU through the deployed feature VNFM and the feature VIM according to the target VDUD.
The method of claim 4, wherein the method further comprises:

The target VNFM generates a DC resource pool according to the obtained basic information of all DCs;

And selecting, by the target VNFM, the feature DC corresponding to the target VDU according to the DC selection information added in the VDUD corresponding to the target VDU, including:

The target VNFM selects, according to the DC selection information added in the VDUD corresponding to the target VDU, that the basic information satisfies the feature DC of the DC selection information in the DC resource pool.
A system for deploying a VNF, the system being deployed in a distributed data center DC network architecture, the system comprising at least a network function virtualization orchestrator NFVO, a virtual network function manager VNFM, and a virtualized infrastructure management VIM, where:

The NFVO is used to obtain a network service NS deployment request, and determine at least one target virtual network function VNF involved in the NS deployment request according to a preset network service description NSD;

The NFVO is further configured to: select, according to the target virtual network function corresponding to the target VNF, DC selection information added in the VNFD, and select a target DC corresponding to the target VNF;

The NFVO is further configured to send a deployment request of the target VNF to the target DC;

The target DC is configured to deploy the target VNF through the deployed target VNFM and the target VIM according to the target VNFD.
The system of claim 6 wherein said DC selection information comprises DC level information and/or DC location information, said DC location information comprising DC coverage area information, DC address information, coverage area radius and/or DC coordinate information.
The system of claim 6 wherein said NFVO is further used to:

Generating a DC resource pool according to the obtained basic information of all DCs;

The NFVO is specifically used to:

The NFVO selects a target DC that satisfies the DC selection information in the DC resource pool according to the DC selection information added in the target VNFD corresponding to the target VNF.
The system according to claim 6, wherein the target VNFM is further configured to: if the target VNF includes a plurality of target virtualization deployment unit VDUs, according to a virtualized deployment unit description corresponding to the target VDU The DC selection information added in the VDUD, the feature DC corresponding to the target VDU is selected, and the deployment request of the target VDU is sent to the feature DC;

The feature DC is configured to deploy the target VDU by using the deployed feature VNFM and the feature VIM according to the target VDUD.
The system of claim 9 wherein said target VNFM is further for:

Generating a DC resource pool according to the obtained basic information of all DCs;

The target VNFM is specifically used to:

And selecting, according to the DC selection information added in the VDUD corresponding to the target VDU, that the basic information satisfies the feature DC of the DC selection information in the DC resource pool.