Secure Messaging Key Rotation in Distributed Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing secure messaging systems between distributed computing nodes face challenges with malicious attacks, data loss in noisy environments, and high complexity in managing key pairs, particularly with asymmetric keys and shared symmetric keys.

Innovation Solution

Implementing a method that uses a hashmap or table to generate symmetric keys, rotating these keys periodically, and detecting data loss for resynchronization, allowing secure messaging without sharing keys or managing key pairs, and enabling secure messaging resynchronization and re-transmission in noisy environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If asymmetric keys are used for secure messaging, then security is improved, but processing requirements and key management complexity increase

Engineering Contradiction:
ImprovesecurityVSAvoidkey management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the key management burden from the messaging system by using a centralized key management server that handles key generation, distribution, and rotation. Individual nodes only need to store and use keys provided by the central server, eliminating the need for complex peer-to-peer key management while maintaining security through asymmetric encryption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a key management server as an intermediary between messaging nodes. This server acts as a trusted mediator that generates, distributes, and manages cryptographic keys for all nodes in the distributed system, simplifying key management complexity while maintaining security through centralized control and automated key rotation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If shared symmetric keys are used for secure messaging, then key management complexity is reduced, but security is compromised due to key exposure risks

Engineering Contradiction:
Improvekey management complexityVSAvoidsecurity
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements periodic key rotation where symmetric keys are automatically renewed at predetermined intervals. The key management server generates new symmetric keys periodically and distributes them to all nodes, ensuring that even if a key is compromised, the window of vulnerability is limited to one rotation period. This maintains security while keeping key management simple through automated periodic updates.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent changes the temporal parameter of key validity by implementing time-based key expiration and rotation. Keys are assigned finite validity periods and automatically renewed, transforming the static key management approach into a dynamic system where key parameters (validity time, rotation schedule) are continuously updated to maintain security without increasing management complexity.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If keys are rotated periodically, then security is improved by reducing key exposure risk, but additional key management operations are required

Engineering Contradiction:
ImprovesecurityVSAvoidmessaging efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent performs preliminary key rotation operations by proactively generating and distributing new keys before the current keys expire. The key management server anticipates key expiration and initiates rotation in advance, ensuring seamless key transitions without interrupting messaging operations. This preliminary action maintains security through frequent key rotation while minimizing impact on messaging efficiency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent ensures continuous messaging capability during key rotation by maintaining multiple valid keys simultaneously. Nodes can switch between current and rotated keys without interruption, ensuring the useful action of secure messaging continues uninterrupted. The key management system orchestrates smooth transitions where old keys remain valid until successfully replaced, maintaining productivity while improving security through rotation.

Inventive Principle:
Principle #20Continuity of useful action

4Adaptability or versatility

If messages are sent in noisy and congested environments, then communication coverage is improved, but data loss increases

Engineering Contradiction:
Improvecommunication coverageVSAvoiddata loss
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where nodes acknowledge receipt of messages and the key management server monitors delivery status. If message delivery is not confirmed within a predetermined time or if errors are detected, the system automatically triggers retransmission. This feedback loop ensures reliable message delivery in noisy environments while maintaining communication coverage, as the feedback-driven retransmission compensates for data loss without requiring reduced communication scope.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10623178B2System and method for secure messaging between distributed computing nodes
Publication Date: 2020.04.14 DELL PROD LP
  • US10623178B2 patent drawing
  • US10623178B2 patent drawing
  • US10623178B2 patent drawing

AI summary

Methods and systems for secure messaging may involve receiving an encrypted message from a node, decrypting the message using a default key, sending a message, rotating a group key, and distributing a key rotation message. The message received may be to discover a master of a group. The message sent may welcome the node into the group as a member. The welcome message may be encrypted with the default key and may include information to determine the group key. The group key may be rotated based on an expiration of a group key rotation window. The group key may become a prior group key and the rotated group key may be a current group key. The key rotation message may be encrypted with one of the default key or the prior group key and may include information to determine the current group key.