APPARATUS AND METHOD FOR RETROFITTING GAMING MACHINES TO ISSUE AND REDEEM TICKETS
CROSS-REFERENCE TO RELATED APPLICATION
The present application is a Continuation-In-Part of U.S. Patent Application Serial No. 09/693,183 filed October 19, 2000.
FIELD OF THE INVENTION The present invention relates generally to a gaming system and, more particularly, to a gaming system that provides for cash-less play through printing and redeeming of tickets, and more particularly relates to ticket validation by validation numbers which are pre-loaded by a central computer system to individual gaming machines. More particularly, a pre-existing gaming machine may be retrofitted with a ticket reader, a ticket printer, and game interface board for printing and validation of tickets.
BACKGROUND OF THE INVENTION Gaming machines, particularly slot machines, have in recent years become one of the more popular, exciting, and sophisticated wagering activities available at casinos and other gambling locations. At the same time, slot machines have also become a source of greater revenue for gaming establishments.
Typically, a player, when finished playing, "cashes out" at the slot machine by activating a cashout button. At that time, the slot machine converts the amount of credits pending in the slot machine to a currency payout that is dispensed (e.g., as coins) to the player. The player must then collect all of the coins, fill a cup or pockets, then move to the next slot machine and reenter all of the coins. Thus, the prior payout techniques tended to interrupt gameplay, thereby reducing profits and also reducing the excitement and entertainment experience that arise from uninterrupted game play.
In the past, slot machines have attempted to address the interruption caused when a player collects coins and moves to another slot machine. In particular, some slot machines have issued paper tickets that encode the amount of credit pending in the slot machine when the player presses the cashout button. The player may then simply pick up the ticket dispensed by the slot machine and proceed to a new slot machine without incurring the time delay and distraction associated with collecting currency and reinserting it into the new slot machine.
Successful ticketing, however, requires a comprehensive system level approach to ensure that the tickets are secure (e.g., they cannot be duplicated and reused, they cannot be forged, and the like), that as many slot machines as possible can accept tickets, and that ticketing does not cause as much interruption as the coin / currency payout that the tickets are designed to replace. However, in prior ticketing systems for example, the slot machines typically had to spend the time and processing resources to generate their own ticket validation numbers, or had to incur the delay of requesting a ticket validation number from a central authority each time the slot machine needed to print a ticket. As a result, prior slot machines exposed the player to unnecessary processing delay, thereby slowing play, and reducing the overall level of player enjoyment.
In addition, preexisting gaming machines do not have the capability to print and redeem tickets, making them apparently obsolete in a ticket environment. A player having received a printed ticket from one gaming machine, crosses the casino floor only to find that the next machine of choice is unable to redeem the ticket. This causes player frustration and potential confusion as to the purpose of the ticket.
It is therefore an object of this invention to solve the need for a secure ticket actuated gaming system that addresses the problems noted above and other problems previously experienced.
It is yet another object of the present invention to retrofit pre-existing gaming machines or systems, to provide for ticket type cashless play.
It is therefore an object of the invention to provide a method for retrofitting preexisting gaming machines. It is therefore an object of the invention to provide a retrofit kit that enables the retrofitting of a gaming machine.
It is another object to provide a cost-effective upgrade for gaming machines that do not have ticketing capabilities.
SUMMARY OF THE INVENTION These and other objects of the invention are achieved in a gaming machine retrofitted with a ticket printer and/or ticket reader for printing a ticket in response to a cashout command by the player and/or for redeeming tickets inserted by a player. In one embodiment, a gaming network includes a central authority, one or more gaming machines, and an interface system for communication via the network. Each gaming machine generally includes a game controller for controlling game operation.
A cashout signal is developed when the player activates a cashout button or the like. A game machine network interface is fitted within the gaming machine and coupled between the game controller and the network medium. In addition, a ticket printer and a ticket reader is fitted within the gaming machine and coupled to the network interface for printing a ticket in response to the cashout signal and for reading tickets inserted by a player. As a result, the central authority may exercise control over the ticket printer and ticket reader through the game machine network interface, and/or the central authority may validate tickets for redemption. In one embodiment, tickets are printed with validation indicia which is preloaded in the game interface by the central authority.
BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 illustrates a block diagram of a gaming system using the present invention. Figure 2 shows a front view of a ticket used with the gaming system of Figure
1.
Figure 3 illustrates a block diagram of a gaming system in which a central authority or game interface exercises direct control over a bill validator, a ticket printer, and a ticket reader of the individual gaming machine.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
Referring to Figure 1, a gaming network 100 includes several gaming machines 102, 104, 106. The gaming machines 102-106 may be implemented, for example, as slot machines, video poker machines, video roulette machines, and the like. Each gaming machine 102-106 includes a game controller 108, a display 110, and a game network interface 112. The game interface 112 may be, for example, an
RS485 interface such as that implemented by a Sentinel™ Interface from Casino Data Systems. Other interfaces and network architectures (e.g., Ethernet, parallel port, and the like) may be substituted however. Furthermore, the game interface 112 may adhere to, for example, the IGT Gaming SAS™ communication protocol, the CDS GDAP™ communication protocol, a custom protocol, or another third party communication protocol for establishing and maintaining communication with the gaming machine 102. The game interface 112 is physically present inside of the gaming machine 102; although, it may be located externally from and coupled to the gaming machine 102. Each gaming machine 102-106 further includes a coin acceptor or comparator 114, a bill validator / ticket reader 116, and a ticket printer 118.
Gaming machine 102 may be originally manufactured with some or all of these components, or may be retrofitted with some or all of these components, as described below. Initially, the embodiment of Figure 1 will be described as if the bill validator/ticket reader 116 and ticket printer 118 are originally manufactured within the gaming machine.
The game controller 108 is responsive to a cashout signal 134 to print a ticket 136 on paper, or other suitable material. Additionally, previously printed tickets (e.g., the ticket 138) may be redeemed for credits by the gaming machines 102-106. The gaming network also includes a central authority or host computer system 120. The central authority 120 includes a ticketing database 122 and a network interface 124 for connection over the network medium 126 to the gaming machines 102-106. Support systems connect to the central authority 120, including a ticketing workstation 128, an administration workstation 130, and an accounting workstation
132.
A dataport unit (DPU) 140 is provided as a data concentrator and buffering communication unit to address multiple gaming machines and to communicate with the poller 142. The poller 142, in turn, communicates with the DPU 140 and the central authority 120. The game interface 112 may be generally configured as shown in Figure 1 to include a CPU 144, a program and data memory 146, and a serial controller 148.
The game controller 108 is responsible for operation of the gaming device 102. Thus, the game controller 108 may include a microprocessor, memory, game software, and support circuitry to implement a slot machine or other type of game. The display 110 presents to the player a representation of the pending credit in the gaming machine 102 (e.g., $455.50). During play, the game controller 108 tracks the pending credit according to the rules of the game and the interaction with the player (including the deposit of additional funds via the coin acceptor 114 and bill validator
116), and further monitors for assertion of the cashout signal 134. Thus, the central authority 120 need not monitor the pending credit in each gaming machine 102-106, as each gaming machine 102-106 preferably tracks the pending credit locally and independently of the central authority 120. In response to the cashout signal 134, the game controller 108 prints the ticket
136 which may be redeemed later at gaming machines 102-106 or at independent workstations with ticket readers. The cashout signal 134 may be generated by a player actuated switch, touchscreen input, or the like. As will be explained in more detail below, the game controller 108 prints the ticket 136 with a pre-loaded ticket validation number obtained from the central authority 120 through the network interfaces 112, 124 and over the network medium 126. The central authority 120 may use a number generator to generate validation numbers, and, if desired, may use an encryption algorithm to generate the validation numbers. The number generated may be based on, for example, the time and/or date as well as the gaming machine number. The ticketing database 122 stores information obtained from the gaming machines 102-106, as well as locally generated validation numbers. The ticketing workstation 128 provides cash redemption of tickets separate from the gaming machines, the administration workstation 130 provides an interface for setting up system parameters, and the accounting workstation 132 provides for ticket and gaming machine accounting functions. Note that in general, when a ticket validation number is pre-loaded into a game interface 112, the ticket validation number is also stored in ticketing database 122 (albeit without an associated pending credit amount). Thus, should the gaming network fail, validation may still occur through human intervention.
Turning next to Figure 2, a ticket 200 includes a validation number bar code 202 (e.g., in JCM or Code 205 format), a human intelligible validation number 204, and a human intelligible pending credit amount 206. The ticket 200, as shown, also includes a machine number 208 and a ticket number 210 (e.g., a sequential ticket number generated in the gaming machine 102). The validation number bar code 202 is a machine readable representation of a pre-loaded validation number (as discussed in more detail below) but the validation number bar code 202 generally does not encode other information (e.g., the pending credit amount). In other words, the ticket 200, when it is advantageous to do so, may omit a machine readable pending credit amount. Additional information may also be printed on the ticket 200, including a date/time of cashout, casino name, ticket expiration date, and the like.
In using the system of Figure 1, a player presses a cashout button and thereby generates the cashout signal 134. In response to the cashout signal 134, game controller 108 proceeds to obtain a pre-loaded validation number from the game interface 112 and to print ticket 136. The game controller 108 sends the necessary information to ticket printer 118 and the ticket is printed.
Information regarding the printed ticket is sent to the central authority 120 through the game interface 112. The printed ticket information may include the casino name, ticket date and time, validation number, a bar code representing the validation number, a numeric pending credit amount, an alphanumeric description of the pending amount, a machine number, and a ticket number (typically up to 9999 and sequentially generated at each gaming machine). The game interface 112 also requests a new ticket validation number from the central authority 120, and pre-loads it into a memory (e.g., the memory 146) for use when the next ticket is printed. Thus, a ticket validation number is immediately available at the gaming machine when the player activates the cashout button.
The ticketing database 122 in the central authority may store, for example, a number of fields as desired. Examples of fields are set forth in Tables 1 , 2 and 3 of parent application Serial No. 09/693,483, the entirety of such application is incorporated herein by reference.
Also, in using the system in Figure 1, a player may insert a ticket into a gaming machine 102-106. The gaming machine queries the central authority 120 for validation of the validation number bar code 202 printed on the ticket. In general, the pending credit printed on the ticket is not read by the ticket reader. Rather, the system itself responds with the pending credit as explained below.
The central authority attempts to find the validation number in its ticketing database 122. If the validation number is not found, the system responds to the gaming machine with a Reject Message. If the ticket is a duplicate, i.e., it has been validated earlier, the system also responds with a Reject Message. If the validation number is not a duplicate, then the system determines whether the ticket status as recorded in the ticketing database 122 is issued and redeemable (i.e., it has not already been redeemed for money). If not, the system again responds with a Reject Message. The ticket / bill validator 116 then rejects the ticket, i.e., returns the ticket to the player.
If the ticket is valid, the central authority responds to the gaming machine via the game interface 112 to indicate that the ticket is valid and provides the amount to be credited (e.g., in cents). The gaming machine loads the amount into its credit meter.
Subsequently, the gaming machine replies to the central authority with the ticket processing result (e.g., the ticket was rejected or accepted). The central authority changes the ticket status in the ticketing database 122 to indicate, for example, that the ticket has been redeemed. With reference next to Figure 3, a block diagram of a gaming network 300 illustrates control by central authority 120 over a coin acceptor 314, a bill validator and ticket reader 316, and a ticket printer 318. As will suggest itself, a separate ticket reader and ticket printer may be used, however the functionality of a reader and printer may be incorporated into a single device. Figure 3 is similar to Figure 1, and like reference numerals denote like parts. Note, however, that the coin comparator
314, bill validator and ticket reader 316, and ticket printer 318 are connected directly to the game interface 312 rather than to the game controller 108.
As a result, the central authority 120 may exercise control over the coin acceptor 314, bill validator and ticket reader 316, and ticket printer 318 through the game interface 312. The game controller 108 is thereby relieved of those duties. Furthermore, pre-existing gaming machines that do not allow convenient game controller ticket printing and reading, may nevertheless issue and redeem tickets when retrofitted with the game interface 312, bill validator and ticket reader 316 and ticket printer 318. In such a retrofit, the coin comparator 314 is connected to game interface
312.
Interface 312 includes software in its memory 146 to directly control ticket printer 318 as well as coin acceptor 314 and bill validator and ticket reader 316, and to correspondingly communicate with central authority 120, as described herein. The hardware components of interface 312 may be incorporated onto a single printed circuit board (or several boards, if desired) which is fitted into gaming machine 102. The printed circuit board may replace an existing machine's original interface board so as to retrofit the existing machine to provide ticketing capabilities. Thus, an existing machine gains the ability to print and redeem tickets. As will suggest itself, apertures may be cut out of the face of the gaming machine in order to locate the typical ticket receiving slot of bill validator and ticket reader 316 and to locate the typical dispensing slot of ticket printer 318. Instructional information may also be printed on the face of the gaming machine, if desired.
Game interface 312 controls the physical cashout button on the gaming machine. As shown in Figure 3, the cashout signal, generated by activation of the cashout button, is sent to the game controller 108 which in turn communicates this event to game interface 312. Alternatively, the cashout signal 134 may bypass game controller 108 and be sent directly to game interface 312. When a player presses the cashout button, credits are removed from the game credit meter, a validation number is assigned to a ticket, information is logged into the database 122 and the ticket 136 is printed. Electronic Funds Transfer (EFT) protocols are used to remove all player credits from the gaming machine. The game interface 312 stores a pre-loaded ticket validation number obtained from the central authority 120, as described above in reference to Figure 1. It is this pre-loaded validation number that is printed on the ticket. Alternatively, game interface 312 may independently generate the validation number by a number generator as previously discussed. Interface 312 may preload its memory 146 with the number generated.
Upon actuation of the cashout button, a validation number, as well as other information, is sent by game interface 312 to the ticket printer 318 and to the ticketing database 122. Other information sent may include machine number, sequential ticket number, amount, date/time, and expiration date. A ticket similar to that shown in Figure 2 is then printed. Ticketing database 122 will then have information regarding the particular ticket that may later be used to validate it.
The flow of the process for printing tickets may be described as follows: 1. A player pushes the cashout button on gaming machine 102. The cashout signal 134 is generated and sent to game interface 312. 2. The game interface 312 responds to the cashout signal by removing all credits from the credit meter using EFT protocol. An EFT message is sent by game interface 312 to the game controller 108 to cause the removal of all credits. As will be understood, gaming machine 102 has EFT protocol capabilities. 3. The game interface 312 also provides a validation ticket number and the credit amount to the printer. The validation number is preloaded into interface 312 after generation by the central authority 120. Alternatively, game interface 312 may generate the validation number independently of the central authority, and provide data regarding that generation to the central authority for storage in database 122.
4. Ticket printer 318 prints a ticket and dispenses the ticket to the player.
5. Data is stored in game interface 312 regarding the printing. Game interface 312 may keep a log of all printed tickets with date and time data, and may keep another log as to printer events.
6. Game interface 312 sends data to central authority 120 regarding the printing, i.e., that the ticket was successfully printed, and a record of the ticket is sent as well.
7. Central authority 120 generates the next validation number to be used by that gaming machine and loads that validation number into game interface
312. When a ticket 138 is inserted into the bill validator and ticket reader 316, the game interface 312 reads the ticket directly and proceeds to verify the validation number bar code with the central authority 120 as explained above. Valid tickets result in credit being applied to the gaming machine 102 using, for example, an
Electronic Funds Transfer (EFT) message. The EFT message may be generated by the central authority. An invalid ticket is rejected, and is returned to the player. In addition, the game interface 312 may also read standard currency (e.g., bills and coins) input to coin comparator 314 and bill validator 316, and appropriately report to the central authority 120. Again, the central authority 120 may respond with an EFT message to the gaming machine 102 to apply credit thereto. Alternatively, the game interface 312 may determine the amount of standard currency inserted and report that amount directly to the gaming machine 102 via an EFT message (to appropriately increment its bill and coin meters). Gaming interface 312 may log the bill and coin amounts into memory. In that regard, the game interface 312 may act as a filter, such that only printed tickets generate appreciable network traffic to the central authority 120.
The flow of the process for redeeming tickets may be described as follows: L A player inserts a ticket into the bill validator and ticket reader 316.
2. The game interface 312 responds by storing pertinent data and transmitting the ticket's validation number to the central authority 120.
3. Central authority 120 checks its database 122 to determine whether the validation number exists in the database, whether the ticket is a duplicate, and the status of the ticket. If valid, the central authority changes the ticket's status to indicate redemption is in process and then sends the ticket type (cashable) and the amount (cents) to the game interface 312.
4. The game interface 312 tells the ticket reader 316 that the ticket is acceptable and data is stored accordingly. The ticket reader 316 retains the ticket.
5. The game interface 312 sends a message to the game via EFT protocol and stores data accordingly.
6. The game controller 108 responds to the EFT message and loads an amount into the credit meter which is displayed at display 110. The game controller 108 may store data and informs interface 312 that credit has been given to the player. 7. The game interface 312 sends data to central authority 120 that the ticket was redeemed. 8. The central authority 120 changes the ticket status to redeemed.
If the ticket is not accepted by the game, the central authority is notified accordingly so that it may change its database to reflect the status of the ticket. If the game is able to accept some, but not all of the ticket amount, the game is able to print a ticket for the difference in order to give "change" back to the player. Some gaming machines can only accept whole dollar amounts, based on the gaming machine's denomination. The game interface 312 may print a change ticket to return the change balance to the player. Game interface 312 prints the change ticket in the same manner it prints a cashout ticket, but using a validation number and communicating with the central authority, as described above. Data is stored in the central authority, accordingly.
Thus, the present invention provides a secure ticket actuated gaming network.
In particular, the gaming machines are pre-loaded with ticket validation numbers in preparation for printing a cashout ticket. As a result, the player need not wait while the gaming machine generates or requests a new validation number. Preexisting machines may be retrofit to participate in the ticketing process..
A retrofit kit may be used to retrofit preexisting gaming machines. As used herein, "retrofit" means to furnish a preexisting machine or system with additional parts, either new parts or used parts. A retrofit kit includes a game interface, a ticket printer and a bill validator and ticket reader. The game interface may include a four port serial I/O Board which connects the serial port of the interface to the ticket printer and bill validator and ticket reader. The game interface will also include the necessary software to perform its functions as described above. As will suggest itself, additional software may be provided so as to permit game interface 312 to display messages on display 110. For example, the message ADDING CREDITS may be displayed to ensure player awareness during the validation process. Other messages may include TICKET ACCEPTED or TICKET REJECTED.
While the invention has been described with reference to particular embodiments, those skilled in the art will understand that various changes may be made and equivalents may be substituted without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular step, structure, or material to the teachings of the invention without departing from its scope. Therefore, it is intended that the invention not be limited to the particular embodiments disclosed, but that the invention will include all embodiments falling within the scope of the appended claims.