Hierarchical Publish Subscribe System for Scalable Message Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional publish/subscribe systems face scalability issues as they are scaled up, leading to increased complexity, security concerns, and performance degradation due to the large number of connections between clients and servers.

Innovation Solution

A hierarchical publish/subscribe system is introduced, where subscription requests are aggregated at remote relays and forwarded to central relays, reducing the number of connections and implementing a 'subscribe to one, publish to all' mechanism to eliminate duplicates and improve message delivery efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a conventional publish/subscribe system is scaled up, then the system can handle more messages and subscribers, but the number of connections between clients and servers increases, leading to increased complexity and security concerns

Engineering Contradiction:
Improvemessage handling capacityVSAvoidnumber of connections
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a hierarchical architecture with multiple levels of relays (remote relays and central relays) to segment the traditional flat client-server connection structure. This segmentation reduces the number of direct connections by routing messages through intermediate relay nodes, thereby maintaining high message handling capacity while reducing connection complexity and security risks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent employs relay nodes as intermediary components between clients and servers. These relays aggregate subscription requests and forward publication requests, acting as mediators that reduce the number of direct connections required. The relays maintain subscription information and route messages efficiently, solving the contradiction between productivity and connection complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If a conventional publish/subscribe system is scaled up, then the system can handle more subscribers, but the number of connections increases, leading to performance degradation

Engineering Contradiction:
Improvesubscriber handling capacityVSAvoidmessage delivery speed
Core Design Contradiction:
ProductivityVSSpeed

Solution Approach 1:

The patent merges multiple subscription requests from different clients into a single subscription request at the relay level. By aggregating subscriptions at remote relays before forwarding to central relays, the system reduces the number of individual connection handling operations, thereby maintaining fast message delivery speeds even as the number of subscribers increases.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

Relay nodes serve as intermediaries that pre-process and aggregate subscription information, reducing the overhead of individual connection handling. This mediation allows the system to maintain high message delivery speeds by minimizing the number of direct server-client interaction cycles required.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If a conventional publish/subscribe system is scaled up, then the system can handle more messages, but the number of connections increases, leading to increased security concerns

Engineering Contradiction:
Improvemessage handling capacityVSAvoidsecurity risks
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The hierarchical relay architecture segments the client-server communication into multiple trusted intermediate layers. By routing messages through relays that maintain authentication and authorization mechanisms, the system reduces the attack surface associated with direct client-server connections, thereby addressing security concerns while maintaining high message handling capacity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Relay nodes act as secure intermediaries that enforce authentication and authorization policies between clients and servers. These intermediaries centralize security management and reduce the number of direct connection points that could be exploited, thereby reducing security risks while maintaining productivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If subscription requests are forwarded to all central relays, then message delivery reliability is improved, but redundant subscriptions and message processing occur

Engineering Contradiction:
Improvemessage delivery reliabilityVSAvoidsubscription aggregation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by having remote relays aggregate and filter subscription requests before forwarding them to central relays. This pre-processing eliminates duplicate subscriptions and reduces the number of messages that need to be processed at the central relay level, thereby maintaining message delivery reliability while reducing processing complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback mechanisms where central relays acknowledge received subscriptions and publications, allowing remote relays to track which subscriptions have been successfully propagated. This feedback loop prevents redundant processing by allowing remote relays to optimize their message forwarding based on confirmation from central relays.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9569753B2Hierarchical publish/subscribe system performed by multiple central relays
Publication Date: 2017.02.14 VERISIGN INC
  • US9569753B2 patent drawing
  • US9569753B2 patent drawing
  • US9569753B2 patent drawing

AI summary

A method for transmitting messages in a publish/subscribe message system. The method also includes: receiving, at a first relay, a subscription request from a first client; recording, at the first relay, subscription information of the first client based on the subscription request; receiving, at the first relay, a publication request from a second client, wherein the publication request includes a message; and transmitting the message to the first client.