Hierarchical Message Flooding with Cascading Triggers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional message flooding in distributed platforms is inefficient and slow due to overhead and delays in establishing connections, and is unsuitable for time-sensitive applications as it relies on the slowest server for completion, potentially leading to indeterminate completion times and exposure to security risks.

Innovation Solution

A distributed hierarchical architecture with persistent connections and cascading triggers is implemented to facilitate simultaneous message propagation and response collection across nodes, reducing network latency and potential failures, while ensuring determinate completion times through time-based or percentage triggers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional message flooding establishes individual connections with each server before contacting them, then secure and reliable communication is achieved, but connection establishment overhead and delay increase significantly

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidmessage flooding completion time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Persistent connections are established and maintained in advance before message flooding is needed. The connection establishment process is performed beforehand and kept alive through keep-alive mechanisms, so that when message flooding occurs, no new connection establishment is required, eliminating the time penalty while maintaining secure communication.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Connections are kept persistent and continuously maintained rather than established and torn down for each message flood operation. The system maintains continuous useful connections between nodes, using keep-alive packets to prevent connection timeout, thereby eliminating repeated connection establishment overhead while ensuring reliable communication channels remain available.

Inventive Principle:
Principle #20Continuity of useful action

2Ease of operation

If a central server establishes all connections and propagates messages to distributed servers, then centralized control is achieved, but propagation delay varies greatly depending on network distance

Engineering Contradiction:
Improvecentralized controlVSAvoidmessage propagation speed
Core Design Contradiction:
Ease of operationVSSpeed

Solution Approach 1:

The centralized message propagation is segmented into a hierarchical structure where messages are propagated through intermediate nodes at different levels. Instead of all messages traveling from the central server to every leaf node, the propagation is divided into segments through parent-child relationships in the hierarchy, reducing the maximum propagation distance and delay while maintaining centralized initiation of the flood.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The message propagation transitions from a single-dimensional radial propagation from central server to all nodes, to a multi-dimensional hierarchical propagation through multiple levels of intermediate nodes. This dimensional change in the propagation path structure reduces the maximum distance any single message must travel while maintaining comprehensive node coverage.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Loss of information

If message flooding waits for the slowest server to respond before completing, then complete information collection is achieved, but completion time becomes indeterminate and potentially very long

Engineering Contradiction:
Improveinformation collection completenessVSAvoidmessage flooding completion time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system collects responses from a sufficient subset of servers rather than waiting for all servers to respond. By using triggers based on time thresholds or percentage thresholds of expected responses, the system obtains enough information to make decisions without being blocked by the slowest servers, achieving partial action that is sufficient for the intended purpose while dramatically reducing completion time.

Inventive Principle:
Principle #16Partial or excessive action

4Speed

If broadcast or multicast messaging is used to contact distributed servers, then message propagation speed is improved, but security is compromised and response collection becomes difficult

Engineering Contradiction:
Improvemessage propagation speedVSAvoidcommunication security
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system uses an intermediary hierarchical structure of intermediate nodes between the central server and leaf nodes. These intermediaries receive messages through secure persistent connections and forward them to their child nodes, maintaining security through authenticated communication channels while achieving fast propagation. The intermediaries act as trusted mediators that enable secure multi-hop message distribution.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10693771B2Optimized message flooding across nodes of a distributed platform
Publication Date: 2020.06.23 VERIZON PATENT & LICENSING INC
  • US10693771B2 patent drawing
  • US10693771B2 patent drawing
  • US10693771B2 patent drawing

AI summary

Optimized message flooding is provided for time sensitive or real-time contacting of nodes across a distributed platform. The propagation of messaging across the distributed platform is accelerated based on a parallel fan-out distribution of the flood messaging from increasing numbers of nodes with the distribution occurring over existing connections maintained between different sets of nodes. Responses are propagated via a reverse traversal of the nodes. The reverse traversal is optimized by merging responses at different tiers. A set of triggers set at the different nodes specify conditions with which to identify and preempt the slowest nodes of a lower tier from withholding message flooding completion. As such, desired messaging and responses can be collected from across the distributed platform in a determinate amount of time with minimal overhead.