Blockchain Network Configuration Consensus Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network infrastructure analysis and convergence methods fail to effectively manage changes in network topology, impacting reliability and security due to the lack of a comprehensive and immutable record of configuration changes across interconnected devices.

Innovation Solution

Implementing a blockchain mechanism to detect network topology changes, determine if a new configuration is required, create a blockchain block containing the new configuration, and add it to a network blockchain, ensuring an immutable history of network configurations and consensus among devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional network configuration management is used, then device changes can be made quickly, but the reliability and security of the network are compromised due to lack of immutable records

Engineering Contradiction:
Improvenetwork reliabilityVSAvoidconfiguration management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates digital copies of network configuration data and stores them as blockchain blocks. Each configuration change is replicated across the distributed network, creating an immutable copy that serves as a permanent record. This copying mechanism ensures reliability without requiring complex centralized management systems.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent replaces traditional mechanical/configurational network management systems with a blockchain-based digital ledger system. Instead of relying on complex configuration management software and centralized controllers, the system uses cryptographic hashing and distributed consensus to manage network configurations, simplifying the overall system architecture while improving reliability.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Adaptability or versatility

If network topology changes are detected and configurations are updated traditionally, then adaptability is improved, but security is worsened due to lack of authenticated change records

Engineering Contradiction:
Improvenetwork adaptabilityVSAvoidsecurity vulnerabilities
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements a feedback mechanism where network devices continuously monitor topology changes and automatically generate blockchain blocks to record configuration updates. This closed-loop system ensures that every change is detected, authenticated, and recorded immutably, providing both adaptability to changes and security through cryptographic verification of each change event.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent performs preliminary authentication and validation of configuration changes before they are implemented on the network. By requiring consensus validation and cryptographic signing before applying topology changes, the system ensures that only authorized changes are made, preventing security vulnerabilities while maintaining network adaptability.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If comprehensive network configuration records are maintained, then forensic analysis capability is improved, but the storage and retrieval complexity increases

Engineering Contradiction:
Improveconfiguration history preservationVSAvoidrecord management complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments the network configuration history into discrete blockchain blocks, each containing specific configuration data and metadata. This segmentation allows for efficient storage and retrieval of configuration history without requiring complex centralized database management. Each block is independently verified and linked, simplifying the overall record management architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent replaces complex database management systems with a blockchain-based ledger. Instead of using traditional relational databases that require complex queries, joins, and transaction management, the system uses a simplified append-only ledger structure where configuration records are added as blocks, making storage and retrieval more straightforward and less complex.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If distributed consensus mechanism is implemented, then security and reliability are improved, but the processing time and energy consumption increase

Engineering Contradiction:
Improveconfiguration consistencyVSAvoidconfiguration update time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements a practical Byzantine Fault Tolerance (pBFT) consensus mechanism that requires only a threshold number of nodes to validate configuration changes rather than requiring complete consensus from all network participants. This partial action approach achieves sufficient configuration consistency and reliability without the excessive time and energy costs of requiring unanimous agreement from every node in the network.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11159376B2System and method for network infrastructure analysis and convergence
Publication Date: 2021.10.26 KYNDRYL INC
  • US11159376B2 patent drawing
  • US11159376B2 patent drawing
  • US11159376B2 patent drawing

AI summary

Disclosed embodiments provide techniques for computer networks infrastructure automatic convergence. The network devices are enabled to communicate with other adjacent network devices, independently of the device type, about detected changes that could affect them and together generate consensus utilizing a blockchain mechanism about the configuration changes that are accepted. A priority table specifies a priority for various device classes on a network. The devices, in response to a new network topology, determine if a new device configuration is necessary. When a new device configuration is necessary, data corresponding to the new device configuration is put into a blockchain block and appended to a network blockchain that is maintained by one or more nodes (devices) on the network. In this way, an immutable history of network configurations is maintained, improving network security and reliability.