CN105812171A - Virtualized network function VNF control method and device - Google Patents

Abstract

The invention discloses a virtualized network function VNF control method and device, comprising: by creating a VNF instance warehouse for direct communication with the VNFM, storing the VNFR of the VNF instance in the VNF instance warehouse, and the VNFM needs to control the VNF instance When operating, there is no need for NFVO coordination, or in the absence of NFVO, directly control the VNFR of the VNF instance in the VNF instance warehouse, or create a communication interface between the VNFM and the NFV instance warehouse, and the VNFM needs to control the VNF When the instance is operated, there is no need for NFVO coordination, or in the absence of NFVO, the VNFR in the NFV instance warehouse is directly controlled through the communication interface created between the NFV instance warehouse, that is, the required information is obtained from the NFV instance warehouse. The VNFR of the controlled VNF instance or directly modify the VNFR recorded in the NFV instance warehouse effectively improves the control efficiency of the VNF instance and saves resource consumption in the process of controlling the VNF instance.

Description

A virtualized network function VNF control method and device

technical field

The present invention relates to the technical field of network function virtualization, in particular to a virtualized network function VNF control method and equipment.

Background technique

With the development of Internet technology, the network deployed by network operators is composed of various physical devices. Different network services require different physical devices. Every time a new network service is developed, a new type of physical device needs to be added accordingly. However, it becomes more and more difficult to determine the spatial location of the new physical device and the power supply line with the increase of network services. difficult, which seriously inhibits the deployment of new network services.

In order to solve the above existing problems, a network function virtualization (abbreviation: NFV; English: NetworkFunctionsVirtualization) solution is proposed. Among them, network function virtualization refers to running network functions on common physical devices, and a common form is: deploying virtual machines on physical devices.

The currently proposed NFV architecture includes business operation and management platform (abbreviation: OSS/BSS; English: Operation-SupportSystem/BusinessSupportSystem), service, virtualized network function and basic equipment description unit (English: Service, VNF (English: VirtualNetworkFunction) andInfrastructureDescription), a network function virtualization management and orchestration platform (abbreviation: NFVM; English: NFVManagementandOrchestration), as shown in FIG. 1 , is a schematic structural diagram of the NFV architecture.

FIG. 2 is a schematic diagram of a specific service virtualization network architecture using NFV technology. In Figure 2, virtualization of communication business services is realized through NFV technology. In FIG. 2, the virtual resources provided by the virtualization layer can realize the virtualization of the functions of the short message center (such as the functions of the ring back tone server and the function of the mobile phone newspaper server), and obtain the corresponding VNF. These VNFs can perform life cycle management, deployment, expansion and contraction, etc. through the VNF manager; NFVO implements network service NS life cycle management (such as deployment/expansion/reduction/offline, etc.), policy management and other functions; NFVO cooperates with VNFM to realize Deployment of VNFs. Specifically, in addition to traditional management functions, the OSS/BSS interacts with the Orchestrator for virtualized applications to complete network operation and maintenance.

Service, virtualized network function and basic equipment description unit includes NS information model description template (abbreviation: NSD; English: NSDescriptor), VNF information model description template (abbreviation: VNFD; English: VNFDescriptor), virtual link description template ( Abbreviation: VLD; English: VirtualLinkDescriptor), VNF software image, etc.

The network function virtualization management and orchestration platform includes network function virtualization orchestration (abbreviation: NFVO; English: NFVOrchestration), VNF manager (abbreviation: VNFM; English: VNFManagement), virtualization infrastructure management system (abbreviation: VIM; English : VirtualInfrastructureManager) and NFVInstances.

Among them, the main function of NFVO is to manage the life cycle of network services (abbreviation: NS; English: NetworkService), and the resource arrangement and policy management of the infrastructure layer of NFV (abbreviation: NFVI; English: NFVInfrastructure). Among them, the life cycle includes: deployment, expansion, reduction, offline, etc.

The main function of VNFM is to manage the life cycle of VNF. For example: according to the VNF information model description template (abbreviation: VNFD; English: VNFDescriptor) and VNF capacity requirements, decompose the virtual resources required by the virtual machine, and cooperate with NFVO and VIM to complete the instantiation of VNF.

The main function of NFVInstances (also known as NFV instance warehouse) is to store VNF instances and NS instances. Among them, each VNF instance is represented by a VNF record (abbreviation: VNFR; English: VNFRecord), which stores the virtual resource layer information of the VNF instance; each NS instance is represented by an NS record (abbreviation: NSR; English: NSRecord ) to indicate that the virtual resource layer information of the NS instance is stored in the NSR.

VNFR and NSR stored in NFVInstances are managed by NFVO. In other words, there is a communication interface between NFVInstances and NFVO. If VNFM needs to find VNF instances from VNFR, it needs to be realized through the communication interface between NFVO and NFVInstances.

However, in the process of network function entity virtualization, if VNFM wants to obtain the virtual resource layer information of VNF instances, it needs to read from VNFR through the communication interface between NFVO and NFVInstances, but for a single network element, it does not Network-level virtualization of multiple network elements is required, so VNFM controls the VNF instance of a single network element through the communication interface between NFVO and NFVInstances, which not only increases the system resource overhead, but also makes VNFM control the single network element The control efficiency of the VNF instance is reduced.

Contents of the invention

In view of this, the embodiments of the present invention provide a virtualized network function VNF control method and device to solve the current problems of low VNFM control efficiency and large system resource overhead for a VNF instance of a single network element.

In the first aspect, a virtualized network function VNF control method is provided, including:

The VNF manager VNFM receives the VNF operation request, wherein the VNF operation request includes operation information about the VNF instance;

The VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNF record VNFR of the VNF instance in the VNF instance warehouse.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the VNF operation request is a request for creating a VNF instance, where the request for creating a VNF instance includes a designated network element of the VNF instance to be created;

The VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNFR of the VNF instance in the VNF instance warehouse, including:

The VNFM sends a virtual resource request to the virtualization infrastructure management system VIM according to the designated network element of the VNF instance to be created included in the VNF instance creation request, wherein the virtual resource request is used to request the VIM to create The VNF instance of the specified network element allocates the required virtual resources;

The VNFM receives the virtual resource allocated by the VIM, and starts to create the VNF instance of the specified network element according to the virtual resource;

After the VNFM successfully creates the VNF instance of the specified network element, it stores the VNFR of the VNF instance in the VNF instance warehouse.

With reference to the first possible implementation manner of the first aspect, in the second possible implementation manner of the first aspect, the VNFM, according to the designated network element of the VNF instance to be created included in the VNF instance creation request, Send a virtual resource request to VIM, including:

When the VNFM determines that the VNF instance creation request received comes from the network function orchestrator NFVO, or when it determines that the management domain where the VNFM is located does not include the NFVO, according to the pending VNF instance request included in the VNF instance creation request Create a designated network element of a VNF instance and send a virtual resource request to the VIM.

With reference to the first possible implementation manner of the first aspect, in the third possible implementation manner of the first aspect, the VNFM, according to the designated network element of the VNF instance to be created included in the VNF instance creation request, Send a virtual resource request to VIM, including:

When the VNFM determines that the management domain where the VNFM is located includes NFVO and the received request for creating a VNF instance is not from the NFVO, it further determines whether the designated network element of the VNF instance to be created is capable of independently executing services network element;

When the VNFM determines that the specified network element of the VNF instance to be created is a network element capable of independently executing services, it sends a virtual resource request to the VIM.

With reference to the third possible implementation manner of the first aspect, in the fourth possible implementation manner of the first aspect, the VNFM, according to the designated network element of the VNF instance to be created included in the VNF instance creation request, Send a virtual resource request to VIM, including:

When the VNFM cannot determine whether the specified network element of the VNF instance to be created is a network element that can independently perform services, send a creation permission request to the NFVO; and

When receiving the permission creation information sent by the NFVO, send a virtual resource request to the VIM.

With reference to the first aspect, in a fifth possible implementation manner of the first aspect, the VNF operation request is a request for querying a VNF instance, where the request for querying a VNF instance includes an identifier of the VNF instance to be queried;

The VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNFR of the VNF instance in the VNF instance warehouse, including:

The VNFM sends a VNFR query request to the VNF instance repository according to the identifier of the VNF instance to be queried included in the query VNF instance request, wherein the VNFR query request includes the identifier of the VNF instance to be queried;

The VNFM receives the VNFR information corresponding to the identifier of the VNF instance to be queried and sent by the VNF instance warehouse.

With reference to the first aspect, in a sixth possible implementation manner of the first aspect, the operation request is a request for updating a VNF instance, where the request for updating a VNF instance includes an identifier of the VNF instance to be updated;

The VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNFR of the VNF instance in the VNF instance warehouse, including:

The VNFM sends a VNFR query request to the VNF instance warehouse according to the identification of the VNF instance to be updated included in the update VNF instance request, wherein the VNFR query request includes the identification of the VNF instance to be updated;

The VNFM receives the VNFR information corresponding to the identifier of the VNF instance to be updated sent by the VNF instance repository;

The VNFM sends a virtual resource request to the VIM according to the received VNFR information, where the virtual resource request is used to request the VIM to allocate virtual resources required for updating to the VNF instance described by the VNFR information;

The VNFM receives the virtual resource allocated by the VIM, and starts updating the VNF instance described in the VNFR information according to the virtual resource;

After the VNFM finishes updating the VNF instance, it updates the VNFR information corresponding to the identifier of the VNF instance to be updated in the VNF instance repository.

With reference to the sixth possible implementation manner of the first aspect, in a seventh possible implementation manner of the first aspect, the VNFM sends a virtual resource request to the VIM according to the received VNFR information, including:

The VNFM sends a virtual resource request to the VIM according to the received VNFR information when determining that the received update VNF instance request is from the NFVO, or when determining that the management domain where the VNFM is located does not include the NFVO .

With reference to the sixth possible implementation manner of the first aspect, in an eighth possible implementation manner of the first aspect, the VNFM sends a virtual resource request to the VIM according to the received VNFR information, including:

When the VNFM determines that the management domain where the VNFM is located contains NFVO and the received request to update the VNF instance is not from the NFVO, it further judges the VNFR information described in the VNFR information according to the received VNFR information. Whether there is an association relationship between the VNF instance to be updated and the network service NS;

When the VNFM determines that there is no association relationship between the VNF instance to be updated described in the VNFR information and the NS, it sends a virtual resource request to the VIM.

With reference to the eighth possible implementation manner of the first aspect, in a ninth possible implementation manner of the first aspect, the VNFM sends a virtual resource request to the VIM according to the received VNFR information, including:

When the VNFM determines that there is an association between the VNF instance to be updated described in the VNFR information and the NS, it sends an update permission request to the NFVO, wherein the update permission request includes the VNF to be updated the identity of the instance; and

