File Replication via Version Difference Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies face challenges in efficiently and securely replicating files across multiple locations, particularly in software development and deployment, due to issues with network bandwidth, latency, and maintaining data consistency.

Innovation Solution

A system and method for replicating files that involves identifying replication information for both the source and target devices, calculating differences between file versions, and transmitting only the necessary update data, allowing the target device to assemble and verify the replicated file.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If files are replicated across multiple locations to maintain data availability and support distributed development teams, then data accessibility and collaboration efficiency are improved, but network bandwidth consumption and data transfer time increase

Engineering Contradiction:
Improvedevelopment productivityVSAvoidnetwork bandwidth usage
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent extracts and transmits only the specific portions of files that differ between source and target locations, rather than replicating entire files. This is achieved by comparing file versions, identifying differences, and selectively transferring only the necessary update data, thereby reducing network bandwidth consumption while maintaining data synchronization.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments files into different versions and identifies specific portions that need to be replicated. By dividing the file replication process into version comparison, difference identification, and selective transmission stages, the system efficiently manages data transfer and reduces unnecessary network traffic.

Inventive Principle:
Principle #1Segmentation

2Reliability

If complete file versions are transmitted to ensure data consistency across locations, then data reliability is improved, but data transfer time and network resource consumption increase

Engineering Contradiction:
Improvedata consistencyVSAvoidsynchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the essential update data that represents differences between file versions, rather than transmitting complete files. This extraction process maintains data consistency by ensuring that target locations receive exactly the changes needed to match the source version, while significantly reducing transfer time.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary file version comparison and difference identification before initiating data transmission. This preliminary action allows the system to pre-calculate which portions of files need to be replicated, ensuring data consistency is maintained while minimizing actual transfer time by avoiding transmission of redundant data.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If file replication is performed frequently to maintain up-to-date data across distributed teams, then data freshness is improved, but network bandwidth consumption and system resources increase

Engineering Contradiction:
Improvedata availabilityVSAvoidnetwork resource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts and transmits only the minimal necessary update data required to maintain data freshness across distributed locations. By identifying and transferring only the specific portions that have changed, the system enables frequent synchronization without proportionally increasing network resource consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by transmitting only the portion of data that is necessary for synchronization rather than complete files. This approach allows frequent replication operations to maintain data availability while consuming fewer network resources compared to transmitting entire files each time.

Inventive Principle:
Principle #16Partial or excessive action

4Reliability

If physical media is used to deploy software updates to multiple locations, then data security and control are improved, but deployment time and human resource requirements increase

Engineering Contradiction:
Improvedeployment securityVSAvoiddeployment efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent replaces the mechanical process of physical media connection and manual file transfer with an automated electronic data transmission system. This substitution enables deployment updates to be transmitted digitally across networks, eliminating the need for physical media handling and manual operations while maintaining security through controlled digital transmission protocols.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12288060B2Data file partition and replication
Publication Date: 2025.04.29 JFROG LTD
  • US12288060B2 patent drawing
  • US12288060B2 patent drawing
  • US12288060B2 patent drawing

AI summary

The present disclosure provides a method, system, and device for file replication. To illustrate, based on target replication information corresponding to a version of a file at a target device, a source device may determine one or more portions of a different version of the file at the source device to be provided to the target device. One or more other aspects of the present disclosure further provide sending, to the target device, the one or more portions and replication information corresponding to the version of the file at the source device. Based on the version of the file at the target device, the one or more portions, and the replication information corresponding to the version of the file at the source device, the target device may assemble and store a file that corresponds to the version of the file at the source device.