Hierarchical Event Component Wrappers for Reusable Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing event processing technologies face limitations in reusability, resource management, and performance due to the inability to reuse event components across different execution types and complex events, leading to increased costs and reduced efficiency in processing large quantities of data in real-time.
Innovation Solution
An event processing method and system that utilizes a hierarchical structure by componentizing event components, allowing for their reuse through event component wrappers and input/output value mapping, enabling efficient event processing by defining events with a tree structure and reusing event processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If event components are instantiated separately for each execution type, then event processing flexibility is maintained, but system resource cost increases and reusability is lost
Solution Approach 1:
The patent implements universality by creating a single event component instance that can serve multiple execution types through the execution type attribute. The event component is designed to be reused across different execution types (e.g., simple events, collection events, reference events) without requiring separate instantiations, thereby reducing system resource cost while maintaining processing flexibility.
Solution Approach 2:
The patent applies dynamics by making the execution type attribute changeable and configurable. The event component can dynamically adapt its behavior based on the execution type specified, allowing the same component to function differently for various event types without structural modification, thus achieving both flexibility and resource efficiency.
2Productivity
If multiple processor queues are used for event processing, then processing capacity is increased, but minimum response time increases and resource management becomes complex
Solution Approach 1:
The patent merges the event processing functionality into a single processor that handles multiple execution types through the event component's execution type attribute. This eliminates the need for multiple separate processor queues, thereby reducing the minimum response time and simplifying resource management while maintaining adequate processing capacity through the unified processor's ability to handle diverse event types.
Solution Approach 2:
The unified processor is designed with universality to handle multiple execution types (simple, collection, reference, connection, standby events) through the configurable execution type attribute of the event component. This multi-functional design allows a single processor to achieve the processing capacity of multiple specialized processors while avoiding the time loss and management complexity associated with multiple queues.
3Device complexity
If rule operation definition is limited to once per event, then event processing simplicity is maintained, but additive event processing and rule determinations cannot be performed
Solution Approach 1:
The patent applies dynamics by making the rule operation definition changeable and configurable multiple times. The event component allows dynamic addition of rule operations through the execution type attribute and associated configuration mechanisms, enabling additive event processing and multiple rule determinations while maintaining a relatively simple base structure that can be extended as needed.
Data Source
AI summary
Provided is a method for event processing and a system for using the same. The system for event processing in a computer may include an interface to detect an input associated with an event, an event definition engine which defines the event using a plurality of event components and a corresponding event component wrapper wrapping each of the plurality of event components, an event processing engine which processes the event, and an event action module to generate an output based on the event. The event definition engine may determine a hierarchical relationship between the plurality of event components and assigns the hierarchical relationship in the corresponding event component wrapper. Moreover, the event processing engine may execute each of the event components according to the hierarchical relationship assigned in the event component wrapper.