When receiving the update permission information sent by the NFVO, send a virtual resource request to the VIM.

With reference to the first aspect, in a tenth possible implementation manner of the first aspect, the operation request is a request to terminate a VNF instance, where the request to terminate a VNF instance includes an identifier of the VNF instance to be terminated;

The VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNFR of the VNF instance in the VNF instance warehouse, including:

The VNFM sends a VNFR query request to the VNF instance warehouse according to the identifier of the VNF instance to be terminated included in the request for terminating the VNF instance, wherein the VNFR query request includes the identifier of the VNF instance to be terminated;

The VNFM receives the VNFR information corresponding to the identifier of the VNF instance to be terminated sent by the VNF instance warehouse;

The VNFM terminates the VNF instance according to the received VNFR information, and sends a virtual resource deletion operation to the VIM, wherein the virtual resource deletion operation includes the virtual resources of the VNF instance to be terminated described in the received VNFR information. resource information;

The VNFM receives the virtual resource deletion response message sent by the VIM, and sends a VNFR deletion request to the VNF instance repository, wherein the VNFR deletion request includes the identifier of the VNF instance to be deleted.

With reference to the tenth possible implementation manner of the first aspect, in the eleventh possible implementation manner of the first aspect, the VNFM sends a virtual resource deletion operation to the VIM according to the received VNFR information, including:

When the VNFM determines that the received request for terminating the VNF instance comes from the NFVO, or when it determines that the management domain where the VNFM is located does not include the NFVO, it terminates the VNF instance according to the received VNFR information, and reports to the VIM Send a virtual resource delete operation.

With reference to the tenth possible implementation manner of the first aspect, in a twelfth possible implementation manner of the first aspect, the VNFM sends a virtual resource deletion operation to the VIM according to the received VNFR information, including:

When the VNFM determines that the management domain where the VNFM is located includes NFVO and the received request to terminate the VNF instance is not from the NFVO, further judge the VNFR information described in the VNFR information according to the received VNFR information. Whether there is an association relationship between the VNF instance to be terminated and the NS;

When the VNFM determines that there is no association relationship between the VNF instance to be terminated and the NS described in the VNFR information, it terminates the VNF instance and sends a virtual resource deletion operation to the VIM.

With reference to the twelfth possible implementation manner of the first aspect, in a thirteenth possible implementation manner of the first aspect, the VNFM sends a virtual resource deletion operation to the VIM according to the received VNFR information, including :

When the VNFM determines that there is an association between the VNF instance to be terminated and the NS described in the VNFR information, it sends a termination permission request to the NFVO, wherein the termination permission request includes the VNF instance to be terminated identify; and

When receiving the permission termination information sent by the NFVO, terminate the VNF instance, and send a virtual resource deletion operation to the VIM.

In combination with the first aspect, or in combination with the first possible implementation manner of the first aspect, or in combination with the second possible implementation manner of the first aspect, or in combination with the third possible implementation manner of the first aspect, or in combination with the second possible implementation manner of the first aspect The fourth possible implementation manner of one aspect, or the fifth possible implementation manner of combining the first aspect, or the sixth possible implementation manner of combining the first aspect, or the seventh possible implementation manner of combining the first aspect Embodiment, or the eighth possible implementation manner in combination with the first aspect, or the ninth possible implementation manner in combination with the first aspect, or the tenth possible implementation manner in combination with the first aspect, or in combination with the first aspect The eleventh possible implementation manner of the first aspect, or the twelfth possible implementation manner in combination with the first aspect, or the thirteenth possible implementation manner in combination with the first aspect, and the fourteenth possible implementation manner in the first aspect In an embodiment, the method also includes:

If the management domain where the VNFM is located includes NFVO, the VNFM sends a notification message to the NFVO after processing the VNF instance, where the notification message includes the identifier of the VNF instance.

In the second aspect, a virtualized network function VNF control device is provided, including:

A receiving unit, configured to receive a VNF operation request, wherein the VNF operation request includes operation information about the VNF instance;

The control unit is configured to process the VNF instance according to the operation information contained in the VNF operation request received by the receiving unit, and control the VNF record VNFR of the VNF instance in the VNF instance warehouse.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the VNF operation request is a request for creating a VNF instance, where the request for creating a VNF instance includes a designated network element of the VNF instance to be created;

The control unit is specifically configured to send a virtual resource request to the virtualization infrastructure management system VIM according to the specified network element of the VNF instance to be created included in the VNF instance creation request, wherein the virtual resource request is used to request The VIM allocates required virtual resources for creating a VNF instance of a specified network element;

receiving the virtual resource allocated by the VIM, and starting to create a VNF instance of the specified network element according to the virtual resource;

After the VNF instance of the specified network element is successfully created, the VNFR of the VNF instance is stored in the VNF instance warehouse.

With reference to the first possible implementation manner of the second aspect, in the second possible implementation manner of the second aspect, the control unit is specifically configured to determine that the received VNF instance creation request comes from a network function The orchestrator NFVO, or when determining that the management domain where it is located does not include the NFVO, sends a virtual resource request to the VIM according to the designated network element of the VNF instance to be created contained in the VNF instance creation request.

With reference to the first possible implementation manner of the second aspect, in a third possible implementation manner of the second aspect, the control unit is specifically configured to include NFVO in the management domain where it is located, and receive When the request for creating a VNF instance is not from the NFVO, further determine whether the designated network element of the VNF instance to be created is a network element that can independently perform services;

When it is determined that the designated network element of the VNF instance to be created is a network element capable of independently performing services, a virtual resource request is sent to the VIM.

With reference to the third possible implementation manner of the second aspect, in the fourth possible implementation manner of the second aspect, the control unit is specifically configured to determine whether the designated network element of the VNF instance to be created is When it is a network element that can independently perform services, send a creation permission request to the NFVO; and

When receiving the permission creation information sent by the NFVO, send a virtual resource request to the VIM.

With reference to the second aspect, in a fifth possible implementation manner of the first aspect, the VNF operation request is a request for querying a VNF instance, wherein the request for querying a VNF instance includes an identifier of the VNF instance to be queried;

The control unit is specifically configured to send a VNFR query request to the VNF instance repository according to the identifier of the VNF instance to be queried contained in the query VNF instance request, wherein the VNFR query request contains the VNF instance to be queried Identification of the VNF instance;

Receive the VNFR information corresponding to the identifier of the VNF instance to be queried sent by the VNF instance repository.

With reference to the second aspect, in a sixth possible implementation manner of the second aspect, the operation request is a request for updating a VNF instance, where the request for updating a VNF instance includes an identifier of the VNF instance to be updated;

The control unit is specifically configured to send a VNFR query request to the VNF instance warehouse according to the identifier of the VNF instance to be updated included in the update VNF instance request, wherein the VNFR query request includes the VNF instance to be updated Identification of the VNF instance;

receiving VNFR information corresponding to the identifier of the VNF instance to be updated sent by the VNF instance repository;

Sending a virtual resource request to the VIM according to the received VNFR information, where the virtual resource request is used to request the VIM to allocate virtual resources required for updating to the VNF instance described in the VNFR information;

receiving the virtual resource allocated by the VIM, and starting to update the VNF instance described in the VNFR information according to the virtual resource;

After the update of the VNF instance is completed, the VNFR information corresponding to the identifier of the VNF instance to be updated in the VNF instance warehouse is updated.

With reference to the sixth possible implementation manner of the second aspect, in a seventh possible implementation manner of the second aspect, the control unit is specifically configured to, when determining that the received request for updating the VNF instance is from the NFVO, or When it is determined that the management domain where it is located does not include the NFVO, send a virtual resource request to the VIM according to the received VNFR information.

With reference to the sixth possible implementation manner of the second aspect, in an eighth possible implementation manner of the second aspect, the control unit is specifically configured to determine that the management domain where it is located contains NFVO and receives all When the request for updating the VNF instance is not from the NFVO, further determine whether there is an association relationship between the VNF instance to be updated described in the VNFR information and the network service NS according to the received VNFR information;

When it is determined that there is no association relationship between the VNF instance to be updated described in the VNFR information and the NS, a virtual resource request is sent to the VIM.

With reference to the eighth possible implementation manner of the second aspect, in a ninth possible implementation manner of the second aspect, the control unit is specifically configured to match the VNF instance to be updated described in the VNFR information with When there is an association relationship between NSs, send an update permission request to the NFVO, where the update permission request includes the identifier of the VNF instance to be updated; and

When receiving the update permission information sent by the NFVO, send a virtual resource request to the VIM.

With reference to the second aspect, in a tenth possible implementation manner of the second aspect, the operation request is a request to terminate a VNF instance, where the request to terminate a VNF instance includes an identifier of the VNF instance to be terminated;

The control unit is specifically configured to send a VNFR query request to the VNF instance repository according to the identifier of the VNF instance to be terminated included in the request for terminating the VNF instance, wherein the VNFR query request includes the VNF instance to be terminated. Identification of the VNF instance;

receiving VNFR information corresponding to the identifier of the VNF instance to be terminated sent by the VNF instance warehouse;

Terminate the VNF instance according to the received VNFR information, and send a virtual resource deletion operation to the VIM, wherein the virtual resource deletion operation includes the virtual resource information of the VNF instance to be terminated described in the received VNFR information;

Receive the virtual resource deletion response message sent by the VIM, and send a VNFR deletion request to the VNF instance repository, where the VNFR deletion request includes the identifier of the VNF instance to be deleted.

With reference to the tenth possible implementation manner of the second aspect, in the eleventh possible implementation manner of the second aspect, the control unit is specifically configured to determine that the received request to terminate the VNF instance is from the NFVO, Or when it is determined that the NFVO is not included in the management domain where it is located, the VNF instance is terminated according to the received VNFR information, and a virtual resource deletion operation is sent to the VIM.

With reference to the tenth possible implementation manner of the second aspect, in a twelfth possible implementation manner of the second aspect, the control unit is specifically configured to include the NFVO in the management domain where it is located and receive the When the request to terminate the VNF instance is not from the NFVO, further judge whether there is an association relationship between the VNF instance to be terminated and the NS described in the VNFR information according to the received VNFR information;

When it is determined that there is no association relationship between the VNF instance to be terminated described in the VNFR information and the NS, the VNF instance is terminated, and a virtual resource deletion operation is sent to the VIM.

With reference to the twelfth possible implementation manner of the second aspect, in a thirteenth possible implementation manner of the second aspect, the control unit is specifically configured to determine the VNF to be terminated described in the VNFR information When there is an association relationship between the instance and the NS, send a termination permission request to the NFVO, wherein the termination permission request includes the identifier of the VNF instance to be terminated; and

