# US 2012/0084341 A1 · Presenting availability statuses of synchronized objects

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

- Number: US 2012/0084341 A1
- Document ID: US20120084341A1
- Status: Published application
- Kind: A1
- Application number: 12/894,679
- Filed: 2010-09-30
- Published: 2012-04-05
- Earliest claimed: 2010-09-30
- Assignees: Microsoft Corporation
- Inventors: Siddharth Mantri; Rachel Karin Popkin
- Web page: https://patentgrep.com/patent/US20120084341A1

## CPC

- G06F 16/2343: {Locking methods, e.g. distributed locking or locking implementation details}
- G06F 16/178: Techniques for file synchronisation in file systems
- G06F 16/2329: {using versioning}
- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04M 3/42178: {by downloading data to substation equipment}
- H04M 1/72406: by software upgrading or downloading
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)

## Abstract

The objects of an on object set may be synchronized across many clients (e.g., various devices may synchronize files of a mirrored filesystem). However, the synchronization of an object may be complicated, and an object may not yet be synchronized in the object set of a client for many reasons, such as an incomplete reception of the object, an unavailability of the object from currently reachable hosts, and a versioning conflict with a different version of the same object in the object set. In order to inform a user of the availability of an object in the object set, an analysis of the availability status of the object may be performed (e.g., by tracking metadata stored in object descriptors of respective objects of the object set, and later examining the metadata of respective objects), and a selected availability status may be presented to the user.

## Claims

### Claim 1

A method of presenting, to a user of a client on a device having a processor and a data store, availability statuses of objects in an object set within a computing environment comprising at least one host, the method comprising:
executing on the processor instructions configured to, upon receiving a request to present to the user an availability status of an object:
upon determining that the object is available in the data store:
upon determining that the object is available in the object set, present to the user an available status; and
upon determining that the object is unavailable in the object set, present to the user a relocating status; and
upon determining that the object is unavailable in the data store:
upon determining that the object is being received from a host, present to the user a receiving status;
upon determining that the object is not being received from a host, present to the user a requesting status.

### Claim 2 (depends on 1)

The method of claim 1, presenting to the user the requesting status comprising:
upon determining that the object is stored on a host represented within the computing environment, present to the user a searching status; and
upon determining that the object is not stored on a host represented within the computing environment, present to the user a lost status.

### Claim 3 (depends on 1)

The method of claim 1, presenting to the user the searching status comprising:
upon determining that hosts storing the object are unreachable, present to the user a host unavailable status; and
upon determining that at least one host storing the object is reachable, present to the user a host connecting status.

### Claim 4 (depends on 1)

The method of claim 1, determining that the object is available in the data store and unavailable in the object set comprising: upon identifying a locking conflict of the object between a first object version that is available in the object set and that is locked against overwriting and a superseding object version that is available in the data store and not in the object set, present to the user a locking conflict status.

### Claim 5 (depends on 1)

The method of claim 1, determining that the object is available in the data store comprising: upon identifying a versioning conflict of the object between a first object version available in the object set and a second object version available in the data store and not in the object set, present to the user a versioning conflict status.

### Claim 6 (depends on 1)

The method of claim 1, respective objects in the object set having an object descriptor comprising at least one object metadatum relating to an availability of the object.

### Claim 7 (depends on 6)

The method of claim 6:
the object set managed by an object server configured to, upon storing an object in the object set, send an object descriptor to the client; and
the instructions configured to, upon receiving from the object server an object descriptor of an object represented in the object set, store the object descriptor in the data store associated with the object.

### Claim 8 (depends on 7)

The method of claim 7:
the object descriptor identifying at least one host that is storing the object;
determining that the object is unavailable in the data store and is not being received from a host comprising: identifying in the object descriptor of the object a requesting metadatum;
determining that the object is unavailable in the data store and is being received from a host comprising: identifying in the object descriptor of the object a receiving metadatum; and
the instructions configured to:
upon receiving from the object server an object descriptor of an object that is unavailable in the data store:
request the object from a host, and
store a requesting metadatum in the object descriptor of the object;
upon receiving at least one object portion of the object from the host, replace the requesting metadatum in the object descriptor of the object with a receiving metadatum.

### Claim 9 (depends on 8)

