Authentication of Game Results

• US 20110130190A1
• Filed: 02/09/2011
• Published: 06/02/2011
• Est. Priority Date: 12/02/2002
• Status: Abandoned Application

• Current Assignee: SCA Promotions, Inc.
• Original Assignee: SCA Promotions, Inc.
• Inventors: Hamman, Robert D., Kennedy, William C. III, Westerlage, Kenneth R.
• Application Number:
  US13/023,720
• Publication Number:
  US 20110130190A1
• Time in Patent Office: Days
• US Class Current: 463/19
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: G06F 2221/2101 Auditing as a secondary aspect
• CPC Class Codes: G06F 2221/2103 Challenge-response
• CPC Class Codes: G06F 2221/2109 Game systems
• CPC Class Codes: G07F 17/32 for games, toys, sports, or amusements
• CPC Class Codes: G07F 17/3223 Architectural aspects of a gaming system, e.g. internal configuration, master/slave, wireless communication
• 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/131 Protocols for games, networked simulations or virtual reality

Abstract

A gaming system includes a game server and a client server. The client server requests random numeric outcomes from the game server and supplies various state and game information. The game server generates one or more random numeric outcomes. The game server communicates the random numeric outcomes to the client server to be used in making a win determination. For purposes of future authentication, the game server stores a digitally-signed file that includes the random numeric outcomes and the state and game information.

Claims

1. A method for providing numeric outcomes to a game operator, comprising:

generating, by a processor, a random numeric outcome having a digital signature, wherein the random numeric outcome is digitally signed using a private key;

verifying that the random numeric outcome has not been changed since being generated; and

communicating the random numeric outcome to a client server for determination of a game winner.

2. The method of claim 1, wherein verifying that the random numeric outcome has not been changed since being generated comprises:

retrieving a public key associated with the private key used to sign the random numeric outcome, wherein the public key indicates that the digital signature for the random numeric outcome was generated using the associated private key; and

verifying, based on the public key, that the random numeric outcome has not been changed since being signed using the private key.

3. The method of claim 2, wherein digitally signing the random numeric outcome comprises digitally signing the random numeric outcome with a private key associated with a current time, and wherein retrieving the public key comprises:

determining a time associated with the random numeric outcome; and

retrieving a public key associated with the determined time.

4. The method of claim 1, further comprising:

storing the random numeric outcome in an audit log in an electronic memory;

after storing the random numeric outcome, retrieving the random numeric outcome from the audit log; and

verifying that the random numeric outcome has not been changed since being stored.

5. The method of claim 4, wherein storing the random numeric outcome in the audit log comprises storing the random numeric outcome in the audit log that includes a plurality of random numeric outcomes indexed by time.

6. The method of claim 1, further comprising:

receiving a draw request that includes a client identifier and commit data that defines conditions under which the random numeric outcome is to be generated;

generating a draw file that includes the random numeric outcome, the client identifier, and the commit data; and

verifying that the draw file has not been changed since being generated.

7. The method of claim 6, further comprising:

storing the draw file in an audit log in an electronic memory, wherein the draw file is associated with an entry index;

after storing the draw file, retrieving the draw file from the audit log; and

verifying that the draw file has not been changed since being stored.

8. The method of claim 1, further comprising:

receiving a draw request that includes a game identifier and commit data that defines conditions under which the random numeric outcome is to be generated;

generating a draw file that includes the random numeric outcome, the game identifier, and the commit data; and

verifying that the draw file has not been changed since being generated.

9. The method of claim 1, further comprising:

receiving a draw request that include a game type, game parameters, and commit data describing the game, wherein;

the game type is selected from a group comprising keno, bingo, and slot-machine game types; and

the game parameters vary depending on the selected game type.

10. The method of claim 1, wherein generating a random numeric outcome comprises generating the random numeric outcome according to an environmental input.

11. A non-transitory computer readable medium comprising logic for providing numeric outcomes to a game operator, the logic, when executed by a processor, operable to:

generate a random numeric outcome having a digital signature, wherein the random numeric outcome is digitally signed using a private key;

verify that the random numeric outcome has not been changed since being generated; and

communicate the random numeric outcome to a client server for determination of a game winner.

12. The non-transitory computer readable medium of claim 11, wherein verifying that the random numeric outcome has not been changed since being generated comprises:

retrieving a public key associated with the private key used to sign the random numeric outcome, wherein the public key indicates that the digital signature for the random numeric outcome was generated using the associated private key; and

verifying, based on the public key, that the random numeric outcome has not been changed since being signed using the private key.

13. The non-transitory computer readable medium of claim 12, wherein digitally signing the random numeric outcome comprises digitally signing the random numeric outcome with a private key associated with a current time, and wherein retrieving the public key comprises:

determining a time associated with the random numeric outcome; and

retrieving a public key associated with the determined time.

14. The non-transitory computer readable medium of claim 11, wherein the logic is further operable to:

store the random numeric outcome in an audit log in an electronic memory;

after storing the random numeric outcome, retrieve the random numeric outcome from the audit log; and

verify that the random numeric outcome has not been changed since being stored.

15. The non-transitory computer readable medium of claim 14, wherein storing the random numeric outcome in the audit log comprises storing the random numeric outcome in the audit log that includes a plurality of random numeric outcomes indexed by time.

16. The non-transitory computer readable medium of claim 11, wherein the logic is further operable to:

receive a draw request that includes a client identifier and commit data that defines conditions under which the random numeric outcome is to be generated;

generate a draw file that includes the random numeric outcome, the client identifier, and the commit data; and

