Emulator-Based Error Scenario Generation for Application Stability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems are inadequate in effectively handling and preventing application installation and execution errors in computer systems, particularly in enterprise networks with multiple workstations, as they fail to determine error causes and provide comprehensive error correction solutions.

Innovation Solution

A method and system utilizing an emulator, expert system, and error processor to analyze and handle errors by recreating system states, generating error handling scenarios, and storing them in an expert database for automated error processing during software application installation and execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If conventional error handling systems are used, then errors can be detected after occurrence, but error causes cannot be determined and comprehensive correction solutions cannot be provided

Engineering Contradiction:
Improveerror cause determination accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system performs preliminary error scenario generation by analyzing application code and system state before actual errors occur. Error scenarios are pre-computed and stored in a database, enabling rapid error cause determination when errors actually happen without complex real-time analysis.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

An intermediary error scenario generation system is introduced between the application and the error handling process. This intermediary analyzes application code, generates potential error scenarios, and stores them in a database, acting as a mediator that prepares error handling information in advance.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If application testing is performed on each user system, then execution errors can be detected, but it is not feasible due to the large number of diverse user systems

Engineering Contradiction:
Improveapplication execution reliabilityVSAvoidtesting efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Instead of testing on each actual user system, the system creates virtual copies of system states and configurations. Error scenarios are generated by analyzing application code against these copied system states, enabling comprehensive error detection without physically testing on every user system.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system varies system configuration parameters and execution environment parameters programmatically to generate diverse error scenarios. By changing parameters such as system state, configuration settings, and execution conditions, the system simulates testing across multiple user systems without actual physical testing.

Inventive Principle:
Principle #35Parameter changes

3Ease of repair

If system roll-back and virtualization means are used for re-installation, then installation errors can be handled, but error causes cannot be determined

Engineering Contradiction:
Improveinstallation error correctionVSAvoiderror cause information
Core Design Contradiction:
Ease of repairVSLoss of information

Solution Approach 1:

The system implements feedback by tracking and recording system states before and after installation operations. Error scenarios are generated that include information about preceding system states, providing feedback loops that preserve error cause information while enabling automated correction through system roll-back and re-installation.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8621279B1System and method for generating emulation-based scenarios for Error Handling
Publication Date: 2013.12.31 AO KASPERSKY LAB
  • US8621279B1 patent drawing
  • US8621279B1 patent drawing
  • US8621279B1 patent drawing

AI summary

A system for processing of errors, including an emulator configured for replicating a state of a computer system so as to trigger an application execution error, and obtaining a cause of the error; an expert system configured for generating a scenario for processing of the error based on the cause; and updating a database that contains an identifier of the error, the cause, the state of the computer and the scenario, including updating an error tree that maintains cumulative information about the errors; and an error processor configured for identifying an occurrence of the error, loading the scenario from the database, and running the scenario.