WO2016206372A1

WO2016206372A1 - Method and apparatus for transferring virtualized network function (vnf)

Info

Publication number: WO2016206372A1
Application number: PCT/CN2016/071400
Authority: WO
Inventors: 邵战领
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-06-26
Filing date: 2016-01-20
Publication date: 2016-12-29
Also published as: CN106302074B; CN106302074A

Abstract

Disclosed are a method and an apparatus for transferring virtualized network function (VNF), including: determining, in original virtualized network function management (VNFM) managed by an original network function virtualization orchestrator (NFVO), the VNF which is managed by the original VNFM and needs to be transferred; determining, in the original NFVO and/or other NFVOs except the original NFVO, target VNFM capable of accepting the VNF needing to be transferred; and transferring the VNF needing to be transferred to the target VNFM. With the technical solution, the existing problem that the VNF can not be transferred between different VNFMs is solved.

Description

Method and device for migrating virtualized network function VNF

Technical field

The present application relates to the field of communications, for example, to a method and apparatus for migrating a virtualized network function VNF.

Background technique

In the context of the rapid development of technologies such as virtualization (IT) in the field of IT (Information Technology), telecom operators have proposed NFV (Network Function Virtualization) in response to the impact of network service providers on operators and increasing demand. It is designed to replace privately-owned network element equipment in the communication network with general-purpose servers, storage devices and switching equipment based on industry standards, reducing the investment and operating costs of operators.

According to the requirements of the ETSI (European Telecommunications Standards Institute), a set of VNF (Virtualization Network Function) is defined in the NFV-MANO (NFV Management and Orchestration) domain. Among them, NFVO (Network Functions Virtualization Orchestrator) is mainly responsible for VNF planning and deployment, and the whole network virtual resource is arranged. VNFM (Virtualized Network Function Manager) is responsible for VNF lifecycle management. One NFVO manages multiple VNFMs, and one VNFM manages multiple VNFs. Currently, VNF cannot be migrated between different VNFMs. This tends to cause uneven distribution of VNFs, and the load of VNFM and NVFO is not balanced, thus affecting the service quality of the entire system.

Summary of the invention

A method and device for migrating a virtualized network function VNF provided by an embodiment of the present invention Some VNFs cannot be migrated between different VNFMs.

To solve the above technical problem, the embodiment of the present invention adopts the following technical solutions:

A method for migrating a virtualized network function VNF, comprising:

Determining the VNF to be migrated managed by the original VNFM in the original virtualized network function management VNFM managed by the original network function virtualization orchestration NFVO;

Determining a destination VNFM capable of receiving the VNF to be migrated in the NFVO other than the original NFVO and/or other than the original NFVO;

The VNF that needs to be migrated is migrated to the target VNFM.

In some embodiments, in the original VNFM managed by the original NFVO, determining the VNF to be migrated managed by the original VNFM includes:

The VNF to be migrated is determined according to the service request success rate of the VNF, the service request completion time of the VNF, and/or the load of the original VNFM.

In some embodiments, in the NFVO other than the original NFVO and/or other than the original NFVO, determining the destination VNFM capable of receiving the VNF requiring migration includes:

In the VNFM managed by the original NFVO except the original VNFM, determining a destination VNFM capable of receiving the VNF to be migrated according to a load balancing principle;

Creating a new VNFM in the original NFVO as the target VNFM;

In the other NFVO, determining a destination VNFM capable of receiving the VNF to be migrated according to a load balancing principle;

And/or, a new VNFM is created in the other NFVO as the destination VNFM.

In some embodiments, if the destination VNFM belongs to the original NFVO management, the migrating the VNF that needs to be migrated to the destination VNFM includes:

And deleting configuration information of the VNF to be migrated from the management information of the original VNFM; The configuration information of the VNF that needs to be migrated is added to the management information of the destination VNFM; and the configuration information of the VNF to be migrated is assigned from the original VNFM to the destination VNFM in the management information of the original NFVO;

