17959497. DATA STORAGE DEVICE WITH FLOW TRACKING ABILITY simplified abstract (Western Digital Technologies, Inc.)

From WikiPatents
Jump to navigation Jump to search

DATA STORAGE DEVICE WITH FLOW TRACKING ABILITY

Organization Name

Western Digital Technologies, Inc.

Inventor(s)

Refael Ben-rubi of Rosh Haayin (IL)

DATA STORAGE DEVICE WITH FLOW TRACKING ABILITY - A simplified explanation of the abstract

This abstract first appeared for US patent application 17959497 titled 'DATA STORAGE DEVICE WITH FLOW TRACKING ABILITY

Simplified Explanation

The present disclosure relates to improved event filtering, debugging, and flow communication through a flow identifier. Messages or events are sent with a flow identifier to allow for easy identification when needed.

  • Flow identifier added to each message/event
  • At least two bits added to each message
  • First message sent to HW or FW module
  • Event generated at HW or FW module
  • Flow identifier added to the event
  • Events sent along with flow identifier to TBRAM
  • TBRAM sends events with flow identifier to PC

Potential Applications

The technology can be applied in various industries such as telecommunications, networking, and software development for improved event handling and debugging.

Problems Solved

1. Lack of identity in messages/events 2. Difficulty in identifying events in a flow

Benefits

1. Improved event filtering 2. Enhanced debugging capabilities 3. Efficient flow communication

Potential Commercial Applications

Enhanced event handling technology for networking equipment SEO Optimized Title: "Enhanced Event Handling Technology for Networking Equipment"

Possible Prior Art

There may be existing technologies or methods that involve event filtering and debugging in communication systems, but the specific implementation of adding a flow identifier to each message/event may be novel.

Unanswered Questions

How does the flow identifier improve event communication?

The flow identifier allows for easy identification and tracking of events within a flow, but the specific technical details of how this improves event communication could be further elaborated.

Are there any limitations to the use of flow identifiers in event handling?

While the use of flow identifiers seems beneficial, there may be potential limitations or drawbacks that need to be considered, such as scalability issues or added complexity in implementation.


Original Abstract Submitted

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.