Context-Based Event Handling with Priority and Interrupt Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing interactions between diverse devices and systems in computer networks is complex due to varying event information formats and functionalities, requiring intelligent integration and prioritization of events for optimal resource execution.

Innovation Solution

A software-based event handling system that receives events from multiple sources, accesses context information, generates new events based on event and context data using rules, assigns priorities, and manages event execution and interrupts across target systems, utilizing a rule engine and dispatch component for efficient communication and protocol conversion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If events from diverse systems are integrated onto a common communication framework, then system functionality and information sharing are enhanced, but event management complexity increases

Engineering Contradiction:
Improvesystem functionalityVSAvoidevent management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an event handler as an intermediary component that sits between diverse event sources and target systems. The event handler receives events from multiple source systems, standardizes their formats, applies context-based rules, and dispatches them to appropriate targets. This mediator abstracts the complexity of managing diverse event formats and routing logic, allowing systems to integrate without directly managing the complexity of event format conversion and routing decisions.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The event management system is segmented into distinct functional components: event sources, event handler, context repository, rule engine, and target systems. Each component has a specific responsibility - sources generate events, the handler processes them, context provides additional information, rules determine routing and priority, and targets execute actions. This segmentation allows each component to be developed, maintained, and scaled independently, reducing overall system complexity.

Inventive Principle:
Principle #1Segmentation

2Productivity

If context information and rules are used to generate and prioritize events, then resource execution is optimized, but processing time increases

Engineering Contradiction:
Improveresource execution efficiencyVSAvoidevent processing time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-defining context information and rules before events are processed. Context data about source systems, target systems, and event types is预先 stored and organized. Rules for event generation, priority assignment, and routing are pre-configured. When events arrive, the handler can quickly match them against pre-established rules and context without performing complex real-time analysis, thus optimizing resource execution while minimizing processing time.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If multiple source systems with different event formats are integrated, then system versatility is improved, but event integration difficulty increases

Engineering Contradiction:
Improvesystem versatilityVSAvoidevent integration difficulty
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The event handler is designed as a universal component that can process events from multiple different source systems with varying formats. It implements a standardized event interface and uses context-based rules to handle different event types, sources, and formats uniformly. This multi-functional design allows the same handler to manage events from diverse systems without requiring system-specific processing logic, thereby improving versatility while reducing integration difficulty.

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

Data Source

PatentUS7865887B2Context based event handling and execution with prioritization and interrupt management
Publication Date: 2011.01.04 SAP SE
  • US7865887B2 patent drawing
  • US7865887B2 patent drawing
  • US7865887B2 patent drawing

AI summary

Embodiments of the present invention provide improved event handling between systems. In one embodiment, the present invention includes software event handling method comprising receiving a first event from a first source system in a plurality of source systems, the first event including event information, accessing context information corresponding to the first event, generating a second event based on at least a portion of the event information and context information using one or more rules, assigning a priority to the second event, and sending the second event to a first target system in a plurality of target systems.