IP Library Granted Patent US 10,924,329
Granted Patent B2
US 10,924,329 · App. 16/358,734 · Granted Feb 16, 2021

Self-healing Telco network function virtualization cloud

Inventors: Radhakrishna Embarmannar Vijayan (Bangalore, IN); Thatayya Naidu Venkata Polamarasetty (Bangalore, IN)
Assignee: VMWARE, INC.
H04L41/0631G06F9/455G06F9/45541H04L41/04H04L41/065H04L41/0654H04L41/0677H04L41/0686H04L41/22H04L43/045H04L43/065H04L43/0829H04L43/12H04L43/14H04L43/16
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,924,329
App. No.
16/358,734
Granted
Feb 16, 2021
Kind
B2
Abstract

Examples herein describe systems and methods for self-healing in a Telco network function virtualization cloud. KPI attributes for virtual network functions can be mapped to physical fault notifications to create synthesized alerts. The synthesized alerts can include information from both a virtual and physical layer, allowing a self-healing action framework to determine root causes of problems in the Telco cloud. Remedial actions can then be performed in either the virtual or physical layer of the Telco cloud. Remedial actions in one layer can be based on root causes identified in the other, which can allow for remediation before network downtime occurs.

Claims (55)

1. A method for network function virtualization self-healing, comprising:

sending an alert from a virtual analytics engine to a physical analytics engine based on a key performance indicator (“KPI”) threshold comparison for a virtual component of a distributed network;

determining, at the physical analytics engine, that a problem with hardware exists based on comparing a virtual KPI attribute from the alert to a symptom threshold;

correlating, by the physical analytics engine, the alert to a physical hardware device by mapping the virtual component associated with the alert to the physical hardware device; and

sending a root cause analysis event used for remediating the problem, wherein the root cause analysis event includes information about the physical hardware device and virtual KPI attribute, and wherein remediating the problem includes at least one of:

presenting a notification on a graphical user interface (“GUI”); and

making a change to at least one of the virtual component and physical hardware device.

2. The method of claim 1 , wherein the root cause analysis event is used to determine a remedial action in the distributed network by comparing information from the root cause analysis event to an action policy file, wherein an adaptor formats a request to perform the remedial action.

3. The method of claim 1 , wherein the root cause analysis event is sent from the physical analytics engine and identifies a problem in the virtual layer.

4. The method of claim 1 , further comprising:

translating the alert from the virtual analytics engine into an object used by the physical analytics engine; and

using the translated object to correlate the alert to the physical hardware device.

5. The method of claim 1 , further comprising:

sending a physical fault notification from the physical analytics engine to the virtual analytics engine;

querying, by the virtual analytics engine, for KPI information based on the physical fault notification; and

wherein the root cause analysis event is a synthesized alert based on the KPI information and physical fault notification.

6. The method of claim 5 , wherein the virtual analytics engine sends the synthesized alert to a self-healing component, and wherein the self-healing component sends a command to perform a remedial action based on the synthesized alert.

7. The method of claim 6 , wherein the synthesized alert from the virtual analytics engine causes the remedial action to take place in a physical layer of the distributed network.

8. A non-transitory, computer-readable medium comprising instructions that, when executed by a processor, perform stages for network function virtualization self-healing, the stages comprising:

sending an alert from a virtual analytics engine to a physical analytics engine based on a key performance indicator (“KPI”) threshold comparison for a virtual component of a distributed network;

determining that a problem exists with hardware based on comparing a virtual KPI attribute from the alert to a symptom threshold;

correlating, by the physical analytics engine, the alert to a physical hardware device by mapping the virtual component associated with the alert to the physical hardware device; and

sending a root cause analysis event used for remediating the problem, wherein the root cause analysis event includes information about the physical hardware device and virtual KPI attribute, and wherein remediating the problem includes at least one of:

presenting a notification on a graphical user interface (“GUI”); and

making a change to at least one of the virtual component and physical hardware device.

9. The non-transitory, computer-readable medium of claim 8 , wherein the root cause analysis event is used to determine a remedial action in the distributed network by comparing information from the root cause analysis event to an action policy.

10. The non-transitory, computer-readable medium of claim 8 , wherein the root cause analysis event is sent from the physical analytics engine and identifies a problem in the virtual layer.

11. The non-transitory, computer-readable medium of claim 8 , the stages further comprising:

translating the alert into an object used by the physical analytics engine; and

using the translated object to correlate the alert to the physical hardware device.

12. The non-transitory, computer-readable medium of claim 8 , the stages further comprising:

sending a physical fault notification from the physical analytics engine to the virtual analytics engine;

querying, by the virtual analytics engine, for KPI information based on the physical fault notification; and

wherein the root cause analysis event is a synthesized alert based on the KPI information and physical fault notification.

13. The non-transitory, computer-readable medium of claim 12 , wherein the virtual analytics engine sends the synthesized alert to a self-healing component, and wherein the self-healing component sends a command to perform a remedial action based on the synthesized alert.

14. The non-transitory, computer-readable medium of claim 13 , wherein the synthesized alert from the virtual analytics engine causes the remedial action to take place in a physical layer of the distributed network.

15. A system for performing self-healing in a distributed network, comprising:

a non-transitory, computer-readable medium containing instructions; and

at least one processor that executes the instructions to perform stages comprising:

sending an alert from a virtual analytics engine to a physical analytics engine based on a key performance indicator (“KPI”) threshold comparison for a virtual component of a distributed network;

determining that a problem with hardware exists based on comparing a virtual KPI attribute from the alert to a symptom threshold;

correlating, by the physical analytics engine, the alert to a physical hardware device by mapping the virtual component associated with the alert to the physical hardware device; and

sending a root cause analysis event used for remediating the problem, wherein the root cause analysis event includes information about the physical hardware device and virtual KPI attribute, and wherein remediating the problem includes at least one of:

presenting a notification on a graphical user interface (“GUI”); and

making a change to at least one of the virtual component and physical hardware device.

16. The system of claim 15 , wherein the root cause analysis event is used to determine a remedial action in the distributed network by comparing information from the root cause analysis event to an action policy file, and wherein an adaptor formats a request to perform the remedial action.

17. The system of claim 15 , wherein the root cause analysis event is sent from the physical analytics engine and identifies a problem in the virtual layer.

18. The system of claim 15 , the stages further comprising:

translating the alert into an object used by the physical analytics engine; and

using the translated object to correlate the alert to the physical hardware device.

19. The system of claim 15 , the stages further comprising:

sending a physical fault notification from the physical analytics engine to the virtual analytics engine;

querying, by the virtual analytics engine, for KPI information based on the physical fault notification; and

wherein the root cause analysis event is a synthesized alert based on the KPI information and physical fault notification.

20. The system of claim 19 , wherein the virtual analytics engine sends the synthesized alert to a self-healing component, and wherein the self-healing component sends a command to perform a remedial action in a physical layer of the distributed network.

Assignments (2)
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067103/0030 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 20, 2019
From: EMBARMANNAR VIJAYAN, RADHAKRISHNA; POLAMARASETTY, THATAYYA NAIDU VENKATA
To: VMWARE, INC.
Reel/Frame 048643/0017 →
Priority Claims (1)
IN 201941002229 · Jan 18, 2019 · national
Continuity (1)
Related Publication 20200235986A1 · Jul 23, 2020
Cited By (1)
US 12,531,775