# US 2012/0254104 A1 · Maintaining client data integrity in a distributed environment using asynchronous data submission

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

- Number: US 2012/0254104 A1
- Document ID: US20120254104A1
- Status: Published application
- Kind: A1
- Application number: 13/494,650
- Filed: 2012-06-12
- Published: 2012-10-04
- Earliest claimed: 2008-11-17
- Assignees: Microsoft Corporation
- Inventors: Jin Wang; Luming Wang; Malik Hussain; Zaiwei Du; Zhenyu Tang; Patrick J. Baumgartner; Mark Xiaohong Yang; Peter Eberhardy
- Web page: https://patentgrep.com/patent/US20120254104A1

## CPC

- G06F 16/273: {Asynchronous replication or reconciliation}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Data processing architecture where submitters can write data and/or metadata changes to a destination through an asynchronous interface. The architecture includes a ticketing system that issues a ticket (a unique identifier) to the submitter in response to receiving a changelist from the submitter. When the changes are successfully completed at the destination, the cached destination data can be re-downloaded to the submitter, and the changes cached in the submitter, discarded. Absent this capability, a user has to manually manage the cached changes and cached data. The architecture can be distributed in that multiple submitters can submit changelists. The destination provides data integrity by managing submissions to assist in ensuring data integrity across multiple submissions. Automatic changelist cleanup is provided on the submitter so that changelists do not impact performance, memory, and storage.

## Claims

### Claim 1

A computer-implemented data processing system, comprising: a data update component of a destination for receiving a copy of an original changelist of data changes from a submitter and updating the changes to destination data of the destination to create updated destination data; a ticket component of the destination for generating a destination ticket related to the copy, and sending the destination ticket to the submitter; and a data component of the submitter for managing the original changelist based on status of the data update at the destination.

### Claim 2 (depends on 1)

The system of claim 1, wherein the submitter locks the original changelist from storing further data changes based on receipt of the destination ticket.

### Claim 3 (depends on 2)

The system of claim 2, wherein the submitter creates a new changelist that accumulates new changes after the original changelist is locked.

### Claim 4 (depends on 3)

The system of claim 3, wherein the submitter creates and assigns a submitter ticket to the new changelist.

### Claim 5 (depends on 3)

The system of claim 3, wherein the data component merges the locked original changelist with the new changelist when the status of the data update at the destination is failed.

### Claim 6 (depends on 2)

The system of claim 2, wherein the data component unlocks the locked original changelist when a new changelist does not exist and the status of the data update at the destination is failed, and the original changelist accumulates the new changes.

### Claim 7 (depends on 1)

The system of claim 1, wherein the submitter downloads the updated destination data and discards the original changelist when the status of the data update at the destination is successful.

### Claim 8 (depends on 1)

The system of claim 1, wherein the submitter is a client, the destination is a server, and the original changelist includes data and metadata.

### Claim 9 (depends on 1)

The system of claim 1, wherein the submitter is a peer to the destination and, the original changelist includes data and metadata.

### Claim 10 (depends on 1)

The system of claim 1, wherein the data update component asynchronously receives and processes copies of original changelists received from multiple submitters.

### Claim 11

A computer-implemented data processing system, comprising: a data update component of a server for receiving a copy of an original changelist of data changes from a client and updating the changes to server data to create updated server data; a ticket component of the server for generating and assigning a server ticket to the copy, and sending the server ticket to the client; and a data component of the client for managing the original changelist based on status of data update at the server.

### Claim 12 (depends on 11)

The system of claim 11, wherein the client locks the original changelist from storing further data changes based on receipt of the server ticket, creates a new changelist that accumulates new changes after the original changelist is locked, and assigns a client ticket to the new changelist.

### Claim 13 (depends on 12)

The system of claim 12, wherein the data component merges the locked original changelist with the new changelist when the status of the data update at the server is failed.

### Claim 14 (depends on 11)

The system of claim 11, wherein the data component locks the original changelist from storing further data changes based on receipt of the server ticket, unlocks the locked original changelist when a new changelist does not exist and the status of the data update at the server is failed, and the original changelist becomes the new changelist that accumulates the new changes.

### Claim 15 (depends on 11)

The system of claim 11, wherein the client downloads the updated server data, discards the original changelist when the status of the data update at the server is successful, and sends a notification that the changelist was successfully submitted.

### Claim 16

A computer-implemented method of processing data, comprising: receiving a copy of an original changelist of data changes from a submitter; updating destination data of a destination with the changes to create updated destination data; generating and assigning a destination ticket to the copy; sending the destination ticket to the submitter; and managing the original changelist at the submitter based on status of the data update at the destination.

### Claim 17 (depends on 16)

The method of claim 16, further comprising: locking the original changelist from storing further data changes based on the destination ticket; creating a new changelist that accumulates new changes after the original changelist is locked; and assigning a submitter ticket to the new changelist.

### Claim 18 (depends on 16)

The method of claim 16, further comprising merging the locked original changelist with the new changelist when the status of the data update at the destination is failed.

### Claim 19 (depends on 16)

The method of claim 16, further comprising: locking the original changelist from storing further data changes based on receipt of the server ticket; unlocking the locked original changelist when a new changelist does not exist and the status of the data update at the destination is failed; and making the original changelist the new changelist to accumulate the new changes.

### Claim 20 (depends on 16)

The method of claim 16, further comprising: downloading the updated destination data; and, discarding the original changelist when the status of the data update is successful.