When receiving the permission termination information sent by the NFVO, terminate the VNF instance, and send a virtual resource deletion operation to the VIM.

In combination with the second aspect, or in combination with the first possible implementation manner of the second aspect, or in combination with the second possible implementation manner of the second aspect, or in combination with the third possible implementation manner of the second aspect, or in combination with the first possible implementation manner of the second aspect The fourth possible implementation of the second aspect, or the fifth possible implementation of the second aspect, or the sixth possible implementation of the second aspect, or the seventh possible implementation of the second aspect Embodiment, or the eighth possible implementation manner in combination with the second aspect, or the ninth possible implementation manner in combination with the second aspect, or the tenth possible implementation manner in combination with the second aspect, or in combination with the second aspect The eleventh possible implementation manner of the second aspect, or the twelfth possible implementation manner in combination with the second aspect, or the thirteenth possible implementation manner in combination with the second aspect, and the fourteenth possible implementation manner in the second aspect In an implementation manner, the control device further includes: a sending unit, wherein:

The sending unit is configured to send a notification message to the NFVO after the VNF instance is processed if the management domain where it is located includes the NFVO, wherein the notification message includes the identifier of the VNF instance.

In the embodiment of the present invention, the VNFM receives a VNF operation request, and the VNF operation request contains operation information about the VNF instance; the VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNF instance warehouse The VNFR of the VNF instance described in . By creating a VNF instance warehouse that directly communicates with the VNFM, the VNFR of the VNF instance is stored in the VNF instance warehouse, so that when the VNFM needs to operate the VNF instance, it can directly operate the VNF in the VNF instance warehouse without NFVO coordination. The VNFR of the instance is managed, which improves the control efficiency of the VNF instance and saves resource consumption in the process of controlling the VNF instance.

In a third aspect, a virtualized network function VNF control method is provided, including:

The VNF manager VNFM receives the VNF operation request, wherein the VNF operation request includes operation information about the VNF instance;

The VNFM processes the VNF instance according to the operation information included in the VNF operation request, and controls the VNF record VNFR of the VNF instance in the NFV instance repository through the communication interface with the NFV instance repository.

In a fourth aspect, a virtualized network function VNF control device is provided, including:

A receiving unit, configured to receive a VNF operation request, wherein the VNF operation request includes operation information about the VNF instance;

A control unit, configured to process the VNF instance according to the operation information contained in the VNF operation request, and control the VNF record of the VNF instance in the NFV instance repository through the communication interface with the NFV instance repository VNFR.

In the embodiment of the present invention, the VNFM receives a VNF operation request, and the VNF operation request contains operation information about the VNF instance; the VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and communicates with the NFV The communication interface between the instance warehouses controls the VNFR of the VNF instance in the NFV instance warehouse, so that when the VNFM needs to control the VNF instance in the future, there is no need for NFVO coordination, or if there is no NFVO, it can directly communicate with The communication interface created between the NFV instance warehouses controls the VNFR in the NFV instance warehouse, that is, obtains the VNFR of the VNF instance that needs to be controlled from the NFV instance warehouse, which improves the control efficiency of the VNF instance and saves the time spent on the VNF instance Resource consumption during control.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings that need to be used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention. For Those of ordinary skill in the art can also obtain other drawings based on these drawings without any creative effort.

FIG. 1 is a schematic structural diagram of the NFV architecture;

FIG. 2 is a schematic diagram of a network architecture of a specific service virtualization using NFV technology;

FIG. 3 is a schematic structural diagram of an NFV architecture provided by an embodiment of the present invention;

FIG. 4 is a schematic flowchart of a VNF control method provided by an embodiment of the present invention;

FIG. 5 is a schematic flowchart of a method for creating a VNF provided by an embodiment of the present invention;

FIG. 6 is a schematic flowchart of a VNF query method provided by an embodiment of the present invention;

FIG. 7 is a schematic flowchart of a VNF update method provided by an embodiment of the present invention;

FIG. 8 is a schematic flowchart of a VNF termination method provided by an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of an NFV architecture provided by an embodiment of the present invention;

FIG. 10 is a schematic flowchart of a VNF control method provided by an embodiment of the present invention;

FIG. 11 is a schematic structural diagram of a VNF control device provided by an embodiment of the present invention;

Fig. 12 is a schematic structural diagram of a VNF control device provided by an embodiment of the present invention.

detailed description

In order to achieve the purpose of the present invention, the embodiment of the present invention provides a VNF control method and device, by creating a VNF instance warehouse that directly communicates with the VNFM, and storing the VNFR of the VNF instance in the VNF instance warehouse. When the VNF instance operates, there is no need for NFVO coordination, or in the absence of NFVO, directly control the VNFR of the VNF instance in the VNF instance warehouse, or create a communication interface between the VNFM and the NFV instance warehouse, and the VNFM needs When operating VNF instances, there is no need for NFVO coordination, or in the absence of NFVO, the VNFR in the NFV instance warehouse is directly controlled through the communication interface created with the NFV instance warehouse, that is, from the NFV instance warehouse Obtaining the VNFR of the VNF instance to be controlled or directly modifying the VNFR recorded in the NFV instance warehouse effectively improves the control efficiency of the VNF instance and saves resource consumption in the process of controlling the VNF instance.

Various embodiments of the present invention will be further described in detail below in conjunction with the accompanying drawings. Apparently, the described embodiments are only some of the embodiments of the present invention, but not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

FIG. 3 is a schematic structural diagram of an NFV architecture provided by an embodiment of the present invention. The embodiment of the present invention adds a VNF instance warehouse on the basis of the current NFV architecture, and the VNFM directly communicates with the VNF instance warehouse, for example: when creating a VNF instance of a specified network element, store the VNFR of the VNF instance in the VNF In the instance warehouse, when the VNFM needs to operate the VNF instance of the specified network element, there is no need for NFVO coordination, or if there is no NFVO, the VNFR of the VNF instance of the specified network element is obtained directly from the VNF instance warehouse. The virtual resource information of the VNF instance is obtained through the VNFR, which improves the control efficiency of the VNF instance and saves resource consumption in the process of controlling the VNF instance.

Fig. 4 is a schematic flowchart of a VNF control method provided by an embodiment of the present invention. The embodiment of the present invention controls the VNF instance in the NFV architecture shown in FIG. 3 . The method can be described as follows.

Step 101: The VNFM receives a VNF operation request.

Wherein, the VNF operation request includes operation information about the VNF instance.

In step 101, the VNFM receives the VNF operation request. The VNF operation request can come from the operation support management system (abbreviation: OSS; English: OperationSupportSystem); it can also come from network element management (abbreviation: EM; English: ElementManagement); it can also come from NFVO , the source of the VNF operation request is not limited here.

It should be noted that the VNF operation request includes at least one of the following:

Create a VNF instance request, modify (or update) a VNF instance request, terminate a VNF instance request, query a VNF instance request, and so on.

Step 102: The VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNFR of the VNF instance in the VNF instance warehouse.

Wherein, the operation information may refer to an operation object, an identifier corresponding to the operation, and the like. For example: the VNF instance creation request includes the specified network element of the VNF instance to be created; the VNF instance query request includes the identifier of the VNF instance to be queried; and so on.

In step 102, the VNFM specifies the VNF management operation and the corresponding virtual resource operation to be performed according to the VNF operation request.

Wherein, the virtual resource operation includes at least one of the following: acquiring virtual resources, querying virtual resources, updating virtual resources, applying for virtual resource expansion, applying for virtual resource migration, virtual resource reservation, operating virtual resources, virtual resource migration, etc.

Fig. 5 is a schematic flowchart of a method for creating a VNF provided by an embodiment of the present invention. In the embodiment of the present invention, the creation of the VNF instance is completed in the NFV architecture shown in FIG. 3 . The method can be described as follows.

Step 201: VNFM receives a request to create a VNF instance.

Wherein, the request for creating a VNF instance includes a designated network element of the VNF instance to be created.

In step 201, when the OSS needs to instantiate a new VNF, it sends a VNF instance creation request to the VNFM, and specifies the network element information for which the VNF instance needs to be created in the VNF instance creation request. For example: short message center, ring back tone center, mobile phone newspaper server, etc.

In addition, the VNF instance creation request can also be sent by OSS/BSS, EM, NFVO, etc. Here, there is no limitation on who sends the VNF instance creation request.

Step 202: The VNFM sends a virtual resource request to the VIM according to the designated network element of the VNF instance to be created contained in the VNF instance creation request.

Wherein, the virtual resource request is used to request the VIM to allocate required virtual resources for creating a VNF instance of a specified network element.

In step 202, the VNFM determines the resources to be applied for according to the designated network element of the VNF instance to be created included in the VNF instance creation request, and the situation of sending a virtual resource request to the VIM includes but is not limited to:

First case:

When the VNFM determines that the VNF instance creation request received is from an NFVO, or determines that the management domain where the VNFM is located does not include the NFVO, according to the VNF instance to be created contained in the VNF instance creation request, Designate network elements, determine the resources to be applied for, and send virtual resource requests to the VIM.

Specifically, if the VNF instance creation request comes from the NFVO, the VNFM can determine that the NFVO needs the VNFM to execute the operation of creating a new VNF instance, and can directly send the virtual resource request to the VIM.

Second case:

When the VNFM determines that the management domain where the VNFM is located includes NFVO and the received request for creating a VNF instance is not from the NFVO, it further determines whether the request for creating a VNF instance includes an identifier for independently executing services.

When the VNFM determines that the request for creating a VNF instance contains an identifier for independently executing services, it determines the resources to be applied for according to the specified network element of the VNF instance to be created contained in the request for creating a VNF instance, and sends a virtual message to the VIM. resource request.

Specifically, when the VNFM receives the request for creating a VNF instance, if the request for creating a VNF instance includes an identifier for independently executing services, it determines that the designated network element that needs to create a VNF instance is a network element that independently executes services, that is, It means that when VNFM creates the VNF instance of the specified network element, it does not need to obtain the creation permission from NFVO, that is, it does not need the assistance of NFVO, and directly determines the For resources that need to be applied for, send a virtual resource request to VIM.

When the VNFM cannot determine whether the specified network element of the VNF instance to be created is a network element that can independently perform services, send a creation permission request to the NFVO; and when receiving the permission creation information sent by the NFVO, According to the specified network element of the VNF instance to be created included in the VNF instance creation request, determine the resources to be applied for, and send a virtual resource request to the VIM.

Specifically, when the VNFM receives the request to create a VNF instance, if the request to create the VNF instance does not include the identifier of the independent execution service, the VNFM may, according to the stored management information or the VNFD information of the designated network element of the VNF instance to be created , or obtain all the VNFR information corresponding to the specified network element of the VNF instance to be created from the VNF instance warehouse to determine whether the specified network element to be created is a network element that can independently perform services.

