Uniform Event Framework for Software Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software systems face challenges in efficiently managing and distributing events across multiple applications and components, as existing solutions lack a unified framework for event handling, leading to inconsistencies and inefficiencies in data dissemination among event publishers and subscribers.

Innovation Solution

A uniform event framework is introduced, which receives event notifications from publishers, generates structured event messages, and distributes them to subscribers through an event bus, allowing different subscribers to retrieve varying sets of data associated with events, and supports different software frameworks and systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If a uniform event framework is implemented to standardize event distribution, then event management consistency is improved, but system complexity increases

Engineering Contradiction:
Improveevent management consistencyVSAvoidsystem complexity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The patent introduces a uniform event framework as an intermediary layer between event publishers and event subscribers. This framework includes standardized components such as event publishers, event subscribers, event buses, and event processors that mediate event distribution. The intermediary framework provides consistent event management through standardized interfaces and protocols, resolving the contradiction by adding structured mediation rather than direct peer-to-peer connections.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The uniform event framework implements universal, multi-functional components that can handle various event types and distribution scenarios through a single standardized interface. The event publisher, subscriber, and bus components are designed to be framework-agnostic and can work across different software architectures, providing consistent event management without requiring separate implementations for each scenario.

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

2Adaptability or versatility

If event publishers send different data to different subscribers, then data customization is improved, but data distribution efficiency deteriorates

Engineering Contradiction:
Improvedata customizationVSAvoiddata distribution efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements preliminary action by having event subscribers register their data requirements in advance with the uniform event framework. The framework pre-configures event processors and filters based on these registered requirements. When events are published, the framework efficiently routes events to appropriate subscribers based on pre-established matching criteria, eliminating the need for publishers to individually customize data for each subscriber while maintaining high data distribution efficiency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The uniform event framework enables self-service event distribution where subscribers independently express their data needs through standardized subscription interfaces. The framework automatically matches events with appropriate subscribers based on event types, filters, and subscriber requirements without requiring manual intervention from publishers. This self-organizing mechanism maintains both customization and efficiency.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10552235B2Uniform event framework
Publication Date: 2020.02.04 SUCCESSFACTORS INC
  • US10552235B2 patent drawing
  • US10552235B2 patent drawing
  • US10552235B2 patent drawing

AI summary

Some embodiments provide a system that includes a set of event publishers configured to publish events occurring on the event publishers. The system also includes a uniform event framework configured to receive, from an event publisher in the set of event publishers, an event notification indicating an event occurred on the event publisher and generate an event structure based on the event notification. The system further includes an event bus configured to receive the event notification from the uniform event framework and send the event structure to a set of event subscribers for consumption of the event structure. Each event publisher in the set of event publishers is further configured to receive different callbacks from different event subscribers in the set of event subscribers for different sets of data associated with the event.