Rich Internet Application Communication via XMPP Event-Driven Architecture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current solutions for Rich Internet Applications face limitations in scalability, performance, customizability, interoperability, and cost, particularly due to reliance on proprietary frameworks and periodic polling mechanisms that result in high latency and limited user participation.

Innovation Solution

A communication system integrating Jabber servers with eJabberD, weblogic, and XMPP presence messages, allowing for scalable, customizable, and cost-effective real-time communication between client and server components, with features like virtual environments and flexible content delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If periodic polling mechanism is used, then implementation simplicity is improved, but communication latency increases and real-time performance deteriorates

Engineering Contradiction:
Improveimplementation simplicityVSAvoidcommunication latency
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent replaces continuous polling with event-driven architecture where clients push updates to a server when changes occur, and the server selectively pushes relevant updates to clients. This transforms periodic action into on-demand action, eliminating unnecessary polling cycles while maintaining real-time communication capability.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system implements feedback mechanisms where clients signal server when they need updates, and server notifies clients when content changes. This bidirectional feedback loop eliminates the need for continuous polling while ensuring real-time information exchange, resolving the latency issue without sacrificing implementation simplicity.

Inventive Principle:
Principle #23Feedback

2Reliability

If proprietary server modules are installed, then messaging protocol integration is improved, but interoperability with other systems deteriorates

Engineering Contradiction:
Improvemessaging protocol integrationVSAvoidinteroperability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a standardized messaging protocol as an intermediary layer between client applications and server components. This protocol acts as a universal translator that enables different systems to communicate without requiring proprietary integration modules, thus maintaining reliability while improving interoperability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system employs a universal messaging protocol that can be implemented across different platforms and systems. This single protocol serves multiple functions: it enables real-time communication, handles content delivery, and facilitates interoperability between proprietary and non-proprietary systems, eliminating the need for multiple proprietary server modules.

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

3Ease of operation

If current communication solutions are used, then basic communication functionality is improved, but scalability to larger numbers of users deteriorates

Engineering Contradiction:
Improvecommunication functionalityVSAvoidnumber of users
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent segments the communication system into independent client-publisher and subscriber components with a centralized messaging broker. This segmentation allows the system to scale horizontally by adding more clients without increasing server processing complexity, as each client operates independently and the broker efficiently routes messages using publish-subscribe patterns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically adjusts its behavior based on the number of active users and message traffic. The publish-subscribe mechanism automatically scales resource allocation, and the system can dynamically add or remove users without affecting overall performance, enabling seamless scalability from small to large user bases.

Inventive Principle:
Principle #15Dynamics

4Productivity

If expensive server components are used, then communication performance is improved, but cost effectiveness deteriorates

Engineering Contradiction:
Improvecommunication performanceVSAvoidcost effectiveness
Core Design Contradiction:
ProductivityVSEase of manufacture

Solution Approach 1:

The patent implements a self-service architecture where clients actively push their own updates to the server and selectively pull updates when needed. This eliminates the need for expensive server components that would be required to continuously monitor and push data to all clients, as clients manage their own data synchronization needs.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system changes the operational parameters of server-client communication from continuous active pushing to event-driven selective pushing. This parameter change reduces server resource requirements and allows the use of more cost-effective server components while maintaining high communication performance through efficient event-triggered transfers.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11971948B1System and method for communication between Rich Internet Applications
Publication Date: 2024.04.30 ON24 INC
  • US11971948B1 patent drawing
  • US11971948B1 patent drawing
  • US11971948B1 patent drawing

AI summary

Systems and methods are disclosed for communicating between applications. In one exemplary embodiment, there is provided a system for communicating between applications where the system includes a Rich Internet Application and a control room within a server system The Rich Internet Application broadcasts information to the control room and the control room broadcasts the information to applications connected to the system. Moreover the Rich Internet Application also transmits low priority information to a web application for delayed logging and processing.