# US 2004/0083263 A1 · Method and apparatus for maintaining consistency of a shared space across multiple endpoints in a peer-to-peer collaborative computer system

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

- Number: US 2004/0083263 A1
- Document ID: US20040083263A1
- Status: Published application
- Kind: A1
- Application number: 10/279,785
- Filed: 2002-10-24
- Published: 2004-04-29
- Earliest claimed: 2002-10-24
- Assignees: Groove Networks, Inc.
- Inventors: Ransom L. Richardson; Raymond E. Ozzie; Jack E. Ozzie
- Web page: https://patentgrep.com/patent/US20040083263A1

## CPC

- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/123: {received data contents, e.g. message integrity}
- Y10S 707/99938: Concurrency, e.g. lock management in shared database
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

In a peer-to-peer collaboration system, deltas containing data change commands are organized in a persistent data structure called a delta log. The delta log is organized into blocks, which are the largest division in the delta log. In turn, blocks contain groups, groups contain chains and chains contain deltas. Delta blocks are used to implement priority deltas that are used to limit the collection of data change commands that must be transferred. Within a block the deltas are organized by groups, each of which is a set of deltas organized into chains. The delta group in used to determine which deltas to purge. The chains are ordered by increasing creator ID of the endpoint that created the chain. Organizing the delta log in this fashion allows the log to be “walked” to detect convergence problems. To achieve causality-preservation, each delta has a list of dependencies representing other deltas that must be executed before the current delta can be executed. The dynamics manager uses the ability to do (execute) and undo commands to perform roll back and roll forward operations on deltas in order to achieve convergence.

## Claims

### Claim 1

Apparatus for maintaining consistency of a shared space across multiple endpoints in a collaborative computer system wherein each endpoint has a local data copy and endpoints transmit data change commands contained in deltas to each other in order to update the local data copies, the apparatus comprising:
a persistent delta log data structure located in each endpoint that stores deltas and their contents;
a mechanism in each endpoint that inserts each delta generated by the each endpoint and received from other endpoints into the delta log so that each delta received from an endpoint is kept in a chain in order of generation and reception; and
a mechanism in each endpoint that executes the data change commands in a delta, the mechanism using the contents of the delta log to selectively undo and redo data change commands in order to achieve convergence of the data change commands at all endpoints.

### Claim 2 (depends on 1)

The apparatus of claim 1 wherein a delta generated by the each endpoint and received from other endpoints is inserted into a delta log at a point determined by the endpoint that generated that delta and a sequence number.

### Claim 3 (depends on 1)

The apparatus of claim 1 wherein each chain in a delta log is comprised of deltas received from an endpoint ordered by the sequence number.

### Claim 4 (depends on 1)

The apparatus of claim 1 wherein each chain in a delta log has a predetermined maximum length.

### Claim 5 (depends on 1)

The apparatus of claim 1 wherein the chains in the delta log are arranged in groups wherein, within each group, chains are arranged in order of increasing creator ID wherein the creator ID is the combination of an endpoint ID for an endpoint and a random number generated each time that endpoint opens the shared space.

### Claim 6 (depends on 1)

The apparatus of claim 1 further comprising a mechanism for generating endpoint pulses that are transmitted between the endpoints in the shared space wherein each endpoint pulse is generated by an endpoint and comprises information identifying a delta group that that endpoint is willing to delete.

### Claim 7 (depends on 6)

The apparatus of claim 6 further comprising means in each endpoint that receives endpoint pulses generated by other endpoints and deletes deltas in groups selected by comparing the information in the endpoint pulses in order to determine delta groups that all endpoints are willing to delete.

### Claim 8 (depends on 1)

The apparatus of claim 1 wherein the mechanism in each endpoint that executes the data change commands in a delta comprises a mechanism that uses the chains in a delta log to sequentially examine deltas in order to undo data change commands in selected deltas.

### Claim 9 (depends on 8)

The apparatus of claim 8 wherein the mechanism in each endpoint that executes the data change commands in a delta comprises a mechanism that uses the chains in a delta log to sequentially examine deltas in order to redo data change commands that had been previously undone.

### Claim 10 (depends on 1)

The apparatus of claim 1 wherein each delta has a list of dependencies representing other deltas that must be executed before the each delta can be executed.

### Claim 11 (depends on 10)

The apparatus of claim 10 wherein the mechanism in each endpoint that executes the data change commands in a delta comprises means for using undo information contained in a delta in order to undo data change commands contained in that delta.

### Claim 12 (depends on 11)

The apparatus of claim 11 further comprising a data change engine that inserts undo information into a delta at the same time that data change commands in the delta are executed.

