Shared-Memory Backup for Heterogeneous Device Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current industrial automation systems lack a method for proactive backup and restoration of data across heterogeneous devices, which are limited by different communication interfaces and lack data encryption protection, leading to ineffective management and security.

Innovation Solution

A distributed data backup, restore, and synchronization method that utilizes a shared memory system among multiple devices, enabling flexible backup and restoration plans with encryption, allowing devices with the same group identifier to access each other's memories for data sharing and synchronization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If centralized backup and restoration through specific equipment is used, then data exchange between specific device types is enabled, but the system is limited to specific devices and lacks support for heterogeneous devices

Engineering Contradiction:
Improvedevice compatibilityVSAvoidcommunication interface requirements
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal backup and restoration system that can work across heterogeneous devices by defining a standardized communication protocol. The system uses a unified data packet structure with standardized fields (header, data block, checksum) that can be applied to any device type, eliminating the need for device-specific communication interfaces while maintaining broad compatibility

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system changes the communication approach from device-specific interfaces to a parameter-based standardized protocol. By defining universal parameters for data packets (header with operation type and group identifier, data block, checksum), the system adapts to different device types without requiring complex interface adaptations

Inventive Principle:
Principle #35Parameter changes

2Extent of automation

If manual backup and restoration processes are used, then data exchange between devices is possible, but proactive backup and restoration are not supported

Engineering Contradiction:
Improvebackup automationVSAvoidbackup response time
Core Design Contradiction:
Extent of automationVSLoss of time

Solution Approach 1:

The system implements proactive backup by automatically triggering backup operations when predefined conditions are met, such as when a device's memory reaches a certain utilization threshold or when specific events occur. The controller monitors device states continuously and initiates backup actions before data loss risks materialize, eliminating the need for manual intervention

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system establishes feedback mechanisms where the controller continuously monitors device memory states and automatically triggers backup operations based on real-time conditions. The system receives feedback from devices about their memory utilization and operational status, and automatically adjusts backup timing and targets accordingly

Inventive Principle:
Principle #23Feedback

3Reliability

If backup data is stored without encryption, then data access and restoration are simple and fast, but information security protection is lacking

Engineering Contradiction:
Improveinformation securityVSAvoidencryption mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary encryption layer managed by the controller that sits between the data storage and access points. The controller handles encryption and decryption operations automatically, so that data is encrypted at rest in device memories and during transmission, while users experience no additional complexity in the backup and restoration process

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If backup operations are performed on a single device, then the backup process is simple, but backup failure risks are higher and computational resources are concentrated

Engineering Contradiction:
Improvebackup success rateVSAvoiddistributed system structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the backup process across multiple target devices instead of relying on a single backup destination. Data can be divided into blocks and distributed across multiple devices' memories, or multiple copies can be stored on different devices. This segmentation reduces the risk of total backup failure and distributes computational loads

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system combines multiple target devices into a distributed backup network where each device contributes its storage capacity and processing power. The controller coordinates these combined resources to perform backup operations, achieving higher reliability through redundancy while distributing the computational burden across the network

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12436846B2Distributed data backup, restore and synchronization method for multiple devices
Publication Date: 2025.10.07 DELTA ELECTRONICS INC(CN)
  • US12436846B2 patent drawing
  • US12436846B2 patent drawing
  • US12436846B2 patent drawing

AI summary

Data backup, restore, and synchronization methods for multiple devices are provided. The data backup method applied for a local device of the multiple devices includes 1) sending a querying packet including a group identifier to at least one of the multiple devices to search for at least one backup provider; 2) receiving at least one response packet including the group identifier to make a backup plan; 3) preparing a data block and setting at a shared memory of at least one backup service provider based on the backup plan to generate a data packet including the group identifier and the data block; and 4) sending the data packet to the at least one backup service provider to back up the data block to the shared memory.