Application Recovery via Network Analysis of Operational Requests
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Client devices face challenges in detecting and correcting abnormal software packages that cause malfunctioning applications, leading to sub-optimal or failed execution of operational functions, especially when multiple devices with different software versions execute the same application.
Innovation Solution
A method and system that utilize a recovery software package to communicate with a network system to determine abnormal operational requests, identify failing functions, and apply recovery instructions to modify or replace malfunctioning software packages, thereby restoring normal application functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If automatic detection and correction systems are implemented, then application functionality recovery is improved, but device complexity increases
Solution Approach 1:
The patent introduces a network entity as an intermediary that performs the complex analysis and diagnosis functions. The client device sends operational request data to the network entity, which then analyzes the data, identifies abnormal software packages, and provides remediation instructions. This intermediary approach transfers the complexity from the client device to the network entity, maintaining client device simplicity while enabling sophisticated automatic detection and correction capabilities.
Solution Approach 2:
The system enables self-service through automated diagnosis and remediation. The client device automatically collects operational request data, sends it to the network entity for analysis, and applies remediation instructions without requiring user intervention. The network entity automatically identifies failing functions and generates correction measures, allowing the system to self-diagnose and self-repair application functionality issues.
2Measurement precision
If detailed analysis of operational requests is performed, then detection precision is improved, but processing time increases
Solution Approach 1:
The system performs preliminary action by collecting and storing operational request data before analysis is needed. Client devices continuously monitor and log operational requests, maintaining a historical record of normal and abnormal operations. When a malfunction is detected, the pre-collected data is immediately available for rapid analysis by the network entity, eliminating the need for real-time data gathering during the diagnostic process.
Solution Approach 2:
The network entity performs partial analysis by focusing on specific aspects of operational requests that are most indicative of software package abnormalities. Rather than analyzing every single operational request in detail, the system identifies key patterns and anomalies in the data that sufficiently indicate malfunction, achieving effective detection with reduced processing requirements.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An application recovery system is configured to recover an application executing on a client device by determining that an application is operating abnormally and providing recovery instructions to the application. The application executing on a client device includes a main portion of the application and a recovery portion of the application. The recovery portion of the application sends requests for recovery instructions to a network system. The network system receives the recovery requests and analyzes operational requests generated by the main portion of the application to identify failing functions and their associated software packages. The recovery instructions are determined based on the identified failing functions and their associated software packages and sent to the client device. The client device applies the recovery instructions to modify the application such that the application recovers normal operation.