After the VNFM determines that the designated network element that needs to create a VNF instance is a network element that independently executes services, the VNFM directly determines the resources that need to be applied for according to the designated network element of the VNF instance to be created contained in the VNF instance creation request, and sends to the VIM Send a virtual resource request.

When the VNFM cannot determine whether the specified network element that needs to create a VNF instance is a network element that can independently perform services, the VNFM sends a creation permission request to the NFVO, and when receiving the permission creation information sent by the NFVO, creates the VNF according to the The designated network element of the VNF instance to be created included in the instance request determines the resources to be applied for, and sends a virtual resource request operation to the VIM.

It should be noted that the VNF instance creation request received by the VNFM is not from the NFVO, but may be from the OSS/BSS, EM or other network elements.

The VNFM determines the resource to be applied for according to the designated network element of the VNF instance to be created contained in the VNF instance creation request, sends a virtual resource request to the VIM, and inquires whether there is an available virtual resource.

Wherein, the VNFM can determine the resources to be applied for according to the virtual resource information in the VNFD, such as: central processing unit (abbreviation: CPU; English: CentralProcessingUnit) resources, memory resources, etc., and the virtual resource request sent to the VIM includes creating The virtual resources required by the VNF instance.

Specifically, before the VNFM sends a virtual resource request to the VIM, it sends a virtual resource query request to the VIM to check whether there are virtual resources required to support the VNFM;

VIM determines whether to support the virtual resources required by VNFM according to the received request for querying virtual resources. If it is determined to support the virtual resources required by VNFM, it sends a virtual resource confirmation response message to VNFM to confirm that the virtual resources required by VNFM can be provided.

Or, the VNFM sends a resource reservation request to the VIM before sending a virtual resource request to the VIM, so that the VIM performs a resource reservation operation when receiving the resource reservation request sent by the VNFM, and sends a virtual resource reservation response to the VNFM .

Alternatively, before sending the virtual resource request to the VIM, the VNFM first sends a virtual resource query request to the VIM, and then sends a resource reservation request to the VIM after receiving the virtual resource confirmation response sent by the VIM.

Step 203: The VNFM receives the virtual resource allocated by the VIM, and starts to create a VNF instance of the designated network element according to the virtual resource.

In step 203, the VNFM sends a virtual resource acquisition request to the VIM, the virtual resource acquisition request includes virtual resource requirements for creating a VNF instance, and the VIM determines whether to support VNFM when receiving the virtual resource acquisition request sent by the VNFM The required virtual resources, if it is determined to support the virtual resources required by the VNFM, allocate virtual resources for the VNF instance to be created, and send a response of successful allocation to the VNFM.

Wherein, the allocated virtual resource may include a virtual machine identifier, a container (English: Container) identifier, and the like.

The VNFM records the allocated virtual resources, and the recorded virtual resources include underlying virtual resources such as virtual machine identifiers and container identifiers, and saves the recorded virtual resources in the VNFR of the VNF instance.

As shown in Table 1, it is the virtual resource recorded in VNFR:

Table 1

Among them, the virtual deployment unit (abbreviation: VDU; English: VirtualDeploymentUnit) is a data collection, including but not limited to: virtual machine image (English: image), the number of instances (English: instances), CPU information (for example: CPU mode, clock), memory information, storage space information, etc.

The VNFM performs a VNF instantiation operation on the corresponding virtual machine or container according to the allocated virtual resources, that is, starts to create the VNF instance of the specified network element.

Step 204: After successfully creating the VNF instance of the specified network element, the VNFM stores the VNFR of the VNF instance in the VNF instance warehouse.

In step 204, after the VNFM successfully starts the VNF instance of the specified network element, it generates the VNFR of the VNF instance, and stores the VNFR of the VNF instance in the VNF through the communication interface with the VNF instance warehouse. In the instance repository.

Or, after successfully creating the new VNF instance of the specified network element, the VNFM sends the information of the VNF instance to the VNF instance warehouse through the communication interface with the VNF instance warehouse, and the information of the VNF instance may include virtual For resource information, VDU information, connection information, interfaces of VNF instances, network address information, etc., the VNF instance repository stores the information of the VNF instances in VNFR format.

After the VNFM successfully creates and starts the VNF instance, it sends a VNF instantiation success message to the EM. The EM configures the VNF instance, that is, configures service parameters and other information into the instantiated VNF.

If the specified network element instantiated in the embodiment of the present invention is a short message center, then the EM configures the service parameters of the short message center on the short message center already running on the virtual machine.

If the management domain where the VNFM is located includes NFVO, the VNFM sends a notification message to the NFVO after successfully creating the VNF instance of the specified network element.

Wherein, the notification message includes the identifier of the VNF instance of the designated network element, so that the identifier of the VNF instance of the designated network element is registered in the NFVO.

It should be noted that the notification message may be a notification message or a response message, which is not limited here.

For example: if in step 202, the second situation is adopted, that is, the management domain where the VNFM is located includes NFVO, the VNFM sends a notification message to the NFVO after successfully creating the VNF instance of the specified network element.

If in step 202, the first situation is adopted and the VNF instance creation request comes from the NFVO, then the VNFM sends a response message to the NFVO.

Specifically, the VNFM sends a notification message to the NFVO through the Hypertext Transfer Protocol (abbreviation: HTTP; English: HyperTextTransferProtocol), and includes the Uniform Resource Locator (abbreviation: URL; English: UniformResourceLocator) in the header of the HTTP message. Specifies the ID of the VNF instance of the NE.

On the basis of the embodiment of the present invention, NFVO is the main body of the network service, and when the VNF instance needs to be added to a network service (English: NetworkService), the following operations can be performed:

Step 1: NFVO receives NS establishment or capacity expansion request.

Wherein, the NS establishment or capacity expansion request includes the ID of the NS.

Step 2: NFVO determines the VNF that needs to be added according to the content recorded in the NS information model description template (abbreviation: NSD; English: NSDescriptor), for example, the VNFD contained in the NSD.

For example: according to the content recorded in the NSD, the NFVO determines that the NS corresponding to the NS identifier contains at least two VNFs. If there is no parent-ns information in the VNFR of one of the VNFs (hereinafter referred to as VNF1), the NFVO can determine that the existing VNF instances of the VNF1 exist as independent VNF instances.

Step 3: NFVO initiates a request to add a VNF instance of VNF1 to the VNFM that manages VNF1. After the newly added VNF instance corresponding to VNF1 is successfully created from the VNFM, according to the received identifier of the newly added VNF instance of VNF1, in Add parent-ns information to the VNFR corresponding to the ID of the newly added VNF instance. The parent-ns information is the ID of the newly created NS instance that needs to be expanded, such as the ID of an NS record (English: NetworkServiceRecord; abbreviation: NSR).

Step 4: NFVO sends a notification message to the VNFM.

Wherein, the notification message includes the identifier of the newly added VNF instance of VNF1 modified by the NFVO.

Further, the notification message may directly indicate changes and operations performed on the VNFR. For example, different notification message types may be used to indicate different operations on the VNFR; the message may also contain network service information associated with the newly added VNF instance of VNF1, such as the NSR identifier.

Step 5: When the VNFM receives the notification message, it determines that the NFVO has updated the VNFR corresponding to the VNF instance identifier according to the VNF instance identifier included in the notification message.

Furthermore, the VNFM may determine that the newly added VNF instance of VNF1 has been modified into a VNF instance that does not independently execute services according to the type of the received notification message or the content of the notification message.

VNFM can also query VNFR information in the VNF instance warehouse according to the VNF instance ID, and determine whether the VNF instance has been modified to a VNF instance that does not independently execute services according to the queried VNFR information.

FIG. 6 is a schematic flowchart of a VNF query method provided by an embodiment of the present invention. In the embodiment of the present invention, in the NFV architecture shown in FIG. 3 , a query operation is performed on the VNFR information in the VFN instance warehouse.

Step 301: The VNFM receives a request for querying a VNF instance.

Wherein, the query VNF instance request includes the identifier of the VNF instance to be queried.

Step 302: The VNFM sends a VNFR query request to the VNF instance warehouse according to the identifier of the VNF instance to be queried included in the VNF instance query request.

Wherein, the VNFR query request includes the identifier of the VNF instance to be queried.

In step 302, if in the NFV architecture, one VNFM corresponds to multiple VNF instance warehouses, if the VNF query request received by the VNFM contains the identifier of the VNF instance warehouse, then the VNFM The identifier of the warehouse, and send a VNFR query request to the VNF instance warehouse corresponding to the identifier of the VNF instance warehouse.

Alternatively, the VNFM determines the VNF instance warehouse corresponding to the identifier of the VNF instance to be queried according to the identifier of the VNF instance to be queried in the VNF query request.

Step 303: The VNFM receives the VNFR information corresponding to the ID of the VNF instance to be queried from the VNF instance warehouse.

FIG. 7 is a schematic flowchart of a VNF updating method provided by an embodiment of the present invention. In the embodiment of the present invention, in the NFV architecture shown in FIG. 3 , an update operation is performed on the VNFR information in the VNF instance warehouse.

Step 401: VNFM receives a request to update a VNF instance.

Wherein, the update VNF instance request includes the identifier of the VNF instance to be updated.

Step 402: The VNFM sends a VNFR information query request to the VNF instance repository according to the identifier of the VNF instance to be updated included in the update VNF instance request.

Wherein, the VNFR information query request includes the identifier of the VNF instance to be updated.

In step 402, if in the NFV architecture, one VNFM corresponds to multiple VNF instance warehouses, if the VNF update request received by the VNFM also includes the identifier of the VNF instance warehouse, then the VNFM will update the VNF according to the VNF contained in the VNF request. The ID of the instance warehouse, and send a VNFR query request to the VNF instance warehouse corresponding to the ID of the VNF instance warehouse.

Alternatively, the VNFM determines the VNF instance repository corresponding to the identifier of the VNF instance to be updated according to the identifier of the VNF instance to be updated in the VNF update request.

Step 403: The VNFM receives the VNFR information corresponding to the identifier of the VNF instance to be updated sent by the VNF instance warehouse.

Step 404: The VNFM sends a virtual resource request to the VIM according to the received VNFR information.

Wherein, the virtual resource request is used to request the VIM to allocate virtual resources required for updating to the VNF instance described in the VNFR information.

According to the received VNFR information and the operation information in the update VNF instance request, the VNFM determines the specific operations to be performed on the VNF instance update, including but not limited to expansion, shrinkage, migration of virtual machines, etc., and further determines specific virtual resources ask.

