Consensus Driven Mesh Organization Service Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mesh network systems struggle to dynamically manage services within zones, leading to service gaps and increased network traffic as nodes access services from outside their zone, resulting in workload imbalances and inefficiencies.

Innovation Solution

A consensus-driven process is implemented where processing logic determines service gaps within a zone, nominates a node to run the missing service, requests consensus among nodes, and pushes the service to the nominated node upon confirmation, ensuring services are managed on a per-zone basis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If services are managed centrally in mesh networks, then service allocation is simplified, but network traffic increases and service gaps occur in specific zones

Engineering Contradiction:
Improveservice management complexityVSAvoidnetwork traffic
Core Design Contradiction:
Device complexityVSLoss of energy

Solution Approach 1:

The patent segments the mesh network into multiple geographic zones, with each zone independently managing its own services. The consensus driver service operates at the zone level rather than network-wide, dividing the service management function into smaller regional units. This segmentation reduces the scope of consensus requests and service discovery traffic within each zone while maintaining overall network functionality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local service management where each zone autonomously handles service allocation and consensus within its boundaries. Services are discovered and managed locally rather than being propagated throughout the entire network. This local quality approach minimizes network traffic by confining service management operations to the specific zone where they are needed.

Inventive Principle:
Principle #3Local quality

2Reliability

If services are accessed from outside the zone, then service availability is maintained, but network traffic increases and efficiency decreases

Engineering Contradiction:
Improveservice availabilityVSAvoidnetwork efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent performs preliminary service discovery and allocation within each zone before nodes need to access services. The consensus driver service proactively identifies service gaps in each zone and orchestrates local service deployment in advance. This preliminary action ensures services are available locally when needed, preventing nodes from having to access services from outside their zone and thereby maintaining network efficiency.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If consensus is required among all nodes, then service allocation reliability is improved, but decision-making time increases

Engineering Contradiction:
Improveservice allocation reliabilityVSAvoiddecision-making time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the consensus process to operate at the zone level rather than requiring network-wide consensus. The consensus driver service collects feedback only from nodes within the specific zone affected by the service allocation decision. This segmentation of the consensus scope reduces the number of nodes that need to participate in each decision, thereby reducing decision-making time while maintaining reliability within each zone.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12328231B2Consensus driven mesh organization
Publication Date: 2025.06.10 RED HAT LLC
  • US12328231B2 patent drawing
  • US12328231B2 patent drawing
  • US12328231B2 patent drawing

AI summary

Processing logic may determine that a service is absent among a plurality of nodes within a zone of a mesh network. Processing logic may nominate one of the plurality of nodes to run the service. Processing logic may request a consensus among the plurality of nodes within the zone of the mesh network to confirm the nomination. Processing logic may, in response to receiving confirmation of the nomination by the plurality of nodes in the zone of the mesh network, push the service to the one of the plurality of nodes to run the service.