Synchronization and recovery of peers in a peer to peer environment

• US 7,177,950 B2
• Filed: 04/26/2001
• Issued: 02/13/2007
• Est. Priority Date: 04/26/2001
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Ogus, Aaron W., Narayan, Michael J.
• Primary Examiner(s): Jaroenchonwanit; Bunjob
• Assistant Examiner(s): Chankong; Dohm
• Application Number:
  US09/843,452
• Publication Number:
  US 20020161821A1
• Time in Patent Office: 2,119 Days
• Field of Search: 709/201, 709/204, 709/205, 709/230
• US Class Current: 709/248
• CPC Class Codes: G06F 2209/505 Clust
• CPC Class Codes: G06F 9/5061 Partitioning or combining of resources
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1048 Departure or maintenance mechanisms
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

A method is provided for use in a computer system that is operating in a peer-to-peer environment. The peer-to-peer environment has a host peer and at least one non-host peer. The method of the invention is used to order the operation requests of the peers so that operations are performed only in the order that they are processed by the host peer. The method includes providing a list of recognized operations which may be requested by any of the peers in the session. The host peer then receives at least one operation request from one of the peers, the request being selected from the provided list. The host then assigns a unique version number to the operation request, so that all peers within the session can determine the proper order in which to process orders given by the host peer.

Claims

1. A method for use in a computer system, operating in a peer-to-peer environment having a host peer and at least one non-host peer, and for ordering operation requests of the at least one non-host peer, the operation requests being one of a provided list of recognized operations which may be requested, comprising:

transmitting a first name table to the at least one non-host peer when the at least one non-host peer joins a session, the name table including a name table entry for each peer within the session, wherein each name table entry contains a version number corresponding to when each peer joined the session;

receiving, by the host peer, a first operation request from the provided list of recognized operations;

assigning, by the host peer, a first unique version number to the first operation request and a second name table;

transmitting the second name table including a first operation order to the at least one non-host peer in the session;

subsequently receiving, by the host peer, a second operation request from the provided list of recognized operations;

assigning, by the host peer, a second unique version number to the second operation request and a third name table, the second unique version number indicating a later receipt time than the first unique version number, such that the host peer evaluates relative arrival times of the first operation request and the second operation request based on the first unique version number and the second unique version number; and

transmitting the third name table including a second operation order to the at least one non-host peer in the session.

2. The method of claim 1, further comprising processing, by the host peer, the first and second operation requests in the order of the first unique version number and the second unique version number.

6. The method of claim 1, wherein the version number is used to determine a subsequent host peer.

11. The method of claim 6, further comprising receiving, by the subsequent host, a fourth name table from the at least one non-host peer to identify any missing operation orders, the fourth name table corresponding to the highest version numbered name table processed by the at least one non-host peer.

12. The method of claim 11, further comprising transmitting an updated name table to the at least one non-host peer after the fourth name table is processed by the subsequent host.

3. A computer readable medium having at least one physical media containing computer executable instructions for performing a method for use in a computer system, operating in a peer-to-peer environment having a host peer and at least one non-host peer, and for ordering operation requests of the at least one non-host peer, the operation requests being one of a provided list of recognized operations which may be requested, the method comprising:

transmitting a first name table to the at least one non-host peer when the at least one non-host peer joins a session, the name table including a name table entry for each peer within the session, wherein each name table entry contains a version number corresponding to when each peer joined the session;

receiving, by the host peer, a first operation request from the provided list of recognized operations;

assigning, by the host peer, a first unique version number to the first operation request and a second name table;

transmitting the second name table including a first operation order to the at least one non-host peer in the session;

subsequently receiving, by the host peer, a second operation request from the provided list of recognized operations;

assigning, by the host peer, a second unique version number to the second operation request and a third name table, the second unique version number indicating a later receipt time than the first unique version number, such that the host peer evaluates relative arrival times of the first operation request and the second operation request based on the first unique version number and the second unique version number; and

transmitting the third name table including a second operation order to the at least one non-host peer in the session.

7. The computer readable medium of claim 3, wherein the version number is used to determine a subsequent host peer.

10. The computer readable medium of claim 3, further comprising processing, by the host peer, the first and second operation requests in the order of the first unique version number and the second unique version number.

13. The computer readable medium of claim 7, further comprising receiving, by the subsequent host, a fourth name table from the at least one non-host peer to identify any missing operation orders, the fourth name table corresponding to the highest version numbered name table processed by the at least one non-host peer.

14. The computer readable medium of claim 13, further comprising transmitting an updated name table to the at least one non-host peer after the fourth name tables is processed by the subsequent host.

4. A method for use in a computer system, operating in a peer-to-peer environment having a host peer and at least one non-host peer, and for requesting operations of the host peer, the operations being one of a provided list of recognized operations which may be requested, comprising:

receiving, by the at least one non-host peer, a first name table including a name table entry for each peer within a session, wherein each name table entry contains a version number corresponding to when each peer joined the session;

sending, by the at least one non-host peer, at least one operation request from the provided list of recognized operations to the host peer;

receiving, by the at least one non-host peer, a second name table including an operation order, the second name table being assigned a first assigned unique version number associated with the operation request;

determining whether the first assigned unique version number received is next in a sequence of version numbers processed by the at least one non-host peer, and if it is not, queuing the operation order until the first assigned unique version number is next in the sequence of version numbers processed by the at least one non-host peer; and

processing, by the at least one non-host peer, the operation order in the order that the first assigned unique version number is in within the sequence of version numbers.

8. The method of claim 4, wherein the version number is used to determine a subsequent host peer.

15. The method of claim 8, further comprising receiving, by the subsequent host, a fourth name table from the at least one non-host peer to identify any missing operation orders, the fourth name table corresponding to the highest version numbered name table processed by the at least one non-host peer.

16. The method of claim 15, further comprising transmitting an updated name table to the at least one non-host peer after the fourth name table is processed by the subsequent host.

5. A computer readable medium having at least one physical media containing computer executable instructions for performing a method for use in a computer system, operating in a peer-to-peer environment having a host peer and at least one non-host peer, and for requesting operations of the host peer, the operations being one of a provided list of recognized operations which may be requested, the method comprising:

receiving, by the at least one non-host peer, a first name table including a name table entry for each peer within a session, wherein each name table entry contains a version number corresponding to when each peer joined the session;

sending, by the at least one non-host peer, at least one operation request from the provided list of recognized operations to the host peer;

receiving, by the at least one non-host peer, a second name table including an operation order, the second name table being assigned a first assigned unique version number associated with the operation request;

determining whether the first assigned unique version number received is next in a sequence of version numbers processed by the at least one non-host peer, and if it is not, queuing the operation order until the first assigned unique version number is next in the sequence of version numbers processed by the at least one non-host peer; and

processing, by the at least one non-host peer, the operation order in the order that the first assigned unique version number is in within the sequence of version numbers.

9. The computer readable medium of claim 5, wherein the version number is used to determine a subsequent host peer.

17. The computer readable medium of claim 9, further comprising receiving, by the subsequent host, a fourth name table from the at least one non-host peer to identify any missing operation orders, the fourth name table corresponding to the highest version numbered name table processed by the at least one non-host peer.

18. The computer readable medium of claim 17, further comprising transmitting an updated name table to the at least one non-host peer after the fourth name table is processed by the subsequent host.