If the destination VNFM is in the other NFVO, the migrating the VNF to be migrated to the destination VNFM includes: generating resource information of the VNF to be migrated in the original NFVO; Importing the product package of the VNF to be migrated; generating new resource information according to the product package and the resource information in the destination NFVO and the destination VNFM, and adding the VNF to be migrated according to the new resource information .

In some embodiments, before the migrating the VNF to the destination VNFM, the method further includes: receiving a modification operation of the user, using the VNFM specified by the user as the destination VNFM; or receiving the confirmation operation of the user, The user confirms the VNFM as the destination VNFM.

A migration device for a virtualized network function VNF, comprising:

a first determining module, configured to determine, in the original virtualized network function management VNFM managed by the original network function virtualization orchestration NFVO, the VNF that is managed by the original VNFM and needs to be migrated;

a second determining module, configured to determine, in the NFVO other than the original NFVO and/or the original NFVO, a destination VNFM capable of receiving the VNF to be migrated;

And a migration module configured to migrate the VNF that needs to be migrated to the destination VNFM.

In some embodiments, the first determining module is configured to determine a VNF that needs to be migrated according to a service request success rate of the VNF, a service request completion time of the VNF, and/or a load of the original VNFM.

In some embodiments, the second determining module is configured to determine a destination VNFM capable of receiving the VNF that needs to be migrated according to the following manner:

Creating a new VNFM in the original NFVO as the target VNFM;

And/or, a new VNFM is created in the other NFVO as the destination VNFM.

In some embodiments, the migration module includes:

The first migration sub-module is configured to delete the configuration information of the VNF to be migrated from the management information of the original VNFM on the premise that the destination VNFM belongs to the original NFVO management; and the management information of the VNFM in the destination Adding the configuration information of the VNF to be migrated; and configuring the configuration information of the VNF to be migrated from the original VNFM to the destination VNFM in the management information of the original NFVO;

And the second migration sub-module, configured to generate the resource information of the VNF to be migrated in the original NFVO on the premise that the destination VNFM is in the other NFVO; and import the required migration in the destination NFVO a product package of the VNF; generating new resource information according to the product package and the resource information in the destination NFVO and the destination VNFM, and adding the VNF to be migrated according to the new resource information.

In some embodiments, the migration device of the virtualized network function VNF further includes a user operation module configured to receive a modification operation of the user and specify the user before migrating the VNF to be migrated to the destination VNFM. The VNFM is used as the destination VNFM; or before the migration of the VNF to be migrated to the destination VNFM, the user's confirmation operation is received, and the user-confirmed VNFM is taken as the destination VNFM.

In the original VNFM managed by the original NFVO, the VNF that is managed by the original VNFM is determined, and in the original NFVO and/or other NFVOs other than the original NFVO, it is determined that the VNF that needs to be migrated can be received. The purpose of VNFM is to migrate the VNF to be migrated to the destination VNFM, realize the migration management of VNF between different VNFMs of the same NFVO, and even between different NFVOs, and realize the redeployment management of virtual machines and network resources of VNF. Effectively integrate system resources to make VNFM and NFVO Load balancing, which improves the response speed of VNFM and NFVO and improves management level.

BRIEF abstract

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

2 is a schematic diagram of a VNF migration apparatus according to an embodiment of the present invention;

FIG. 3 is a flowchart of a method for migrating a VNF under the same NFVO according to an embodiment of the present invention;

FIG. 4 is a flowchart of a method for migrating a VNF under different NFVO according to an embodiment of the present invention.

Embodiments of the invention

According to ETSI's specification requirements, a set of VNFs is defined in the NFV-MANO domain. Among them, NFVO is mainly responsible for VNF planning and deployment, and the whole network virtual resources are arranged. VNFM is responsible for VNF lifecycle management. One NFVO manages multiple VNFMs, and one VNFM manages multiple VNFs. The embodiment of the present invention proposes a scheme to implement migration management between VNFs of different NFVOs and even between different NFVOs. The embodiments of the present invention are described in detail below with reference to the accompanying drawings.

