Dynamic configuration of a gaming system

• US 20050223219A1
• Filed: 05/25/2005
• Published: 10/06/2005
• Est. Priority Date: 03/10/2003
• Status: Active Grant

• Current Assignee: IGT (International Game Technology)
• Original Assignee: Cyberview Technology, Inc. (International Game Technology)
• Inventors: Gatto, Jean-Marie, Brunet De Courssou, Thierry
• Granted Patent: US 7,337,330 B2
• Time in Patent Office: Days
• US Class Current: 713/156
• CPC Class Codes: G07F 17/32 for games, toys, sports, or amusements
• CPC Class Codes: G07F 17/323 wherein the player is informed, e.g. advertisements, odds, instructions
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/60 Digital content management, e.g. content distribution
• CPC Class Codes: H04L 2209/76 Proxy, i.e. using intermediary entity to perform cryptographic operations network architectures or network communication protocols using hop-by-hop encryption H04L63/0464
• CPC Class Codes: H04L 63/102 Entity profiles
• 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 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 9/006 involving public key infrastructure [PKI] trust models network architecture or network communication protocol for supporting authentication of entities using certificates in a packet data network H04L63/0823
• CPC Class Codes: H04L 9/3263 involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823

Abstract

A universal method and system for downloading game software to legacy gaming machines. A gaming machine includes a locked enclosure; a first computing device disposed within the locked enclosure, the first computing device being programmed to enable game play of the gaming machine; a second computing device disposed within the locked enclosure of the gaming machine, the second computing device being configured for network access, and an interface between the first and the second computing devices. The second computing device is configured to receive game software components over the network that are compatible with (e.g., executable by) the first computing device but not compatible with (e.g., not executable by) the second computing device and to transfer the received game software components to the first computing device over the interface. The second computing device may include, for example, a PC. When the first computing device is a PC, it may be configured with dual-boot capability between two operating systems. When the first operating system is booted, game play may be enabled and when the second operating system is booted, game software components may be received over the network.

Claims

1. A method for downloading software components to a non PC-based gaming machine over a network, the non PC-based gaming machine including a locked enclosure and persistent storage, the method comprising the steps of:

providing a PC controlled by policies and disposed within the locked enclosure of the non-PC gaming machine, the PC including local storage;

connecting the PC to the network;

providing an interface between the PC and the non PC-based gaming machine;

downloading a package authenticated by a certificate only to the PC over the network, the package including the software components to be installed on the non-PC gaming machine;

verifying the certificate and unpacking the software components included in the package, and

enabling the non PC-based gaming machine to execute the unpacked software components.

2. The method of claim 1, wherein the first providing step is carried out such that the PC is configured to run a version of the Microsoft Windows®

operating system.

3. The method of claim 1, wherein the software components are authorized by a regulatory authority.

4. The method of claim 1, wherein the downloading step uses the Software Installation Policy (SIP) feature of the Windows®

operating system.

5. The method of claim 1, wherein the downloading step uses the Microsoft SMS Systems Management Server.

6. The method of claim 1, wherein the downloading step is carried out such that the package is a Microsoft MSI package.

7. The method of claim 1, wherein the downloading step is carried out such that the package is equivalent to a Microsoft MSI package.

8. The method of claim 1, wherein the second providing step is carried out such that the interface includes an Application Program Interface (API).

9. The method of claim 1, wherein the persistent storage of the non-PC gaming machine includes a disk drive or a recordable solid state memory storage.

10. The method of claim 9, wherein the enabling step includes a step of storing the unpacked software components on the disk drive or the recordable solid state memory storage through the interface.

11. The method of claim 1, wherein the persistent storage of the non-PC gaming machine includes a ROM.

12. The method of claim 1, wherein the persistent storage of the non-PC gaming machine includes a ROM, wherein the second providing step is carried out such that the interface includes a ROM emulator and wherein the enabling step includes sending the unpacked software components to the ROM emulator such that the non PC-based gaming machine executes the software components from the ROM emulator, bypassing the ROM of the non-PC gaming machine.

13. The method of claim 1, wherein the verifying step includes one of issuing a verification command and a step of rebooting the PC.

14. The method of claim 1, further comprising the step of rebooting the PC and verifying the certificate of any package stored in the PC'"'"'s local memory upon reboot.

