Generalized Event Notification System for Scalable Component Updates

Solution Overview

Problem

Updating systems with related/coupled components, such as MMO game systems, is complex and time-consuming due to the need for manual identification and updating of affected components, making change implementation unscalable.

Innovation Solution

Implementing a system manager that provides layers of abstraction or generalization in the system architecture, allowing for generalized event notifications that do not change when specific component actions are modified, enabling changes to be made without affecting related components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional manual updating methods are used for systems with related/coupled components, then changes can be implemented in components, but the process becomes complex and time-consuming requiring manual identification and checking of all affected components

Engineering Contradiction:

ImproveAbility to change and adapt system componentsVSAvoidComplexity of updating process

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an event notification system as an intermediary layer between system components. This mediator publishes events that components can subscribe to, eliminating the need for manual identification and updating of affected components. When a component changes, it simply publishes an event notification, and all subscribed components automatically receive and process the notification, greatly simplifying the updating process while maintaining adaptability.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the system into independent components with loose coupling through the event notification mechanism. Each component operates independently and communicates through standardized event notifications rather than direct connections. This segmentation allows individual components to be updated without affecting others, reducing the complexity of system-wide updates while preserving the ability to adapt individual components.

Inventive Principle:

Principle #1Segmentation

2Reliability

If manual identification and checking of affected components is performed, then all components can be updated, but the process is time-consuming and unscalable

Engineering Contradiction:

ImproveCompleteness of component updatingVSAvoidTime required for system updates

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by having components pre-register their event subscriptions before changes occur. Components declare which events they are interested in advance, creating a subscription list. When changes occur, the system automatically routes event notifications to all pre-registered subscribers, ensuring complete and reliable updates without manual identification while dramatically reducing the time required compared to conventional methods.

Inventive Principle:

Principle #10Preliminary action

3Ease of operation

If direct coupling between components is maintained, then components can communicate directly, but changes in one component require updates to related components

Engineering Contradiction:

ImproveDirect communication between componentsVSAvoidFlexibility to make changes without affecting other components

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces an event notification system as an intermediary layer between system components. This mediator publishes events that components can subscribe to, eliminating the need for manual identification and updating of affected components. When a component changes, it simply publishes an event notification, and all subscribed components automatically receive and process the notification, greatly simplifying the updating process while maintaining adaptability.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the system into independent components with loose coupling through the event notification mechanism. Each component operates independently and communicates through standardized event notifications rather than direct connections. This segmentation allows individual components to be updated without affecting others, reducing the complexity of system-wide updates while preserving the ability to adapt individual components.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS8566844B2Generalized event and response system (GEARS)

Publication Date: 2013.10.22 DISNEY ENTERPRISES INC

AI summary

Embodiments of the invention broadly provide a system configured to receive, process and broadcast generalized event notifications from components and provide these generalized event notifications (messages) to a predetermined set of subscriber components. Accordingly, embodiments of the invention broadly contemplate a messaging system providing increased system flexibility for implementing and managing changes in complex computing systems having one or more related system components.