### Claim 13 (depends on 10)

The apparatus of claim 10 wherein the mechanism in each endpoint that inserts each delta generated by the each endpoint and received from other endpoints into the delta log inserts the delta chains into blocks based on a priority assigned to each delta so that each block contains one delta with highest priority, all deltas on which the highest priority delta depends are located in blocks created before the each block, all deltas that are independent of the highest priority delta are in the each block and all deltas that depend on the highest priority delta are in the each block and blocks created after the each block.

### Claim 14 (depends on 10)

The apparatus of claim 10 further comprising a mechanism for creating an asynchronous delta wherein no other deltas are dependent on the asynchronous delta.

### Claim 15 (depends on 10)

The apparatus of claim 10 further comprising a mechanism in an endpoint for fetching from other endpoints deltas in a list of dependencies, which deltas are not in the delta log of that endpoint.

### Claim 16 (depends on 15)

The apparatus of claim 15 wherein the mechanism for fetching deltas sends a fetch request to another endpoint including a fetch request sequence number and wherein the other endpoint comprises a fetch response mechanism that includes a fetch response sequence number and wherein the fetch response mechanism returns requested deltas to the mechanism for fetching deltas when the fetch request sequence number is equal to the fetch response sequence number.

### Claim 17 (depends on 16)

The apparatus of claim 16 wherein the fetch response mechanism sends an update message to the mechanism for fetching when the fetch request sequence number is not equal to the fetch response sequence number.

### Claim 18 (depends on 17)

The apparatus of claim 17 wherein the mechanism for fetching is responsive to the update message for incrementing the fetch request sequence number.

### Claim 19 (depends on 10)

The apparatus of claim 10 further comprising a mechanism for creating an identity disseminated delta that is sent to a subset of endpoints in the shared space and which is inserted into a delta log at a point determined by the endpoint that generated that delta and a sub-sequence number.

### Claim 20 (depends on 1)

The apparatus of claim 1 further comprising a mechanism in each endpoint for storing persistent data representing a state of all endpoints in the shared space including an active state and a mechanism for sending deltas only to endpoints with an active state.

### Claim 21 (depends on 20)

The apparatus of claim 20 wherein the mechanism in each endpoint that executes the data change commands in a delta is responsive to a state of the endpoint that generated the delta for selectively executing the data change commands in the delta.

### Claim 22 (depends on 20)

The apparatus of claim 20 wherein each endpoint has a current state and each endpoint comprises a mechanism that changes the endpoint current state to another state in response to a predetermined event.

### Claim 23

A method for maintaining consistency of a shared space across multiple endpoints in a collaborative computer system wherein each endpoint has a local data copy and endpoints transmit data change commands contained in deltas to each other in order to update the local data copies, the method comprising:
(a) storing deltas and their contents in a persistent delta log data structure located in each endpoint;
(b) inserting each delta generated by the each endpoint and received from other endpoints into the delta log so that each delta received from an endpoint is kept in a chain in order of generation and reception; and
(c) executing the data change commands in a delta, the mechanism using the contents of the delta log to selectively undo and redo data change commands in order to achieve convergence of the data change commands at all endpoints.

### Claim 24 (depends on 23)

The method of claim 23 wherein step (b) comprises inserting a delta generated by the each endpoint and received from other endpoints into a delta log at a point determined by the endpoint that generated that delta and a sequence number.

### Claim 25 (depends on 23)

The method of claim 23 wherein each chain in a delta log is comprised of deltas received from an endpoint ordered by the sequence number.

### Claim 26 (depends on 23)

The method of claim 23 wherein each chain in a delta log has a predetermined maximum length.

### Claim 27 (depends on 23)

The method of claim 23 wherein step (b) comprises arranging the chains in the delta log in groups wherein, within each group, chains are arranged in order of increasing creator ID wherein the creator ID is the combination of an endpoint ID for an endpoint and a random number generated each time that endpoint opens the shared space.

### Claim 28 (depends on 23)

The method of claim 23 further comprising:
(d) generating endpoint pulses that are transmitted between the endpoints in the shared space wherein each endpoint pulse is generated by an endpoint and comprises information identifying a delta group that that endpoint is willing to delete.

### Claim 29 (depends on 28)

The method of claim 28 further comprising:
(e) receiving endpoint pulses generated by other endpoints and deleting deltas in groups selected by comparing the information in the endpoint pulses in order to determine delta groups that all endpoints are willing to delete.

### Claim 30 (depends on 23)

The method of claim 23 wherein step (c) comprises using the chains in a delta log to sequentially examine deltas in order to undo data change commands in selected deltas.