15. The method of claim 1, further including a step of sending a menu of available games to the non PC-based gaming machine and wherein when a game is selected from the menu and software for the selected game is not stored in the non-PC gaming machine, the API further causes the verifying and enabling steps to be carried out on a package corresponding to the selected game.

16. The method of claim 15, wherein the package corresponding to the selected game in the verifying and enabling steps is stored in the PC'"'"'s local storage.

17. The method of claim 15, wherein the package corresponding to the selected game is stored on a server coupled to the network and wherein the package corresponding to the selected game is downloaded to the local storage of the PC prior to the verifying and enabling steps being carried out on the downloaded and stored package.

18. The method of claim 1, wherein the first providing step is carried out with the policies controlled by .ADM administrative scripts or equivalent commands by a central server.

19. The method of claim 1, wherein the first providing step is carried out with a local password of the PC being configured by a central server.

20. The method of claim 1, wherein the first providing step is carried out with a local password of the PC being randomly configured by a central server.

36. The method of claim 1, wherein the second computing device is configured with a local password that is configured by a central server.

37. The method of claim 1, wherein the second computing device is configured with a local password that is configured randomly by a central server.

21. A method for ensuring that only authorized software components execute on a non PC-based gaming machine connected to a network, the non PC-based gaming machine including a locked enclosure, the method comprising the steps of:

providing a PC controlled by policies and disposed within the locked enclosure of the non-PC gaming machine;

connecting the PC to the network;

providing an interface between the PC and the non PC-based gaming machine;

packaging authorized software components that are executable to the non-PC gaming machine but not to the PC into a code signed MSI installation package;

configuring certificate rule policies to enable execution of the code signed MSI installation package;

enforcing the policies, and

sending the code signed MSI installation package to the PC within the secure locked enclosure of the non-PC gaming machine, and

executing the code signed MSI installation package upon startup of the non PC-based gaming machines or upon a command.

22. The method of claim 21, further comprising the step of booting up the PC within the locked enclosure upon startup of the non-PC gaming machine.

23. The method of claim 21, wherein the code signing uses a distinctive PKI certificate for each MSI installation package.

24. The method of claim 21, wherein the first providing step is carried out such that the policies are controlled by .ADM administrative scripts or equivalent commands by a central server.

25. The method of claim 21, wherein the first providing step is carried out with a local password of the PC being configured by a central server.

26. The method of claim 21, wherein the first providing step is carried out with a local password of the PC being configured randomly by a central server.

27. A gaming machine, comprising:

a locked enclosure;

a first computing device disposed within the locked enclosure, the first computing device being programmed to enable game play of the gaming machine;

a second computing device controlled by policies and disposed within the locked enclosure of the gaming machine, the second computing device being configured for network access, and

an interface between the first and the second computing devices,

wherein the second computing device is configured to receive game software components over the network that are compatible with the first computing device but not compatible with the second computing device and to transfer the received game software components to the first computing device over the interface.

28. The gaming machine of claim 27, wherein the first computing device is configured to execute the game software components received by the second computing device, and wherein the second computing device is configured so as to be unable to execute the received game software components.

29. The gaming machine of claim 27, wherein the gaming machine is a non PC-based gaming machine.

30. The gaming machine of claim 27, wherein the gaming machine is a PC-based gaming machine that is not capable of securely receiving game software components over the network.

31. The gaming machine of claim 27, wherein the second computing device includes a PC.

32. The gaming machine of claim 27, wherein the second computing device runs a version of the Microsoft Windows®

operating system.

33. The gaming machine of claim 27, wherein the first computing device includes a ROM and wherein the interface includes a ROM emulator and the received game software components transferred via the interface to the emulator is executable by the first computing device.

34. The gaming machine of claim 27, wherein the first computing device includes a plurality of ROMs and wherein the interface includes a multi-ROM emulator configured to couple to selected ones of the plurality of ROMs and the received game software components transferred via the interface to the emulator is executable by the first computing device.

35. The gaming machine of claim 27, wherein the policies are controlled by .ADM administrative scripts or equivalent commands configured by a central server.

38. A method for downloading software components over a network to a gaming machine controlled by a first computing device, the gaming machine being disposed within a locked enclosure, the method comprising the steps of:

providing a second computing device controlled by policies and disposed within the locked enclosure of the gaming machine;

connecting the second computing device to the network;

providing an interface between the second computing device and the gaming machine;

