Methods and systems for state synchronization over a non-reliable network using signature processing

• US 8,812,856 B2
• Filed: 02/10/2012
• Issued: 08/19/2014
• Est. Priority Date: 02/10/2012
• Status: Active Grant

• Current Assignee: Zynga Incorporated
• Original Assignee: Zynga Incorporated
• Inventors: Tamma, Leela
• Primary Examiner(s): Barron, Jr., Gilberto
• Assistant Examiner(s): Nobahar, Abdulhakim
• Application Number:
  US13/371,365
• Publication Number:
  US 20130212396A1
• Time in Patent Office: 921 Days
• US Class Current: 713/176
• CPC Class Codes: G06F 21/645 using a third party
• CPC Class Codes: G06F 2221/2109 Game systems
• CPC Class Codes: G07F 17/3241 Security aspects of a gaming system, e.g. detecting cheating, device integrity, surveillance computer security G06F21/00
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/131 Protocols for games, networked simulations or virtual reality
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

Abstract

Systems and methods for facilitating confirmation of completion of a transaction(s) for state synchronization over a non reliable network using signature processing are described. One of the methods includes receiving a read request from a first client, sending a last known signature with a context object to the first client in response to receiving the read request, and receiving an appended signature from the first client with a context object for a transaction at the first client. The appended signature includes the last known signature and an increment by the first client. The operation of receiving the appended signature occurs upon execution of the transaction at the first client. The method further includes updating the last known signature to the appended signature and sending the updated last known signature to the first client to facilitate marking of the transaction as complete resulting in a definitive state synchronization.

Claims

1. A method comprising:

receiving a read request from a first client;

sending a last known signature with a first context object to the first client in response to receiving the read request;

receiving an appended signature from the first client with a second context object for a transaction at the first client, the appended signature including the last known signature and an increment by the first client, wherein receiving the appended signature occurs upon execution of the transaction at the first client;

updating the last known signature to the appended signature;

sending the updated last known signature to the first client to facilitate marking of the transaction as complete;

receiving a read request from a second client other than the first client; and

sending the updated last known signature with the second context object to the second client in response to receiving the read request from the second client.

2. The method of claim 1, further comprising:

losing access to the first client after sending the updated last known signature;

gaining access to the first client after losing access to the first client;

receiving an additional read request from the first client after gaining access to the first client; and

sending the updated last known signature with the second context object in response to receiving the additional read request, wherein sending the updated last known signature is performed to facilitate marking the transaction as complete.

3. The method of claim 2, further comprising:

receiving an appended signature from the second client with a third context object upon execution of a transaction at the second client, the appended signature that is received from the second client includes the updated last known signature and an increment by the second client; and

modifying the updated last known signature to match the appended signature that is received from the second client; and

sending the modified last known signature to the second client to facilitate marking of the transaction at the second client as complete.

4. The method of claim 1, further comprising:

receiving an appended signature from the second client with a third context object upon execution of a transaction at the second client, the appended signature that is received from the second client includes the updated last known signature and an increment by the second client; and

modifying the updated last known signature to match the appended signature that is received from the second client; and

sending the modified last known signature to the second client to facilitate marking of the transaction at the second client as complete.

5. The method of claim 4, wherein the second client includes a client device or a game application.

6. The method of claim 4, wherein the second client includes a combination of a client device and a gaming service.

7. The method of claim 1, wherein the appended signature distinguishes the transaction and the first client from a transaction performed at the second client and the second client.

8. The method of claim 1, wherein the first client includes a client device or a gaming application.

9. The method of claim 1, wherein the appended signature distinguishes the first client from the second client.

10. The method of claim 1, wherein the first client includes a combination of a client device and a game application.

11. A method comprising:

sending a read request to a server;

receiving, at a first client, a last known signature with a first context object from the server in response to sending the read request;

determining whether a transaction is performed;

sending an appended signature with a second context object to the server in response to determining that the transaction is performed, the appended signature including the last known signature and an increment by the first client; and

determining whether the appended signature is received from the server,

the server receiving a read request from a second client other than the first client, and the server sending the appended signature with the second context object to the second client in response to receiving the read request from the second client.

12. The method of claim 11, further comprising marking the transaction as complete in response to determining that the appended signature is received from the server.

13. The method of claim 12, further comprising updating the last known signature to the appended signature upon marking the transaction as complete.

14. The method of claim 11, further comprising:

sending an additional read request;

receiving an updated last known signature with the second context object from the server in response to sending the additional read request;

comparing the updated last known signature with the appended signature;

updating the last known signature at the first client to match the updated last known signature in response to determining based on the comparison that a lack of the match between the updated last known signature and the appended signature exists; and

marking the transaction as complete upon updating the last known signature at the first client to match the updated last known signature.

15. The method of claim 11, further comprising:

sending an additional read request;

receiving the last known signature with the second context object from the server in response to sending the additional read request;

comparing the last known signature with the appended signature; and

determining that there is a lack of match between the last known signature and the appended signature.

16. The method of claim 15, further comprising:

sending the appended signature with the second context object to the server in response to determining that there is a lack of match between the last known signature and the appended signature;

receiving an updated last known signature in response to sending the appended signature;

comparing the updated last known signature with the appended signature; and

marking the transaction as complete in response to determining that the updated last known signature matches the appended signature.

18. The method of claim 16, further comprising:

determining whether an updated last known signature received by the first client matches the appended signature; and

marking the transaction as complete at the first client upon determining that the updated last known signature matches the appended signature.

17. A method comprising:

sending a read request to a server;

receiving a last known signature with a first context object in response to sending the read request;

determining whether a transaction is complete at a first client;

adding an increment signature to the last known signature after determining the transaction is complete, wherein adding the increment is performed to generate an appended signature; and

sending the appended signature with a second context object to the server,

the server receiving a read request from a second client other than the first client, and the server sending the appended signature with the second context object to the second client in response to receiving the read request from the second client.

19. The method of claim 17, further comprising:

sending the appended signature with the second context object in response to determining that there is a lack of match between a signature received by the first client from the server and the appended signature;

receiving an updated last known signature from the server;

comparing the updated last known signature with the appended signature; and

determining that the transaction is complete in response to determining that the updated last known signature matches the appended signature.

20. The method of claim 17, wherein the appended signature distinguishes the first client from a second client.