Mesh Network Key Management with Version-Based Update Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In mesh networks, nodes may use outdated encryption keys due to network conditions hindering key updates, leading to communication failures and excessive bandwidth consumption from frequent key request overload on the key management service.

Innovation Solution

Nodes detect outdated keys by comparing version identifiers and perform key mismatch resolution to regulate key update requests, ensuring timely key updates and reducing network bandwidth consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If nodes frequently request key updates from the key management service, then encryption security is improved, but network bandwidth consumption increases and the key management service becomes overloaded

Engineering Contradiction:
Improveencryption securityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary key version comparison before initiating key update requests. Nodes include version identifiers in messages and proactively check whether their local keys are outdated before requesting updates, preventing unnecessary key request transmissions and reducing network bandwidth consumption while maintaining security

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The key management service provides feedback to nodes about key version status. When the service detects that a node is using an outdated key, it sends a notification message containing the new key version information, enabling the node to update its key without needing to request updates frequently, thus reducing network overhead

Inventive Principle:
Principle #23Feedback

2Loss of energy

If nodes wait for key updates from the key management service, then network bandwidth consumption is reduced, but communication reliability deteriorates due to use of outdated keys

Engineering Contradiction:
Improvenetwork bandwidth consumptionVSAvoidcommunication reliability
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The system performs preliminary key version comparison before initiating key update requests. Nodes include version identifiers in messages and proactively check whether their local keys are outdated before requesting updates, preventing unnecessary key request transmissions and reducing network bandwidth consumption while maintaining security

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The key management service provides feedback to nodes about key version status. When the service detects that a node is using an outdated key, it sends a notification message containing the new key version information, enabling the node to update its key without needing to request updates frequently, thus reducing network overhead

Inventive Principle:
Principle #23Feedback

3Reliability

If nodes proactively request key updates, then encryption security is improved, but the key management service becomes overloaded and network efficiency decreases

Engineering Contradiction:
Improveencryption securityVSAvoidnetwork efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary key version comparison before initiating key update requests. Nodes include version identifiers in messages and proactively check whether their local keys are outdated before requesting updates, preventing unnecessary key request transmissions and reducing network bandwidth consumption while maintaining security

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The key management service provides feedback to nodes about key version status. When the service detects that a node is using an outdated key, it sends a notification message containing the new key version information, enabling the node to update its key without needing to request updates frequently, thus reducing network overhead

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250310102A1Encryption key management in mesh networks
Publication Date: 2025.10.02 ITRON INC
  • US20250310102A1 patent drawing
  • US20250310102A1 patent drawing
  • US20250310102A1 patent drawing

AI summary

Various embodiments disclosed herein provide techniques for managing encryption keys at nodes in a mesh network. In various embodiments, a method includes, during a key failure detection time period associated with a first key, counting, by a node in a mesh network using a failure counter, one or more decryption failures using the first key; while in a key update time period and in response to detecting a decryption failure using the first key, determining, by the node, that the failure counter is above a threshold; and in response to determining that the failure count is above the threshold, transmitting, by the node to a key management service, a request for an update to the first key.