Network Infrastructure Recovery via Generalized Descriptive Language

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current disaster recovery methods for network infrastructures are time-consuming and costly, often requiring expensive proprietary software and struggling with interoperability across multiple vendor systems, leading to inefficiencies in reconstructing complex networks after catastrophic failures.

Innovation Solution

A method and system that capture and transform data and ecology information of existing networks into generalized descriptive languages, enabling the reconstruction of a functionally equivalent network using existing vendor interfaces and a recovery inventory, without the need for intrusive software installations, thus facilitating rapid and cost-effective recovery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional disaster recovery methods are used to reconstruct network infrastructure, then the network can be recovered, but the process is time-consuming and costly

Engineering Contradiction:

Improvenetwork recovery capabilityVSAvoidrecovery time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by capturing and storing data and ecology information about the existing network infrastructure before disasters occur. This pre-captured information is then used to rapidly reconstruct the network after failures, eliminating the need for time-consuming post-disaster assessment and planning.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system creates a generalized descriptive language representation (a copy) of the original network infrastructure's data and ecology information. This abstract model can be quickly instantiated to rebuild the network, avoiding the need to manually recreate each component from scratch.

Inventive Principle:

Principle #26Copying

2Extent of automation

If proprietary software is used for network reconstruction, then the recovery process can be automated, but the cost increases significantly

Engineering Contradiction:

Improverecovery automationVSAvoidrecovery cost

Core Design Contradiction:

Extent of automationVSLoss of energy

Solution Approach 1:

The system uses vendor-agnostic generalized descriptive language that can work with multiple network equipment vendors' interfaces. This universal approach eliminates the need for expensive proprietary recovery software for each vendor, allowing a single system to automate recovery across heterogeneous networks using standard protocols and open interfaces.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system introduces a generalized descriptive language as an intermediary layer between the recovery system and vendor-specific network interfaces. This mediator enables automation without requiring vendor-specific proprietary software, reducing costs while maintaining automated capabilities.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Manufacturing precision

If complex network infrastructure is reconstructed manually, then accuracy can be maintained, but the process becomes difficult and time-consuming

Engineering Contradiction:

Improvenetwork reconstruction accuracyVSAvoidnetwork infrastructure complexity

Core Design Contradiction:

Manufacturing precisionVSDevice complexity

Solution Approach 1:

The system captures the complete data and ecology information of the original network infrastructure and stores it as a generalized descriptive language model. This accurate copy preserves all network relationships, configurations, and ecological dependencies, enabling precise reconstruction without manual intervention despite the complexity of the original system.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system replaces manual mechanical reconstruction processes with automated computational methods. By using algorithms to process the generalized descriptive language and automatically provision network components, the system maintains high accuracy while handling complex network infrastructures that would be impractical to reconstruct manually.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

4Adaptability or versatility

If vendor-specific interfaces are used for network recovery, then compatibility with specific equipment is improved, but interoperability across multiple vendors deteriorates

Engineering Contradiction:

Improvevendor equipment compatibilityVSAvoidmulti-vendor interoperability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system employs a vendor-agnostic generalized descriptive language that can interface with multiple vendor-specific equipment through standardized protocols. This universal language layer maintains compatibility with various vendors while ensuring reliable interoperability across heterogeneous networks, eliminating the trade-off between specificity and versatility.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10129373B2Recovery of a network infrastructure to facilitate business continuity

Publication Date: 2018.11.13 KYNDRYL INC

AI summary

Methods and systems for disaster recovery of a network infrastructure to facilitate business continuity. A method including capturing, by at least one computer device, data and ecology information about an entire existing network infrastructure. The method further including generating, by the at least one computer device, a generalized descriptive language for the captured data and ecology information. The method further including reconstructing, by the at least one computer device, the entire existing network infrastructure by introducing functionally equivalent components that correspond to the generalized descriptive language.