In step 404, the VNFM sends a virtual resource request to the VIM according to the received VNFR information, including but not limited to the following:

First case:

The VNFM sends a virtual resource request to the VIM according to the received VNFR information when determining that the received update VNF instance request is from the NFVO, or when determining that the management domain where the VNFM is located does not include the NFVO .

Second case:

When the VNFM determines that the management domain where the VNFM is located contains NFVO and the received request to update the VNF instance is not from the NFVO, it further judges the VNFR information described in the VNFR information according to the received VNFR information. Whether there is an association relationship between the VNF instance to be updated and the network service NS.

When the VNFM determines that there is no association relationship between the VNF instance to be updated described in the VNFR information and the NS, it sends a virtual resource request to the VIM.

When the VNFM determines that there is an association between the VNF instance to be updated described in the VNFR information and the NS, it sends an update permission request to the NFVO, wherein the update permission request includes the VNF to be updated The identifier of the instance; and after receiving the permission update permission information sent by the NFVO, send a virtual resource request to the VIM.

Step 405: The VNFM receives the virtual resource allocated by the VIM, and starts to update the VNF instance described in the VNFR information to be updated according to the virtual resource.

It should be noted that updates include but are not limited to: adding VDUs, scaling VNFs, migrating VNFs to new virtual machines or containers, etc.

Step 406: After the VNFM finishes updating the VNF instance, it updates the VNFR information corresponding to the identifier of the VNF instance to be updated in the VNF instance repository.

For example: record the newly added VDU and the virtual machine information of the corresponding VDU into the VNFR.

If the management domain where the VNFM is located includes NFVO, the VNFM sends a notification message to the NFVO after successfully updating the VNFR instance.

It should be noted that the notification message may be a notification message or a response message, which is not limited here.

Wherein, the notification message includes the identifier of the updated VNF instance, and is used to notify that the VNF instance has been updated.

FIG. 8 is a schematic flowchart of a VNF termination method provided by an embodiment of the present invention. In the embodiment of the present invention, in the NFV architecture shown in FIG. 3 , a termination operation is performed on the VNFR information in the VFN warehouse.

Step 501: VNFM receives a request to terminate a VNF instance.

Wherein, the request for terminating the VNF instance includes the identifier of the VNF instance to be terminated.

Step 502: The VNFM sends a VNFR query request to the VNF instance warehouse according to the identifier of the VNF instance to be terminated included in the request for terminating the VNF instance.

Wherein, the VNFR query request includes the identifier of the VNF instance to be terminated.

In step 502, if in the NFV architecture, one VNFM corresponds to multiple VNF instance warehouses, then the VNF termination operation request received by the VNFM also needs to include the identifier of the VNF instance warehouse, so that the VNFM according to the VNF termination operation request The identifier of the included VNF instance warehouse is used to send a VNFR request to the VNF instance warehouse corresponding to the identifier of the VNF instance warehouse.

Alternatively, the VNFM determines the VNF instance warehouse corresponding to the identifier of the VNF instance to be terminated according to the identifier of the VNF instance to be terminated in the VNF termination request.

Step 503: The VNFM receives the VNFR information corresponding to the identifier of the VNF instance to be terminated sent by the VNF instance warehouse.

Step 504: The VNFM terminates the corresponding VNF instance according to the received VNFR information, and sends a virtual resource deletion operation to the VIM.

Wherein, the virtual resource deletion operation sent to the VIM includes the virtual resource information of the VNF instance to be terminated described in the received VNFR information.

It should be noted that the virtual resource information here includes, but is not limited to: VMimage information of the VDU, VM identifier, connection relationship information of the VDU, and the like.

In step 504, the VNFM terminates the corresponding VNF instance according to the received VNFR information, and sends a virtual resource deletion operation to the VIM, including but not limited to:

First case:

When the VNFM determines that the received request for creating a VNF instance comes from an NFVO, or when it determines that the management domain where the VNFM is located does not include the NFVO, terminate the corresponding VNF instance according to the received VNFR information, Send a virtual resource delete operation to VIM.

Second case:

When the VNFM determines that the management domain where the VNFM is located contains NFVO and the received request to update the VNF instance is not from the NFVO, it further judges the VNFR information described in the VNFR information according to the received VNFR information. Whether there is an association relationship between the VNF instance to be terminated and the NS.

When the VNFM determines that there is no association relationship between the VNF instance to be terminated described in the VNFR information and the NS, it terminates the corresponding VNF instance and sends a virtual resource deletion operation to the VIM.

When the VNFM determines that there is an association between the VNF instance to be terminated and the NS described in the VNFR information, it sends a termination permission request to the NFVO, wherein the termination permission request includes the VNF instance to be terminated and when receiving the permission termination information sent by the NFVO, terminate the corresponding VNF instance, and send a virtual resource deletion operation to the VIM.

Specifically, when the VIM receives the virtual resource deletion operation sent by the VNFM, it stops the work of the virtual machine corresponding to the VM ID according to the VM ID; deletes the logical connection relationship of the virtual resource according to the connection relationship information of the VDU, and sends the deletion response The message is sent to VNFM.

Step 505: The VNFM receives the virtual resource deletion response message sent by the VIM, and sends a VNFR deletion request to the VNF instance warehouse.

Wherein, the VNFR deletion request includes the identifier of the VNF instance to be deleted.

The VNF instance warehouse deletes the corresponding VNFR according to the identifier of the VNF instance.

Step 506: The VNFM receives the deletion response sent by the VNF instance warehouse.

If the management domain where the VNFM is located includes NFVO, the VNFM sends a notification message to the NFVO after successfully terminating the VNFR instance.

It should be noted that the notification message may be a notification message or a response message, which is not limited here.

Wherein, the notification message includes the identifier of the deleted VNF instance, and is used to notify that the VNF instance has been deleted.

FIG. 9 is a schematic structural diagram of another NFV architecture provided by an embodiment of the present invention. On the basis of the current NFV architecture, the embodiment of the present invention creates a communication interface between the VNFM and the NFV instance warehouse, so that when the VNFM needs to control the VNF instance, there is no need for NFVO coordination, or if there is no NFVO, Control the VNFR in the NFV instance warehouse directly through the communication interface created between the NFV instance warehouse, that is, obtain the VNFR of the VNF instance that needs to be controlled from the NFV instance warehouse, which improves the control efficiency of the VNF instance and saves Resource consumption during the process of controlling VNF instances.

FIG. 10 is a schematic flowchart of a VNF control method provided by an embodiment of the present invention. The embodiment of the present invention controls the VNF instance in the NFV architecture shown in FIG. 9 . The method can be described as follows.

Step 601: The VNFM receives a VNF operation request.

Wherein, the VNF operation request includes operation information about the VNF instance.

In step 601, the VNFM, as the manager of the VNF instance, receives an operation request from OSS, EM or NFVO, and the VNF operation request can be one of the following:

Create a VNF instance request, modify (or update) a VNF instance request, terminate a VNF instance request, etc.

Step 602: The VNFM processes the VNF instance according to the VNF operation request, and controls the VNFR of the VNF instance in the NFV instance repository through a communication interface with the NFV instance repository.

In step 602, the first situation: the VNF operation request is a request to create a VNF instance.

If the VNF operation request is a request to create a VNF instance, the VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNF instance through the communication interface with the NFV instance warehouse. The VNFR of the VNF instance described in the NFV instance repository, including:

The VNFM sends a virtual resource request to the VIM according to the specified network element of the VNF instance to be created included in the VNF instance creation request.

Wherein, the virtual resource request is used to request the VIM to allocate required virtual resources for creating a VNF instance of a specified network element.

It should be noted that, the situation where the VNFM sends a virtual resource request to the VIM according to the designated network element of the VNF instance to be created included in the VNF instance creation request includes at least the situations described in the above embodiments, which will not be repeated here. repeat.

The VNFM receives the virtual resources allocated by the VIM, and starts to create a new VNF instance of the specified network element according to the virtual resources; and performs a VNF instantiation operation on the allocated virtual machine or container, and starts to create the new VNF instance Describe the VNF instance of the specified NE.

After the VNFM successfully creates and starts the VNF instance, it sends a VNF instantiation success response to the EM.

The EM configures the VNF instance, that is, configures service parameters and other information into the instantiated VNF.

After the VNFM successfully creates the new VNF instance of the specified network element, it generates the VNFR of the VNF instance, and stores the VNFR of the VNF instance in the NFV instance repository through the communication interface with the NFV instance repository.

Or, after successfully creating the new VNF instance of the specified network element, the VNFM sends the created VNF instance information to the NFV instance warehouse through the communication interface with the NFV instance warehouse, and the NFV instance warehouse stores it in VNFR format Information about the virtual resources used by the VNF instance.

Optionally, the method also includes:

If the management domain where the VNFM is located includes NFVO, the VNFM sends a notification message to the NFVO after successfully creating the VNF instance of the specified network element.

Wherein, the notification message includes the identifier of the created VNF instance of the designated network element, so that the identifier of the VNF instance of the designated network element is registered in the NFVO.

The second situation: the VNF operation request is a request for querying a VNF instance.

If the VNF operation request is a request for querying a VNF instance, the VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the NFV through the communication interface with the NFV instance warehouse. The VNFR of the VNF instance described in the instance repository, including:

The VNFM sends a VNFR read request to the NFV instance warehouse through the communication interface with the NFV instance warehouse according to the identifier of the VNF instance to be queried included in the query VNF instance request.

Wherein, the VNFR request includes the identifier of the VNF instance to be queried;

The VNFM receives the VNFR information corresponding to the identifier of the VNF instance to be queried and sent by the VNF instance warehouse.

The third situation: the VNF operation request is a request to update the VNF instance.

If the VNF operation request is a request for updating a VNF instance, the VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the NFV through the communication interface with the NFV instance warehouse. The VNFR of the VNF instance described in the instance repository, including:

The VNFM sends a VNFR query request to the NFV instance warehouse through the communication interface with the NFV instance warehouse according to the identifier of the VNF instance to be updated included in the update VNF instance request.

Wherein, the VNFR query request includes the identifier of the VNF instance to be updated;

The VNFM receives the VNFR information corresponding to the identifier of the VNF instance to be updated sent by the NFV instance repository.

The VNFM sends a virtual resource request to the VIM according to the received VNFR information.

Wherein, the virtual resource request is used to request the VIM to allocate virtual resources required for updating to the VNF instance described in the VNFR information.

It should be noted that, the situation where the VNFM sends a virtual resource request to the VIM according to the received VNFR information also includes at least the situations described in the above embodiments, which will not be repeated here.

The VNFM receives the virtual resource allocated by the VIM, and starts to update the VNF instance described in the VNFR information according to the virtual resource.

