IP Library Granted Patent US 10,606,718
Granted Patent B1
US 10,606,718 · App. 15/586,087 · Granted Mar 31, 2020

System, method, and computer program for managing fault recovery in network function virtualization (Nfv) based networks

Inventors: Nimrod Sandlerman (Ramat Gan, IL); Ofer Hermoni (Plano, TX); Eyal Felstaine (Kfar Shmaryahu, IL)
Assignee: AMDOCS DEVELOPMENT LIMITED
G06F11/203G06F2201/805
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,606,718
App. No.
15/586,087
Granted
Mar 31, 2020
Kind
B1
Abstract

According to one aspect of the present invention there is provided a system, method, and computer program product for recovering from a network failure in a communication network using network function virtualization (NFV-based network), the method including: selecting a first network component of the NFV-based network, detecting at least one probable failure of the first network component, selecting a second network component to be used for replacing the instance of the VNF in the first network component prior to a failure of the first network component, and securing at least one resource of the selected second network component for the other instance of the VNF and maintaining, in the selected second network component, an updated copy of data associated with the instance of the VNF in the first network component.

Claims (37)

1. A method, comprising:

selecting a first network component of a network function virtualization (NFV) based network, the first network component being a first hardware unit having one or more computer processors for executing an instance of a virtual network function (VNF) on a virtual machine of the first hardware unit;

detecting at least one probable failure of the first network component;

prior to a failure of the first network component, selecting a second network component to be used for replacing the instance of the VNF in the first network component when the first network component is faulty, the second network component being a second hardware unit having one or more computer processors for executing another instance of the VNF on a virtual machine of the second hardware unit;

securing at least one resource of the selected second network component for the other instance of the VNF and maintaining, in the selected second network component, an updated copy of data associated with the instance of the VNF in the first network component, for use when the first network component is detected to be faulty in order to initiate in the second network component the other instance of the VNF that replaces in the NFV based network the instance of the VNF in the faulty first network component.

2. The method of claim 1 , wherein the at least one resource of the selected second network component that is secured is at least one of processing power, memory, and storage.

3. The method of claim 1 , further comprising installing the other instance of the VNF in the selected second network component for use when the first network component is detected to be faulty.

4. The method of claim 3 , wherein the securing, maintaining, and installing are performed prior to a detection that the first network component is faulty.

5. The method of claim 1 , wherein the updated copy of data maintained in the selected second network component enables initiating the other instance of the VNF in the selected second network component with minimal delay.

6. The method of claim 1 , wherein selecting the second network component and securing the at least one resource of the second network component are performed as part of creating a plan for replacing, upon detection of the failure of the first network component, the instance of the VNF operating in the first network component by operating the other instance of the VNF in the second network component.

7. The method of claim 1 , further comprising, for a third network component of the NFV-based network that is a third hardware unit having one or more computer processors for executing a third instance of the VNF on a virtual machine of the third hardware unit:

detecting at least one probable failure of the third network component;

prior to a failure of the third network component, selecting a fourth network component to be used for replacing the third instance of the VNF in the third network component when the third network component is faulty;

securing at least one resource of the selected fourth network component for the third instance of the VNF.

8. The method of claim 1 , wherein the VNF is a software program implementation of a function, feature or service provided by the NFV based network.

9. The method of claim 8 , wherein each instance of the VNF is a separate implementation of the software program.

10. The method of claim 1 , wherein a fault recovery module of a NFV management system enables the selecting of the second network component to be used for replacing the instance of the VNF in the first network component when the first network component is faulty.

11. The method of claim 10 , wherein a user selects, through the fault recovery module, the second network component to be used for replacing the instance of the VNF in the first network component when the first network component is faulty.

12. The method of claim 1 , wherein securing the at least one resource of the selected second network component for the other instance of the VNF includes securing all resources required for the second network component to host the other instance of the VNF.

13. The method of claim 1 , wherein the selecting of the second network component to be used for replacing the instance of the VNF in the first network component when the first network component is faulty is performed responsive to detecting the at least one probable failure of the first network component.

14. The method of claim 13 , wherein the selecting of the second network component to be used for replacing the instance of the VNF in the first network component when the first network component is faulty is performed based on a priority given to the at least one probable failure of the first network component.

15. The method of claim 14 , wherein the priority is given based on a probability of the at least one probable failure of the first network component.

16. The method of claim 1 , wherein securing the at least one resource of the selected second network component for the other instance of the VNF prevents the at least one resource from being allocated to any other consumer of the at least one resource.

17. The method of claim 16 , wherein the any other consumer is another VNF in the NFV based network.

18. The method of claim 1 , securing the at least one resource of the selected second network component for the other instance of the VNF ensures availability of the at least one resource of the selected second network component for use when the first network component is detected to be faulty in order to initiate in the second network component the other instance of the VNF that replaces in the NFV based network the instance of the VNF in the faulty first network component.

