Event Notification Context Aggregation for Handling Bottlenecks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional event management techniques in computer systems require event handling components to retrieve additional context information from multiple sources, leading to inefficiencies and delays in event handling, as each component may need to duplicate information retrieval efforts and handle events sequentially, causing bottlenecks.

Innovation Solution

An event generation component provides context information along with event notifications, allowing event handling components to apply business process rules without additional information retrieval, and enables administrators to configure the order of event handling and organize components into logical pools for improved efficiency and fault tolerance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If event handling components retrieve additional context information from multiple sources, then the components can make informed decisions about event handling, but the time required to handle events increases and system efficiency decreases

Engineering Contradiction:
Improvedecision accuracyVSAvoidevent handling time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The event generating component performs preliminary actions by collecting and assembling all necessary context information from multiple sources before generating the event notification. This includes retrieving user identity, operation details, and other contextual data in advance, so that the event notification contains complete information for immediate decision-making by event handling components, eliminating the need for them to perform additional information retrieval.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges multiple information retrieval operations into a single event notification transmission. The event generating component consolidates event details and all relevant context information into one comprehensive notification that is sent to event handling components in a single communication, rather than requiring separate retrieval operations from multiple sources.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If multiple event handling components process events sequentially, then each component can apply its business process rules thoroughly, but the overall event handling throughput decreases

Engineering Contradiction:
Improverule application accuracyVSAvoidevent handling throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements dynamic event handling where the processing mode (sequential or parallel) adapts based on the specific event type and the capabilities of the event handling components. The system can dynamically switch between sequential processing for complex events requiring thorough analysis and parallel processing for simpler events that can be handled independently, optimizing both accuracy and throughput for different scenarios.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent segments the event handling process into independent processing stages that can be executed in parallel. Different event handling components can process different aspects of the same event simultaneously, with each component focusing on its specific business process rules, and then combining their results to form the final event handling decision.

Inventive Principle:
Principle #1Segmentation

3Loss of information

If event handling components retrieve context information from multiple sources, then complete information is available for decision-making, but the complexity of information retrieval and management increases

Engineering Contradiction:
Improvecontext information completenessVSAvoidinformation retrieval complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The event generating component is designed as a universal information gathering entity that can retrieve and assemble all types of context information from multiple sources using a standardized process. This multi-functional component handles diverse information retrieval tasks (user identity, operation details, contextual data) through a unified mechanism, reducing the overall system complexity despite the variety of information sources.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Reliability

If each event handling component independently retrieves context information, then each component has access to necessary data, but duplicate information retrieval efforts waste system resources

Engineering Contradiction:
Improveinformation availabilityVSAvoidsystem resource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The event generating component performs self-service by proactively collecting and assembling all necessary context information from multiple sources before generating the event notification. This eliminates the need for event handling components to independently retrieve the same information, as the event notification already contains all required contextual data, thereby avoiding duplicate retrieval efforts and reducing system resource consumption.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8239880B1Orchestrating flow of event information to several event handling components
Publication Date: 2012.08.07 EMC IP HLDG CO LLC
  • US8239880B1 patent drawing
  • US8239880B1 patent drawing
  • US8239880B1 patent drawing

AI summary

Event management techniques for use in a computer system comprising an event generating component generating at least one event and a plurality of event handling components applying one or more business process rules in response to the event. In one embodiment of the invention, an event generation component provides to an event handling component a notification of an event and context information about the event, in the same communication. The context information may provide all the information necessary for the event handling component to apply one or more business policy rules to determine how to handle the event. In some implementations having multiple event handling components of different types, the event generating component may be configured to provide notification of events to the event handling components in a specified order. In some implementations, multiple event handling components may be joined in a logical pool, sharing responsibility for handling events.