After the VNF instance is updated, the VNFM updates the VNFR information corresponding to the identifier of the VNF instance to be updated in the NFV instance repository through the communication interface with the NFV instance repository.

The fourth situation: the VNF operation request is a request to terminate the VNF instance.

If the VNF operation request is a request to terminate a VNF instance, the VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the NFV through the communication interface with the NFV instance warehouse. The VNFR of the VNF instance described in the instance repository, including:

The VNFM sends a VNFR query request to the NFV instance warehouse through the communication interface with the NFV instance warehouse according to the identification of the VNF instance to be terminated included in the termination VNF instance request.

Wherein, the VNFR query request includes the identifier of the VNF instance;

The VNFM receives the VNFR information corresponding to the identifier of the VNF instance to be terminated sent by the NFV instance warehouse.

The VNFM terminates the corresponding VNF instance according to the VNFR information, and sends a virtual resource deletion operation to the VIM.

Wherein, the virtual resource deletion operation includes the determined virtual resource information of the VNF instance to be terminated described in the VNFR information.

It should be noted that, the situation where the VNFM sends the virtual resource deletion operation to the VIM according to the VNFR information at least includes the situations recorded in the above embodiments, which will not be repeated here.

The VNFM receives the virtual resource deletion response message sent by the VIM, and sends a VNFR deletion request to the VNF instance warehouse.

Wherein, the VNFR deletion request includes the identifier of the VNF instance to be deleted.

FIG. 11 is a schematic structural diagram of a VNF control device provided by an embodiment of the present invention. The control device includes: a receiving unit 71 and a control unit 72, wherein:

The receiving unit 71 is configured to receive a VNF operation request, wherein the VNF operation request includes operation information about the VNF instance;

The control unit 72 is configured to process the VNF instance according to the operation information contained in the VNF operation request received by the receiving unit, and control the VNF record VNFR of the VNF instance in the VNF instance warehouse.

Specifically, the VNF operation request is a request to create a VNF instance, wherein the request to create a VNF instance includes a designated network element of the VNF instance to be created;

The control unit 72 is specifically configured to send a virtual resource request to the virtualization infrastructure management system VIM according to the designated network element of the VNF instance to be created contained in the VNF instance creation request, wherein the virtual resource request is used for Requesting the VIM to allocate required virtual resources for creating a VNF instance of a specified network element;

receiving the virtual resource allocated by the VIM, and starting to create a VNF instance of the specified network element according to the virtual resource;

After the VNF instance of the specified network element is successfully created, the VNFR of the VNF instance is stored in the VNF instance repository.

Specifically, the control unit 72 is specifically configured to, when it is determined that the received request for creating a VNF instance comes from the network function orchestrator NFVO, or when it is determined that the management domain where it is located does not include the NFVO, according to the created The designated network element of the VNF instance to be created included in the VNF instance request sends a virtual resource request to the VIM.

Specifically, the control unit 72 is specifically configured to, when it is determined that the management domain where it is located includes NFVO and the received request for creating a VNF instance is not from the NFVO, further determine the designated network element to create a VNF instance Whether it is a network element that can independently perform services;

When it is determined that the designated network element of the VNF instance to be created is a network element capable of independently performing services, a virtual resource request is sent to the VIM.

Specifically, the control unit 72 is specifically configured to send a creation permission request to the NFVO when it cannot be determined whether the specified network element of the VNF instance to be created is a network element that can independently perform services; and

When receiving the permission creation information sent by the NFVO, send a virtual resource request to the VIM.

Specifically, the VNF operation request is a request for querying a VNF instance, wherein the request for querying a VNF instance includes the identifier of the VNF instance to be queried;

The control unit 72 is specifically configured to send a VNFR query request to the VNF instance warehouse according to the identifier of the VNF instance to be queried contained in the query VNF instance request, wherein the VNFR query request contains the VNF instance to be queried The identification of the VNF instance;

Receive the VNFR information corresponding to the identifier of the VNF instance to be queried sent by the VNF instance warehouse.

Specifically, the operation request is a request for updating a VNF instance, wherein the request for updating a VNF instance includes the identifier of the VNF instance to be updated;

The control unit 72 is specifically configured to send a VNFR query request to the VNF instance warehouse according to the identifier of the VNF instance to be updated included in the update VNF instance request, wherein the VNFR query request includes the VNF instance to be updated The identification of the VNF instance;

receiving VNFR information corresponding to the identifier of the VNF instance to be updated sent by the VNF instance warehouse;

Sending a virtual resource request to the VIM according to the received VNFR information, where the virtual resource request is used to request the VIM to allocate virtual resources required for updating to the VNF instance described in the VNFR information;

receiving the virtual resource allocated by the VIM, and starting to update the VNF instance described in the VNFR information according to the virtual resource;

After the update of the VNF instance is completed, the VNFR information corresponding to the identifier of the VNF instance to be updated in the VNF instance warehouse is updated.

Specifically, the control unit 72 is specifically configured to, according to the received VNFR information, when it is determined that the received request for updating the VNF instance is from the NFVO, or when it is determined that the management domain where it is located does not include the NFVO, , to send a virtual resource request to VIM.

Specifically, the control unit 72 is specifically configured to further judge according to the received VNFR information when it is determined that the management domain where it is located contains NFVO and the received request for updating the VNF instance is not from the NFVO. Whether there is an association relationship between the VNF instance to be updated described in the VNFR information and the network service NS;

When it is determined that there is no association relationship between the VNF instance to be updated described in the VNFR information and the NS, a virtual resource request is sent to the VIM.

Specifically, the control unit 72 is specifically configured to send an update permission request to the NFVO when it is determined that there is an association relationship between the VNF instance to be updated described in the VNFR information and the NS, wherein the update permission The request includes the identifier of the VNF instance to be updated; and

When receiving the update permission information sent by the NFVO, send a virtual resource request to the VIM.

Specifically, the operation request is a request for terminating a VNF instance, wherein the request for terminating a VNF instance includes the identifier of the VNF instance to be terminated;

The control unit 72 is specifically configured to send a VNFR query request to the VNF instance repository according to the identifier of the VNF instance to be terminated included in the request for terminating the VNF instance, wherein the VNFR query request includes the identifier of the VNF instance to be terminated. The identification of the VNF instance;

receiving VNFR information corresponding to the identifier of the VNF instance to be terminated sent by the VNF instance warehouse;

Terminate the VNF instance according to the received VNFR information, and send a virtual resource deletion operation to the VIM, wherein the virtual resource deletion operation includes the virtual resource information of the VNF instance to be terminated described in the received VNFR information;

Receive the virtual resource deletion response message sent by the VIM, and send a VNFR deletion request to the VNF instance repository, where the VNFR deletion request includes the identifier of the VNF instance to be deleted.

Specifically, the control unit 72 is specifically configured to, according to the received VNFR information, when it is determined that the received request for terminating a VNF instance comes from an NFVO, or when it is determined that the management domain where it is located does not include the NFVO, , terminate the VNF instance, and send a virtual resource deletion operation to the VIM.

Specifically, the control unit 72 is specifically configured to further judge according to the received VNFR information when it is determined that the management domain where it is located contains NFVO and the received request to terminate the VNF instance is not from the NFVO. Whether there is an association relationship between the VNF instance to be terminated and the NS described in the VNFR information;

When it is determined that there is no association relationship between the VNF instance to be terminated described in the VNFR information and the NS, the VNF instance is terminated, and a virtual resource deletion operation is sent to the VIM.

Specifically, the control unit 72 is specifically configured to send a termination permission request to the NFVO when it is determined that there is an association relationship between the VNF instance to be terminated described in the VNFR information and the NS, wherein the termination permission The request includes the identification of the VNF instance to be terminated; and

When receiving the permission termination information sent by the NFVO, terminate the VNF instance, and send a virtual resource deletion operation to the VIM.

Optionally, the control device further includes: a sending unit 73, wherein:

The sending unit 73 is configured to send a notification message to the NFVO after the VNF instance is processed if the management domain where it is located includes the NFVO, wherein the notification message includes the identifier of the VNF instance .

It should be noted that the control device described in the embodiments of the present invention may be implemented by means of software or hardware, which is not limited here.

Fig. 12 is a schematic structural diagram of a VNF control device provided by an embodiment of the present invention. The control device is capable of executing the functions described in FIG. 3 to FIG. 8 in the embodiment of the present invention. The control device may adopt a general-purpose computer system structure, and the computer system may specifically be a computer based on a processor. The control device entity includes a processor 81 , a memory 82 and an interface 83 . The processor 81 is connected to the interface 83 and to the memory 82 . For example, the processor 81, the interface 83 and the memory 82 may be connected via a bus.

The processor 81 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the program execution of the present invention.

Wherein, the communication bus may include a path for transmitting information between the above-mentioned components. The interface 83 uses any device such as a transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (Wireless Local Area Networks, WLAN) and the like.

The computer system includes one or more memories 82, which may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory, RAM) or information and instructions of other types of dynamic storage devices, can also be Electrically Erasable Programmable Read-Only Memory (Electrically Erasable Programmable Read-OnlyMemory, EEPROM), CD-ROM (CompactDiscRead-OnlyMemory, CD-ROM) or other CD-ROM storage, CD-ROM storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage medium or other magnetic storage device, or can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer any other media, but not limited to. These memories are connected to the processor via a bus.

Wherein, the memory 82 is used to store the application program code for executing the solution of the present invention, and the application program code for executing the solution of the present invention is stored in the memory and executed under the control of the processor 81 . The processor 81 is used to execute the application programs stored in the memory 82:

Receive a VNF operation request through the interface 83, wherein the VNF operation request includes operation information about the VNF instance;

According to the operation information contained in the VNF operation request, the VNF instance is processed, and the VNF record VNFR of the VNF instance in the VNF instance repository is controlled.

Optionally, the VNF operation request is a request for creating a VNF instance, wherein the request for creating a VNF instance includes a designated network element of the VNF instance to be created;

The processor 81 processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNFR of the VNF instance in the VNF instance warehouse, including:

Send a virtual resource request to the virtualization infrastructure management system VIM according to the specified network element of the VNF instance to be created contained in the VNF instance creation request, wherein the virtual resource request is used to request the VIM to create a specified network element The VNF instance allocates the required virtual resources;

receiving the virtual resource allocated by the VIM, and starting to create a VNF instance of the specified network element according to the virtual resource;

After the VNF instance of the specified network element is successfully created, the VNFR of the VNF instance is stored in the VNF instance repository.

Optionally, the VNFM sends a virtual resource request to the VIM according to the designated network element of the VNF instance to be created included in the VNF instance creation request, including:

