The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Jul. 22, 2003
Filed:
Jan. 04, 2000
Alec Ginsburg, Las Vegas, NV (US);
Darin T. Gifford, Las Vegas, NV (US);
Robert J. Piechowiak, Las Vegas, NV (US);
Sigma Game, Inc., Las Vegas, NV (US);
Abstract
A method and apparatus for securing the game program software and related data files used by a gaming device and for authenticating such files during game startup and play. In one embodiment of the present invention, a verification code is generated by the manufacturer for each software file and data file used by the game. The verification codes are stored in a non-volatile, tamper-proof, read-only memory device, which is (in some embodiments) securely attached to the gaming device. On some or every download of the game software and/or related data files into the gaming device, commencement of a game, or on the occurrence of certain pre-defined events, the stored verification code is used to validate the game software and data files. In some embodiments, verification is performed automatically on a periodic basis without operator or player action. Verification consists of calculating a live verification code for some or all of the software and data files present in the alterable random access memory using the same method chosen to create the stored verification code. In some embodiments of the present invention, the verification code is the result of a hash function of trusted copies of each software and related data file. If the live code matches the stored code for every suspect file, then operation and play proceeds normally. If, however, one or more codes do not match, an error condition is declared, operation is halted, and notification of the error condition follows.