verify that the draw file has not been changed since being generated.

17. The non-transitory computer readable medium of claim 16, wherein the logic is further operable to:

store the draw file in an audit log in an electronic memory, wherein the draw file is associated with an entry index;

after storing the draw file, retrieve the draw file from the audit log; and

verify that the draw file has not been changed since being stored.

18. The non-transitory computer readable medium of claim 11, wherein the logic is further operable to:

receive a draw request that includes a game identifier and commit data that defines conditions under which the random numeric outcome is to be generated;

generate a draw file that includes the random numeric outcome, the game identifier, and the commit data; and

verify that the draw file has not been changed since being generated.

19. The non-transitory computer readable medium of claim 11, wherein the logic is further operable to:

receive a draw request that include a game type, game parameters, and commit data describing the game, wherein;

the game type is selected from a group comprising keno, bingo, and slot-machine game types; and

the game parameters vary depending on the selected game type.

20. The non-transitory computer readable medium of claim 11, wherein generating a random numeric outcome comprises generating the random numeric outcome according to an environmental input.

21. A system for providing numeric outcomes to a game operator, comprising:

a random number generator operable to generate a random numeric outcome having a digital signature, wherein the random numeric outcome is digitally signed using a private key;

a digital signature generator operable to verify that the random numeric outcome has not been changed since being generated; and

an interface module operable to communicate the random numeric outcome to a client server for determination of a game winner.

22. The system of claim 21, wherein the digital signature generator is further operable to:

retrieve a public key associated with the private key used to sign the random numeric outcome, wherein the public key indicates that the digital signature for the random numeric outcome was generated using the associated private key; and

verify, based on the public key, that the random numeric outcome has not been changed since being signed using the private key.

23. The system of claim 21, further comprising:

an audit log memory operable to store the random numeric outcome; and

the digital signature generator is further operable to;

retrieve the random numeric outcome from the audit log; and

verify that the random numeric outcome has not been changed since being stored.

24. The system of claim 23, wherein the audit log memory is operable to store a plurality of random numeric outcomes indexed by time.

25. The system of claim 21, wherein:

the interface module is further operable to receive a draw request that includes a client identifier and commit data that defines conditions under which the random numeric outcome is to be generated;

the random number generator is further operable to generate a draw file that includes the random numeric outcome, the client identifier, and the commit data; and

the digital signature generator is further operable to verify that the draw file has not been changed since being generated.

26. The system of claim 25, further comprising:

an audit log memory operable to store the draw file, wherein the draw file is associated with an entry index; and

the digital signature generator is further operable to;

retrieve the draw file from the audit log; and

verify that the draw file has not been changed since being stored.

27. The system of claim 21, wherein the system is enclosed in a compartment operable to disable the signature generator upon breach of the compartment.

28. The system of claim 21, wherein:

the interface module is further operable to receive a draw request that includes a game identifier and commit data that defines conditions under which the random numeric outcome is to be generated;

the random number generator is further operable to generate a draw file that includes the random numeric outcome, the game identifier, and the commit data; and

the digital signature generator is further operable to verify that the draw file has not been changed since being generated.

29. The system of claim 21, wherein the interface module is further operable to receive a draw request that include a game type, game parameters, and commit data describing the game, wherein:

the game type is selected from a group comprising keno, bingo, and slot-machine game types; and

the game parameters vary depending on the selected game type.

30. The system of claim 21, wherein the a random number generator is further operable to generate the random numeric outcome according to an environmental input.

31. A non-transitory computer readable medium comprising logic for providing numeric outcomes to a game operator, the logic, when executed by a processor, operable to:

receive a draw request that includes commit data that defines conditions under which random numeric outcomes to be generated will result in a win for a player of a game;

generate, with an electronic processor, a random numeric outcome based on the draw request;

communicate the random numeric outcome to a game operator to be used by the game operator to determine whether a win has occurred in the game;

generate a draw file that includes the random numeric outcome and the commit data;

digitally sign the draw file with a digital signature using a private key;

store the draw file in an audit log in an electronic memory;

after storing the draw file, retrieve the draw file from the audit log;

verify that the draw file has not been changed since being stored, wherein verifying that the draw file has not been changed since being stored comprises;

retrieve a public key associated with the private key used to sign the draw file, wherein the public key indicates that the digital signature for the draw file was generated using the associated private key; and

verify, based on the public key, that the draw file has not been changed since being signed using the private key; and

confirm, based on information in the draw file, that the random numeric outcome resulted in a game win.

32. The non-transitory computer readable medium of claim 31, wherein digitally signing the draw file comprises digitally signing the draw file with a private key associated with a current time, and wherein retrieving the public key comprises:

determining a time associated with the draw file; and

retrieving a public key associated with the determined time.

33. The non-transitory computer readable medium of claim 31, wherein storing the draw file in an audit log comprises storing the draw file in an audit log that includes a plurality of draw files indexed by time.

34. The non-transitory computer readable medium of claim 31, wherein receiving a draw request further comprises receiving a draw request that includes game parameters and the game parameters describe parameters for one or more random numeric outcomes to be generated.

35. The non-transitory computer readable medium of claim 31, wherein receiving a draw request further comprises receiving a draw request that includes a game type and the game type is selected from a group comprising keno, bingo, and slot-machine game types.

36. The non-transitory computer readable medium of claim 31, wherein retrieving the draw file comprises:

receiving an indication that a random numeric outcome included in the draw file resulted in a game win; and

in response to receiving the indication, retrieving the draw file from the audit log.