When the processor 81 determines that the received request for creating a VNF instance comes from the network function orchestrator NFVO, or when it determines that the management domain where it is located does not include the NFVO, according to the waiting list included in the request for creating a VNF instance Create a designated network element of a VNF instance and send a virtual resource request to the VIM.

Optionally, the processor 81 sends a virtual resource request to the VIM according to the designated network element of the VNF instance to be created contained in the VNF instance creation request, including:

When it is determined that NFVO is included in the management domain where it is located, and the received request for creating a VNF instance is not from the NFVO, further determine whether the designated network element of the VNF instance to be created is a network element that can independently perform services;

When it is determined that the designated network element of the VNF instance to be created is a network element capable of independently performing services, a virtual resource request is sent to the VIM.

Optionally, the processor 81 sends a virtual resource request to the VIM according to the designated network element of the VNF instance to be created contained in the VNF instance creation request, including:

When it cannot be determined whether the specified network element of the VNF instance to be created is a network element that can independently perform services, send a creation permission request to the NFVO; and

When receiving the permission creation information sent by the NFVO, send a virtual resource request to the VIM.

Optionally, the VNF operation request is a request for querying a VNF instance, wherein the request for querying a VNF instance includes an identifier of the VNF instance to be queried;

The processor 81 processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNFR of the VNF instance in the VNF instance warehouse, including:

Sending a VNFR query request to the VNF instance warehouse according to the identifier of the VNF instance to be queried included in the query VNF instance request, wherein the VNFR query request includes the identifier of the VNF instance to be queried;

Receive the VNFR information corresponding to the identifier of the VNF instance to be queried sent by the VNF instance repository.

Optionally, the operation request is a request for updating a VNF instance, wherein the request for updating a VNF instance includes an identifier of the VNF instance to be updated;

The processor 81 processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNFR of the VNF instance in the VNF instance warehouse, including:

Sending a VNFR query request to the VNF instance warehouse according to the identification of the VNF instance to be updated included in the update VNF instance request, wherein the VNFR query request includes the identification of the VNF instance to be updated;

receiving VNFR information corresponding to the identifier of the VNF instance to be updated sent by the VNF instance repository;

Sending a virtual resource request to the VIM according to the received VNFR information, where the virtual resource request is used to request the VIM to allocate virtual resources required for updating to the VNF instance described in the VNFR information;

receiving the virtual resource allocated by the VIM, and starting to update the VNF instance described in the VNFR information according to the virtual resource;

After the update of the VNF instance is completed, the VNFR information corresponding to the identifier of the VNF instance to be updated in the VNF instance warehouse is updated.

Optionally, the processor 81 sends a virtual resource request to the VIM according to the received VNFR information, including:

When it is determined that the received VNF instance update request comes from the NFVO, or when it is determined that the management domain where the VNF is located does not include the NFVO, send a virtual resource request to the VIM according to the received VNFR information.

Optionally, the processor 81 sends a virtual resource request to the VIM according to the received VNFR information, including:

When it is determined that NFVO is included in its management domain and the received request for updating the VNF instance is not from the NFVO, further judge the VNF instance to be updated described in the VNFR information according to the received VNFR information Whether there is an association relationship with the network service NS;

When it is determined that there is no association relationship between the VNF instance to be updated described in the VNFR information and the NS, a virtual resource request is sent to the VIM.

The processor 81 sends a virtual resource request to the VIM according to the received VNFR information, including:

When it is determined that there is an association relationship between the VNF instance to be updated and the NS described in the VNFR information, send an update permission request to the NFVO, where the update permission request includes the identifier of the VNF instance to be updated ;and

When receiving the update permission information sent by the NFVO, send a virtual resource request to the VIM.

Optionally, the operation request is a request for terminating a VNF instance, wherein the request for terminating a VNF instance includes an identifier of the VNF instance to be terminated;

The processor 81 processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNFR of the VNF instance in the VNF instance warehouse, including:

Sending a VNFR query request to the VNF instance warehouse according to the identifier of the VNF instance to be terminated included in the request for terminating the VNF instance, wherein the VNFR query request includes the identifier of the VNF instance to be terminated;

receiving VNFR information corresponding to the identifier of the VNF instance to be terminated sent by the VNF instance warehouse;

Terminate the VNF instance according to the received VNFR information, and send a virtual resource deletion operation to the VIM, wherein the virtual resource deletion operation includes the virtual resource information of the VNF instance to be terminated described in the received VNFR information;

Receive the virtual resource deletion response message sent by the VIM, and send a VNFR deletion request to the VNF instance repository, where the VNFR deletion request includes the identifier of the VNF instance to be deleted.

The processor 81 sends a virtual resource deletion operation to the VIM according to the received VNFR information, including:

When it is determined that the received request to terminate the VNF instance comes from NFVO, or when it is determined that the management domain where it is located does not include the NFVO, terminate the VNF instance according to the received VNFR information, and send a virtual resource deletion operation to the VIM .

The processor 81 sends a virtual resource deletion operation to the VIM according to the received VNFR information, including:

When it is determined that NFVO is included in its management domain and the received request to terminate the VNF instance is not from the NFVO, further judge the VNF instance to be terminated described in the VNFR information according to the received VNFR information Whether there is an association relationship with NS;

When it is determined that there is no association relationship between the VNF instance to be terminated described in the VNFR information and the NS, the VNF instance is terminated, and a virtual resource deletion operation is sent to the VIM.

The processor 81 sends a virtual resource deletion operation to the VIM according to the received VNFR information, including:

When it is determined that there is an association relationship between the VNF instance to be terminated and the NS described in the VNFR information, send a termination permission request to the NFVO, where the termination permission request includes the identifier of the VNF instance to be terminated; and

When receiving the permission termination information sent by the NFVO, terminate the VNF instance, and send a virtual resource deletion operation to the VIM.

Optionally, the processor 81 is further configured to send a notification message to the NFVO after the VNF instance is processed if the management domain where it is located includes the NFVO, wherein the notification message includes the The identifier of the VNF instance.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, devices (devices), or computer program products. Accordingly, the present invention can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices) and computer program products according to embodiments of the invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

While preferred embodiments of the invention have been described, additional changes and modifications to these embodiments can be made by those skilled in the art once the basic inventive concept is appreciated. Therefore, it is intended that the appended claims be construed to cover the preferred embodiment as well as all changes and modifications which fall within the scope of the invention.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and equivalent technologies thereof, the present invention also intends to include these modifications and variations.

Claims (32)

