# US 2024/0179212 A1 · Hosted file sync with stateless sync nodes

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

- Number: US 2024/0179212 A1
- Document ID: US20240179212A1
- Status: Published application
- Kind: A1
- Application number: 18/430,943
- Filed: 2024-02-02
- Published: 2024-05-30
- Earliest claimed: 2015-09-14
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Michael MURSTEIN; Cristian TEODORESCU; Jason SHAY; James BENTON; Ivelin ZHEGLOV
- Web page: https://patentgrep.com/patent/US20240179212A1

## CPC

- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- G06F 16/178: Techniques for file synchronisation in file systems
- G06F 16/183: {Provision of network file services by network file servers, e.g. by using NFS, CIFS (network file access protocols H04L67/1097)}
- G06F 16/1873: {Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files}
- G06F 16/235: {Update request formulation}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06F 16/252: {between a Database Management System and a front-end application}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/278: {Data partitioning, e.g. horizontal or vertical partitioning}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Disclosed herein is a system and method to synchronize files from a hosted file system where the client endpoint devices have direct access to the files stored on a hosted file store. When the client desires to synchronize with the files stored on the hosted file store the process identifies a sync role that can process the request. The particular sync role does not need to maintain state with the client device or the file store. The state necessary for the processing of the synchronization process is maintained separate from the sync role such that any sync role in the system can pick up the requests and process the requests. Once the role has been selected the synchronization process proceeds as normal. As state is not maintained by the sync role multiple roles can process the request or two roles can handle different portions of the process.

## Claims

### Claim 1

A method comprising:
receiving, from a client device, a sync request for synchronizing data between the client device and a remote file store;
transmitting a synchronization state of the data between the client device and the remote file store from a runtime state store to a stateless sync node that is stateless with respect to the data synchronization between the client device and the remote file store;
synchronizing, via the stateless sync node, the data based on the synchronization state which results in changes to the data stored by at least one of the client device and the remote file store; and
committing the synchronized data.

### Claim 2 (depends on 1)

The method of claim 1, wherein the synchronization state comprises a synchronization history of the data between the client and the remote file store performed by at least one different stateless sync node.

### Claim 3 (depends on 1)

The method of claim 1, further comprising selecting the stateless sync node from among a plurality of stateless sync nodes based on a current sync load among the plurality of stateless sync nodes.

### Claim 4 (depends on 1)

The method of claim 1, further comprising selecting the stateless sync node from among a plurality of stateless sync nodes based on an expected duration of a sync task identified by the sync request.

### Claim 5 (depends on 1)

The method of claim 1, further comprising selecting the stateless sync node from among a plurality of stateless sync nodes based on a round-robin approach.

### Claim 6 (depends on 5)

The method of claim 5, wherein the selecting comprises selecting a different stateless sync node than a most recently selected stateless sync node from among the plurality of stateless sync nodes.

### Claim 7 (depends on 1)

The method of claim 1, further comprising dividing a sync task associated with the sync request into a plurality shards, and distributing the plurality of shards to a plurality of stateless sync nodes, respectively.

### Claim 8 (depends on 1)

The method of claim 1, wherein the synchronizing comprises resuming synchronizing of the data between the client device and the remote file store based on a point at which a different stateless sync node finished synchronizing the data between the client device and the remote file store.

### Claim 9

A computing system comprising:
a network interface configured to receive, from a client device, a sync request for synchronizing data between the client device and a remote file store; and
a processor configured to
transmit a synchronization state of the data between the client device and the remote file store from a runtime state store to a stateless sync node that is stateless with respect to the data synchronization between the client device and the remote file store,
control the stateless sync node to synchronize the data based on the synchronization state which results in changes to the data stored by at least one of the client device and the remote file store, and
commit the synchronized data.

### Claim 10 (depends on 9)

The computing system of claim 9, wherein the synchronization state comprises a synchronization history of the data between the client and the remote file store performed by at least one different stateless sync node.

### Claim 11 (depends on 9)

The computing system of claim 9, wherein the processor is further configured to select the stateless sync node from among a plurality of stateless sync nodes based on a current sync load among the plurality of stateless sync nodes.

### Claim 12 (depends on 9)

The computing system of claim 9, wherein the processor is further configured to select the stateless sync node from among a plurality of stateless sync nodes based on an expected duration of a sync task identified by the sync request.

### Claim 13 (depends on 9)

The computing system of claim 9, wherein the processor is further configured to select the stateless sync node from among a plurality of stateless sync nodes based on a round-robin approach.

### Claim 14 (depends on 13)

The computing system of claim 13, wherein the processor selects a different stateless sync node than a most recently selected stateless sync node from among the plurality of stateless sync nodes.

### Claim 15 (depends on 9)

The computing system of claim 9, wherein the processor is further configured to divide a sync task associated with the sync request into a plurality shards, and distribute the plurality of shards to a plurality of stateless sync nodes, respectively.

### Claim 16 (depends on 9)

The computing system of claim 9, wherein the processor is configured to control the stateless sync node to resume synchronizing of the data between the client device and the remote file store based on a point at which a different stateless sync node finished synchronizing the data between the client device and the remote file store.

### Claim 17

A non-transitory computer-readable medium comprising instructions which when executed by a processor cause a computer to perform a method comprising:
receiving, from a client device, a sync request for synchronizing data between the client device and a remote file store;
transmitting a synchronization state of the data between the client device and the remote file store from a runtime state store to a stateless sync node that is stateless with respect to the data synchronization between the client device and the remote file store;
synchronizing, via the stateless sync node, the data based on the synchronization state which results in changes to the data stored by at least one of the client device and the remote file store; and
committing the synchronized data.

### Claim 18 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein the method further comprises selecting the stateless sync node from among a plurality of stateless sync nodes based on a current sync load among the plurality of stateless sync nodes.

### Claim 19 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein the method further comprises selecting the stateless sync node from among a plurality of stateless sync nodes based on an expected duration of a sync task identified by the sync request.

### Claim 20 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein the method further comprises selecting the stateless sync node from among a plurality of stateless sync nodes based on a round-robin approach in which a different stateless sync node than a most recently selected stateless sync node is selected from among the plurality of stateless sync nodes.
