Flow Identifier Mechanism for Event Filtering in Data Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems face challenges in efficiently filtering and communicating events across multiple modules, leading to event loss due to the lack of a unique identifier, resulting in inefficient debugging and increased event logging complexity.
Innovation Solution
The introduction of a flow identifier, consisting of at least two bits added to each message, allows for identification and filtering of specific events, enabling efficient communication and debugging by associating events with specific flows, reducing the need to read entire logs and minimizing event loss.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If events are logged from multiple parallel modules without flow identifiers, then comprehensive event collection is achieved, but event identification and filtering become difficult leading to increased complexity and potential event loss
Solution Approach 1:
The patent segments the event logging system by introducing flow identifiers that divide events into distinct flow groups. Each module's events are tagged with flow identifiers, allowing the system to segment and filter specific event streams from the overall event log, making identification and analysis more reliable without increasing overall system complexity.
Solution Approach 2:
The flow identifier acts as an intermediary element between multiple parallel modules and the event logging system. This intermediary tag allows events from different modules to be distinguished and filtered efficiently, reducing the complexity of event management while maintaining comprehensive collection capabilities.
2Productivity
If the serial channel capacity is limited, then system resource constraints are managed, but event loss increases due to inability to handle all generated events
Solution Approach 1:
The patent extracts only the necessary events from the complete event stream by using flow identifiers for filtering. Instead of attempting to transmit all events through the limited serial channel, the system can extract and prioritize specific flow events, reducing event loss while managing serial channel capacity constraints effectively.
Solution Approach 2:
The system implements partial action by selectively logging and transmitting only relevant events based on flow identifiers rather than attempting to process all events. This approach accepts that not all events will be logged but ensures that critical events from specific flows are captured, minimizing information loss within channel capacity limits.
3Measurement precision
If debugging requires reading entire event logs, then complete event data is available, but debugging time and parsing overhead increase significantly
Solution Approach 1:
The patent applies preliminary action by pre-tagging events with flow identifiers during event generation. This preliminary classification allows debugging processes to directly filter and access relevant events without scanning entire logs, maintaining debugging accuracy while dramatically reducing the time and parsing overhead required to locate specific events.
4Ease of operation
If flow identifiers are added to each message, then event filtering capability is improved, but message size and processing overhead increase
Solution Approach 1:
The flow identifier is implemented as a localized field within the message structure rather than a complete restructuring of communication protocols. This local quality approach adds filtering capability to individual messages without significantly increasing overall message size or processing complexity, enabling efficient event filtering while maintaining message structure simplicity.
Data Source
AI summary
The present disclosure generally relates to improved event filtering, debugging, and flow communication through a flow identifier. Rather than sending messages or events with no identity or with local identity (that is identity that has meaning only to a few modules, and not to all the modules), this disclosure suggests adding a flow identifier to each message or event. The flow identifier is at least two bits added to each message to be later identified when needed. A first message is sent to a HW or FW module. At either the HW or FW module an event will be generated. When the event is generated the flow identifier will be added to the event. The HW or FW module will then send the generated events along with the flow identifier to the TBRAM. Once received, the TBRAM will send the events along with the flow identifier to a PC.