1. A virtualized network function VNF control method, characterized in that, comprising: The VNF manager VNFM receives the VNF operation request, wherein the VNF operation request includes operation information about the VNF instance; The VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNF record VNFR of the VNF instance in the VNF instance warehouse. 2. The VNF control method according to claim 1, wherein the VNF operation request is to create a VNF instance request, wherein the VNF instance request includes a designated network element to be created in the VNF instance; The VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNFR of the VNF instance in the VNF instance warehouse, including: The VNFM sends a virtual resource request to the virtualization infrastructure management system VIM according to the designated network element of the VNF instance to be created included in the VNF instance creation request, wherein the virtual resource request is used to request the VIM to create The VNF instance of the specified network element allocates the required virtual resources; The VNFM receives the virtual resource allocated by the VIM, and starts to create the VNF instance of the specified network element according to the virtual resource; After the VNFM successfully creates the VNF instance of the specified network element, it stores the VNFR of the VNF instance in the VNF instance warehouse. 3. The VNF control method according to claim 2, wherein the VNFM sends a virtual resource request to the VIM according to the designated network element of the VNF instance to be created included in the VNF instance request, including: When the VNFM determines that the VNF instance creation request received comes from the network function orchestrator NFVO, or when it determines that the management domain where the VNFM is located does not include the NFVO, according to the pending VNF instance request included in the VNF instance creation request Create a designated network element of a VNF instance and send a virtual resource request to the VIM. 4. The VNF control method according to claim 2, wherein the VNFM sends a virtual resource request to the VIM according to the designated network element of the VNF instance to be created contained in the VNF instance request, comprising: When the VNFM determines that the management domain where the VNFM is located includes NFVO and the received request for creating a VNF instance is not from the NFVO, it further determines whether the designated network element of the VNF instance to be created is capable of independently executing services network element; When the VNFM determines that the specified network element of the VNF instance to be created is a network element capable of independently executing services, it sends a virtual resource request to the VIM. 5. The VNF control method according to claim 4, wherein the VNFM sends a virtual resource request to the VIM according to the designated network element of the VNF instance to be created contained in the VNF instance request, comprising: When the VNFM cannot determine whether the specified network element of the VNF instance to be created is a network element that can independently perform services, send a creation permission request to the NFVO; and When receiving the permission creation information sent by the NFVO, send a virtual resource request to the VIM. 6. The VNF control method according to claim 1, wherein the VNF operation request is a query VNF instance request, wherein the query VNF instance request includes the identification of the VNF instance to be queried; The VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNFR of the VNF instance in the VNF instance warehouse, including: The VNFM sends a VNFR query request to the VNF instance repository according to the identifier of the VNF instance to be queried included in the query VNF instance request, wherein the VNFR query request includes the identifier of the VNF instance to be queried; The VNFM receives the VNFR information corresponding to the identifier of the VNF instance to be queried and sent by the VNF instance repository. 7. The VNF control method according to claim 1, wherein the operation request is an update VNF instance request, wherein the update VNF instance request includes the identification of the VNF instance to be updated; The VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNFR of the VNF instance in the VNF instance warehouse, including: The VNFM sends a VNFR query request to the VNF instance warehouse according to the identification of the VNF instance to be updated included in the update VNF instance request, wherein the VNFR query request includes the identification of the VNF instance to be updated; The VNFM receives the VNFR information corresponding to the identifier of the VNF instance to be updated sent by the VNF instance repository; The VNFM sends a virtual resource request to the VIM according to the received VNFR information, where the virtual resource request is used to request the VIM to allocate virtual resources required for updating to the VNF instance described by the VNFR information; The VNFM receives the virtual resource allocated by the VIM, and starts updating the VNF instance described in the VNFR information according to the virtual resource; After the VNFM finishes updating the VNF instance, it updates the VNFR information corresponding to the identifier of the VNF instance to be updated in the VNF instance warehouse. 8. The VNF control method according to claim 7, wherein the VNFM sends a virtual resource request to the VIM according to the received VNFR information, comprising: The VNFM sends a virtual resource request to the VIM according to the received VNFR information when determining that the received update VNF instance request is from the NFVO, or when determining that the management domain where the VNFM is located does not include the NFVO . 9. The VNF control method according to claim 7, wherein the VNFM sends a virtual resource request to the VIM according to the received VNFR information, comprising: When the VNFM determines that the management domain where the VNFM is located contains NFVO and the received request to update the VNF instance is not from the NFVO, it further judges the VNFR information described in the VNFR information according to the received VNFR information. Whether there is an association relationship between the VNF instance to be updated and the network service NS; When the VNFM determines that there is no association relationship between the VNF instance to be updated described in the VNFR information and the NS, it sends a virtual resource request to the VIM. 10. The VNF control method according to claim 9, wherein the VNFM sends a virtual resource request to the VIM according to the received VNFR information, comprising: When the VNFM determines that there is an association between the VNF instance to be updated described in the VNFR information and the NS, it sends an update permission request to the NFVO, wherein the update permission request includes the VNF to be updated the identity of the instance; and When receiving the update permission information sent by the NFVO, send a virtual resource request to the VIM. 11. The VNF control method according to claim 1, wherein the operation request is a request for terminating a VNF instance, wherein the request for terminating a VNF instance includes the identification of the VNF instance to be terminated; The VNFM processes the VNF instance according to the operation information contained in the VNF operation request, and controls the VNFR of the VNF instance in the VNF instance warehouse, including: The VNFM sends a VNFR query request to the VNF instance warehouse according to the identifier of the VNF instance to be terminated included in the request for terminating the VNF instance, wherein the VNFR query request includes the identifier of the VNF instance to be terminated; The VNFM receives the VNFR information corresponding to the identifier of the VNF instance to be terminated sent by the VNF instance repository; The VNFM terminates the VNF instance according to the received VNFR information, and sends a virtual resource deletion operation to the VIM, wherein the virtual resource deletion operation includes the virtual resources of the VNF instance to be terminated described in the received VNFR information. resource information; The VNFM receives the virtual resource deletion response message sent by the VIM, and sends a VNFR deletion request to the VNF instance repository, wherein the VNFR deletion request includes the identifier of the VNF instance to be deleted. 12. The VNF control method according to claim 11, wherein the VNFM sends a virtual resource deletion operation to the VIM according to the received VNFR information, comprising: When the VNFM determines that the received request for terminating the VNF instance comes from the NFVO, or when it determines that the management domain where the VNFM is located does not include the NFVO, it terminates the VNF instance according to the received VNFR information, and reports to the VIM Send a virtual resource delete operation. 13. The VNF control method according to claim 11, wherein the VNFM sends a virtual resource deletion operation to the VIM according to the received VNFR information, comprising: When the VNFM determines that the management domain where the VNFM is located includes NFVO and the received request to terminate the VNF instance is not from the NFVO, further judge the VNFR information described in the VNFR information according to the received VNFR information. Whether there is an association relationship between the VNF instance to be terminated and the NS; When the VNFM determines that there is no association relationship between the VNF instance to be terminated and the NS described in the VNFR information, it terminates the VNF instance and sends a virtual resource deletion operation to the VIM. 14. The VNF control method according to claim 13, wherein the VNFM sends a virtual resource deletion operation to the VIM according to the received VNFR information, comprising: When the VNFM determines that there is an association between the VNF instance to be terminated and the NS described in the VNFR information, it sends a termination permission request to the NFVO, wherein the termination permission request includes the VNF instance to be terminated identify; and When receiving the permission termination information sent by the NFVO, terminate the VNF instance, and send a virtual resource deletion operation to the VIM. 15. The VNF control method according to any one of claims 1 to 14, wherein the method further comprises: If the management domain where the VNFM is located includes NFVO, the VNFM sends a notification message to the NFVO after processing the VNF instance, where the notification message includes the identifier of the VNF instance. 16. A virtualized network function VNF control method, characterized in that, comprising: The VNF manager VNFM receives the VNF operation request, wherein the VNF operation request includes operation information about the VNF instance; The VNFM processes the VNF instance according to the operation information included in the VNF operation request, and controls the VNF record VNFR of the VNF instance in the NFV instance repository through the communication interface with the NFV instance repository. 17. A virtualized network function VNF control device, characterized in that it comprises: A receiving unit, configured to receive a VNF operation request, wherein the VNF operation request includes operation information about the VNF instance; The control unit is configured to process the VNF instance according to the operation information contained in the VNF operation request received by the receiving unit, and control the VNF record VNFR of the VNF instance in the VNF instance warehouse. 18. The VNF control device according to claim 17, wherein the VNF operation request is a request for creating a VNF instance, wherein the request for creating a VNF instance includes a specified network element to be created for the VNF instance; The control unit is specifically configured to send a virtual resource request to the virtualization infrastructure management system VIM according to the specified network element of the VNF instance to be created included in the VNF instance creation request, wherein the virtual resource request is used to request The VIM allocates required virtual resources for creating a VNF instance of a specified network element; receiving the virtual resource allocated by the VIM, and starting to create a VNF instance of the specified network element according to the virtual resource; After the VNF instance of the specified network element is successfully created, the VNFR of the VNF instance is stored in the VNF instance repository. 19. The VNF control device according to claim 18, wherein: The control unit is specifically configured to, when it is determined that the received request for creating a VNF instance comes from a network function orchestrator NFVO, or when it is determined that the management domain where it is located does not include the NFVO, according to the request for creating a VNF instance The specified network element included in the VNF instance to be created sends a virtual resource request to the VIM. 20. The VNF control device according to claim 19, wherein: The control unit is specifically configured to further determine whether the designated network element of the VNF instance to be created can be independent when it is determined that the management domain where it is located contains NFVO and the received request for creating a VNF instance is not from the NFVO. Network elements that perform services; When it is determined that the designated network element of the VNF instance to be created is a network element capable of independently performing services, a virtual resource request is sent to the VIM. 21. The VNF control device according to claim 20, wherein: The control unit is specifically configured to send a creation permission request to the NFVO when it cannot be determined whether the specified network element of the VNF instance to be created is a network element that can independently perform services; and When receiving the permission creation information sent by the NFVO, send a virtual resource request to the VIM. 22. The VNF control device according to claim 17, wherein the VNF operation request is a query VNF instance request, wherein the query VNF instance request includes the identifier of the VNF instance to be queried; The control unit is specifically configured to send a VNFR query request to the VNF instance repository according to the identifier of the VNF instance to be queried contained in the query VNF instance request, wherein the VNFR query request contains the VNF instance to be queried Identification of the VNF instance; Receive the VNFR information corresponding to the identifier of the VNF instance to be queried sent by the VNF instance repository. 23. The VNF control device according to claim 17, wherein the operation request is an update VNF instance request, wherein the update VNF instance request includes the identifier of the VNF instance to be updated; The control unit is specifically configured to send a VNFR query request to the VNF instance warehouse according to the identifier of the VNF instance to be updated included in the update VNF instance request, wherein the VNFR query request includes the VNF instance to be updated Identification of the VNF instance; receiving VNFR information corresponding to the identifier of the VNF instance to be updated sent by the VNF instance repository; Sending a virtual resource request to the VIM according to the received VNFR information, where the virtual resource request is used to request the VIM to allocate virtual resources required for updating to the VNF instance described in the VNFR information; receiving the virtual resource allocated by the VIM, and starting to update the VNF instance described in the VNFR information according to the virtual resource; After the update of the VNF instance is completed, the VNFR information corresponding to the identifier of the VNF instance to be updated in the VNF instance repository is updated. 24. The VNF control device according to claim 23, wherein: The control unit is specifically configured to, according to the received VNFR information, send an Virtual resource request. 25. The VNF control device according to claim 23, wherein: The control unit is specifically configured to further judge the VNFR information according to the received VNFR information when it is determined that NFVO is included in the management domain where it is located and the received request for updating the VNF instance is not from the NFVO. Whether there is an association relationship between the VNF instance to be updated and the network service NS described in ; When it is determined that there is no association relationship between the VNF instance to be updated described in the VNFR information and the NS, a virtual resource request is sent to the VIM. 26. The VNF control device according to claim 25, wherein: The control unit is specifically configured to send an update permission request to the NFVO when it is determined that there is an association between the VNF instance to be updated described in the VNFR information and the NS, where the update permission request includes the Describe the identity of the VNF instance to be updated; and When receiving the update permission information sent by the NFVO, send a virtual resource request to the VIM. 27. The VNF control device according to claim 17, wherein the operation request is a request for terminating a VNF instance, wherein the request for terminating a VNF instance includes an identifier of the VNF instance to be terminated; The control unit is specifically configured to send a VNFR query request to the VNF instance repository according to the identifier of the VNF instance to be terminated included in the request for terminating the VNF instance, wherein the VNFR query request includes the VNF instance to be terminated. Identification of the VNF instance; receiving VNFR information corresponding to the identifier of the VNF instance to be terminated sent by the VNF instance warehouse; Terminate the VNF instance according to the received VNFR information, and send a virtual resource deletion operation to the VIM, wherein the virtual resource deletion operation includes the virtual resource information of the VNF instance to be terminated described in the received VNFR information; Receive the virtual resource deletion response message sent by the VIM, and send a VNFR deletion request to the VNF instance repository, where the VNFR deletion request includes the identifier of the VNF instance to be deleted. 28. The VNF control device according to claim 27, wherein: The control unit is specifically configured to terminate the VNF instance according to the received VNFR information when it is determined that the received request for terminating the VNF instance is from the NFVO, or when it is determined that the management domain where it is located does not include the NFVO , to send a virtual resource deletion operation to VIM. 29. The VNF control device according to claim 27, wherein: The control unit is specifically configured to further judge the VNFR information according to the received VNFR information when it is determined that the management domain where it is located contains NFVO and the received request to terminate the VNF instance is not from the NFVO Whether there is an association relationship between the VNF instance to be terminated and the NS described in ; When it is determined that there is no association relationship between the VNF instance to be terminated described in the VNFR information and the NS, the VNF instance is terminated, and a virtual resource deletion operation is sent to the VIM. 30. The VNF control device according to claim 29, wherein: The control unit is specifically configured to send a termination permission request to the NFVO when it is determined that there is an association relationship between the VNF instance to be terminated described in the VNFR information and the NS, wherein the termination permission request includes a pending the identification of the terminated VNF instance; and When receiving the permission termination information sent by the NFVO, terminate the VNF instance, and send a virtual resource deletion operation to the VIM. 31. The VNF control device according to any one of claims 17 to 30, wherein the control device further comprises: a sending unit, wherein: The sending unit is configured to send a notification message to the NFVO after the VNF instance is processed if the management domain where it is located includes the NFVO, wherein the notification message includes the identifier of the VNF instance. 32. A virtualized network function VNF control device, characterized in that it comprises: A receiving unit, configured to receive a VNF operation request, wherein the VNF operation request includes operation information about the VNF instance; A control unit, configured to process the VNF instance according to the operation information contained in the VNF operation request, and control the VNF record of the VNF instance in the NFV instance repository through the communication interface with the NFV instance repository VNFR.