System, method, and computer program for managing hierarchy and optimization in a network function virtualization (NFV) based communication network

• US 10,063,633 B1
• Filed: 08/01/2016
• Issued: 08/28/2018
• Est. Priority Date: 12/19/2013
• Status: Active Grant

• Current Assignee: Amdocs Development Limited (Amdocs Ltd.)
• Original Assignee: Amdocs Development Limited (Amdocs Ltd.)
• Inventors: Felstaine, Eyal, Hermoni, Ofer, Sandlerman, Nimrod
• Primary Examiner(s): Chavis, John
• Application Number:
  US15/225,737
• Time in Patent Office: 757 Days
• Field of Search: 718 1
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/5088 involving task migration
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/122 of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/131 Protocols for games, networked simulations or virtual reality
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A system, method, and computer program product are provided for managing hierarchy and optimization in network function virtualization based networks. In use, a first hardware unit of a plurality of hardware units associated with a network function virtualization (NFV) based communication network is identified, the first hardware unit being identified based on a first load characteristic associated with the first hardware unit. Further, a first virtual network function (VNF) instance associated with the first hardware unit is identified, the first VNF instance being associated with usage of at least one service. Additionally, at least one traffic route associated with the first VNF instance is identified, the at least one traffic route being associated with usage of the at least one service. Furthermore, a second hardware unit for handling at least a portion of a workload associated with the at least one service is identified, the second hardware unit being identified based on a second load characteristic associated with the second hardware unit, and the second hardware unit being capable of utilizing the at least one traffic route. Still yet, a second VNF instance is initiated in the second hardware unit. Moreover, at least part of the at least one service is migrated from the first VNF instance to the second VNF instance without disrupting the service.

Claims

1. A method, comprising:

identifying a first hardware unit of a plurality of hardware units associated with a network function virtualization (NFV) based communication network, the first hardware unit being identified based on a first load characteristic associated with the first hardware unit;

identifying a first virtual network function (VNF) instance associated with the first hardware unit, the first VNF instance being associated with usage of at least one service;

identifying at least one traffic route associated with the first VNF instance, the at least one traffic route being associated with usage of the at least one service;

identifying a second hardware unit for handling at least a portion of a workload associated with the at least one service, the second hardware unit being identified based on a second load characteristic associated with the second hardware unit, and the second hardware unit being capable of utilizing the at least one traffic route;

initiating a second VNF instance in the second hardware unit; and

migrating at least a part of the at least one service from the first VNF instance to the second VNF instance without disrupting the service.

2. The method of claim 1, wherein the first load characteristic associated with the first hardware unit indicates the first hardware unit has a highest load of the plurality of hardware units, and the second load characteristic associated with the second hardware unit indicates the second hardware unit has a load lower than the first hardware unit.

3. The method of claim 1, wherein the first load characteristic associated with the first hardware unit indicates the first hardware unit has a highest load growth of the plurality of hardware units, and the second load characteristic associated with the second hardware unit indicates the second hardware unit has a load decreasing with time.

4. The method of claim 1, wherein the first load characteristic associated with the first hardware unit indicates the first hardware unit has a highest anticipated load growth of the plurality of hardware units, and the second load characteristic associated with the second hardware unit indicates the second hardware unit has an anticipated decrease in a load over time.

5. The method of claim 1, wherein the first load characteristic associated with the first hardware unit indicates the first hardware unit is below a low load threshold, and the second load characteristic associated with the second hardware unit indicates the second hardware unit is below the low load threshold and is anticipated to be below the low load threshold longer than any other of the plurality of hardware units.

6. The method of claim 1, further comprising turning off the first hardware unit, in response to migrating the at least one service from the first VNF instance to the second VNF instance.

7. The method of claim 1, wherein the first VNF instance includes a plurality of VNF instances and the second load characteristic associated with the second hardware unit indicates the second hardware unit is at least one of:

a hardware unit with a lowest load among a plurality of hardware units associated with the at least one traffic route;

a hardware unit with a fastest rate of decreasing load of the plurality of hardware units associated with the at least one traffic route;

a hardware unit with a highest anticipated rate of decreasing load of the plurality of hardware units associated with the at least one traffic route; and

a hardware unit with a longest anticipated time to reach a threshold load of the plurality of hardware units associated with the at least one traffic route; and

further comprising migrating the at least one service from the plurality of VNF instances to the second VNF instance without disrupting the service.

8. A computer program product embodied on a non-transitory computer readable medium, comprising:

computer code for identifying a first hardware unit of a plurality of hardware units associated with a network function virtualization (NFV) based communication network, the first hardware unit being identified based on a first load characteristic associated with the first hardware unit;

computer code for identifying a first virtual network function (VNF) instance associated with the first hardware unit, the first VNF instance being associated with usage of at least one service;

