Message Input Output Device Reducing Overload via Merging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In monitoring systems, frequent alternation of failure and recovery messages from monitored devices within a short time period leads to message overload, making it difficult for monitoring personnel to notice critical messages and increasing database storage and deletion processing loads, while existing methods fail to notify the final state effectively.
Innovation Solution
A message input/output device and method that receive and output messages only when a related message is not received within a predetermined time frame, ensuring that the final state of messages is conveyed while reducing overall message output.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If all received messages are output immediately, then message output completeness is improved, but message output volume increases and visibility of critical messages deteriorates
Solution Approach 1:
The patent merges multiple related messages (failure messages and recovery messages) into a single output message. When a failure message and its corresponding recovery message are both received, they are combined and only one notification is output, reducing message volume while preserving complete information about the failure-recovery cycle.
Solution Approach 2:
The patent performs preliminary judgment about message relatedness before output. By determining in advance whether a received message is related to a previously received message (using message IDs and type comparison), the system can proactively suppress redundant outputs, improving visibility without losing information.
2Loss of information
If all received messages are stored in database, then message history completeness is improved, but database storage volume and deletion processing load increase
Solution Approach 1:
The patent merges related messages before database storage. When a failure message and recovery message are identified as related, only one record (representing the combined information) is stored in the database, reducing storage volume and subsequent deletion processing load while maintaining complete historical information.
Solution Approach 2:
The patent extracts only the essential information from related message pairs for database storage. By storing a single representative record that captures the complete failure-recovery cycle information, the system removes redundant data while preserving historical completeness.
3Productivity
If related messages are suppressed within predetermined time, then message output volume is reduced, but final state notification capability deteriorates
Solution Approach 1:
The patent performs preliminary classification of messages as related or unrelated based on message IDs and types before suppression. This preliminary action ensures that only truly related messages (failure-recovery pairs) are suppressed, while unrelated messages are output normally, maintaining reliable final state notification.
Solution Approach 2:
The patent uses message ID comparison as a feedback mechanism to determine message relatedness. By checking whether a received message's ID matches a previously stored message ID and comparing message types, the system provides accurate feedback on whether suppression should occur, ensuring reliable final state notification.
Data Source
AI summary
In order to enable to output a final state of a message while reducing output of a message, a message input/output method includes: receiving a reception message; and outputting, when a reception time of the reception message falls within a first predetermined time from reception of a related message related to the reception message, the reception message when a next of the related message is not received within a second predetermined time exceeding the first predetermined time from the reception time.


