Automated Application Failure Recovery System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The conventional process of fixing failures in software applications is time-consuming due to manual identification and execution of solutions, which can be inefficient and prone to errors, especially when system changes occur.

Innovation Solution

A method and system for automatically selecting and executing solutions on a target application by identifying failure events, classifying them as labeled or unlabeled, and using a recovery database to apply appropriate solutions, with machine learning models aiding in classification and solution selection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual identification and execution of solutions is used, then the application development team can resolve failure events, but the process consumes excessive time and is inefficient

Engineering Contradiction:
Improvefailure resolution efficiencyVSAvoidtime consumed in identifying and executing solutions
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system enables self-service by automatically monitoring the application, identifying failure events, selecting appropriate solutions from the recovery database, and executing them without human intervention. The automated agent performs all these tasks independently, freeing the application development team from manual failure resolution work.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Solutions are pre-stored in a recovery database before failures occur. When a failure event is detected, the system quickly retrieves and executes the pre-prepared solution, eliminating the time needed for analysis and solution development during the failure event itself.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual monitoring and analysis is performed, then failure events can be detected and resolved, but the process is prone to errors and delays

Engineering Contradiction:
Improveaccuracy of failure detection and solution executionVSAvoidtime for manual analysis and solution mapping
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces the mechanical manual process of monitoring, analyzing, and resolving failures with an automated software agent that uses machine learning models and algorithms to detect failures and execute solutions, eliminating human error and speeding up the process.

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

Solution Approach 2:

The system continuously monitors the application and provides feedback on its state. When failures are detected, the automated agent executes solutions and monitors the results, creating a closed-loop feedback system that ensures reliable and timely failure resolution.

Inventive Principle:
Principle #23Feedback

3Productivity

If the application development team manually handles each failure event, then solutions can be applied, but time is lost that could be invested in more critical issues

Engineering Contradiction:
Improvetime allocation for critical issuesVSAvoidmanual effort required for failure resolution
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The automated monitoring and recovery system handles routine failure events independently, allowing the application development team to focus their manual efforts on more critical and complex issues that require human judgment and expertise.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12292785B2Method and system for automatically selecting and executing solutions on the target application
Publication Date: 2025.05.06 JPMORGAN CHASE BANK NA
  • US12292785B2 patent drawing
  • US12292785B2 patent drawing
  • US12292785B2 patent drawing

AI summary

A method for automatically selecting and executing solutions on a target application is disclosed. The method includes: identifying at least one failure event associated with the target application based on monitoring of the target application; classifying each of the identified failure events as one from among a labeled failure event and an unlabeled failure event; selecting a recovery solution for the labeled failure event from at least one recovery database; and automatically executing the selected recovery solution on the target application for the labeled failure event.