computer code for identifying at least one traffic route associated with the first VNF instance, the at least one traffic route being associated with usage of the at least one service;

computer code for identifying a second hardware unit for handling at least a portion of a workload associated with the at least one service, the second hardware unit being identified based on a second load characteristic associated with the second hardware unit, and the second hardware unit being capable of utilizing the at least one traffic route;

computer code for initiating a second VNF instance in the second hardware unit; and

computer code for migrating at least part of the at least one service from the first VNF instance to the second VNF instance without disrupting the service.

9. The computer program product of claim 8, wherein the computer program product is operable such that the first load characteristic associated with the first hardware unit indicates the first hardware unit has a highest load of the plurality of hardware units, and the second load characteristic associated with the second hardware unit indicates the second hardware unit has a load lower than the first hardware unit.

10. The computer program product of claim 8, wherein the computer program product is operable such that the first load characteristic associated with the first hardware unit indicates the first hardware unit has a highest load growth of the plurality of hardware units, and the second load characteristic associated with the second hardware unit indicates the second hardware unit has a load decreasing with time.

11. The computer program product of claim 8, wherein the computer program product is operable such that the first load characteristic associated with the first hardware unit indicates the first hardware unit has a highest anticipated load growth of the plurality of hardware units, and the second load characteristic associated with the second hardware unit indicates the second hardware unit has an anticipated decrease in a load over time.

12. The computer program product of claim 8, wherein the computer program product is operable such that the first load characteristic associated with the first hardware unit indicates the first hardware unit is below a low load threshold, and the second load characteristic associated with the second hardware unit indicates the second hardware unit is below the low load threshold and is anticipated to be below the low load threshold longer than any other of the plurality of hardware units.

13. The computer program product of claim 8, further comprising computer code for turning off the first hardware unit, in response to migrating the at least one service from the first VNF instance to the second VNF instance.

14. The computer program product of claim 8, wherein the computer program product is operable such that the first VNF instance includes a plurality of VNF instances and the second load characteristic associated with the second hardware unit indicates the second hardware unit is at least one of:

a hardware unit with a lowest load among a plurality of hardware units associated with the at least one traffic route;

a hardware unit with a fastest rate of decreasing load of the plurality of hardware units associated with the at least one traffic route;

a hardware unit with a highest anticipated rate of decreasing load of the plurality of hardware units associated with the at least one traffic route; and

a hardware unit with a longest anticipated time to reach a threshold load of the plurality of hardware units associated with the at least one traffic route; and

further comprising computer code for migrating the at least one service from the plurality of VNF instances to the second VNF instance without disrupting the service.

15. A system comprising:

a memory system; and

one or more processing cores coupled to the memory system and that are each configured to;

identify a first hardware unit of a plurality of hardware units associated with a network function virtualization (NFV) based communication network, the first hardware unit being identified based on a first load characteristic associated with the first hardware unit;

identify a first virtual network function (VNF) instance associated with the first hardware unit, the first VNF instance being associated with usage of at least one service;

identify at least one traffic route associated with the first VNF instance, the at least one traffic route being associated with usage of the at least one service;

identify a second hardware unit for handling at least a portion of a workload associated with the at least one service, the second hardware unit being identified based on a second load characteristic associated with the second hardware unit, and the second hardware unit being capable of utilizing the at least one traffic route;

initiate a second VNF instance in the second hardware unit; and

migrate at least part of the at least one service from the first VNF instance to the second VNF instance without disrupting the service.

16. The system of claim 15, wherein the system is operable such that the first load characteristic associated with the first hardware unit indicates the first hardware unit has a highest load of the plurality of hardware units, and the second load characteristic associated with the second hardware unit indicates the second hardware unit has a load lower than the first hardware unit.

17. The system of claim 15, wherein the system is operable such that the first load characteristic associated with the first hardware unit indicates the first hardware unit has a highest load growth of the plurality of hardware units, and the second load characteristic associated with the second hardware unit indicates the second hardware unit has a load decreasing with time.

18. The system of claim 15, wherein the system is operable such that the first load characteristic associated with the first hardware unit indicates the first hardware unit has a highest anticipated load growth of the plurality of hardware units, and the second load characteristic associated with the second hardware unit indicates the second hardware unit has an anticipated decrease in a load over time.

19. The system of claim 15, wherein the system is operable such that the first load characteristic associated with the first hardware unit indicates the first hardware unit is below a low load threshold, and the second load characteristic associated with the second hardware unit indicates the second hardware unit is below the low load threshold and is anticipated to be below the low load threshold longer than any other of the plurality of hardware units.

20. The system of claim 15, wherein the one or more processing cores coupled to the memory system are each further configured to turn off the first hardware unit, in response to migrating the at least one service from the first VNF instance to the second VNF instance.