Dataflow Graph Performance Debugger And Design Rule Checker For CGRA
US-2024345936-A1 · Oct 17, 2024 · US
US9058359B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9058359-B2 |
| Application number | US-201213672770-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 9, 2012 |
| Priority date | Nov 9, 2012 |
| Publication date | Jun 16, 2015 |
| Grant date | Jun 16, 2015 |
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.
An incompatible software level of an information technology infrastructure component is determined by comparing collected inventory information to a minimum recommended software level. If a knowledge base search finds that the incompatible software level is associated with a prior infrastructure outage event, an outage count score is determined for the incompatible software level by applying an outage rule to a historic count of outages caused by a similar incompatible software level, and combined with an average outage severity score assigned to the incompatible software level based on a level of severity of an actual historic failure of the component within a context of the infrastructure to generate a normalized historical affinity risk score. The normalized historical affinity risk score is provided for prioritizing the correction of the incompatible software level in the context of other normalized historical risk level scores of other determined incompatible software levels.
Opening claim text (preview).
What is claimed is: 1. A method for management of information technology component software levels, the method comprising: determining an incompatible software level of one component of a plurality of components in an information technology infrastructure by comparing inventory information relevant to each of the components to a minimum recommended software level, wherein the incompatible software level is a stale current version of software that does not meet a minimum version re…
Physics · mapped topic
Physics · mapped topic
Physics · mapped topic
Physics · mapped topic
Physics · mapped topic
Related publications grouped by family.
Free tools are coming soon. Tell us what you want to track and we'll notify you.
Answers are generated from the same data shown on this page.