FIG. 1 is a flowchart of a method for migrating a virtualized network function VNF according to an embodiment of the present invention. Referring to FIG. 1, the following process is included:

S101. Determine, in the original VNFM managed by the original NFVO, the VNF that needs to be migrated managed by the original VNFM.

In this step, each VNFM under the management of each NFVO can be used as the original VNFM. The original VNFM can calculate whether it needs to migrate some of the VNFs it manages according to the preset VNF migration strategy. If it needs to be moved out, it reports NFVO.

The VNF migration policy can be formulated according to the three performance parameters of the VNFM load, the VNF service request success rate, and/or the VNF service request completion time.

The load of VNFM refers to the percentage of the number of VNFs currently managed by VNFM to the maximum number of VNFM management. The higher the percentage, the higher the load of VNFM. If the load of VNFM is too high, there will be It may reduce the management quality of the VNFM, so that the VNF's service request cannot be answered in a timely and effective manner.

The VNF service request success rate is the percentage of the VNF service request success rate when the VNF initiates a service request such as elastic scalability. The higher the percentage, the higher the service success rate of the VNF service. An important indicator of VNFM management quality. If the VNF service request success rate is high, then even if the VNFM is under full load, it is not necessary to migrate the VNF.

The service request completion time of the VNF refers to the time taken from the VNF to initiate a service request until the request is successfully completed. The shorter the time, the better. If the majority of the service request completion time is greater than the expected time, then the VNF can be considered to be moved out. Reduce the load of VNFM and improve the response efficiency of VNFM.

Step S101 may consider any of the foregoing performance parameters to determine the VNF to be migrated, or may combine three performance parameters to determine the VNF to be migrated.

S102. Determine, in the original NFVO and/or other NFVOs other than the original NFVO, a destination VNFM capable of receiving the VNF that needs to be migrated;

The original NFVO and other NFVOs can notify each VNFM they manage. Each VNFM determines whether it can receive the VNF that needs to be migrated according to its own load, and then reports it to its management NFVO. NFVO can be managed according to the load balancing principle. The VNFM report results from which the destination VNFM is determined. If the existing VNFM it manages cannot receive the VNF that needs to be migrated, the NFVO may suggest that the user create a new VNFM or automatically create a new VNFM as the destination VNFM. In summary, the principle of the purpose of VNFM is to try to balance the load of each VNFM.

In some embodiments, because the destination VNFM determined in step S102 may be inconsistent with the user's intention, in order to embody humanization, the user may be allowed to modify, that is, the following steps are also included:

Receiving the user's modification operation, using the VNFM specified by the user as the destination VNFM; or receiving the user's confirmation operation, using the VNFM confirmed by the user as the destination VNFM. After the user confirms the modification, the process proceeds to step S103.

S103. Migrate the VNF that needs to be migrated to the destination VNFM.

The migration step is completed according to the above-defined purpose VNFM, and may migrate to other existing VNFMs of the same NFVO, or new VNFMs under the same NFVO, or existing VNFMs under other NFVOs, Or other new VNFM under NFVO.

If the migration is to another existing VNFM of the same NFVO, or a new VNFM under the same NFVO, the migration step includes at least: deleting the configuration information of the VNF to be migrated from the management information of the original VNFM; The configuration information of the VNF to be migrated is added to the management information; in the management information of the original NFVO, the configuration information of the VNF to be migrated is transferred from the original VNFM to the destination VNFM, and the configuration of the same VNF in the original VNFM, the destination VNFM, and the original NFVO Information may be the same or it may be different.

If the migration is to an existing VNFM under other NFVOs, or a new VNFM under other NFVOs, the migration step includes at least: generating resource information of the VNF to be migrated in the original NFVO; and importing the required migration in the destination NFVO. The VNF product package; in the destination NFVO and the destination VNFM, generates new resource information according to the product package and the resource information, and adds the VNF to be migrated according to the new resource information.

2 is a schematic diagram of a device for migrating a virtualized network function VNF according to an embodiment of the present invention. As shown in FIG. 2, the device for migrating a virtualized network function VNF includes:

