Mesh Network Update Manager for Node Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional mesh networks lack granular management of updates, leading to potential network compromise if a single node is compromised, as they treat the entire network as a single entity for security and access, without ensuring each node has the most up-to-date software or firmware.

Innovation Solution

A mesh network update manager is introduced, utilizing a rule engine to configure and manage updates, track software and firmware versions, and employ peer-to-peer communication to ensure all nodes receive updates, with mechanisms to handle nodes without network access and remove unresponsive nodes to maintain network integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If conventional mesh networks treat the entire network as a single entity for security and access, then network simplicity is maintained, but network security deteriorates as a single compromised device can result in the entire network being compromised

Engineering Contradiction:
Improvenetwork management structureVSAvoidnetwork security
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the mesh network into individual node entities, each with its own security context and update management. The update manager treats each node as a separate target for update delivery and status tracking, enabling granular security control where compromise of one node does not automatically compromise the entire network.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by applying differentiated security and update management policies to individual nodes based on their specific characteristics, such as device type, firmware version, and security posture. Each node can have customized update requirements and security parameters rather than a uniform network-wide approach.

Inventive Principle:
Principle #3Local quality

2Ease of operation

If conventional mesh networks do not track individual node software versions, then management overhead is reduced, but software update reliability deteriorates as nodes may lack the most up-to-date software

Engineering Contradiction:
Improveupdate management overheadVSAvoidsoftware update status
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The update manager implements feedback mechanisms where each node reports its software and firmware versions to the manager, which tracks this information and uses it to determine update eligibility. This continuous feedback loop ensures the manager has current knowledge of each node's software state without requiring manual tracking, balancing automation with accurate information.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Nodes autonomously report their software versions and update status to the update manager, eliminating the need for centralized manual tracking. Each node serves itself by providing update information and receiving update instructions, reducing management overhead while maintaining accurate software version awareness across the network.

Inventive Principle:
Principle #25Self-service

3Reliability

If mesh networks implement granular update management for each node, then network security is improved, but device complexity increases due to the need to track and manage updates individually

Engineering Contradiction:
Improvenetwork securityVSAvoidupdate management system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The update manager serves multiple functions within a single system: it discovers nodes, tracks software versions, determines update eligibility, delivers updates, and verifies update status. This multi-functional approach consolidates what could be separate complex systems into one unified manager, reducing overall system complexity while maintaining granular control.

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

Solution Approach 2:

The update manager acts as an intermediary between the external update source and individual mesh nodes, centralizing the complexity of update management in a single coordinating entity rather than requiring each node to independently manage its own updates or for multiple distributed managers to coordinate.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If mesh networks notify nodes to retrieve updates autonomously, then update delivery simplicity is maintained, but update reliability deteriorates as nodes may fail to retrieve updates due to network access issues

Engineering Contradiction:
Improveupdate delivery mechanismVSAvoidupdate retrieval success
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The update manager performs preliminary actions by notifying nodes of available updates and monitoring their retrieval status before considering the update process complete. This preliminary monitoring allows the manager to detect failures early and initiate retry logic or alternative delivery methods before the node permanently misses the update.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements preliminary anti-action by preparing alternative update delivery paths in advance, such as direct manager-to-node delivery or multi-hop routing through intermediate nodes, to counteract potential network access failures before they prevent update delivery.

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS12155528B2Mesh network update management
Publication Date: 2024.11.26 RED HAT LLC
  • US12155528B2 patent drawing
  • US12155528B2 patent drawing
  • US12155528B2 patent drawing

AI summary

A method of managing updates in a mesh network includes determining that an update is available for a first computing node of a mesh network and identifying one or more characteristics of the first computing node of the mesh network. The method further includes determining an update strategy for providing the update to the first computing node in view of the one or more characteristics of the first computing node and providing the update to the first computing node in view of the update strategy.