IP Library Granted Patent US 11,474,918
Granted Patent B1
US 11,474,918 · App. 16/790,981 · Granted Oct 18, 2022

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

Inventors: Nimrod Sandlerman (Ramat Gan, IL); Ofer Hermoni (Tenafly, NJ); Eyal Felstaine (Herzliya, IL)
Assignee: AMDOCS DEVELOPMENT LIMITED
G06F11/203H04L67/1034G06F2201/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 11,474,918
App. No.
16/790,981
Granted
Oct 18, 2022
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 (33)

1. A method, comprising:

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

selecting a second network component to be used for replacing the instance of the VNF in the first network component, the second network component being a second server having one or more computer processors for executing another instance of the VNF on a virtual machine of the second server, wherein the second server is separate from the first server;

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 replacing the instance of the VNF in the first network component in order to initiate in the second network component the other instance of the VNF.

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.

4. The method of claim 3 , wherein the securing, maintaining, and installing are performed prior to determining to replace the instance of the VNF in the first network component.

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 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 server having one or more computer processors for executing a third instance of the VNF on a virtual machine of the third hardware unit:

selecting a fourth network component to be used for replacing the third instance of the VNF in the third network component;

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.

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.

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 is performed responsive to detecting 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 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 replaced 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 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:

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

selecting a second network component to be used for replacing the instance of the VNF in the first network component, the second network component being a second server having one or more computer processors for executing another instance of the VNF on a virtual machine of the second server, wherein the second server is separate from the first server;

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 replacing the instance of the VNF in the first network component in order to initiate in the second network component the other instance of the VNF.

20. A system comprising:

a memory system; and

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

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

selecting a second network component to be used for replacing the instance of the VNF in the first network component, the second network component being a second server having one or more computer processors for executing another instance of the VNF on a virtual machine of the second server, wherein the second server is separate from the first server;

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 replacing the instance of the VNF in the first network component in order to initiate in the second network component the other instance of the VNF.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 14, 2020
From: SANDLERMAN, NIMROD; HERMONI, OFER; FELSTAINE, EYAL
To: AMDOCS DEVELOPMENT LIMITED
Reel/Frame 051942/0024 →
Continuity (99)
Continuation In Part 16782934 · Feb 5, 2020
Continuation In Part 16782956 · Feb 5, 2020
Continuation In Part 16782906 · Feb 5, 2020
Continuation In Part 16453584 · Jun 26, 2019
Continuation In Part 16290779 · Mar 1, 2019
Continuation In Part 16290773 · Mar 1, 2019
Continuation In Part 16287922 · Feb 27, 2019
Continuation In Part 16280634 · Feb 20, 2019
Continuation In Part 16280245 · Feb 20, 2019
Continuation In Part 16280310 · Feb 20, 2019
Continuation In Part 16280301 · Feb 20, 2019
Continuation In Part 16280259 · Feb 20, 2019
Continuation In Part 16280246 · Feb 20, 2019
Continuation In Part 16280320 · Feb 20, 2019
Continuation In Part 16280386 · Feb 20, 2019
Continuation In Part 16280286 · Feb 20, 2019
Continuation In Part 16280260 · Feb 20, 2019
Continuation In Part 16280265 · Feb 20, 2019
Continuation In Part 16280272 · Feb 20, 2019
Continuation In Part 16280312 · Feb 20, 2019
Continuation In Part 16280353 · Feb 20, 2019
Continuation In Part 16280367 · Feb 20, 2019
Continuation In Part 16280279 · Feb 20, 2019
Continuation 16280513 · Feb 20, 2019
Continuation In Part 16255635 · Jan 23, 2019
Continuation In Part 16255609 · Jan 23, 2019
Continuation In Part 16044442 · Jul 24, 2018
Continuation In Part 15981804 · May 16, 2018
Continuation In Part 62648287 · Mar 26, 2018
Continuation In Part 62648287 · Mar 26, 2018
Continuation In Part 62648287 · Mar 26, 2018
Continuation 62637337 · Mar 1, 2018
Continuation 16790981
Continuation In Part 15841123 · Dec 13, 2017
Continuation In Part 15672068 · Aug 8, 2017
Continuation In Part 15586087 · May 3, 2017
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 14606991 · Jan 27, 2015
Continuation In Part 14606999 · 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 14572716 · Dec 16, 2014
Continuation 14572723 · Dec 16, 2014
Continuation In Part 14572726 · Dec 16, 2014
Continuation In Part 14572729 · Dec 16, 2014
Continuation In Part 14572728 · Dec 16, 2014
Continuation 14572719 · Dec 16, 2014
Continuation In Part 14572732 · 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
Provisional Application 62690290 · Jun 26, 2018
Provisional Application 62660142 · Apr 19, 2018
Provisional Application 62648287 · Mar 26, 2018
Provisional Application 62648281 · Mar 26, 2018
Provisional Application 62642524 · Mar 13, 2018
Provisional Application 62639910 · Mar 7, 2018
Provisional Application 62639913 · Mar 7, 2018
Provisional Application 62639923 · Mar 7, 2018
Provisional Application 62637337 · Mar 1, 2018
Provisional Application 62539362 · Jul 31, 2017
Provisional Application 62509623 · May 22, 2017
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 62026508 · Jul 18, 2014
Provisional Application 62026512 · Jul 18, 2014
Provisional Application 62020939 · Jul 3, 2014
Provisional Application 62014005 · Jun 18, 2014
Provisional Application 62013997 · 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