Event-Based Coordination Middleware for Runtime Process Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing process modeling technologies face challenges in dynamically adapting and personalizing composite software applications at runtime, limiting their flexibility and ability to respond to changing user needs or contexts without requiring significant modifications to the underlying process model.

Innovation Solution

An event-based coordination system that translates process models into event-based applications, allowing for runtime adaptation by modifying the composition of event-based applications and using an object-oriented coordination middleware to manage tasks and events, enabling personalized and context-aware behavior without altering the original process model.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If process models are used to coordinate composite applications, then the process execution can be controlled and managed, but the system lacks flexibility for dynamic adaptation and personalization at runtime

Engineering Contradiction:
Improvedynamic adaptation and personalizationVSAvoidprocess model modification complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the process model into two independent layers: the process model layer (defining tasks and control flow) and the event-based application layer (providing runtime adaptability). This segmentation allows modifications to the event-based layer without affecting the original process model, enabling dynamic adaptation while maintaining model integrity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An event-based execution environment acts as an intermediary between the process model and the composite applications. It translates process model tasks into event-based applications and enables runtime modifications through event subscriptions and publications, bridging the gap between rigid process models and flexible runtime adaptations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the process model is modified to add new features or personalize behavior, then the system becomes more adaptable, but the original process model integrity is compromised and redeployment is required

Engineering Contradiction:
Improveruntime adaptation capabilityVSAvoidprocess model integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system extracts the adaptability functionality from the process model itself and places it in the event-based execution environment. Runtime modifications are performed on event-based applications rather than the process model, taking out the variability aspect and leaving the process model intact and reliable.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The process model is preliminarily transformed into event-based applications during deployment, preparing the system for runtime adaptations. This preliminary transformation enables subsequent modifications without affecting the original process model, as the event-based layer is pre-configured to accept runtime changes.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If event-based applications are used to enable runtime modifications, then the system flexibility is improved, but the coordination complexity between multiple applications increases

Engineering Contradiction:
Improveruntime modification flexibilityVSAvoidapplication coordination complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The event-based execution environment provides universal coordination mechanisms that work across all event-based applications. Standard event subscriptions, publications, and translations provide multi-functional coordination capabilities, reducing the need for application-specific coordination logic and simplifying the overall system complexity.

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

Data Source

PatentEP1760588B1Event-based coordination of process-oriented composite applications
Publication Date: 2009.04.08 SAP SE
  • EP1760588B1 patent drawingFigure 1
  • EP1760588B1 patent drawingFigure 2
  • EP1760588B1 patent drawingFigure 3

AI summary

A process model (104) specified using, for example, UML activity diagrams can be translated into an event-based model that can be executed on top of a coordination middleware (116). For example, a process model (104) may be encoded as a collection of coordinating objects (126, 128) that interact with each other through a coordination middleware including a shared memory space (124). This approach is suitable for undertaking post-deployment adaptation of process-oriented composite applications. In particular, new control dependencies can be encoded by dropping new (or enabling existing) coordinating objects (126, 128) into the space and/or disabling existing ones.