Dynamic Event Subscription for Enterprise Data Objects

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing enterprise business applications face inefficiencies in defining characteristics and events of business objects at design time, limiting flexibility and practicality in managing changes and associations between business entities.

Innovation Solution

A computer-implemented information system that allows for the definition of customized data object events post-design time, enabling the association of subscriber and publisher objects, and using a messaging manager to manage event subscriptions and notifications, including a message broker and event controller for efficient communication and reference counting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If business object characteristics and events are defined at design time, then system structure is stable and manageable, but flexibility and adaptability to changing business requirements deteriorate

Engineering Contradiction:

Improveflexibility in managing business object eventsVSAvoidsystem complexity for managing post-design changes

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic event subscription mechanisms that allow subscriber objects to be added, removed, or modified at runtime without requiring system redesign. The event subscription system maintains dynamic registries of publisher-subscriber relationships, enabling the system to adapt to changing business requirements while maintaining structured event notification pathways.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system segments business objects into publisher objects and subscriber objects with distinct roles and responsibilities. Publisher objects generate events based on their state changes, while subscriber objects independently subscribe to specific events of interest. This segmentation allows flexible configuration of event relationships without affecting the entire system structure.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If customized data object events are associated post-design time, then system flexibility improves, but system complexity and management overhead increase

Engineering Contradiction:

Improveability to define custom events post-designVSAvoidease of managing event subscriptions

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements self-service mechanisms where subscriber objects automatically register their event subscriptions with publisher objects through standardized interfaces. The event notification system automatically routes events to appropriate subscribers without requiring manual configuration or intervention, reducing operational complexity despite the flexibility gained.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system employs universal event subscription interfaces and standardized event notification mechanisms that work across different types of business objects. The same subscription and notification infrastructure handles diverse event types uniformly, simplifying management while supporting custom event definitions.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Productivity

If event notification systems are implemented with multiple subscribers, then system functionality and responsiveness improve, but communication overhead and processing time increase

Engineering Contradiction:

Improvesystem responsiveness to business eventsVSAvoidtime for event notification processing

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-establishing event subscription relationships and maintaining ready-state notification pathways before events occur. Subscriber objects are pre-registered with publishers, and event routing paths are pre-configured, allowing immediate event notification without runtime configuration delays.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system introduces an event notification intermediary that manages the communication between publishers and multiple subscribers. This intermediary consolidates event distribution, manages subscriber registries, and handles routing efficiently, reducing the direct communication overhead between each publisher-subscriber pair.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8341646B2Information system with event-enabled data objects

Publication Date: 2012.12.25 SAP SE

AI summary

A computer-implemented information system involves data objects stored in the database with characteristics of such data objects defined at a design time. The system is able to associate customized data object events with at least some of the data objects subsequent to the design time to define subscriber objects. Data objects which are publisher objects are determined based on the events. In one implementation, the information system includes a messaging manager, with a message broker and an event controller associated therewith.