Paired Computing Device Offloading in Degrading-Device Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Migrating data from a degrading computing device to a new, healthy computing device is a complex task that requires significant computing resources and can result in data loss or corruption if the degrading device fails before the migration is complete.

Innovation Solution

An engine pairs an intermediate computing device with another computing device to perform a paired migration, reducing the computational burden on the degrading device and maintaining data availability during the process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data migration is performed directly from a degrading computing device to a target device, then the migration process can be completed, but the degrading device may fail during migration causing data loss or corruption

Engineering Contradiction:
Improvedata migration reliabilityVSAvoidmigration system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a paired computing device as an intermediary between the degrading source device and the target device. This paired device receives data from the source device and forwards it to the target device, acting as a mediator that protects against data loss if the source device fails during migration.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The migration process is segmented into multiple paths: one path handles data migration through the paired device, while another path allows the source device to continue serving data requests. This segmentation distributes the migration workload and reduces the burden on the degrading source device.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If the degrading computing device continues to serve data requests during migration, then data availability is maintained, but the device may fail due to excessive computational burden

Engineering Contradiction:
Improvedata availabilityVSAvoiddevice operational reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the data serving function from the migration function by introducing a paired device. The source device continues to serve data requests while the paired device handles migration tasks, allowing both operations to proceed simultaneously without interfering with each other's reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a paired computing device that copies the essential data transfer functionality from the source device. This paired device can handle migration operations independently, allowing the source device to maintain its data serving role without the additional burden of migration processing.

Inventive Principle:
Principle #26Copying

3Productivity

If computational resources are allocated for migration from a degrading device, then migration can proceed, but the device may fail before migration completion

Engineering Contradiction:
Improvemigration throughputVSAvoidmigration completion reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The paired computing device serves as an intermediary that performs the actual data transfer operations during migration. By offloading these computational resources from the degrading source device to the paired device, the system maintains high migration throughput while protecting against failures of the source device during the process.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12386716B2Method and system for pairing computing devices for offloading actions during data migration from degrading computing devices
Publication Date: 2025.08.12 DELL PROD LP
  • US12386716B2 patent drawing
  • US12386716B2 patent drawing
  • US12386716B2 patent drawing

AI summary

A method for performing data migration for devices includes identifying, by a device migration delegator of a device, a migration delegation event associated with the device; in response to identifying the migration delegation event: selecting at least one delegation action based on the migration delegation event; requesting a duplicator to allocate another device for pairing; obtaining a paired device from the duplicator; obtaining a token from the paired device; authenticating the paired device using the token; authorizing the paired device to perform the at least one delegation action using the token; performing at least one non-delegation action of migration by the device; and initiating, by the device, the performance of the at least one delegation action by the paired device.