# US 2020/0349126 A1 · Data file partition and replication

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0349126 A1
- Document ID: US20200349126A1
- Status: Published application
- Kind: A1
- Application number: 16/399,938
- Filed: 2019-04-30
- Published: 2020-11-05
- Earliest claimed: 2019-04-30
- Assignees: JFrog Ltd.
- Applicants: JFrog. Ltd.
- Inventors: Yoav LANDMAN
- Web page: https://patentgrep.com/patent/US20200349126A1

## CPC

- G06F 16/1844: {Management specifically adapted to replicated file systems}
- G06F 16/1873: {Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files}
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

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.

## Claims

### Claim 1

A method for replicating one or more files across a multi-node network, the method comprising:
identifying first replication information comprising a first plurality of checksums corresponding to a first version of a file utilized by a first node in the multi-node network;
identifying second replication information comprising a second plurality of checksums corresponding to a second version of the file utilized by a second node in the multi-node network;
calculating a difference between the first version of the file and the second version of the file;
based on the calculated difference, identifying update data that is included in the first version of the file and not included in the second version of the file; and
transmitting, to the second node, the update data.

### Claim 2 (depends on 1)

The method of claim 1, where:
the first version of the file utilized by the first node comprises a file name and a first version identifier; and
the second version of the file utilized by the second node comprises the file name and a second version identifier.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
determining the first version of the file utilized by the first node corresponds to a source node; and
determining the second version of the file utilized by the second node corresponds to a target node.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
receiving, at the first node, an acknowledgment from the second node that the update data was received.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
receiving, at the first node, a notification from the second node that at least a portion of the update data was not received; and
responsive to the notification, transmitting the portion of the update data to the second node.

### Claim 6 (depends on 1)

The method of claim 1, where the first version of the file includes a plurality of parts, each of the plurality of parts including a set of data blocks.

### Claim 7 (depends on 6)

The method of claim 6, where:
the update data comprises multiple parts of the plurality of parts; and
each part of the multiple parts is individually sent to the second node.

### Claim 8 (depends on 6)

The method of claim 6, where:
the update data comprises multiple parts of the plurality of parts; and
the multiple parts are sent together to the second node.

### Claim 9 (depends on 6)

The method of claim 6, where at least one part of the plurality of parts includes a header.

### Claim 10 (depends on 6)

The method of claim 6, where the first replication information includes, for each part, a checksum and a size indicator.

### Claim 11 (depends on 10)

The method of claim 10, where the first replication information includes a first checksum for an entirety of the first version of the file.

### Claim 12 (depends on 10)

The method of claim 10, where the size indicator for a particular part includes a start location of the particular part within the first version of the file and an end location of the particular part within the first version of the file.

### Claim 13 (depends on 1)

The method of claim 1, where calculating the difference comprises identifying one or more checksums of the first replication information not included in the second plurality of checksums included in the second replication information.

### Claim 14 (depends on 13)

The method of claim 13, further comprising:
for each of the one or more checksums:
identifying a corresponding size indicator of the file for the checksum; and
retrieving a portion of the first version of the file based on the identified corresponding size.

### Claim 15 (depends on 13)

The method of claim 13, further comprising:
identifying additional replication information corresponding to the second node, the additional replication information accessible to the first node.

### Claim 16 (depends on 15)

The method of claim 15, further comprising:
comparing the one or more checksums to a plurality of checksums included in the additional replication information.

### Claim 17 (depends on 1)

The method of claim 1, where determining the second version of the file comprises:
sending, to the second node, a request to the second node for a version identifier of the second version of the file at the second node, the request including a file name of the file;
receiving, from the second node, a response including the version identifier; and
identifying the second version based on the version identifier.

### Claim 18 (depends on 1)

The method of claim 1, where determining the second version of the file comprises accessing a version log maintained by the first node to identify the second version of the file stored at a memory of the first node.

### Claim 19 (depends on 1)

