Event Action Management Mechanism Consolidating Redundant Operations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional event handling systems become unresponsive when overwhelmed by a high rate of incoming events, leading to delayed or missed actions, and inefficiently use CPU resources due to redundant actions and lack of prioritization.

Innovation Solution

An event management mechanism that consolidates redundant actions, prioritizes actions based on urgency, and optimally selects actions for execution by examining event and action information, using a system comprising an event receiver, handler, tracker, and executor to manage events and actions efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system processes all incoming events immediately, then the system remains responsive to events, but CPU resources are wasted on redundant actions and the system becomes overwhelmed under high event rates

Engineering Contradiction:
Improvesystem responsivenessVSAvoidCPU resource usage
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies preliminary action by pre-processing incoming events to identify and consolidate redundant actions before execution. The event management mechanism examines incoming events, determines associated actions, and consolidates redundant actions with other pending actions for the same resource, thereby reducing CPU waste while maintaining responsiveness.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the parameter of action execution by introducing a consolidation step that modifies how actions are processed. Instead of executing each action immediately upon event receipt, the system consolidates redundant actions and prioritizes them, changing the execution parameters to optimize resource usage while maintaining system responsiveness.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If the system executes actions in the order events arrive, then event processing is simple, but urgent actions may be delayed by non-urgent actions

Engineering Contradiction:
Improveevent processing simplicityVSAvoidaction execution delay
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent applies preliminary action by assigning priority levels to actions before execution. The event management mechanism determines the urgency of each action in advance and uses this information to prioritize the action queue, ensuring that urgent actions are executed before non-urgent actions without complicating the overall processing flow.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces dynamics by making the action execution order adaptive rather than static. The system dynamically prioritizes actions based on their urgency and the current system state, allowing the processing order to change in response to varying conditions while maintaining a relatively simple processing mechanism.

Inventive Principle:
Principle #15Dynamics

3Use of energy by moving object

If the system consolidates redundant actions, then CPU resource usage is reduced, but the system complexity increases

Engineering Contradiction:
ImproveCPU resource usageVSAvoidevent management mechanism complexity
Core Design Contradiction:
Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The patent applies universality by designing the event management mechanism to perform multiple functions within a single component. The mechanism not only consolidates redundant actions but also prioritizes actions, manages action queues, and coordinates execution, thereby reducing overall system complexity despite the added consolidation functionality.

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

Solution Approach 2:

The patent introduces an intermediary component (the event management mechanism) that mediates between event reception and action execution. This intermediary handles the complexity of consolidation and prioritization internally, presenting a simplified interface to the rest of the system and isolating the complexity to a single manageable component.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If the system processes high rates of incoming events, then event handling capacity is maximized, but actions become delayed or missed

Engineering Contradiction:
Improveevent handling capacityVSAvoidaction completion rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by pre-consolidating redundant actions before execution. The event management mechanism examines incoming events, determines associated actions, and consolidates redundant actions with other pending actions for the same resource, thereby reducing the total number of actions that need to be executed and improving both event handling capacity and action completion rate.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the parameter of action processing by introducing consolidation and prioritization. This transforms the system from processing individual actions to processing consolidated action groups, changing the processing parameters to handle high event rates while ensuring critical actions are completed.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10970143B1Event action management mechanism
Publication Date: 2021.04.06 HEWLETT PACKARD ENTERPRISE DEV LP
  • US10970143B1 patent drawing
  • US10970143B1 patent drawing
  • US10970143B1 patent drawing

AI summary

A system to facilitate event management is described. The system includes a processor and a machine readable medium storing instructions that, when executed, cause the processor to select a first event including first action information indicating a first action to be performed on a first of a plurality of resources, examine the first action information to determine whether the first action matches stored pending action information associated with one or more actions to be performed on the first resource and merge the first action information with the pending action information upon a determination that the first action matches pending action information.