The first determining module 21 is configured to determine, in the original VNFM managed by the original NFVO, the VNF that needs to be migrated managed by the original VNFM;

The second determining module 22 is configured to determine, in the NFVO other than the original NFVO and/or the original NFVO, a destination VNFM capable of receiving the VNF that needs to be migrated;

The migration module 23 is configured to migrate the VNF that needs to be migrated to the destination VNFM.

In some embodiments, the first determining module 21 is configured to determine the VNFs that need to be migrated based on the service request success rate of the VNF, the service request completion time of the VNF, and/or the load of the original VNFM.

In some embodiments, the second determining module 22 is configured to determine a destination VNFM capable of receiving the VNF that needs to be migrated according to the following manner:

In the VNFM other than the original VNFM managed by the original NFVO, according to the load balancing principle Determining a destination VNFM capable of receiving the VNF to be migrated;

Creating a new VNFM in the original NFVO as the target VNFM;

And/or, a new VNFM is created in the other NFVO as the destination VNFM.

In some embodiments, the migration module 23 includes:

The first migration submodule 231 is configured to delete the configuration information of the VNF to be migrated from the management information of the original VNFM on the premise that the destination VNFM belongs to the original NFVO management; and manage the VNFM in the destination The configuration information of the VNF to be migrated is added to the information; the configuration information of the VNF to be migrated is classified from the original VNFM to the destination VNFM in the management information of the original NFVO;

And the second migration sub-module 232, configured to: in the other NFVO, generate the resource information of the VNF to be migrated in the original NFVO; import the required migration in the destination NFVO a product package of the VNF; generating new resource information according to the product package and the resource information in the destination NFVO and the destination VNFM, and adding the VNF to be migrated according to the new resource information.

In some embodiments, the user operation module 24 is further configured to receive a modification operation of the user and use the VNFM specified by the user as the destination VNFM before migrating the VNF to be migrated to the destination VNFM; or Before the VNF to be migrated migrates to the destination VNFM, the user confirms the operation and uses the VNFM confirmed by the user as the destination VNFM.

The solution of the embodiment of the present invention is exemplified below. VNFM (hereinafter referred to as the original VNFM) calculates whether it is necessary to move out part of the VNF under its management according to the VNF migration strategy. If it needs to move out, it reports its management NFVO (hereinafter referred to as the original NFVO); the original NFVO is received. After the report, send messages to other VNFMs under its management to determine which VNFMs under its management can receive new VNFs; receive VNFM calculations for messages Whether it is capable of receiving VNF and feedback to the original NFVO; the original NFVO summarizes the return message, formulates the migration plan, and reports to the user, and the user determines whether to execute the migration plan; when all the VNFM under the original NFVO management does not have In the case of receiving VNF, the original NFVO will recommend that the user create a new VNFM to receive the VNF. After the new VNFM is built, the original NFVO will re-define the migration plan; or it is recommended that the user migrate the VNF to other NFVOs and execute the migration plan after confirmation by the user. . The VNF migration policy is not limited to the following: according to the VNF service request success rate, the VNF service request completion time, and the VNFM load, to determine the VNF under the VNFM management that needs to be migrated; the migration plan enables the original NFVO management. Each VNFM load underneath tends to be balanced. The migration plan formulated by the original NVFO may be inconsistent with the user's intention. Therefore, in this embodiment, the user may be allowed to modify, and the VNF migration may be performed after the user modifies and confirms. VNF migration is divided into two cases: direct migration under the same NFVO and migration between different NFVOs.

FIG. 3 is a flowchart of a method for migrating a VNF under the same NFVO according to an embodiment of the present invention. The original VNFO migrates the VNF according to the migration plan. The process is as follows:

S301. The original NFVO initiates a migration VNF task according to the migration plan.

S302: After the original VNFM receives the notification, the VNF to be migrated is deleted from the original VNFM, and the configuration information of the VNF to be migrated is deleted from the management information of the original VNFM.