### Claim 31 (depends on 30)

The method of claim 30 wherein step (c) comprises using the chains in a delta log to sequentially examine deltas in order to redo data change commands that had been previously undone.

### Claim 32 (depends on 23)

The method of claim 23 wherein each delta has a list of dependencies representing other deltas that must be executed before the each delta can be executed.

### Claim 33 (depends on 32)

The method of claim 32 wherein step (c) comprises using undo information contained in a delta in order to undo data change commands contained in that delta.

### Claim 34 (depends on 33)

The method of claim 33 further comprising:
(d) inserting undo information into a delta at the same time that data change commands are executed.

### Claim 35 (depends on 32)

The method of claim 32 wherein step (b) comprises inserting the delta chains into blocks based on a priority assigned to each delta so that each block contains one delta with highest priority, all deltas on which the highest priority delta depends are located in blocks created before the each block, all deltas that are independent of the highest priority delta are in the each block and all deltas that depend on the highest priority delta are in the each block and blocks created after the each block.

### Claim 36 (depends on 32)

The method of claim 32 further comprising:
(d) creating an asynchronous delta wherein no other deltas are dependent on the asynchronous delta.

### Claim 37 (depends on 32)

The method of claim 32 further comprising:
(d) fetching to a first endpoint from other endpoints deltas in a list of dependencies, which deltas are not in the delta log of the first endpoint.

### Claim 38 (depends on 37)

The method of claim 37 wherein step (d) comprises sending a fetch request from the first endpoint to another endpoint including a fetch request sequence number and wherein the other endpoint comprises a fetch response mechanism that includes a fetch response sequence number and wherein step (d) further comprises returning requested deltas from the another endpoint to the first endpoint when the fetch request sequence number is equal to the fetch response sequence number.

### Claim 39 (depends on 38)

The method of claim 38 wherein step (d) further comprises sending an update message to first endpoint when the fetch request sequence number is not equal to the fetch response sequence number.

### Claim 40 (depends on 39)

The method of claim 39 wherein step (d) further comprises incrementing the fetch request sequence number in response to the update message.

### Claim 41 (depends on 32)

The method of claim 32 further comprising creating an identity disseminated delta that is sent to a subset of endpoints in the shared space and inserting the identity disseminated delta into the delta log at a point determined by the endpoint that generated that delta and a sub-sequence number.

### Claim 42 (depends on 23)

The method of claim 23 further comprising:
(d) storing persistent data in each endpoint representing a state of all endpoints in the shared space including an active state; and
(e) sending deltas only to endpoints with an active state.

### Claim 43 (depends on 42)

The method of claim 42 wherein step (c) comprises selectively executing the data change commands in the delta in response to a state of the endpoint that generated the delta.

### Claim 44 (depends on 42)

The method of claim 42 wherein each endpoint has a current state and the method further comprises:
(f) changing the endpoint current state to another state in response to a predetermined event.

### Claim 45

A computer program product for maintaining consistency of a shared space across multiple endpoints in a collaborative computer system wherein each endpoint has a local data copy and endpoints transmit data change commands contained in deltas to each other in order to update the local data copies, the computer program product comprising a computer usable medium having computer readable program code thereon, including:
program code for storing deltas and their contents in a persistent delta log data structure located in each endpoint;
program code for inserting each delta generated by the each endpoint and received from other endpoints into the delta log so that each delta received from an endpoint is kept in a chain in order of generation and reception; and
program code for executing the data change commands in a delta, the mechanism using the contents of the delta log to selectively undo and redo data change commands in order to achieve convergence of the data change commands at all endpoints.

### Claim 46 (depends on 45)

The computer program product of claim 45 wherein the program code for inserting each delta into the delta log comprises program code for inserting a delta generated by the each endpoint and received from other endpoints into a delta log at a point determined by the endpoint that generated that delta and a sequence number.

### Claim 47 (depends on 45)

The computer program product of claim 45 wherein each chain in a delta log is comprised of deltas received from an endpoint ordered by the sequence number.

### Claim 48 (depends on 45)

The computer program product of claim 45 wherein each chain in a delta log has a predetermined maximum length.

### Claim 49 (depends on 45)

The computer program product of claim 45 wherein the program code for inserting each delta into the delta log comprises program code for arranging the chains in the delta log in groups wherein, within each group, chains are arranged in order of increasing creator ID wherein the creator ID is the combination of an endpoint ID for an endpoint and a random number generated each time that endpoint opens the shared space.

### Claim 50