19. A non-transitory computer readable medium storing computer code executable by a computer processor to perform a method, the method comprising:

selecting a first network component of a network function virtualization (NFV) based network, the first network component being a first hardware unit having one or more computer processors for executing an instance of a virtual network function (VNF) on a virtual machine of the first hardware unit;

detecting at least one probable failure of the first network component;

prior to a failure of the first network component, selecting a second network component to be used for replacing the instance of the VNF in the first network component when the first network component is faulty, the second network component being a second hardware unit having one or more computer processors for executing another instance of the VNF on a virtual machine of the second hardware unit;

securing at least one resource of the selected second network component for the other instance of the VNF and maintaining, in the selected second network component, an updated copy of data associated with the instance of the VNF in the first network component, for use when the first network component is detected to be faulty in order to initiate in the second network component the other instance of the VNF that replaces in the NFV based network the instance of the VNF in the faulty first network component.

20. A system comprising:

a memory system; and

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

selecting a first network component of a network function virtualization (NFV) based network, the first network component being a first hardware unit having one or more computer processors for executing an instance of a virtual network function (VNF) on a virtual machine of the first hardware unit;

detecting at least one probable failure of the first network component;

prior to a failure of the first network component, selecting a second network component to be used for replacing the instance of the VNF in the first network component when the first network component is faulty, the second network component being a second hardware unit having one or more computer processors for executing another instance of the VNF on a virtual machine of the second hardware unit;

securing at least one resource of the selected second network component for the other instance of the VNF and maintaining, in the selected second network component, an updated copy of data associated with the instance of the VNF in the first network component, for use when the first network component is detected to be faulty in order to initiate in the second network component the other instance of the VNF that replaces in the NFV based network the instance of the VNF in the faulty first network component.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 7, 2018
From: SANDLERMAN, NIMROD; HERMONI, OFER; FELSTAINE, EYAL
To: AMDOCS DEVELOPMENT LIMITED
Reel/Frame 046819/0254 →
Continuity (52)
Continuation In Part 15331724 · Oct 21, 2016
Continuation In Part 15275189 · Sep 23, 2016
Continuation In Part 15268427 · Sep 16, 2016
Continuation In Part 15225737 · Aug 1, 2016
Continuation In Part 15222844 · Jul 28, 2016
Continuation In Part 15166186 · May 26, 2016
Continuation In Part 15083150 · Mar 28, 2016
Continuation In Part 15081746 · Mar 25, 2016
Continuation In Part 15007076 · Jan 26, 2016
Continuation In Part 14977489 · Dec 21, 2015
Continuation In Part 14940083 · Nov 12, 2015
Continuation In Part 14819263 · Aug 5, 2015
Continuation In Part 14673587 · Mar 30, 2015
Continuation In Part 14673602 · Mar 30, 2015
Continuation In Part 14631707 · Feb 25, 2015
Continuation In Part 14625596 · Feb 18, 2015
Continuation In Part 14606999 · Jan 27, 2015
Continuation In Part 14606991 · Jan 27, 2015
Continuation In Part 14605856 · Jan 26, 2015
Continuation In Part 14597165 · Jan 14, 2015
Continuation In Part 14593505 · Jan 9, 2015
Continuation In Part 14593538 · Jan 9, 2015
Continuation In Part 14572728 · Dec 16, 2014
Continuation In Part 14572732 · Dec 16, 2014
Continuation In Part 14572726 · Dec 16, 2014
Continuation In Part 14572729 · Dec 16, 2014
Continuation In Part 14572735 · Dec 16, 2014
Continuation In Part 14561126 · Dec 4, 2014
Continuation In Part 14538754 · Nov 11, 2014
Continuation In Part 14538731 · Nov 11, 2014
Continuation 14572716 · Dec 16, 2014
Continuation 14572719 · Dec 16, 2014
Continuation 14572723 · Dec 16, 2014
Provisional Application 62447855 · Jan 18, 2017
Provisional Application 62244674 · Oct 21, 2015
Provisional Application 62140353 · Mar 30, 2015
Provisional Application 62138897 · Mar 26, 2015
Provisional Application 62107943 · Jan 26, 2015
Provisional Application 62078365 · Nov 11, 2014
Provisional Application 62034721 · Aug 7, 2014
Provisional Application 62034715 · Aug 7, 2014
Provisional Application 62033615 · Aug 5, 2014
Provisional Application 62033606 · Aug 5, 2014
Provisional Application 62027709 · Jul 22, 2014
Provisional Application 62026512 · Jul 18, 2014
Provisional Application 62026508 · Jul 18, 2014
Provisional Application 62020939 · Jul 3, 2014
Provisional Application 62013997 · Jun 18, 2014
Provisional Application 62014005 · Jun 18, 2014
Provisional Application 61981116 · Apr 17, 2014
Provisional Application 61941380 · Feb 18, 2014
Provisional Application 61918597 · Dec 19, 2013
Cited By (1)
US 12,265,843