S303: The original VNFM notifies the original NFVO after deleting the VNF.

S304. After receiving the notification that the original VNFM completes the deletion of the VNF, the original NFVO initiates a notification to the destination VNFM.

S305. After receiving the request, the destination VNFM adds the VNF to be migrated to the destination VNFM, and includes adding configuration information of the VNF to be migrated to the management information of the destination VNFM. And notify the original NFVO reception is completed.

S306. In the original NFVO, the VNF to be migrated is classified from the original VNFM to the destination VNFM, and the configuration information of the VNF to be migrated is transferred from the original VNFM to the destination in the management information of the original NFVO. VNFM. This completes the migration of a single VNF.

S307. The original NFVO determines whether the VNF migration is completed. If the migrated VNF has completed the migration, the entire migration task is completed; if there is still no migration of the VNF, then the step S301 is continued to execute the migration plan.

FIG. 4 is a flowchart of a method for migrating a VNF under different NFVO according to an embodiment of the present invention. The original VNFO migrates the VNF according to the migration plan. The process is as follows:

S401. Generate resource information of the VNF to be migrated on the original NFVO according to the migration plan, and the generation process needs to be completed by the original VNFM.

S402. The destination NFVO introduces a product package of the VNF to be migrated, and the product package may be one or more.

S403. The destination NFVO queries, according to the product package information, whether the VNFM under its management can receive the VNF. If you can't find a VNFM that can receive VNF, you can request a new VNFM.

S404, the original NFVO and the original VNFM terminate the management of the VNF that needs to be migrated, and the VNF related information that needs to be migrated will be cleared from the original NFVO and the original VNFM, but the resources of the VNF can be reserved.

S405. The destination NFVO and the destination VNFM generate resource information of the new VNF according to the resource information and the product package of the VNF. Most of the resources of the VNF will be preserved, and some unavailable resources, such as network resources whose destination VNFM is unavailable, will be replaced.

S406: Modify the VNF resource according to the newly generated VNF resource information, where the network resource is mainly used, and the network of the VNF is included in the management plane of the VNFM by modifying the network resource.

S407, the destination NFVO, and the destination VNFM complete the access to the VNF, and store the information of the VNF.

The embodiment of the invention provides a method for migrating a VNF in an NFV. The method can realize the redeployment management of the virtual machine and the network resource of the VNF, effectively integrate the system resources, and balance the load of the VNFM and the NFVO, thereby improving the VNFM. And NFVO's response speed, improve management level.

The above content is a detailed description of the present application in combination with the embodiment, and the actual application of the present application cannot be determined. The application is limited to these instructions. It will be apparent to those skilled in the art that the present invention can be made in the form of a single deduction or substitution without departing from the scope of the present application.

Industrial applicability

The method and device for migrating the virtualized network function VNF of the present application, in the original virtualized network function management VNFM managed by the original network function virtualization orchestration NFVO, determining the VNF to be migrated managed by the original VNFM; In the NFVO and/or other NFVOs other than the original NFVO, a destination VNFM capable of receiving the VNF to be migrated is determined; and the VNF to be migrated is migrated to the destination VNFM. Through the above technical solutions, the problem that the existing VNF cannot be migrated between different VNFMs is solved.

Claims

A method for migrating a virtualized network function VNF, comprising:

Determining the VNF to be migrated managed by the original VNFM in the original virtualized network function management VNFM managed by the original network function virtualization orchestration NFVO;

Determining a destination VNFM capable of receiving the VNF to be migrated in the NFVO other than the original NFVO and/or other than the original NFVO;

The VNF that needs to be migrated is migrated to the target VNFM.
The method for migrating a virtualized network function VNF according to claim 1, wherein in the original VNFM managed by the original NFVO, determining the VNF to be migrated managed by the original VNFM includes:

The VNF to be migrated is determined according to the service request success rate of the VNF, the service request completion time of the VNF, and/or the load of the original VNFM.
The method for migrating a virtualized network function VNF according to claim 1, wherein in the NFVO other than the original NFVO and/or the original NFVO, determining the destination VNFM capable of receiving the VNF to be migrated comprises:

In the VNFM managed by the original NFVO except the original VNFM, determining a destination VNFM capable of receiving the VNF to be migrated according to a load balancing principle;

Creating a new VNFM in the original NFVO as the target VNFM;

In the other NFVO, determining a destination VNFM capable of receiving the VNF to be migrated according to a load balancing principle;

And/or, a new VNFM is created in the other NFVO as the destination VNFM.
The method for migrating a virtualized network function VNF according to claim 3, wherein, if the destination VNFM belongs to the original NFVO management, the migrating the VNF to be migrated to the destination VNFM includes:

Deleting the configuration information of the VNF to be migrated from the management information of the original VNFM; adding configuration information of the VNF to be migrated to the management information of the destination VNFM; and in the management information of the original NFVO The configuration information of the VNF to be migrated is classified from the original VNFM to the destination VNFM;

If the destination VNFM is in the other NFVO, the migrating the VNF to be migrated to the destination VNFM includes: generating resource information of the VNF to be migrated in the original NFVO; Importing the product package of the VNF to be migrated; generating new resource information according to the product package and the resource information in the destination NFVO and the destination VNFM, and adding the VNF to be migrated according to the new resource information .
The method for migrating a virtualized network function VNF according to any one of claims 1 to 4, before the migrating the VNF to the destination VNFM, the method further includes: receiving a modification operation of the user, and specifying the user The VNFM is used as the destination VNFM; or the user's confirmation operation is performed, and the user-confirmed VNFM is used as the destination VNFM.
A migration device for a virtualized network function VNF, comprising:

a first determining module, configured to determine, in the original virtualized network function management VNFM managed by the original network function virtualization orchestration NFVO, the VNF that is managed by the original VNFM and needs to be migrated;

a second determining module, configured to determine, in the NFVO other than the original NFVO and/or the original NFVO, a destination VNFM capable of receiving the VNF to be migrated;

And a migration module configured to migrate the VNF that needs to be migrated to the destination VNFM.
The migration device of the virtualization network function VNF according to claim 6, wherein the first determining module is configured to be based on a service request success rate of the VNF, a service request completion time of the VNF, and/or a load of the original VNFM, To determine the VNF that needs to be migrated.
The migration device of the virtualization network function VNF of claim 6, wherein the second determining module is configured to determine a destination VNFM capable of receiving the VNF to be migrated according to the following manner:

In the VNFM managed by the original NFVO except the original VNFM, determining a destination VNFM capable of receiving the VNF to be migrated according to a load balancing principle;

Creating a new VNFM in the original NFVO as the target VNFM;

In the other NFVO, determining a destination VNFM capable of receiving the VNF to be migrated according to a load balancing principle;

And/or, a new VNFM is created in the other NFVO as the destination VNFM.
The migration device of the virtualization network function VNF of claim 7, wherein the migration module comprises:

The first migration sub-module is configured to delete the configuration information of the VNF to be migrated from the management information of the original VNFM on the premise that the destination VNFM belongs to the original NFVO management; and the management information of the VNFM in the destination Adding the configuration information of the VNF to be migrated; and configuring the configuration information of the VNF to be migrated from the original VNFM to the destination VNFM in the management information of the original NFVO;

And the second migration sub-module, configured to generate the resource information of the VNF to be migrated in the original NFVO on the premise that the destination VNFM is in the other NFVO; and import the required migration in the destination NFVO a product package of the VNF; generating new resource information according to the product package and the resource information in the destination NFVO and the destination VNFM, and adding the VNF to be migrated according to the new resource information.
The migrating device of the virtualized network function VNF according to any one of claims 6 to 9, further comprising a user operation module configured to receive a modification operation of the user before migrating the VNF to be migrated to the destination VNFM The user-specified VNFM is used as the destination VNFM; or before the migration of the VNF to be migrated to the destination VNFM, the user's confirmation operation is received, and the user-confirmed VNFM is used as the destination VNFM.