Event Services Editor for Visualizing Complex Configurations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional event notification and management services are static and difficult for users to visualize and customize, making it challenging to model and manage complex event configurations in a user-friendly manner within software systems.

Innovation Solution

The event services editor provides a user-friendly interface for defining and customizing event services models, enabling users to connect events with actions, set conditions, and configure notifications, allowing for seamless event flows across multiple systems and applications, including third-party integrations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If conventional static event notification services are used, then system stability is maintained, but user ability to visualize and customize event configurations deteriorates

Engineering Contradiction:
Improveuser ability to visualize and customize event configurationsVSAvoidcomplexity of event configuration management
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an event configuration interface as an intermediary between users and the event notification system. This interface provides visual modeling capabilities that mediate between user requirements and system implementation, allowing users to configure complex event flows without directly managing underlying system complexity. The interface acts as a mediator that translates user-friendly visual configurations into system-executable event subscription and publication logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces traditional mechanical configuration approaches (manual coding, configuration files, direct system manipulation) with a visual modeling system. Users interact with event configurations through graphical interfaces where they can drag, drop, and connect event sources, subscriptions, and actions visually, rather than manually configuring system parameters or writing code. This substitution of mechanical configuration with visual modeling resolves the contradiction by improving ease of operation while managing complexity through abstraction.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Adaptability or versatility

If complex event configurations are implemented, then event management capability is improved, but ease of visualization and understanding deteriorates

Engineering Contradiction:
Improveevent management capabilityVSAvoiddifficulty of visualizing end-to-end events
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent segments complex event configurations into manageable visual components including event sources, subscriptions, filters, and actions. Each component can be independently configured and visualized, then assembled into complete event flows. This segmentation allows users to understand and manage complex event management capabilities by breaking them down into discrete, visualizable units rather than presenting monolithic complex configurations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a visual dimension to event configuration management by providing graphical representations of event flows, subscriptions, and actions. Instead of managing complex configurations through text-based or abstract interfaces, users can visualize event architectures in spatial and relational dimensions through diagrams, flow charts, and graphical editors. This dimensional transformation makes complex event management capabilities detectable and measurable through visual inspection.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Ease of operation

If user-friendly interface is provided for event modeling, then ease of operation is improved, but system complexity increases

Engineering Contradiction:
Improveuser-friendliness of event configurationVSAvoidcomplexity of event services framework
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent uses template-based configuration where common event patterns and workflows are pre-defined as reusable templates. Users can copy and instantiate these templates rather than building event configurations from scratch, significantly improving ease of operation. The templates encapsulate complex system logic, allowing users to benefit from sophisticated event management capabilities without directly engaging with the underlying system complexity. This copying approach provides user-friendly access while managing complexity through pre-packaged solutions.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent implements a universal event configuration interface that handles multiple event types, sources, and actions through a single unified system. Rather than providing separate configuration mechanisms for different event scenarios, the interface provides universal modeling capabilities that work across diverse event management needs. This universality improves ease of operation by providing consistent interaction patterns while managing system complexity through a single integrated framework rather than multiple specialized systems.

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

Data Source

PatentUS10338796B2Event services modeling framework for computer systems
Publication Date: 2019.07.02 SAP SE
  • US10338796B2 patent drawing
  • US10338796B2 patent drawing
  • US10338796B2 patent drawing

AI summary

Embodiments include an event services modeling framework. The event services modeling framework includes an event services modeling editor that provides a user interface and mechanism for users to model and customize event flow configurations within a system and/or network. The user interface can be used to connect events with actions that will take place in response to the events. The system components and/or modules that need to receive the information from the events can then react and respond appropriately. Users can modify event configurations based on their own particular needs. the event services editor can be used for generating one or more event services models. The event services models may include events, conditions (rules) for processing the events, activities to be perform during event processing, subscriber modules defined for performing the activities during event processing, and a specified time for processing the events in each modeled event flow.