The method of claim 1, where the first node and the second node use a shared naming convention.

### Claim 20

A system for replicating one or more files at a target node, the system comprising:
at least one memory storing instructions; and
one or more processors coupled to the at least one memory, the one or more processors configured to execute the instructions to cause the processor to:
identify first replication information comprising a first plurality of checksums corresponding to a first version of a file utilized by a source node;
identify second replication information comprising a second plurality of checksums corresponding to a second version of the file utilized by a target node;
calculate a difference between the first version of the file and the second version of the file;
based on the calculated difference, identify update data that is included in the first version of the file and not included in the second version of the file; and
transmit, to the target node, the update data.

### Claim 21 (depends on 20)

The system of claim 20, where the one or more processors are further configured to execute the instructions to cause the one or more processors to:
receive an upload of the first version of the file at the source node; and
responsive to the upload of the first version of the file, generate the update data.

### Claim 22 (depends on 21)

The system of claim 21, where the one or more processors are further configured to execute the instructions to cause the one or more processors to:
receive, at the source node, a request to replicate the first version of the file at the target node;
determine a size of the first version of the file;
perform a comparison between the size and a threshold;
if the size of the file is greater than or equal to the threshold, determine the second version of the file utilized by the target node; and
if the size of the file is less than the threshold, send an entirety of the first version of the file to the target node.

### Claim 23 (depends on 21)

The system of claim 21, where the one or more processors are further configured to execute the instructions to cause the one or more processors to:
receive, at the source node, a request to replicate the first version of the file at the target node;
determine a file type of the first version of the file;
determine whether the file type is one of a plurality of supported file types;
if the file type is included in the plurality of supported file types, determine the second version of the file utilized by the target node; and
if the file type is not included in the plurality of supported file types, send the first version of the file to the target node.

### Claim 24 (depends on 23)

The system of claim 23, where, to send the first version of the file to the target node, the one or more processors are further configured to execute the instructions to cause the one or more processors to:
determine a size of the first version of the file;
perform a comparison between the size and a threshold;
if the size of the first version of the file is less than or equal to the threshold, send an entirety of the first version of the file to the target node; and
if the size of the first version of the file is greater than the threshold:
divide the first version of the file into multiple portions; and
send each portion of the multiple portions to the target node.

### Claim 25 (depends on 24)

The system of claim 24, where at least two portions of the multiple portions are sent concurrently to the target node.

### Claim 26

A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations for replicating one or more files at a target node, the operations comprising:
executing a first routine to identify first replication information comprising a first plurality of checksums corresponding to a first version of a file utilized by a first node;
executing a second routine to identify second replication information comprising a second plurality of checksums corresponding to a second version of the file utilized by a second node;
executing a third routine to calculate a difference between the first version of the file and the second version of the file;
executing a fourth routine to, based on the calculated difference, identify update data that is included in the first version of the file and not included in the second version of the file; and
executing a fifth routine to transmit, to the second node, the update data.

### Claim 27 (depends on 26)

The non-transitory computer-readable storage medium of claim 26, where executing the fifth routine to send the update data as one or more portions comprises sending a first portion of the update data and sending a second portion of the update data.

### Claim 28 (depends on 27)

The non-transitory computer-readable storage medium of claim 27, where the first portion of the update data and the second portion of the update data are sent in parallel.

### Claim 29 (depends on 26)

The non-transitory computer-readable storage medium of claim 26, where the first version of the file comprises a zip file.

### Claim 30 (depends on 26)

The non-transitory computer-readable storage medium of claim 26, where the operations further comprise:
send, to the second node, a request for identification of a particular version of the file utilized by the second node.

### Claim 31 (depends on 26)

The non-transitory computer-readable storage medium of claim 26, where the operations further comprise:
send, to the second node, a request for particular replication information corresponding to the file utilized by the second node; and
responsive to the request, receiving the second replication information.
