Event Indication Filtering via Top-Level Class Hierarchy

Solution Overview

Problem

In data processing systems, the excessive generation and delivery of event indications can lead to 'indication storms,' overwhelming network resources and causing unacceptably high usage levels, especially when many lifecycle or state change events occur simultaneously.

Innovation Solution

Implementing a method that detects object behavior changes in an information model and sends indications of interest only when they correspond to a specified top-level indication class in the indication class hierarchy, reducing the number of indications sent and preventing indication storms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all object behavior changes are monitored and indications are sent for every event, then complete event coverage is achieved, but network resources become overwhelmed and system performance degrades

Engineering Contradiction:

Improveevent detection completenessVSAvoidsystem performance

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The indication class hierarchy is segmented into top-level classes and subordinate classes. The patent filters indications by evaluating whether they belong to specified top-level indication classes, thereby segmenting the indication flow to prevent storms while maintaining coverage of critical events.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Instead of filtering out all indications except critical ones (excessive filtering), the patent applies partial filtering by sending indications only when they correspond to specified top-level classes. This partial action approach maintains sufficient event coverage while preventing network saturation.

Inventive Principle:

Principle #16Partial or excessive action

2Loss of information

If indications are sent for every object behavior change, then all events are communicated to listeners, but the number of indications becomes excessive and causes indication storms

Engineering Contradiction:

Improveevent information completenessVSAvoidnumber of indications

Core Design Contradiction:

Loss of informationVSQuantity of substance

Solution Approach 1:

The indication class hierarchy is segmented into top-level classes and subordinate classes. The patent filters indications by evaluating whether they belong to specified top-level indication classes, thereby segmenting the indication flow to prevent storms while maintaining coverage of critical events.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent extracts only the necessary indications by checking if an indication's class corresponds to a specified top-level indication class. This extraction process removes excessive indications from the system while retaining those that are truly needed, preventing indication storms.

Inventive Principle:

Principle #2Taking out (Extraction)

3Productivity

If a hierarchical filtering approach is implemented to reduce indication volume, then indication storms are prevented, but some event information may be filtered out

Engineering Contradiction:

Improvenetwork resource efficiencyVSAvoidevent information loss

Core Design Contradiction:

ProductivityVSLoss of information

Solution Approach 1:

Instead of filtering out all indications except critical ones (excessive filtering), the patent applies partial filtering by sending indications only when they correspond to specified top-level classes. This partial action approach maintains sufficient event coverage while preventing network saturation.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The patent implements a feedback mechanism where the filter evaluates each indication against the indication class hierarchy and only blocks indications that do not correspond to specified top-level classes. This feedback loop ensures that critical events are not lost while excessive indications are filtered out.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS8493211B2Providing event indications to prevent indication storms in an event model

Publication Date: 2013.07.23 LENOVO GLOBAL TECHNOLOGIES SWITZERLAND INTERNATIONAL GMBH

AI summary

A method, apparatus, and computer program product for providing event indications in an event model in a manner so that indication storms resulting from excessive indication generation and delivery is prevented. An object behavior change in an information model corresponds to an event. An indication of interest is sent to a listener process when the detected object behavior change corresponds to a specified top level indication class in an indication class hierarchy.