Event Distribution Framework for Collaboration Environments

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current collaboration environments lack support for both pre-defined and dynamically defined events with varying payloads, and they do not provide seamless event distribution and subscription management with an easy-to-administer user interface, making them insufficiently general-purpose for many users.

Innovation Solution

A collaboration environment with a generic event distribution framework that supports both synchronous and asynchronous events, using two separate APIs to separate event producers from consumers, and allowing multiple data formats for event payloads, with features like event declaration, subscription management, and translation between languages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a collaboration environment supports both pre-defined and dynamically defined events with varying payloads, then the system's adaptability and versatility improve, but the device complexity increases due to the need for multiple data formats and event types

Engineering Contradiction:
Improveevent distribution flexibilityVSAvoidframework complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal event distribution framework that can handle multiple event types (pre-defined and dynamic) and various data formats through a single standardized API interface. The framework uses a common event structure with flexible payload types, allowing it to accommodate different event scenarios without requiring separate systems for each event type, thus achieving multi-functionality while maintaining manageable complexity

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

Solution Approach 2:

The framework employs parameter-based event definitions where events are characterized by configurable parameters such as event type, payload format, and delivery mode (synchronous/asynchronous). By changing these parameters, the system can adapt to different event scenarios without structural modifications, enabling flexibility through parameter variation rather than system complexity

Inventive Principle:
Principle #35Parameter changes

2Reliability

If synchronous event processing is implemented where the first consumer can modify event data, then the reliability and data accuracy improve, but the loss of time increases due to sequential processing requirements

Engineering Contradiction:
Improveevent data accuracyVSAvoidevent distribution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements dynamic event processing modes that can switch between synchronous and asynchronous delivery based on event type and consumer requirements. For events requiring data modification, the system uses synchronous mode with sequential consumer notification, allowing data accuracy to be maintained while providing the option for asynchronous mode in scenarios where time is more critical than data modification, thus dynamically balancing reliability and speed

Inventive Principle:
Principle #15Dynamics

3Ease of operation

If separate APIs are used to separate event producers from consumers, then the system's ease of operation improves through clear interface separation, but the device complexity increases due to multiple API components

Engineering Contradiction:
Improveinterface usabilityVSAvoidAPI structure complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent divides the event distribution system into distinct API components: a producer API for event creation and publication, and a consumer API for event subscription and reception. This segmentation provides clear interface separation that improves ease of operation, as each API has a specific, well-defined purpose. The complexity is managed by ensuring these segmented APIs communicate through a standardized internal event format, preventing the need for complex integration logic

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9807143B2Systems and methods for event routing and correlation
Publication Date: 2017.10.31 AVAYA INC
  • US9807143B2 patent drawing
  • US9807143B2 patent drawing
  • US9807143B2 patent drawing

AI summary

A collaboration environment provides a generic event distributing framework that can distribute both synchronous and asynchronous events. The distributed events may be pre-defined or dynamically defined. Further, the framework can support multiple data formats for the event payload. The collaboration environment relies on two separate APIs to separate event producers from event consumers.