The method of claim 8:
requesting the object from the host comprising:
upon receiving the object descriptor from the object server, storing in the object descriptor a searching metadatum;
contacting at least one host; and
upon contacting at least one host:
requesting the object from the host; and
replacing the searching metadatum in the object descriptor with a requesting metadatum; and
presenting to the user the requesting status of an object comprising:
upon identifying in the object descriptor of the object a searching metadatum, presenting to the user a searching status of the object.

### Claim 10 (depends on 8)

The method of claim 8:
the instructions configured to, upon receiving from the object server a host removal notification indicating a removal of a host from the object set:
for respective object descriptors of objects that are unavailable in the data store and that are not stored by a host represented in the object set, store in the object descriptor of the object a lost metadatum; and
presenting to the user the requesting status of an object comprising: upon identifying in the object descriptor of the object a lost metadatum, presenting to the user a lost status of the object.

### Claim 11 (depends on 7)

The method of claim 7:
the instructions configured to:
upon receiving an object descriptor of an object from the object server, store in the object descriptor of the object an unverified object metadatum;
upon verifying that the object is unavailable in the data store, replace the unverified object metadatum in the object descriptor of the object an unavailable metadatum; and
upon determining the object is available in the data store, replace the unverified object metadatum in the object descriptor of the object an available metadatum; and
determining that the object is unavailable in the data store comprising:
identifying in the object descriptor of the object an unavailable metadatum.

### Claim 12 (depends on 6)

The method of claim 6, the instructions configured to:
upon receiving an object descriptor of an object, store in the object descriptor of the object a requesting metadatum;
upon receiving an object portion of an object having at least one missing object portion, replace the searching metadatum in the object descriptor of the object with a receiving metadatum;
upon receiving an object portion of an object having no missing object portions, replace the receiving metadatum in the object descriptor of the object with an available metadatum;
determining that the object is unavailable in the data store and is being received from a host comprising: identifying in the object descriptor of the object a receiving metadatum;
determining that the object is unavailable in the data store and is not being received from a host comprising: identifying in the object descriptor of the object a requesting metadatum; and
determining that the object is available in the data store comprising: identifying in the object descriptor of the object an available metadatum.

### Claim 13 (depends on 12)

The method of claim 12:
the instructions configured to:
upon receiving the object portion of the object having no missing object portions, store in the object descriptor of the object a relocating metadatum, and
upon inserting the object into the object set, replacing the relocating metadatum in the object descriptor of the object with an available metadatum; and
determining that the object is available in the data store and unavailable in the object set comprising: identifying in the object descriptor of the object a relocating metadatum.

### Claim 14 (depends on 12)

The method of claim 12:
the instructions configured to, upon receiving the object portion of a first object version of the object having no missing object portions:
upon identifying a versioning conflict wherein the object exists in the data store in a second object version, store in the object descriptor of the object a versioning conflict metadatum; and
determining that the object is available in the data store comprising: upon identifying in the object descriptor of the object a versioning conflict metadatum, presenting to the user a versioning conflict status.

### Claim 15 (depends on 14)

The method of claim 14:
respective versions of an object having at least one object version identifier selected from an object version identifier set comprising:
an object hashcode;
an object modification date; and
an object version indicator; and
the instructions configured to identify a versioning conflict by identifying an object version identifier of the first object version that differs from a corresponding object version identifier of the second object version.

### Claim 16 (depends on 15)

The method of claim 15, presenting to the user the conflict status comprising: presenting to the user the object version identifier of the first object version and the corresponding object version identifier of the second object version.

### Claim 17 (depends on 16)

The method of claim 16, the instructions configured to, upon receiving from the user selection of a selected object version over an unselected object version:
if the selected object version comprises the object version available in the data store and unavailable in the object set, copy the selected object version over the unselected object version;
if the selected object version comprises the object version available in the object set, delete the unselected object version available in the data store and unavailable in the object set; and
replace the versioning conflict metadatum in the object descriptor of the object with an available metadatum.

### Claim 18 (depends on 4)

The method of claim 4, the instructions configured to, upon detecting a version resolution of the first object version and the second object version of the object, replace the conflict metadatum with an available metadatum.

### Claim 19

A system for presenting, to a user of a client on a device having a processor and a data store, availability statuses of objects in an object set within a computing environment comprising at least one host, the system comprising:
an object status determining component configured to, for respective objects of the object set, select an availability status by:
upon determining that the object is available in the data store:
upon determining that the object is available in the object set, selecting an available status; and
upon determining that the object is unavailable in the object set, selecting a relocating status; and
upon determining that the object is unavailable in the data store:
upon determining that the object is being received from a host, selecting a receiving status; and
upon determining that the object is not being received from a host, selecting a requesting status; and
an object status presenting component configured to, for respective objects of the object set, present to the user the availability status.

