Network anomaly detection and mitigation simulation tool
US-2022103576-A1 · Mar 31, 2022 · US
US11924020B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11924020-B2 |
| Application number | US-202217729278-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 26, 2022 |
| Priority date | Apr 26, 2022 |
| Publication date | Mar 5, 2024 |
| Grant date | Mar 5, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A data processing system is implemented for detecting changes to infrastructure components, and extracting metadata associated with the changes. The data processing system also implements grouping the changes based on the metadata, ranking the groups of changes based on past incidents of service outages, and displaying the ranked groups of changes to a user.
Opening claim text (preview).
What is claimed is: 1. A data processing system comprising: a processor; and a machine-readable storage medium storing executable instructions that, when executed, cause the processor to perform operations of: detecting software changes to infrastructure components; extracting metadata associated with the software changes; grouping the software changes based on the metadata; determining correlations between the groups of software changes and past incidents of service outages, the past incidents of service outages including situations in which a service offered by a cloud service supported by the infrastructure components is unavailable; ranking the groups of software changes based on the determined correlations; and displaying the ranked groups of software changes to a user, wherein the software changes to the infrastructure components include at least one of a code change applied to the infrastructure components and a configuration update applied to the infrastructure components. 2. The data processing system of claim 1 , wherein the metadata includes a type of infrastructure component, a location of an infrastructure component, a time of a change, and a date of a change. 3. The data processing system of claim 1 , wherein the infrastructure components include a tenant, a farm, virtual machine, and a physical machine. 4. The data processing system of claim 1 , wherein the infrastructure components support a cloud service. 5. The data processing system of claim 1 , wherein the machine-readable storage medium includes instructions configured to cause the processor to perform an operation of: detecting alerts of a service outage caused by the changes to the infrastructure components. 6. The data processing system of claim 1 , wherein the detecting the software changes to the infrastructure components includes analyzing a service tree of the infrastructure components. 7. The data processing system of claim 1 , wherein the detecting the software changes to the infrastructure components includes analyzing an object map of the infrastructure components. 8. A method implemented in a data processing system, the method comprising: detecting software changes to infrastructure components; extracting metadata associated with the software changes; grouping the software changes based on the metadata; determining correlations between the groups of software changes and past incidents of service outages, the past incidents of service outages including situations in which a service offered by a cloud service supported by the infrastructure components is unavailable; ranking the groups of software changes based on the determined correlations; and displaying the ranked groups of software changes to a user, wherein the software changes to the infrastructure components include at least one of a code change applied to the infrastructure components and a configuration update applied to the infrastructure components. 9. The method of claim 8 , wherein the ranking the groups of software changes includes correlating the groups of changes to past groups of changes of the past incidents of service outages. 10. The method of claim 8 , further comprising: detecting alerts of a service outage caused by the software changes to the infrastructure components. 11. The method of claim 8 , wherein the detecting the software changes to the infrastructure components includes analyzing a service tree of the infrastructure components. 12. The method of claim 8 , wherein the detecting the software changes to the infrastructure components includes analyzing an object map of the infrastructure components. 13. The method of claim 8 , wherein the grouping the software changes based on the metadata includes grouping based on an operation stage in which the software changes occurred. 14. A non-transitory machine-readable medium on which are stored instructions that, when executed, cause a processor of a programmable device to perform operations of: detecting software changes to infrastructure components; extracting metadata associated with the software changes; grouping the software changes based on the metadata; determining correlations between the groups of software changes and past incidents of service outages, the past incidents of service outages including situations in which a service offered by a cloud service supported by the infrastructure components is unavailable; ranking the groups of software changes based on the determined correlations; and displaying the ranked groups of software changes to a user, wherein the software changes to the infrastructure components include at least one of a code change applied to the infrastructure components and a configuration update applied to the infrastructure components. 15. The non-transitory machine-readable medium of claim 14 , wherein the metadata includes a type of infrastructure component, a location of an infrastructure component, a time of a change, and a date of a change. 16. The non-transitory machine-readable medium of claim 14 , wherein the infrastructure components include a tenant, a farm, virtual machine, and a physical machine. 17. The non-transitory machine-readable medium of claim 14 , wherein infrastructure components support a cloud service.
using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis · CPC title
by acting on the notification or alarm source · CPC title
by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure · CPC title
Additional information in the notification, e.g. enhancement of specific meta-data · CPC title
Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.