Unified Event Framework Views via Shared Data Store

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional event management frameworks in servers manage system events through multiple, independently stored data stores, leading to increased complexity and inefficiency, with limited inter-framework communication and disparate data store views, making unified event management challenging.

Innovation Solution

Implementing a shared event data store with a generic distribution system, allowing event frameworks to store data in BasicEvent objects and manage their lifetime, enabling unified views across frameworks through the EventDirector object, which forwards notifications of events and maintains references for consistent event management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple independent event data stores are implemented for different event frameworks, then each framework can manage its own events independently, but the overall system complexity and storage requirements increase

Engineering Contradiction:
ImproveEvent framework independenceVSAvoidSystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple independent event data stores into a single shared event data store that serves all event frameworks. This shared data store contains event information objects that can be referenced by multiple frameworks simultaneously, eliminating the need for separate data stores while maintaining framework independence through reference-based access and unification rules.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The shared event data store is designed as a universal structure that can serve multiple event frameworks with different requirements. Event information objects in the shared data store can be referenced by any framework, and unification rules enable different frameworks to access and manage events according to their specific needs while sharing the same underlying data structure.

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

2Ease of operation

If each event framework maintains its own private data store, then event management is straightforward within each framework, but inter-framework communication and unified views are limited

Engineering Contradiction:
ImproveEvent management simplicityVSAvoidInter-framework event visibility
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The shared event data store acts as an intermediary between multiple event frameworks. Instead of frameworks directly communicating with each other or maintaining separate data stores, they all interact with the shared data store through a common interface. This intermediary structure enables unified views across frameworks while maintaining operational simplicity through standardized access methods.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments event information into discrete event information objects that can be independently managed and referenced. Each framework can work with specific event objects while the shared data store maintains the complete set. This segmentation allows frameworks to access only the events they need while maintaining visibility of the complete event universe through the shared structure.

Inventive Principle:
Principle #1Segmentation

3Reliability

If event frameworks copy and store event information in private data stores, then each framework has full control over its event data, but resource utilization and system efficiency decrease

Engineering Contradiction:
ImproveEvent data controlVSAvoidSystem efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Instead of copying entire event data stores, the patent uses reference-based access where frameworks maintain references to event information objects in the shared data store. This selective copying of only necessary references (not full data copies) maintains framework control over their specific events while dramatically reducing resource consumption and improving system efficiency.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS7694309B2Method for facilitating unification of event framework views and system comprising same
Publication Date: 2010.04.06 SANMINA CORP
  • US7694309B2 patent drawing
  • US7694309B2 patent drawing
  • US7694309B2 patent drawing

AI summary

An object model comprises a data store and a plurality of event framework information objects. The data store including a plurality of event information objects each defining server event information for a respective one of a plurality of unique events exhibited by a server during operation. The plurality of event framework information objects each define event framework characteristics for a respective one of a plurality of event frameworks implemented in the server. At least one of the event framework information objects reference a common one of the event information objects for enabling server event information defined by the common one of the event information objects to be viewed using the respective one of the event frameworks corresponding thereto. Each one of the event framework information objects define event framework unification rules under which unification of event framework views provided in accordance with each one of the event framework information objects is facilitated.