Edge Device Bootstrapping Package for Automated Disaster Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The manual configuration of replacement edge devices is cumbersome, prone to errors, and time-consuming, especially when the new device has different hardware or software than the device being replaced, and often requires transmitting large configuration data across limited or disconnected networks.

Innovation Solution

The system generates a bootstrapping package based on the current device configuration of the first edge device, segmenting the device state and workload configuration into namespaces, which is then automatically installed on a second edge device, allowing for seamless configuration without manual intervention and accommodating differences in hardware or software.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual configuration is used for replacement edge devices, then configuration can be performed with basic tools, but the process is cumbersome, error-prone, and time-consuming

Engineering Contradiction:
Improveconfiguration processVSAvoidconfiguration time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent creates a virtual copy of the failed edge device's configuration state and workload information, packaging it into a bootstrapping package that can be automatically deployed to the replacement device. This copying approach eliminates manual configuration by transferring the complete operational state as a template.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary actions by capturing the device state and workload configuration before the device fails, and pre-processes this information into a ready-to-install bootstrapping package. This preliminary preparation ensures that when replacement is needed, the configuration is already prepared and can be applied immediately without manual intervention.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual configuration is used for replacement edge devices, then simplicity is maintained, but errors are prone and reliability is reduced

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidconfiguration process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The replacement edge device performs self-configuration by automatically receiving and installing the bootstrapping package containing the failed device's configuration state and workload information. The system enables the device to configure itself without human intervention, eliminating manual errors while managing complexity through automation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

By creating an accurate virtual copy of the device state, workload configurations, and other critical information, the system ensures reliable replication of the failed device's operational state. This copying mechanism guarantees configuration accuracy while the automated process manages the complexity of transferring comprehensive device information.

Inventive Principle:
Principle #26Copying

3Reliability

If complete configuration data is transmitted for replacement devices, then configuration accuracy is maintained, but network bandwidth consumption increases and disconnected networks cannot be used

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidnetwork bandwidth
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments the complete device configuration into distinct components: device state information, workload configuration data, and other metadata. This segmentation allows the system to package and transmit only the essential configuration elements needed for replacement, reducing network bandwidth requirements while maintaining configuration accuracy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system creates an optimized virtual copy of the configuration data, capturing only the critical state information and workload configurations necessary for functional replication. This selective copying approach ensures configuration accuracy while minimizing the data volume transmitted over the network, enabling operation even in disconnected or low-bandwidth environments.

Inventive Principle:
Principle #26Copying

4Productivity

If automated configuration is implemented, then configuration time is reduced and productivity increases, but system complexity increases

Engineering Contradiction:
Improveconfiguration speedVSAvoidconfiguration system
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The automated configuration system uses virtual copying to capture the complete operational state of the failed device and replicate it on the replacement device. This copying mechanism enables rapid configuration deployment, significantly improving productivity while the systematic approach to packaging and installing configuration data manages the added system complexity.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary capture and processing of device state and workload information before the actual replacement occurs. By pre-packaging the configuration data into a bootstrapping package, the system prepares everything needed for rapid deployment, improving configuration speed while the preliminary processing steps manage the complexity of handling comprehensive device information.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12222825B2Systems and methods for disaster recovery for edge devices
Publication Date: 2025.02.11 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12222825B2 patent drawing
  • US12222825B2 patent drawing
  • US12222825B2 patent drawing

AI summary

Examples of the present disclosure describe improved systems and methods for disaster recovery for edge devices. In one example implementation, a current device configuration for a first device is received. The current device configuration comprises a device state and a workload configuration of the first device. A bootstrapping package for the first device is generated based on the current device configuration for the first device. Generating the bootstrapping package comprises segmenting the device state and the workload configuration into a namespace. The bootstrapping package is provided to a second device. The bootstrapping package is configured to be automatically installed on the second device.