### Claim 20

A computer-readable medium comprising instructions that, when executed on a processor of a device comprising a data store and a client operated by a user, present availability statuses of objects in an object set within a computing environment stored in the data store and comprising at least one host, the object set managed by an object server configured to, upon storing an object in the object set, send an object descriptor to the client, by:
upon receiving from the object server an object descriptor of an object represented in the object set, the object descriptor identifying at least one host represented in the computing environment that is storing the object:
storing the object descriptor in the data store associated with the object with an unverified object metadatum;
upon verifying that the object is unavailable in the data store:
replacing the unverified object metadatum in the object descriptor of the object with a searching metadatum;
contacting at least one host storing the object to request the object using a peer-to-peer exchange protocol;
upon contacting at least one host:
requesting the object from the host; and
replacing the searching metadatum in the object descriptor with a requesting metadatum;
upon receiving from a host an object portion of an object having at least one missing object portion, replacing the requesting metadatum in the object descriptor of the object with a receiving metadatum; and
upon receiving from a host an object portion of an object having no missing object portions:
replacing the receiving metadatum in the object descriptor of the object with a relocating metadatum;
upon identifying a versioning conflict of the object between a first object version available in the object set and a second object version available in the data store and not in the object set, respective versions of an object having at least one object version identifier selected from an object version identifier set comprising:
an object hashcode;
an object modification date; and
an object version indicator, by identifying an object version identifier of the first object version that differs from a corresponding object version identifier of the second object version, replacing the receiving metadatum in the object descriptor with a versioning conflict metadatum; and
upon inserting the object into the object set, replacing the relocating metadatum in the object descriptor of the object with an available metadatum; and
upon determining the object is available in the data store, replacing the unverified object metadatum in the object descriptor of the object with an available metadatum;
upon receiving from the object server a host removal notification indicating a removal of a host from the object set, for respective object descriptors of objects that are unavailable in the data store and that are not stored by a host represented in the object set, storing in the object descriptor of the object a lost metadatum; and
upon receiving from the user a request to present an availability status of at least one object of the object set:
upon determining that the object is available in the data store:
upon determining that the object is unavailable in the object set by identifying in the object descriptor of the object a relocating metadatum, presenting to the user a relocating status;
upon identifying a locking conflict of the object between a first object version that is available in the object set and that is locked against overwriting and a superseding object version that is available in the data store and not in the object set, present to the user a locking conflict status;
upon determining that a versioning conflict of the object exists by identifying in the object descriptor of the object a versioning conflict metadatum:
presenting to the user a versioning conflict status with the object version identifier of the first object version and the corresponding object version identifier of the second object version; and
upon receiving from the user selection of a selected object version over an unselected object version:
if the selected object version comprises the object version available in the data store and unavailable in the object set, copying the selected object version over the unselected object version;
if the selected object version comprises the object version available in the object set, deleting the unselected object version available in the data store and unavailable in the object set; and
replacing the versioning conflict metadatum in the object descriptor of the object with an available metadatum; and
upon determining that the object is available in the object set by identifying in the object descriptor of the object an available metadatum, presenting to the user an available status; and
upon determining that the object is unavailable in the data store by identifying in the object descriptor of the object an unavailable metadatum:
upon determining that the object is being received from a host by identifying in the object descriptor of the object a receiving metadatum, presenting to the user a receiving status;
upon determining that the object is not being received from a host and is stored on a host represented within the computing environment:
upon determining that hosts storing the object are unreachable, presenting to the user a host unavailable status; and
upon determining that at least one host storing the object is reachable, presenting to the user a host connecting status;
upon determining that the object is not being received from a host and is not stored on a host represented within the computing environment by identifying in the object descriptor of the object a lost metadatum, presenting to the user a lost status; and
upon determining that the object is not being received from a host:
upon determining that the client is contacting at least one host storing the object by identifying in the object descriptor of the object a searching metadatum, presenting to the user a searching status of the object; and
upon determining that the client has contacted at least one host storing the object by identifying in the object descriptor of the object a requesting metadatum, presenting to the user a requesting status.