downloading a package authenticated by a certificate only to the second computing device over the network, the package including software components to be installed and executed on the first computing device, the software components not being compatible with the second computing device;

verifying the certificate and unpacking the software components included in the package, and

enabling the first computing device to execute the unpacked software components.

39. The method of claim 38, wherein the downloading step is carried out with the software components not being executable by the second computing device.

40. The method of claim 38, wherein the wherein the second computing device runs a version of the Microsoft Windows®

operating system.

41. The method of claim 38, wherein the first providing step is carried out with the second computing device including a PC.

42. The method of claim 38, wherein the package downloading step is carried out with the software components being authorized by a regulatory authority.

44. The method of claim 40, wherein the sending step uses the Microsoft SMS Systems Management Server.

45. The method of claim 40, wherein the package includes a Microsoft MSI package or equivalent package.

46. The method of claim 38, wherein the second providing step is carried out with the interface including an Application Program Interface (API).

47. The method of claim 38, wherein the gaming machine includes a disk drive or a solid state data storage device and wherein the enabling step includes a step of storing the unpacked software components on the disk drive or to the solid state data storage device through the interface.

48. The method of claim 38, wherein the gaming machine includes a ROM, the interface includes a ROM emulator and wherein the enabling step includes sending the unpacked software components to the ROM emulator such that the non PC-based gaming machine executes the software components from the ROM emulator, bypassing the ROM.

49. The method of claim 38, wherein the verifying step includes one of issuing a verification command and a step of rebooting the second computing device.

50. The method of claim 38, further comprising the step of rebooting the second computing device and verifying the certificate of any package stored in a local memory of the second computing device upon reboot.

51. The method of claim 38, further including a step of sending a menu of available games to the non PC-based gaming machine and wherein when a game is selected from the menu and software for the selected game is not stored in the non-PC gaming machine, the API further causes the verifying and enabling steps to be carried out on a package corresponding to the selected game.

52. The method of claim 51, wherein the package corresponding to the selected game in the verifying and enabling steps is stored in local storage of the second computing device.

53. The method of claim 51, wherein the package corresponding to the selected game is stored on a server coupled to the network and wherein the package corresponding to the selected game is sent to local storage of the second computing device prior to the verifying and enabling steps being carried out on the sent and stored package.

54. The method of claim 38, wherein the first providing step is carried out such that the policies are controlled by .ADM administrative scripts or equivalent commands by a central server.

55. The method of claim 38, wherein the first providing step is carried out with the second computing device being configured with a password that is configured by a central server.

56. The method of claim 38, wherein the first providing step is carried out with the second computing device being configured with a local password that is configured randomly by a central server.

43. 40, wherein the downloading step uses the Software Installation Policy (SIP) feature of the Windows®

operating system.

57. A method for downloading software components to a PC based gaming machine over a network, the PC based gaming machine including a persistent data storage, the method comprising the steps of:

configuring the PC based gaming machine with a dual-boot capability including a first operating system and a second operating system, the second operating system being controlled by policies, the persistent storage being accessible by the first operating system and by the second operating system;

executing the game software when the first operating system is booted;

connecting the PC based gaming machine to the network when the second operating system is booted;

downloading over the network a package authenticated by a certificate to the PC based gaming machine only when booted under the second operating system, the package including the software components to be installed on the persistent data storage;

verifying the certificate and unpacking the software components included in the package when booted under the second operating system, and

enabling the PC based gaming machine when booted under the first operating system to execute the unpacked software components.

58. The method of claim 57, wherein the configuring step is carried out with the first operating system being a selected one of Linux, an embedded commercial operating system and a proprietary operating system.

59. The method of claim 57, wherein the configuring step is carried out with the second operating system being a selected one of Microsoft Windows, a commercial operating system capable of secure network communication by enforcing policies via build-in or third party add-in functionalities.

60. The method of claim 57, wherein the configuring step is carried out with each of the first and second operating systems being capable of requesting a reboot under the first or second operating systems.

61. The method of claim 57, wherein the software components are authorized by a regulatory authority.

63. The method of claim 57, wherein the downloading step uses the Microsoft SMS Systems Management Server.

64. The method of claim 57, wherein the downloading step is carried out with package being a Microsoft MSI package.

65. The method of claim 57, wherein the downloading step is carried out with the package being equivalent to a Microsoft MSI package.

62. 57, wherein the downloading step uses the Software Installation Policy (SIP) feature of the Windows®

operating system.