Notification Queue for Single Client Connection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems require multiple connections between client devices and server resources for real-time data updates, leading to inefficiencies and increased complexity, especially when clients subscribe to multiple resources simultaneously.

Innovation Solution

Implementing a notification queue system within a data center that allows multiple server resources to share a single connection with a client device, where updates are sent to the queue and then communicated to the client, reducing the need for multiple connections and enhancing resource management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple connections are established between client devices and server resources for real-time data updates, then data synchronization reliability is improved, but system complexity and resource consumption increase

Engineering Contradiction:
Improvedata synchronization reliabilityVSAvoidconnection management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines multiple separate connections into a single unified connection. A notification queue is introduced as an intermediary that consolidates notifications from multiple server resources, allowing a single client connection to receive updates from multiple resources without requiring separate connections for each resource.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The notification queue serves as an intermediary component between server resources and the client connection. It receives notifications from multiple server resources and manages their delivery through a single connection, reducing the complexity of direct multi-connection management while maintaining reliable data synchronization.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If multiple connections are maintained for subscribing to multiple server resources, then real-time update delivery is improved, but resource management efficiency deteriorates

Engineering Contradiction:
Improveupdate delivery speedVSAvoidconnection resource consumption
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

Multiple connection resources are merged into a single connection through the notification queue mechanism. The queue consolidates the communication channel, allowing real-time updates from multiple server resources to be delivered through one connection, thereby reducing resource consumption while maintaining update delivery speed.

Inventive Principle:
Principle #5Merging (Combining)

3Use of energy by moving object

If a single connection is used to communicate with multiple server resources, then resource management efficiency is improved, but the ability to maintain real-time updates from multiple resources deteriorates

Engineering Contradiction:
Improveconnection resource consumptionVSAvoidreal-time update delivery
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The notification queue acts as an intermediary that enables a single connection to reliably receive real-time updates from multiple server resources. It manages the incoming notifications from different resources and ensures they are properly delivered through the single connection, maintaining both resource efficiency and update reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10063663B2Subscribing to multiple resources through a common connection
Publication Date: 2018.08.28 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10063663B2 patent drawing
  • US10063663B2 patent drawing
  • US10063663B2 patent drawing

AI summary

Methods, systems, and computer-readable media are provided to allow multiple server resources to share a single connection to a client device. The single connection may be maintained between a notification queue on the server side and the client device. Multiple server resources share the notification queue. When a resource changes or a service wants to communicate information to a client, corresponding messages are sent to the notification queue over a connection within the data center. Once in the notification queue, the updates are communicated to the client device.