Network Backup Reconfiguration for EMP Resilience

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computer networks are vulnerable to disruption events such as earthquakes and electromagnetic pulses (EMPs), which can cause significant damage to hardware and data loss, and existing technologies lack effective methods to proactively protect and reconfigure networks against such events.

Innovation Solution

A combined hardware and software system that includes a hardened battery backup with a Faraday cage and a main control system (MCS) for continuous local and remote data node backups, prioritizing remote backups based on capability, geographic location, and third-party system availability, allowing for swift reconfiguration and data redundancy during disruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If continuous local and remote backups are maintained, then data loss is minimized during disruptions, but system complexity and resource consumption increase

Engineering Contradiction:
Improvedata loss preventionVSAvoidbackup system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The backup system is segmented into multiple independent remote backup locations rather than relying on a single centralized backup system. Each remote backup location stores copies of data nodes, and the system can select from multiple candidates during disruption. This segmentation distributes the complexity across independent components while improving reliability through redundancy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by continuously maintaining updated remote backups before disruptions occur. The ordered list of remote backups is pre-established and continuously updated, so when a disruption occurs, the system can immediately promote a capable remote backup to primary status without needing to create backups during the crisis.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If remote backups are prioritized based on capability and location, then network resilience is improved during disruptions, but the complexity of backup management increases

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

Solution Approach 1:

The system implements self-service through automated evaluation and selection of remote backups. The MCS automatically assesses the capability of each remote backup location, maintains an ordered list based on this evaluation, and autonomously promotes the most capable backup to primary status during disruption. This automation reduces manual management complexity while improving network resilience through intelligent selection.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses feedback mechanisms to continuously evaluate remote backup capability and update the ordered list accordingly. The MCS monitors the status and capability of remote backups, and this feedback information drives the selection process during disruption events, ensuring that the most capable backup is always chosen without requiring complex manual assessment.

Inventive Principle:
Principle #23Feedback

3Object-affected harmful factors

If critical systems are shut down during disruption warning, then protection against EMP damage is improved, but operational capability is reduced

Engineering Contradiction:
ImproveEMP damage protectionVSAvoidoperational capability
Core Design Contradiction:
Object-affected harmful factorsVSProductivity

Solution Approach 1:

The system applies preliminary anti-action by proactively shutting down critical systems before the disruption event occurs. When a disruption warning is received, the MCS identifies systems that cannot withstand the disruption and shuts them down in advance, preventing EMP damage before it can occur. This preemptive action protects hardware while the system maintains operational capability through remote backups.

Inventive Principle:
Principle #9Preliminary anti-action

Solution Approach 2:

The system uses copying to maintain operational capability during shutdown. By having pre-established remote backups that contain copies of data nodes, the system can promote a remote backup to primary status and continue operations even while critical systems are shut down for protection. The copy serves as a substitute that maintains productivity during the protective shutdown.

Inventive Principle:
Principle #26Copying

Applied Scientific Principles

This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.

Function Achieved in This Case

The system effectively protects and reconfigures computer networks by promoting a capable remote backup as the primary data node, minimizing data loss and ensuring network resilience during disruptions, while also shutting down non-essential systems to conserve resources.

Implementation Method 1

a hardened battery backup with a Faraday cage

Methodology Applied
Scientific EffectFaraday cage: Faraday Cage

Data Source

PatentUS10031821B2Distributed network electronic interference abatement system and method
Publication Date: 2018.07.24 NELSON JAMES
  • US10031821B2 patent drawing
  • US10031821B2 patent drawing
  • US10031821B2 patent drawing

AI summary

A system to protect and reconfigure a computer network in case of advance warning of a disruption event that would disrupt the operation of the computer network is presented. The system comprises a main control system (MCS) that comprises a software system that makes continuous local backups of data nodes, maintains a plurality of remote backups, and maintains an ordered list of the remote backups. With the first warning of the disruption event, the MCS: 1) locks down some virtual servers at each remote backup and secures a selected remote backup; 2) determines the expected start and end time of the disruption event; 3) warns users about the disruption event; 4) uses the selected remote backup to provide a local copy of the data nodes; and 5) shuts down vulnerable critical systems. When the disruption event occurs, the MCS promotes the selected remote backup to be the primary data node.