Self-Resolving Exception Errors in Distributed Network Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies lack efficient and reliable solutions for detecting the root cause of exception errors in distributed networks, leading to time-consuming and error-prone manual inspections, and inadequate system corrections.
Innovation Solution
A system comprising a processor and memory that monitors communication data and acknowledgement messages between servers in a distributed network, using an exception monitoring module, exception listener module, and multi-layer detection module to identify the root cause of exception errors and automatically implement corrective actions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual inspection is used to detect root causes of exception errors, then operators can investigate failures, but the process is time-consuming and error-prone
Solution Approach 1:
The system enables self-service by having the distributed network automatically monitor its own communication data and acknowledgement messages to detect root causes of exception errors without requiring manual operator intervention. The exception monitoring module and multi-layer detection module autonomously analyze communication patterns to identify failures.
Solution Approach 2:
The patent replaces the mechanical manual inspection process with an automated electronic system. The processor automatically collects, analyzes, and processes communication data and acknowledgement messages to detect root causes, substituting human operators with an automated detection mechanism that operates continuously without interruption.
2Productivity
If automated monitoring is implemented to detect root causes automatically, then detection speed improves, but system complexity increases
Solution Approach 1:
The exception monitoring module serves multiple functions: it monitors communication data, tracks acknowledgement messages, detects exception errors, and identifies root causes across the distributed network. This multi-functionality consolidates what would otherwise require multiple separate systems into a single integrated module.
Solution Approach 2:
The patent introduces an intermediary layer of monitoring that sits between the servers and the detection process. The exception monitoring module acts as a mediator that collects communication data and acknowledgement messages from multiple servers, processes them through the multi-layer detection module, and identifies root causes without requiring direct complex interactions between all system components.
3Measurement precision
If comprehensive monitoring of all communication data is performed, then detection accuracy improves, but processing resources are consumed
Solution Approach 1:
The patent extracts only the essential information needed for detection from the communication data. Instead of processing every detail of all communications, the system selectively monitors and analyzes only the acknowledgement messages and communication patterns that indicate exception errors, extracting relevant data while filtering out unnecessary information to reduce processing overhead.
Solution Approach 2:
The system applies partial action by monitoring only the critical aspects of communication data related to exception errors rather than all possible communication activities. The exception monitoring module focuses on tracking acknowledgement messages and communication failures, which are the partial set of data most relevant to detecting root causes, rather than analyzing every data packet exchanged between servers.
Data Source
AI summary
A solution implementation system includes a solution registry with a corrective action for each of a plurality of predefined root causes of exception errors. The system receives communication data transmitted through a distributed network comprising a plurality of servers. An exception error is detected corresponding to a failed transmission of the communication data between communicatively coupled servers of the distributed network. A first root cause of the exception error is determined. Properties of the distributed network at the time of the detected exception error are determined. Using the solution registry, a first corrective action is determined for the first root cause that is associated with the determined properties of the distributed network at the time of the detected exception error. The first corrective action is automatically implemented to resolve the exception error.