Resource Event Mapping Logic for Asynchronous Rule Correlation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Computer systems face challenges in managing asynchronous data pushes, where resources send event data to a central manager without specifying the appropriate rule for processing, leading to inefficiencies in rule application.
Innovation Solution
Implementing a Resource:Event Mapping Logic (REML) that defines event types, correlates asynchronous data with relevant rules, and applies the appropriate rules to the data, enabling efficient processing and filtering of resource-based events in a rule system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If resources send asynchronous event data to a central manager without specifying the appropriate rule, then the system can handle diverse events flexibly, but the rule system cannot determine which rule to apply efficiently
Solution Approach 1:
The patent applies preliminary action by pre-defining event types with their associated properties and creating a mapping between event types and rules before asynchronous data arrives. The central manager maintains a repository of event type definitions and uses these pre-established definitions to quickly match incoming asynchronous data with appropriate rules, eliminating the need to search for matching rules in real-time.
Solution Approach 2:
The patent introduces an intermediary layer (event type definition and mapping mechanism) between the asynchronous data and the rule application process. This intermediary translates raw asynchronous event data into structured event type identifiers that can be efficiently matched with predefined rules, serving as a mediator that bridges the gap between diverse event sources and the rule engine.
2Reliability
If the rule system queries resources for data to process rules, then it can obtain necessary input parameters, but it increases system complexity and communication overhead
Solution Approach 1:
The patent applies preliminary action by having resources pre-structure their asynchronous event data according to predefined event type schemas before sending data to the central manager. The event type definitions specify which properties are required, so resources can prepare complete data packets in advance, eliminating the need for subsequent queries to retrieve missing information.
Solution Approach 2:
The patent enables self-service by having resources automatically structure and send complete event data according to predefined event type definitions without requiring the rule system to query them. The resources themselves are responsible for ensuring their event data includes all necessary properties as defined by the event type schema, reducing communication overhead.
3Productivity
If the system defines event types according to resource properties and creates resource definitions, then it can efficiently correlate asynchronous data with rules, but it increases initial setup complexity
Solution Approach 1:
The patent applies universality by creating a standardized event type definition framework that can be reused across multiple resources and event types. Instead of creating custom mappings for each resource-event combination, the system defines universal event type templates with common properties that can be instantiated for different resources, reducing overall configuration complexity while maintaining efficient correlation.
Data Source
AI summary
A computer-implementable method, system and computer media for typing a resource-based event in a rule system. In one embodiment, the computer-implementable method includes the steps of: defining an event type according to a resource property that is associated with the event type; creating a resource definition that describes which one or more event type can occur in a resource; storing the resource definition in the rule system; receiving asynchronous data from a particular resource in the data processing system; correlating the asynchronous data with a particular rule that is associated with a resource definition for the particular resource; and applying the particular rule to the asynchronous data.