Apparatus for maintaining consistency of a shared space across multiple endpoints in a collaborative computer system wherein each endpoint has a local data copy and endpoints transmit data change commands contained in deltas to each other in order to update the local data copies, the apparatus comprising:
a persistent delta log data structure located in each endpoint that stores deltas and their contents;
means in each endpoint for inserting each delta generated by the each endpoint and received from other endpoints into the delta log so that each delta received from an endpoint is kept in a chain in order of generation and reception; and
means in each endpoint for executing the data change commands in a delta, the executing means using the contents of the delta log to selectively undo and redo data change commands in order to achieve convergence of the data change commands at all endpoints.

### Claim 51 (depends on 50)

The apparatus of claim 50 wherein the inserting means is responsive to a delta generated by the each endpoint and received from other endpoints for inserting the delta into a delta log at a point determined by the endpoint that generated that delta and a sequence number.

### Claim 52 (depends on 50)

The apparatus of claim 50 wherein each chain in a delta log is comprised of deltas received from an endpoint ordered by the sequence number.

### Claim 53 (depends on 50)

The apparatus of claim 50 wherein each chain in a delta log has a predetermined maximum length.

### Claim 54 (depends on 50)

The apparatus of claim 50 wherein the inserting means comprises means for arranging chains in the delta log into groups wherein, within each group, chains are arranged in order of increasing creator ID wherein the creator ID is the combination of an endpoint ID for an endpoint and a random number generated each time that endpoint opens the shared space.

### Claim 55

Apparatus for maintaining consistency of a shared space across multiple endpoints in a collaborative computer system wherein each endpoint has a local data copy and endpoints transmit data change commands to each other in order to update the local data copies, the apparatus comprising:
a first tool in one endpoint that is responsive to user actions at the endpoint for creating a first delta container to transmit data change commands to other endpoints and for adding data change commands to the first delta container;
a second tool in the one endpoint that is called by the first tool to add data change commands to the first delta container; and
means in the second tool for creating a second delta container, adding the second delta container to the first delta container and adding data change commands to the second delta container.

### Claim 56 (depends on 55)

The apparatus of claim 55 wherein at least one of the data change commands includes undo information for reversing the data change performed by the command.

### Claim 57 (depends on 55)

The apparatus of claim 55 further comprising a data change engine for executing the data change commands in the first delta container and the data change commands in the second delta container and a dynamics manager for adding the data change commands in the second delta container and undo information corresponding to the data change commands in the second delta container to the beginning of the first delta container.

### Claim 58 (depends on 57)

The apparatus of claim 57 wherein the data change engine executes data change commands added to the first delta container before the second delta container was added to the first delta container after the data change commands in the second delta container are executed and added.

### Claim 59 (depends on 58)

The apparatus of claim 58 wherein the data change engine comprises means responsive to the occurrence of an error during the execution of the data change commands in the first delta container for aborting the execution of the data change commands in the second delta container.

### Claim 60

A method for maintaining consistency of a shared space across multiple endpoints in a collaborative computer system wherein each endpoint has a local data copy and endpoints transmit data change commands to each other in order to update the local data copies, the method comprising:
(a) using a first tool to create a first delta container in response to user actions at one endpoint to transmit data change commands to other endpoints;
(b) using the first tool to add data change commands to the first delta container;
(c) calling a second tool in the one endpoint with the first tool to add data change commands to the first delta container;
(d) creating a second delta container with the second tool; and
(e) using the second tool to add the second delta container to the first delta container and to add data change commands to the second delta container.

### Claim 61 (depends on 60)

The method of claim 60 wherein at least one of the data change commands includes undo information for reversing the data change performed by the command.

### Claim 62 (depends on 60)

The method of claim 60 further comprising:
(f) executing the data change commands in the second delta container and the data change commands in the first delta container; and
(g) after executing the data change commands in the second delta container, adding the data change commands in the second delta container and undo information corresponding to the data change commands in the second delta container to the beginning of the first delta container.

### Claim 63 (depends on 62)

The method of claim 62 wherein step (f) comprises executing the data change commands added to the first delta container before the second delta container was added after step (g) is performed.

### Claim 64 (depends on 58)

The method of claim 58 further comprising:
(h) aborting the execution of the data change commands in the second delta container upon the occurrence of an error during the execution of the data change commands in the first delta container.

### Claim 65

Apparatus for maintaining consistency of a shared space across multiple endpoints in a collaborative computer system wherein each endpoint has a local data copy and endpoints transmit data change commands contained in delta containers to each other in order to update the local data copies, the apparatus comprising:
a data change engine in one endpoint for executing the data change commands in a first delta container, for generating undo information in order to reverse the effects of the data change commands and for storing the undo information in the first data change container;
means in the data change engine and responsive to the execution of a selected data change command for creating a second delta container in the one endpoint and for adding data change commands to the second delta container.

