System and method for detection of, prevention of, and recovery from software execution failure
US-2021365321-A1 · Nov 25, 2021 · US
US12430191B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12430191-B2 |
| Application number | US-202418416499-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 18, 2024 |
| Priority date | Apr 27, 2018 |
| Publication date | Sep 30, 2025 |
| Grant date | Sep 30, 2025 |
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.
Systems and methods are disclosed herein for monitoring, detecting, and mitigating hardware and software failures. An error detection module monitors the execution of software processes and detects failures of the monitored processes. The error detection module may monitor reboot events and correlate reboot events with failures of the monitored software processes. If a monitored process fails, the error detection module may log the failure and its cause. If the same process has failed numerous times, causing the user device to experience a reboot loop, remedial action may be taken based on the cause of the failure.
Opening claim text (preview).
What is claimed is: 1. A method for handling software execution failures on a user device, the method comprising: monitoring execution of a plurality of software processes on the user device; detecting on the user device a first failure at a first step of a first software process and a second failure at a second step of a second software process; in response to determining that a number of failures on the user device exceeds a low failure threshold, preventing normal execution of the plurality of software processes; and beginning the first software process at a step after the first step. 2. A method as in claim 1 wherein the second failure prevents the execution of a software process subsequent the first software process. 3. A method as in claim 2 wherein the executing the first software process at a step after the first step allows the software process subsequent the first software process to execute successfully. 4. A method as in claim 1 , wherein the first step occurs before the second step. 5. A method as in claim 1 , wherein the first step occurs concurrently with the second step. 6. A method as in claim 1 wherein the first step and the second step are part of the same function. 7. A method as in claim 1 wherein the first software process and the second software process are the same function. 8. A method as in claim 1 further comprising based on a result of the execution of the first software process at a step after the first step, determining a remedial action. 9. A method as in claim 1 further comprising determining that the number of failures exceeds both the low failure threshold and a high failure threshold and in response transmitting to a server a request for assistance. 10. A method as in claim 1 wherein the software process is a virtual process encompassing a plurality of software processes. 11. A system for handling software execution failures on a user device, the system comprising: control circuitry configured to: monitor execution of a plurality of software processes on the user device; detect on the user device a first failure at a first step of the first process and a second failure at a second step of a second software process; in response to determining that a number of failures on the user device exceeds a low failure threshold, prevent normal execution of the plurality of software processes; and begin the first software process at a step after the first step. 12. A system as in claim 11 wherein the second failure prevents the execution of a software process subsequent the first software process. 13. A system as in claim 12 wherein the executing the first software process at a step after the first step allows the software process subsequent the first software process to execute successfully. 14. A system as in claim 11 , wherein the first step occurs before the second step. 15. A system as in claim 11 , wherein the first step occurs concurrently with the second step. 16. A system as in claim 11 wherein the first step and the second step are part of the same function. 17. A system as in claim 11 wherein the first software process and the second software process are the same function. 18. A system as in claim 11 the control circuitry further configured to, based on a result of the execution of the first software process at a step after the first step, determine a remedial action. 19. A system as in claim 11 the control circuitry further configured to determine that the number of failures exceeds both the low failure threshold and a high failure threshold and in response transmit to a server a request for assistance. 20. A system as in claim 11 wherein the software process is a virtual process encompassing a plurality of software processes.
the processing taking place on a specific hardware platform or in a specific software environment · CPC title
Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36) · CPC title
where the computing system component is a software system · CPC title
Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40) · CPC title
using diagnostics (G06F11/0703 takes precedence) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.