Dynamic Computing Resource Availability Rating via Probability Models

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In complex IT infrastructures, it is challenging to determine the impact of component-level outages on dependent applications and resources due to obscured health of underlying components and multi-layer dependencies, making it difficult to predict and prevent infrastructure and application outages.

Innovation Solution

A system and method that dynamically determine computing resource availability by generating application session data matrices, deriving component and metric signature blocks, and classifying them using probability models to identify dependencies and predict potential outages, enabling proactive measures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If virtualization layer is created on top of IT infrastructure, then resource abstraction and flexibility are improved, but the health of underlying components becomes obscured and difficult to detect

Engineering Contradiction:
Improveresource abstractionVSAvoidcomponent health detection
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent introduces an intermediary system that sits between the virtualization layer and the physical infrastructure, translating and correlating data from multiple sources including virtual machine metrics, physical hardware status, and application performance. This intermediary layer reconstructs the obscured health information by aggregating data from various levels of the stack, making it visible and actionable despite the virtualization abstraction.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system adds a new dimension of observation by creating a multi-layered view that correlates virtual, physical, and application-level metrics simultaneously. Instead of viewing infrastructure health from a single perspective, the system creates a holistic model that spans multiple dimensions including virtual machine status, physical hardware health, network conditions, and application performance, enabling detection that would be impossible from any single layer alone.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If multi-layer dependencies are implemented between applications, then system functionality and integration are improved, but determining the full scope of impacted applications during outages becomes exceedingly difficult

Engineering Contradiction:
Improveapplication integrationVSAvoiddependency mapping complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by automatically discovering and mapping all application dependencies and infrastructure relationships before outages occur. The system continuously builds and updates a dependency graph that captures multi-layer relationships between applications, virtual machines, physical hardware, and external services. This pre-established knowledge base enables rapid impact analysis when outages occur, eliminating the need to manually trace complex dependency chains during crisis situations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system replaces manual dependency analysis and troubleshooting processes with an automated computational approach. Instead of requiring operators to manually trace through complex multi-layer dependencies during outages, the system uses automated algorithms to instantly calculate and present the full scope of impacted applications and services, substituting mechanical human analysis with automated computational reasoning.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If comprehensive monitoring of all IT infrastructure components and applications is implemented, then outage detection capability is improved, but system complexity and resource consumption increase significantly

Engineering Contradiction:
Improveoutage detection capabilityVSAvoidmonitoring system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies the extraction principle by selectively pulling out and focusing on the most critical metrics and dependencies that actually impact service availability. Instead of monitoring every possible parameter uniformly, the system identifies and extracts the key performance indicators and dependency relationships that are most relevant to outage detection and impact analysis, reducing data volume while maintaining detection effectiveness.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements local quality by applying different monitoring intensities and granularities to different parts of the infrastructure based on their criticality and risk profiles. Critical components and applications receive more detailed monitoring and analysis, while less critical elements receive lighter monitoring. This differentiated approach optimizes resource utilization and reduces overall system complexity while maintaining high reliability for critical services.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10467360B1System and method for dynamically determining availability of a computing resource
Publication Date: 2019.11.05 FMR CORP
  • US10467360B1 patent drawing
  • US10467360B1 patent drawing
  • US10467360B1 patent drawing

AI summary

A method is described for dynamically determining availability of a computing resource. An application session is established, and an application session data matrix is generated including parameters specifying aspects of the application session, an application associated with the application session, and a computing resource on which the application session depends. A component signature block is derived based on the parameters of the application session data matrix. The component signature block identifies the computing resource on which the application session depends and a total number of sessions dependent on the computing resource. A metric signature block is generated based on one or more parameters of the application session data matrix and the component signature block. The metric signature block is classified according to one or more probability models. A computing resource availability rating for the computing resource is derived based on an output of the one or more probability models.