### Claim 66 (depends on 65)

The apparatus of claim 65 further comprising means for executing the commands in the second delta container and for generating undo information for reversing the effects of the commands in the second delta container and means operable upon execution for storing the commands in the second delta container and undo information generated for those commands in the undo information of the first delta container.

### Claim 67 (depends on 66)

The apparatus of claim 66 further comprising means for using the undo information in the first delta container to reverse the effect of the commands contained in the first delta container wherein the means for using the undo information reverses commands originally stored in the second delta container before the selected command that caused the second delta container to be created is reversed.

### Claim 68

A method for maintaining consistency of a shared space across multiple endpoints in a collaborative computer system wherein each endpoint has a local data copy and endpoints transmit data change commands contained in delta containers to each other in order to update the local data copies, the method comprising:
(a) executing the data change commands in a first delta container, generating undo information in order to reverse the effects of the data change commands and storing the undo information in the first data change container;
(b) responsive to the execution of a selected data change command, creating a second delta container in the one endpoint; and
(c) adding data change commands to the second delta container.

### Claim 69 (depends on 68)

The method of claim 68 further comprising:
(d) executing the commands in the second delta container and generating undo information for reversing the effects of the commands in the second delta container; and
(e) storing the executed commands from the second delta container and undo information generated for those commands in the undo information of the first delta container.

### Claim 70 (depends on 69)

The method of claim 69 further comprising:
(f) using the undo information in the first delta container to reverse the effect of the commands contained in the first delta container; and
(g) during the performance of step (f) reversing commands originally stored in the second delta container before the selected command that caused the second delta container to be created is reversed.

### Claim 71

Apparatus for maintaining consistency of a shared space across multiple endpoints in a collaborative computer system wherein each endpoint has a local data copy and endpoints transmit data change commands contained in deltas to each other in order to update the local data copies, the apparatus comprising:
a conflict region in each delta that identifies other deltas with which the execution of the each delta conflicts;
a persistent delta log data structure located in each endpoint that stores deltas and their contents;
a mechanism in each endpoint that inserts each delta generated by the each endpoint and received from other endpoints into the delta log in a consistent order across all endpoints based on a group number and sequence number in that delta; and
a data engine that walks backward over the delta log starting from the last delta entered and proceeding towards the first delta entered and compares the conflict regions of each executed delta with the conflict regions of other deltas entered into the log and reverses the effect of each executed delta that conflicts with another delta entered into the log.

### Claim 72 (depends on 71)

The apparatus of claim 71 wherein the data engine comprises means for reversing the effect of each executed delta that has a conflict by iterating in reverse order over the data change commands in the delta and using undo information in the delta for each data change command to reverse the effect of the command.

### Claim 73 (depends on 72)

The apparatus of claim 72 wherein, after reversing the effect of each delta that conflicts with another delta, the data change engine walks backward over the delta log starting from the last delta entered and proceeding towards the first delta entered and re-executes the data change commands in each delta that was reversed.

### Claim 74 (depends on 73)

The apparatus of claim 73 wherein the conflict region of each delta is set when the delta is created.

### Claim 75

A method for maintaining consistency of a shared space across multiple endpoints in a collaborative computer system wherein each endpoint has a local data copy and endpoints transmit data change commands contained in deltas to each other in order to update the local data copies, the method comprising:
(a) creating a conflict region in each delta that identifies other deltas with which the execution of the each delta conflicts;
(b) storing deltas and their contents in a persistent delta log data structure located in each endpoint;
(c) inserting each delta generated by the each endpoint and received from other endpoints into the delta log in a consistent order across all endpoints based on a group number and a sequence number in that delta; and
(d) walking backward over the delta log starting from the last delta entered and proceeding towards the first delta entered, comparing the conflict regions of each executed delta with the conflict regions of other deltas entered into the log and reversing the effect of each executed delta that conflicts with another delta entered into the log.

### Claim 76 (depends on 75)

The method of claim 75 wherein step (d) comprises reversing the effect of each executed delta that has a conflict by iterating in reverse order over the data change commands in the delta and using undo information in the delta for each data change command to reverse the effect of the command.

### Claim 77 (depends on 76)

The method of claim 76 further comprising:
(e) after reversing the effect of each delta that conflicts with another delta, walking backward over the delta log starting from the last delta entered and proceeding towards the first delta entered and re-executing the data change commands in each delta that was reversed.

### Claim 78 (depends on 77)

The method of claim 77 wherein step (a) comprises creating the conflict region of each delta when the delta is created.
