Telemetry Notification Device for Controller Failure Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing telemetry information notification systems face challenges in efficiently managing telemetry data with a small number of resources, leading to potential data loss and wasteful resource allocation when a controller failure occurs, as they either overload other controllers or experience time lags in generating new controllers or enhancing performance.
Innovation Solution
A telemetry information notification device with a detection unit to identify controller failures, an identification unit to determine telemetry requirements, and a determination unit to decide on alternative notification methods, such as frequency and destination, based on these requirements, allowing for efficient data handling with minimal resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all telemetry information is relayed to another controller when a failure occurs, then telemetry information can be acquired without loss, but the processing load of other controllers increases and resources are wasted
Solution Approach 1:
The patent applies local quality by differentiating the handling of telemetry information based on its importance level. Critical telemetry information is immediately relayed to alternative controllers to ensure reliability, while non-critical information is temporarily stored and processed later. This selective approach ensures that only necessary resources are consumed for each type of data, optimizing the balance between reliability and resource usage.
Solution Approach 2:
The system dynamically adjusts the notification destination and timing of telemetry information based on real-time conditions. When a controller failure is detected, the system dynamically redirects critical telemetry notifications to alternative controllers while delaying non-critical ones. This dynamic adaptation allows the system to maintain reliability for essential data while conserving processing resources during failure scenarios.
2Reliability
If a new controller is generated or performance is enhanced when a failure occurs, then telemetry information can be acquired, but time lags occur during the generation or enhancement process
Solution Approach 1:
The patent implements preliminary action by pre-configuring alternative controllers and establishing notification destination information before failures occur. The system maintains a list of potential alternative controllers and their capabilities in advance. When a failure is detected, the system can immediately redirect telemetry notifications to pre-identified alternative controllers without requiring time-consuming generation or configuration processes, thus eliminating time lags while ensuring reliability.
3Reliability
If other controllers handle increased processing load during failure relief, then telemetry information can be acquired, but processing impossibility increases and data loss may occur
Solution Approach 1:
The patent applies local quality by classifying telemetry information into different importance levels and applying different handling strategies to each class. Critical telemetry information requiring immediate processing is selectively relayed to alternative controllers, while non-critical information is temporarily stored and processed when resources are available. This differentiated approach ensures that alternative controllers are not overwhelmed by all telemetry data, maintaining their processing capacity while still ensuring reliable acquisition of essential information.
Solution Approach 2:
The system implements periodic action by temporarily storing non-critical telemetry information and processing it at intervals when controller resources are available. Instead of immediately forwarding all telemetry data to alternative controllers during failures, the system batches and periodically processes less urgent data, allowing alternative controllers to maintain their processing capacity for critical information while still eventually handling comprehensive telemetry data.
Data Source
AI summary
A node (100) includes a detection unit (122), an identification unit (123), and a determination unit (124). A detection unit (122) detects occurrence of a failure in a controller to which telemetry information in a slice is notified. An identification unit (123) identifies telemetry requirements of the slice when the detection unit (122) detects occurrence of the failure. A determination unit (124) determines whether to notify an alternative controller of the telemetry information in the slice in accordance with the telemetry requirements identified by the identification unit (123).